Conflict between Oculus CV1 and Saitek X56
- Thread starter Poz1t1v
- Start date
![[VR] Frank_G](https://forums-cdn.zaonce.net/data/avatars/m/59/59394.jpg?1553527111){kind=avatar}
I had the X-55 and it spontaneous fired commands now and then, even without VR. It turned out, that it did not receive enough power. This might explain, why your X-56 works without VR, but not with the HMD online.
Maybe plugging joystick and controller into different usb-controllers might help. Usually, the front and rear usb ports on a case are on separate usb controllers.
Otherwise, you might use a powered usb hub for the joystick and throttle. I can't tell, if this will help, but this was definitely a known issue.
Maybe plugging joystick and controller into different usb-controllers might help. Usually, the front and rear usb ports on a case are on separate usb controllers.
Otherwise, you might use a powered usb hub for the joystick and throttle. I can't tell, if this will help, but this was definitely a known issue.
I had to plug my X-56 directly into my mobo to stop this.
Weird stuff happened when I ran the HOTAS on a USB-hub. Put high-power stuff straight in, and mice and such on the hub.
Weird stuff happened when I ran the HOTAS on a USB-hub. Put high-power stuff straight in, and mice and such on the hub.
Get a powered USB hub for peripherals, high data capacity stuff directly on board.
The rift needs all the bandwidth and power it can get out of a USB controller, that's not just port, controller, if you for instance have 2-4 ports stacked on top of eachother on a motherboard, all those ports go on the same controller.
And VR headsets need all the power and bandwidth available, so plug that into USB 3 ports.
Get a hub with it's own DC\wallplug adapter, USB 2 should be fine, I have not seen a usb 3 hub that actually handles full bandwidth.
Plug all your joysticks\gamepads etc into that and plug into a usb2 port.
That would make certain that they aren't sharing USB controllers with the rift.
USB in general though is dogshite.
The rift needs all the bandwidth and power it can get out of a USB controller, that's not just port, controller, if you for instance have 2-4 ports stacked on top of eachother on a motherboard, all those ports go on the same controller.
And VR headsets need all the power and bandwidth available, so plug that into USB 3 ports.
Get a hub with it's own DC\wallplug adapter, USB 2 should be fine, I have not seen a usb 3 hub that actually handles full bandwidth.
Plug all your joysticks\gamepads etc into that and plug into a usb2 port.
That would make certain that they aren't sharing USB controllers with the rift.
USB in general though is dogshite.
Last edited:
If it works it works, if not try a hub, any hub with a dedicated wall plug, so your closest electronics store should have a few.
Things doesn't necessarily fail completely when USB devices start running low on power as mentioned, weird stuff starts, instead.
And even though the USB 2 won't use the same data controller as the USB 3 ports, I imagine the motherboard could still run it off the same power feed, it depends how many corners they cut in the motherboard designs, and they tend to cut a lot of corners on USB's..
Seriously I have been using a powered hub with just one device attached at times, just to get it off the PC internal power.
I would follow TorTorden's advice if the issue persists. I own a X56 and had the same problem. I bought an Amazon Basics USB HUB with two fast charge ports that has its own power supply and plugged it into that. Never had the issue again.
Thank you all for the tips!
I connected hotas through our hub. For several hours of play, the buttons once worked themselves, lowered the quality of the settings in the game, and watched on.
There was one problem: before starting the game (if the computer was turned off) I set up dead zones on the stick. If they are unconfigured, the ship turns on one of the axes.
I connected hotas through our hub. For several hours of play, the buttons once worked themselves, lowered the quality of the settings in the game, and watched on.
There was one problem: before starting the game (if the computer was turned off) I set up dead zones on the stick. If they are unconfigured, the ship turns on one of the axes.