I recently got a G29 racing wheel and I was trying to set it up, with some difficulty. My setup is the wheel physically connected to a linux machine and in use by a windows machine, which I then use remotely using moonlight. I can see the wheel in windows and in G Hub, but when I try to run a game in steam everything except the control buttons are unresponsive.
I looked for a solution and most of them referred to a special-purpose build of the program from a few years ago. Is that still necessary for this device? Or am I missing something else?
.
Stop the virtualhere server process (e.g
systemctl stop virtualhere)edit the
/usr/local/etc/virtualhere/config.inifile and add the lineClaimPorts=1then start the virtualhere server process again (e.g systemctl start virtualhere)
now see if it works ok.
.
That did the trick. Thank you so much!
.
So, this worked perfectly for me on my old system last month running an older flavor of kernel 6. I've since switched out hardware and did a new clean install and now running virtualhere as a service with this configuration results in the usb system failing to register hotplugged devices. Devices present at boot are recognized but once unplugged can't be re-registered. dmesg | tail showed that devices were being identified but never assigned a unit in the /devices or usb-* system trees. When I turned off the virtualhere process the problem was resolved.
.
Yes that is expected behavior, with ClaimPorts=1 it suspends local driver binding so it doesn't interrupt passthrough. Stopping vh will resume driver binding as so you can see USB system trees. Do the hotplugged devices still appear in the vh client?
.
That makes sense, thank you for the clarification. I'll test it a bit more, but when I unplugged the wheel and plugged it back in it did appear on the vh client but didn't bind correctly; it wasn't recognized by motorfest or oversteer.