search

crosire / d3d8to9

A D3D8 pseudo-driver which converts API calls and bytecode shaders to equivalent D3D9 ones.
BSD 2-Clause "Simplified" License
911 stars 83 forks source link

Strange problem with d3d8to9 on Empire Earth 2 after installing Windows 10 build 17133. #69

Closed HerMajestyDrMona closed 6 years ago

HerMajestyDrMona commented 6 years ago

Hi. Yesterday I decided to install Windows 10 build 17133. It is supposed to be Redstone 4 RTM version. I'm developing Unofficial Patch for Empire Earth 2 and I am using d3d8to9, because it fixes stability problems and allows using the Nvidia GPU on laptops with Optimus. More about this problem.

Unfortunately, as fast as I installed the Windows 10 update - I noticed that the game can not be maximized with d3d8to9. It seems to work fine in the normal DX8 mode. As first I thought it's Nvidia GPU problem, but then I noticed that it's the same when I'm trying to run it on the Intel HD GPU.

I recorded a video showing the problem: https://www.youtube.com/watch?v=sqgRPujYiI0 Please don't get surprised that there is no d3d8.dll file - I called it UP15.dll, to allow users to easy switch between two versions. I tested it on many d3d8to9 versions (since 2016) with the same results. I know this isn't really a d3d8to9 issue, because it worked just fine on the older Windows version, but I bet Microsoft will never fix it, so I already should find a workaround...

Does anybody know what part of d3d8to9 I should focus on when trying to debug this problem? I would very appreciate any tips, especially from @elishacloud who has already proven many times that there are no impossible things to fix :)

HerMajestyDrMona commented 6 years ago

I found a solution for this problem :) Seems like there was a new option added under: "Properties" -> "Compatibility". It's called: "Disable fullscreen optimizations". After checking this option, the game works fine in the Full Screen mode :)

I was actually changing the compatibility settings before, however some other program was minimizing my game. Thankfully I repeated tests on a clean Win10 installation and detected what was causing it.

Have a nice day.