64bit FFB sticks and CTD
one of my squadron mates has a problem with his Saitek Evo Force Stick and the 64bit version of BMS.
If plugged in, BMS loads a black screen and then “is not working” anymore. Removing the stick or using the 32bit exe works without issues. We tried the 32 and 64bit driver versions, both didn’t work.
Part of the error message:
We figured out a work around, disable the SaiQFFB5.dll (rename it), then startup BMS, rename the file back to original. BMS however still crashes on exit.
Without the SaiQFFB5.dll the Force Feedback and artificial spring don’t work, so just disabling the dll for the whole time is not an option.
hmmm possible reason for my 4.33 64bit not running??? I have the saitek wheels for rudder. but he gets an error message, I don’t.
Good find though.
Update on this issue:
Several collegues of mine had problems with their FFB sticks and the 64bit exe. Disabling the .dll mentioned in the windows event viewer fixed the problem.
Yeap I also did the trick with my saitek r440 FFB wheel and it worked…
The dll was: C:\Windows\System32\SaiQFF04.Dll
just renamed it to SaiQFF04.Dxx
Darkman last edited by
Please post a bug report using this guide: https://www.benchmarksims.org/forum/showthread.php?6181-How-to-write-good-bug-reports
Remember to zip/7z the crash dump and post a link to it, so the the developers can see what is happening.
Darkman last edited by
While we’re waiting for the crashdumps some feedback and a suggestion from a developer:
_I tested with some force feedback hardware here (non-Saitek) and had no issues, neither in 4.33 public nor in the dev branch, 32-bit and 64-bit behaved identically.
However: I did some research, and it looks like especially Saitek is known for having buggy 64-bit FF drivers. Most solutions recommend removing the default definition for the Joystick from the registry (written by the driver), so that Windows can re-query the device capabilities and re-create the registry definition at the next restart.
The steps to be taken would be:
Open the registry editor.
Navigate to HKEY_CURRENT_USER\System\CurrentControlSet\Control \MediaProperties\PrivateProperties\Joystick\OEM
Check each subkey (VID_xyz…) in there for the “OEMName” entry. If you found “your” stick, remove the whole corresponding “VID_xyz…” entry.
Restart Windows(!), and check again.
I’m not saying that this is THE solution, I’m just saying that this is what seems to have helped most users suffering from 64-bit FF issues. Maybe you want to post this info in the public forum and ask for feedback on this? However, if it does not help, of course the CTD dumps are still welcome._
not my case, no logs, neither Darkman Solution works for me. which I have tried before Darkmans post.
It’s getting even more strange:
a friend of mine (mentioned in the original post) actually needs the FFB for his artifical spring, so we figured a workaround to use FFB on that Saitek Evo Force Stick in 64bit. We created a batch file that disables the .dll, starts BMS, waits 30 seconds, and .enables the dll again. Another batch file for the same thing backwards for closing BMS again without crashing. By doing so, FFB actually still WORKS within 64bit.
ZaidAlkalaldeh last edited by
HEY! i have the same problem ,but where to find the saiqffb5.dll file?? many thanks!
yura last edited by
Thank you very much! I have exactly same problem and I’ll try to fix it on your way.