search

UCyborg / LegacyD3DResolutionHack

Simple proxy DLL which removes artificial resolution limit from Direct3D 7 and below.
MIT No Attribution
60 stars 6 forks source link

Second check? #2

Open mirh opened 7 years ago

mirh commented 7 years ago

https://sourceforge.net/p/dxwnd/discussion/general/thread/bee67290/#c6c7/2c59/2f39

UCyborg commented 7 years ago

I did notice the second occurrence, I just didn't touch it because nobody knows for sure what's it for. It would be nice if someone could confirm if it really is related to screen resolution.

mirh commented 7 years ago

@ghotik

fluxx0r commented 5 years ago

I installed the newest version of thirteens widescreenfix and I used the d3dresolutionhack, now my game starts with 21:9 format in 2560x1080 but when I drive a very fast car I have graphic problems, maybe anyone knows a solution? https://www.youtube.com/watch?v=JeKS1T5Smmo I'm using windows 10, with a nividia 980gtx ti, newest updates and drivers are installed

fluxx0r commented 5 years ago

problem seems to be solved. I had to change to zoomfactor from the widescreenfix from auto to 4.0 now it works!

elishacloud commented 5 years ago

The second occurrence is located inside the DLLMain entry point function (with both d3dim.dll and d3dim700.dll). I could not tell for sure what it was checking (since I don't really want to spend the time to debug an entry point function) but I don't think it has to do with the resolution.

However, either way the code only seems to run when the dll is loading so changing it would not do any good since LegacyD3DResolutionHack is only able to change the code after the dll is already loaded. At that point it is too late since the code has already executed.

Bottom line: I think it is safe to ignore the second check.