X wing vs tie fighter remastered driver#
This way the old workarounds are no longer required and I was able to force AA from the driver controlpanel which didn't work before.Įdit: If your desktop color depth is lower than 32 bit or the game fails to launch you still need these workarounds:Ĥ. Run wined3dcfg.cpl and select "backbuffer" as Offscreen Rendering Mode. Download and extract the files to the game directory.Ĥ. \Steam\steamapps\common\STAR WARS Tie Fighter\remasteredģ. I finally found a way to make 3D acceleration work in the Steam version. Then I moved the files back to the BoP directory and BoP was miraculously fixed as well. Surprisingly they worked like they should there. Since I couldn't find any error in the configuration on my part I copied all the aqrit/dgVoodoo dll and config files from the BoP to the XvT folder unchanged. This only happened to me a couple of times when freshly applying the fix to BoP. This is immediately noticeable by the dgVoodoo watermark missing from the screen (that is unless you disabled it) and results in 3D acceleration not working on AMD and invisible ships with acceleration enabled on Nvidia. On Windows 10 the game sometimes doesn't take advantage of dgVoodoo. If that happens enable "ColorFix" in aqrit.cfg by replacing the 0 with 1.Īnother way to fix it is using this tool: There's a bug in Windows 7 that affects a lot of old DirectDraw games resulting in distorted colors. (This issue is not present when using dgVoodoo.) See dgVoodoo Readme.)īefore you put dgvoodoo's DDraw.dll into the game folder rename it to voodraw.dll (If you use dgVoodooSetup.exe / dgVoodooCpl.exe to change settings (like enabling AA and removing the watermark) make sure the conf file it creates is also placed in the game directory by clicking on the ".\" button. And extract dgVoodooSetup.exe / dgVoodooCpl.exe and D3DImm.dll to the game directory.