Openbor games conflicting with wheel on PC

Krellos

New member
Hey everyone. I've got an odd situation and not sure if fixable. My Arcade PC has a wheel attached to it. As well as two joysticks. Some Openbor games open and close right away. When I look at the log, I get errors like this (this was he-man):

Warning: Unable to initialize rumble for joystick: Logitech G HUB G29 Driving Force Racing Wheel USB in port: 2! SDL Error: Haptic error Unable to create effect

I'm not trying to use my wheel to play them, but for some reason OpenBor is seeing my wheel as the first controller. That being said, some other games play just fine. Any suggestions are greatly appreciated!
 
Hey everyone. I've got an odd situation and not sure if fixable. My Arcade PC has a wheel attached to it. As well as two joysticks. Some Openbor games open and close right away. When I look at the log, I get errors like this (this was he-man):

Warning: Unable to initialize rumble for joystick: Logitech G HUB G29 Driving Force Racing Wheel USB in port: 2! SDL Error: Haptic error Unable to create effect

I'm not trying to use my wheel to play them, but for some reason OpenBor is seeing my wheel as the first controller. That being said, some other games play just fine. Any suggestions are greatly appreciated!

Welcome to the community @Krellos. The wheel problem is a new one. My guess is you are playing a game that uses an older version of the engine? We had some control bugs that were ironed out in 4.0, but your specific issue isn't one I've heard of. Which games in particular caused the crash? Also, as a control group, have you tried them with a known good setup (i.e. no wheel)?

DC
 
Hey DC. Thanks for the quick response! So far Dungeons & Dragons Animated Series and Super Karate Kid launched and play just fine. Double Dragon Alternative and He-Man don't. The error I posted was from He-Man. All obtained from this site. On my PC I run Launchbox. I've tried launching via the self-contained files obtained here, as well as the file from SourceForge updated 2017-04-01 (looks like version 3). I will try the 4.0 version on this site later tonight see if that fixes the problem.

To answer your other question, I tried he-man on my laptop with nothing attached to it (WIndows 10) and it loaded just fine. But the error I saw on my Arcade (Windows 11) with the joysticks and wheel had me puzzled.

I will try tonight and respond. Thanks again!
 
Welcome to the community @Krellos. The wheel problem is a new one. My guess is you are playing a game that uses an older version of the engine? We had some control bugs that were ironed out in 4.0, but your specific issue isn't one I've heard of. Which games in particular caused the crash? Also, as a control group, have you tried them with a known good setup (i.e. no wheel)?

DC
I downloaded the current Openbor 4 from the site here. And just launching without trying to load any games I still get:

Total Ram: 17040277504 Bytes ( 16250 MB )
Free Ram: 9979957248 Bytes ( 9517 MB )
Used Ram: 6938624 Bytes ( 6 MB )

debug:nativeWidth, nativeHeight, bpp, Hz 1920, 1080, 24, 60

Warning: Unable to initialize rumble for joystick: Logitech G HUB G29 Driving Force Racing Wheel USB in port: 2! SDL Error: Haptic error Unable to create effect.

It's trying to do something with my wheel as a default for some reason!
 
@DCurrent

have not had the chance to check version 4, so the "enumeration limit" issues that 6391 had are gone?

@Krellos
on openbor 6391, lightguns , wheels etc, are best if you keep them as controllers enumerated beyond 5, openbor 6391 "wants dibs" on the devices 1 2 3 and 4
there are programs that can help change the enumeration of USB devices, that means your other emulators or games will have to be re-mapped taking into account the wheel as input device 5 or 6 or whatever
 
@DCurrent

have not had the chance to check version 4, so the "enumeration limit" issues that 6391 had are gone?

@Krellos
on openbor 6391, lightguns , wheels etc, are best if you keep them as controllers enumerated beyond 5, openbor 6391 "wants dibs" on the devices 1 2 3 and 4
there are programs that can help change the enumeration of USB devices, that means your other emulators or games will have to be re-mapped taking into account the wheel as input device 5 or 6 or whatever
hmm, ok, thank you Oldyz for that info. I have WAY too much already setup to make that change just for Openbor. But good to know that's an option. Sounds like I'll just have to skip for now.
 
hmm, ok, thank you Oldyz for that info. I have WAY too much already setup to make that change just for Openbor. But good to know that's an option. Sounds like I'll just have to skip for now.
well, if you manage to find a program that can change device enumeration as a command line, you could make a .bat file or script that
1 - changes the wheel to device 6
2- runs openbor
3- after openbor closes wheel turns back to device #1

if your arcade PC has mouse and keyboard, the other thing you can do is use JoyID before playing openbor, after you are done, change the wheel back to controller usb 1 or 2

 
well, if you manage to find a program that can change device enumeration as a command line, you could make a .bat file or script that
1 - changes the wheel to device 6
2- runs openbor
3- after openbor closes wheel turns back to device #1

if your arcade PC has mouse and keyboard, the other thing you can do is use JoyID before playing openbor, after you are done, change the wheel back to controller usb 1 or 2

ah ok! I'll try that. Thank you very much.
 
Back
Top Bottom