[HELP] xwa_hook_main (DInput.dll) error message on startup
[HELP] xwa_hook_main (DInput.dll) error message on startup
-
- Posts: 9
- Joined: Wed Sep 16, 2020 4:46 pm
Hi everyone, I'm new here. I recently did a fresh install of the GOG version of XWA and then installed the XWAUCP 1.6 and all of the things (except additional craft) listed on the August 20th news post on the website front page, and in that order.
When I start the game, I get an error message stating '"To call the hook that sets full FPS" is not correctly initialized'. The title bar of the error message says "xwa_hook_main (DInput.dll)". I can click OK and the game will go ahead and start, and I can even play missions and stuff, and the new cockpits and effects look great. However, the briefings run at crazy fast speed, and the ship models in them are gigantic. I also get a sense that maybe timing is screwed up in the game, almost like laser rates of fire feel too fast, etc.
Edit: forgot to add, I'm running all this on Windows 10 version 2004 x64. Lots of CPU and RAM, nVidia RTX2070 with latest drivers installed as well.
When I start the game, I get an error message stating '"To call the hook that sets full FPS" is not correctly initialized'. The title bar of the error message says "xwa_hook_main (DInput.dll)". I can click OK and the game will go ahead and start, and I can even play missions and stuff, and the new cockpits and effects look great. However, the briefings run at crazy fast speed, and the ship models in them are gigantic. I also get a sense that maybe timing is screwed up in the game, almost like laser rates of fire feel too fast, etc.
Edit: forgot to add, I'm running all this on Windows 10 version 2004 x64. Lots of CPU and RAM, nVidia RTX2070 with latest drivers installed as well.
- JeremyaFr
- Posts: 4007
- Joined: Mon Jan 18, 2010 5:52 pm
- Contact:
Hello,
The error message means that there is a conflict with the time hook.
Did you use XwaHacker to set the limit FPS?
The error message means that there is a conflict with the time hook.
Did you use XwaHacker to set the limit FPS?
-
- Posts: 9
- Joined: Wed Sep 16, 2020 4:46 pm
xwahacker shows that my .exe is using the original 30fps. Should I change it to some other value?
- JeremyaFr
- Posts: 4007
- Joined: Mon Jan 18, 2010 5:52 pm
- Contact:
You can try to rename "hook_time.dll" with another extension. For example, "hook_time.dll_". This will disable this hook.
-
- Posts: 9
- Joined: Wed Sep 16, 2020 4:46 pm
That did make the error message go away, and the briefings now run at normal speed. Game appears to be running at 30fps now but still looks great and timing problems seem to have gone away.
- blue_max
- Posts: 2296
- Joined: Wed Mar 20, 2019 5:12 am
If you have "hook_60fps.dll" that may also cause a conflict with "hook_time.dll". I'm not sure this is what's happening here, but you can also try keeping "hook_time.dll" and renaming "hook_60fps.dll" to "hook_60fps.dl_"
I feel like "hook_time.dll" may give you better performance over "hook_60fps.dll"
I feel like "hook_time.dll" may give you better performance over "hook_60fps.dll"
-
- Posts: 9
- Joined: Wed Sep 16, 2020 4:46 pm
Thanks very much for your help guys. Hook_60fps.dll was there. I have renamed it now and re-enabled hook_time.dll. No error message on startup, but briefings run very fast again. Gameplay feels like 60fps again now though.
-
- Posts: 9
- Joined: Wed Sep 16, 2020 4:46 pm
I just checked VRParams.cfg - it is already set to that value.
-
- Posts: 9
- Joined: Wed Sep 16, 2020 4:46 pm
It’s just 60hz. It’s actually a 4k tv, if that makes any difference.
- blue_max
- Posts: 2296
- Joined: Wed Mar 20, 2019 5:12 am
A 4K TV? I wonder if the problem will go away when you plug it into a standard monitor. Let me see if I can see/fix the problem on my end, thanks for the tip.
-
- Posts: 9
- Joined: Wed Sep 16, 2020 4:46 pm
I don't know if the windows desktop scaling factor has any effect on the game either, but it could be useful information. I have it set to 150% scale so that window elements aren't obnoxiously tiny.
- blue_max
- Posts: 2296
- Joined: Wed Mar 20, 2019 5:12 am
I don't think that's relevant to your problem (but feel free to try setting it to 100%!) I've got mine set to 225% (or something like that) for the same reason. However, setting it to something other than 100% may cause mouse look to jump all over the place.