Open djdallmann opened 8 years ago
It loads the d3d libraries and checks the registry key, but does it render using D3D? Is there a reliable way to check?
@djdallmann you mean you also have FPS problems with the latest version if you use OpenGL rendering? cause i'm have FPS issues on Windows 10.
I changed the "EngineD3D" key in my registry to "1", started Half-Life and a game. According to Process Explorer, the only DirectX components that are loaded are DirectSound and DirectInput but there is nothing mentioning Direct3D.
So unless you give us a proof that counter what I'm saying, I consider this as a fake.
UPDATE : OpenGL can't be the cause of mouse movements problems. OpenGL is a graphics API not an input API, so if you have to blame an API, blame DirectInput.
And I would like to know how people are getting FPS issues with Windows 10. I never had a single problem with any GoldSource game/mod on Windows 10 and some people know that my laptop is a piece of **\ when it comes to gaming.
Here are some of the events I found to be notable, I'm not personally familiar with these DLLs but the name definitely seems related to things hl.exe was doing during execution. "hl.exe","2252","RegQueryValue","HKU\S-1-5-21-1871063118-2744621327-3756644626-1001\Software\Valve\Half-Life\Settings\EngineD3D","SUCCESS" "hl.exe","2252","QueryBasicInformationFile","C:\Windows\SysWOW64\d3d9.dll","SUCCESS" "hl.exe","2252","QueryStandardInformationFile","C:\Windows\SysWOW64\d3d8.dll","SUCCESS" "hl.exe","2252","QueryBasicInformationFile","C:\Windows\SysWOW64\dxgi.dll","SUCCESS"
Can I see the output of version
in the console ?
Protocol version 48 Exe version 1.1.2.7/Stdio (cstrike) Exe build: 13:14:12 Aug 29 2013 (6153)
I used process monitor from microsoft it captures all forms of access to the system, similar to process explorer but has more features.
Note that the engine uses SDL for input these days, unless you're playing a mod that uses another API in the client dll.
Is that why people get weird mouse accel and half the settings related to it don't work?
Change the following registry value to dword value 1 to enable D3D and use -nofbo with mouse options (-noforcemparms etc) [HKEY_CURRENT_USER\Software\Valve\Half-Life\Settings] "EngineD3D"=dword:00000001
I noticed hl.exe still loads all the d3d[89] libraries and also checks the registry key EngineD3D. This restores cs movement mouse movement and most likely fixes fps too, the new opengl rendering (even nofbo) changes broke the game.