<pclass="rvps2"><spanclass="rvts6">DirectX emulation determines how the fullscreen DirectX operations are managed to fit a windowed environment, with the following options:</span></p>
<tdwidth="1259"style="border-color: #000000; border-style: solid; padding: 1px;"><pclass="rvps2"><spanclass="rvts6">The primary surface and backbuffers are simply scaled to the desired size, but no other characteristic is altered. In particular, the pixel color depth and mode are not altered.</span></p>
<tdwidth="1259"style="border-color: #000000; border-style: solid; padding: 1px;"><pclass="rvps2"><spanclass="rvts6">Same as "None," but blit operations are made against a memory surface and then transferred to the real primary surface – this handles the so-called "pitch-bug" problem.</span></p>
<tdwidth="1259"style="border-color: #000000; border-style: solid; padding: 1px;"><pclass="rvps2"><spanclass="rvts6">Same as "Primary Buffer" (</span><spanclass="rvts15">EMULATEBUFFER</span><spanclass="rvts6">) but the buffer is the surface of an </span><spanclass="rvts15">OFFSCREENPLAIN</span><spanclass="rvts6"> DirectDraw surface, so it is handled similarly to a DirectX surfacebuffer.</span></p>
<tdwidth="1259"style="border-color: #000000; border-style: solid; padding: 1px;"><pclass="rvps2"><spanclass="rvts6">The virtual primary surface has a different color depth from the real primary surface, and DxWnd takes care of the color transformation internally: it might be a little slower but it involves no screen mode changes. Furthermore, this option allows you to set the "Set AERO compatible mode" that avoids making a temporary color conversion and stretching it to the primary surface (which would break the AERO desktop composition mode).</span></p>
<tdwidth="1259"style="border-color: #000000; border-style: solid; padding: 1px;"><pclass="rvps2"><spanclass="rvts6">Similar to "Primary Surface" mode (</span><spanclass="rvts15">EMULATESURFACE</span><spanclass="rvts6">), but DxWnd forwards the palette and color conversion to GDI calls instead of managing them internally. It is usually less compatible than primary surface, but in some rare cases it may better at managing unusual color conversions. Try this option if the game works but the colors are wrong or the screen is black.</span></p>
<tdwidth="1259"style="border-color: #000000; border-style: solid; padding: 1px;"><pclass="rvps2"><spanclass="rvts6">Similar to "Primary Surface" mode (</span><spanclass="rvts15">EMULATESURFACE</span><spanclass="rvts6">), but DxWnd forwards all the conversion between the virtual primary interface and the window surface instead of managing it internally. Because of recent optimizations to GDI that can now take advantage of hardware-accelerated functions, this mode is becoming particularly interesting, and the lack of extra service surfaces brings it closer to the original game schema. It is also quite respectful of AERO desktop modes.</span></p>
<pclass="rvps2"><spanclass="rvts6">Note that the chosen option only influences DirectDraw1 through DirectDraw7 interfaces. Interfaces with Direct3D8 and up (or OpenGL) are not affected by these options.</span></p>
