WinG: Difference between revisions
typo, file name supposed to be wingpal.wnd |
Added Civilization II to the list of applications using WinG API. |
||
| Line 54: | Line 54: | ||
*[[Adobe Photoshop]] 4.0 (1997) |
*[[Adobe Photoshop]] 4.0 (1997) |
||
*''[[Alone in the Dark 3|Alone in the Dark: Ghosts in Town]]'' (1996) |
*''[[Alone in the Dark 3|Alone in the Dark: Ghosts in Town]]'' (1996) |
||
*[[Civilization II]] (1996) |
|||
*''[[Comix Zone]]'' (1995) |
*''[[Comix Zone]]'' (1995) |
||
*''[[Dark Seed II]]'' (1995) |
*''[[Dark Seed II]]'' (1995) |
||
Revision as of 12:13, 27 November 2020
In computing, WinG (pronounced Win Gee) is an application programming interface that was designed to provide faster graphics performance on Windows 3.x operating environments, and was initially positioned as a way to help game developers more easily port their DOS games to Microsoft Windows,[1] although it was quickly discontinued in favor of DirectX.
Background
WinG fixed two problems. The first problem that WinG fixed was that Windows 3.x did not support creating Device Contexts (DCs) based on device independent bitmaps, only actual display devices. One major limitation of the GDI DCs was that they were write-only. Data, once written, could not be retrieved. The second problem was that all GDI drawing was implemented in the Windows 3.x video drivers. This included the drawing of bitmaps. Obviously performance of such routines varied across drivers.
Alex St. John, one of the creators of DirectX, said in a 2000 interview that,
WinG was a technology being built by Chris Hecker in the research group, and at the time it was one of the small Microsoft Skunkworks projects, very low profile and off-the-wall. Basically it was fixing broken Windows drivers to make them run faster and more acceptably. Using it, we were actually able to create a video API that could run DOOM almost as fast under Windows as it did in DOS.[2]
Microsoft announced WinG at the 1994 Game Developers Conference, demonstrating it with a port by id Software of Doom.[3] WinG was shipped on September 21, 1994.[4] WinG, while interesting, was still fundamentally based on drawing bitmaps in memory and outputting frames after the drawing was done. As a result, WinG was deprecated and DirectX was built. However, Windows NT 3.5 and Windows 95 introduced CreateDIBSection to provide support for creating DCs based on DIBs and video drivers also eventually improved.
Implementation
WinG introduced a new type of DC called a WinGDC,[5] which allowed programmers to both read and write to it directly using device-independent bitmaps (DIBs) with the wingdib.drv driver. Effectively, it gave programmers the ability to do with Windows what they'd been doing without hardware access limitations in DOS for years. Programmers could write DIBs to the WinGDC, yet would still have access to the individual bits of the image data. This meant that fast graphics algorithms could be written to allow fast scrolling, overdraw, dirty rectangles, double buffering, and other animation techniques. WinG also provided much better performance when blitting graphics data to physical graphics device memory. Since WinG used the DIB format, it was possible to mix original GDI API calls and WinG calls.[5]
WinG would also perform a graphics hardware/driver profiling test on the first execution of the program in order to determine the best way to draw DIBs. This test showed a window full of red curved lines, sections of which would wobble as performance was tested. Once WinG had determined the fastest calls that did not cause graphics corruption, a profile would be saved so that the test would not need to be performed again.
Support
WinG out-of-the-box support (i.e. as a separate API to Win32) was dropped in Windows 98 Second Edition (which integrated DirectX 6), as it did nothing but pass through to the Win32 APIs that it was wrapping (including CreateDIBSection). WinG DLLs were sometimes distributed with an application, at which point it merely became a matter of copying the files wing.dll, wing32.dll, wingde.dll, wingdib.drv and wingpal.wnd to the system32 directory (for 32 bit Windows) or SysWOW64 directory (for 64 bit Windows) to regain system-wide support.
List of applications using WinG API
- Adobe Photoshop 3.0 (1994)
- Adobe Photoshop 4.0 (1997)
- Alone in the Dark: Ghosts in Town (1996)
- Civilization II (1996)
- Comix Zone (1995)
- Dark Seed II (1995)
- Doom (1995)
- Dust: A Tale of the Wired West (1995)
- Fury3 (1995)
- Grant - Lee - Sherman: Civil War 2: Generals (1997)
- Heroes of Might and Magic II (1996)
- The Lion King (1994)
- Microsoft Bob (1995)
- Microsoft Oceans (1995)
- Microsoft Return of Arcade (1996)[6]
- Monopoly (Westwood Studios) (1995)
- Nitemare 3D (1994)
- Noir: A Shadowy Thriller (1996)
- P.T.O. II (1995)
- The Rise & Rule of Ancient Empires (1996)
- This Means War! (1995)
- Sid Meier's Colonization (1995)
- Sid Meier's Civilization II (1996)
- SimCity 2000 (Windows 16-bit) (1995)
- SimTower (1994)
- Star Wars Screen Entertainment (1994)
- Sonic's Schoolhouse (1996)
- Time Gate: Knight's Chase (1996)
- Titanic: Adventure Out of Time (1996)
- Warcraft II: Tides of Darkness Map editor
- Woodruff and the Schnibble of Azimuth (1995)
See also
- Windows API
- DOSBox, allows emulation of DOS programs
References
- ^ Hecker, Chris (1 June 1997). "A Whirlwind Tour of WinG". Gamasutra. Retrieved 2009-01-19.
- ^ Colayco, Bob (7 March 2000). "Alex St. John Interview". firingsquad.com. Retrieved 2009-01-19.
- ^ Wilson, Johnny L.; Brown, Ken; Lombardi, Chris; Weksler, Mike; Coleman, Terry (July 1994). "The Designer's Dilemma: The Eighth Computer Game Developers Conference". Computer Gaming World. pp. 26–31.
- ^ Eisler, Craig (February 20, 2006). "DirectX Then and Now (Part 1)". Craig's Musings. Retrieved 2008-01-19.
- ^ a b "HOWTO: How to Mix GDI and WinG (MSKB125928)". Knowledge Base. Microsoft. Retrieved 2009-01-19.
- ^ Microsoft Return of Arcade 1996 review: RGB Classic Games