emoose
Instant Crash on Vibration Mode 2
Even after dragging the mentioned x1nput files to the game folder, the game crashes when virbration mode 2 is on,. It opens fine on all other modes. I am using an Xbox Series controller connected via bluetooth.
When the x1nput files are removed, mode 1 and 2 don't crash the game but of course mode 2 doesn't work as intended
Maybe some issue with x1nput, had a lot of crashes with the different versions on there, only 1.3 really seemed to work with C2C, maybe that ver has some issue with bluetooth connections though.
Really it's kinda strange that mode 3 works while others don't, all those modes are really doing is changing motor %, not sure why that would break it...
Did try looking into building impulse support into the mod itself, it's a little tricky since MS only seem to support it properly on UWP/Xbox/x64 games, not old win32 stuff, couldn't really find any "official" ways to get it added.
Did find a new way to do what x1nput does using a slightly different method, maybe that would work better for you. If you want to try it here's a build: Outrun2006Tweaks-0.2.5-xinputImpulse.zip
Make sure to remove the xinput1_4 from x1nput, and enable both VibrationMode and VibrationImpulseEnable inside tweaks INI, let me know whether that helps or not.
The new implementation solves this issue, at least for me. I guess this issue can be closed.
Can also confirm this fixes impulse triggers, however I'm getting an odd bug where sometimes at the start of a race my wireless controller will disconnect and then reconnecting, losing about five seconds in the race. This doesn't happen everytime but when it does it's always when the loading screen finishes and the race starts
Ah darn, probably is related to the impulse stuff then, just to make sure does setting ImpulseVibrationMode = 0 in the INI stop the disconnects?
The impulse code from X1nput does mention something about bluetooth ID numbers: https://github.com/emoose/OutRun2006Tweaks/blob/d87a6fef378962e4306ee32736e9c879dcc5328e/src/hooks_input.cpp#L75 I wasn't sure about that since I use xbox wireless adapter which worked fine with that code, but guess it could be causing some issue with it, will try seeing if there's some way to find that number properly.
E: hm, tried connecting controller with bluetooth but it just made game start stuttering every second, odd, did that happen for anyone else?
Sorry for my late reply but the problem still persists with ImpulseVibrationMode set to 0
Hm, wonder if it's the ControllerHotPlug setting, that tries scanning for any newly connected devices, maybe has some issue with bluetooth?
Could be worth seeing if VibrationMode = 0 helps at all too, not really sure what else it might be besides those two.