Tested the new version: the "out-of-track" rumble works great (like before), but the "collision with other cars" one is not working
on my wheel BUT
i must say that only one rumble output is connected to my wheel (i don't remember if it's the left or right ATM) so i cannot feel the one not connected. Another possibility is that you set a strenght <10000 which, in mamehooker, is not sufficient to rumble the motor i am using so probably it's not with OR2FXT too.
I also reactivated the windows "beeps and annoying loging logoff popup ---steaming pile of meadow muffin---", but i was not able to hear the jap tracks (nor the activation beep).
The horn is still not played.
I gave a check to the button press detection by the debug utility, and the button presses are not recorded untill the start of the race, then they are. So, in the mode/car/music selection menu they are not recorded but i can see a full brake press (255) while in game. The debug window shows the pressing of the horn (button "16" , right arrow) too, but only in-game.
The brake is mapped to the "2" keyboard button and the horn to the "RIGHT" arrow. Maybe the mixed configuration i am using (360 pad X-axis for wheel,
PS/2 keyboard for the digital buttons) makes things harder?
just that i am here, let me suggest a couple of things:
- possibility to control the rumble strenght (i know that this could be an easy task, i learned it from mamehooker advanced Xinput outputs
)
- possibility to send all the outputs to one single rumble motor...
Ah, almost forgot: the first time i launched the config utility (with the first exe i mean) the default resolution set was "0x640" ... not a big problem, you can change it easily, but for sure fixing this could avoid some "issue not issue" reported from the casual user that launches the main program straight forward
(don't ask me why i noticed that running it straight forward doesn't work
)