Is anyone else seeing this? A weigh in from Oculus would be nice right about now. I'm using an optimal set up ( Centaurus Proton Gaming Computer - Intel Core i7 4790 4.0GHz Quad Core + HT, 8GB 1600MHz, Nvidia GTX 970 4GB, 250GB SSD, Windows 8.1 64bit) and my experience with 2 sensors right out of the box was great. Not perfect but good enough to make me very excited about the prospects of having full 360 coverage when the additional sensors were available.
Took delivery and immediately installed the additional sensors this evening. No issues, set up went off without a hitch, but the latency and the artifacts are horrible. I'm a pilot, so getting sick using this rig was never an issue until now. Jumpy, jittery, disorientation, vertigo, the whole enchilada. I reverted to just two sensors and back to normal. The real pity here is that some of these games would be SO much better with full 360 coverage. SuperHot for one. I'm constantly dancing out on the edge of the playing area only to see the images jump and shutter. I need the rest of my holodeck to be filled in.
I only have a 2 sensor setup and apart from feeling a little sick playing The Vanishing Of Ethan Carter haven't had a problem, I was thinking about a 3rd sensor to get 360 but my PC room is only about 15 x 5Ft and I don't thing it worthwhile for such a small space.
3 is better, no doubt. Generally back to normal without any of the issues I experienced with 4. I did find that even 3 does create an edge case for some games. Pro Fishing Challenge for instance. With 3 sensors, it just crashes. You can work your way into the game, but after a few clicks, the side of the box that the third sensor is on goes black. I guess we are the testers in this case.
So, what's the deal? Is a forth sensor configuration even supported... ultimately? If so, will there be faster hardware required to make it work, or will this be a software fix? It seemed pretty obvious that the construct was having issues keeping up with the additional load.
I'm enjoying the ride whatever the current issues are.
I'm using an optimal set up (Centaurus Proton Gaming Computer - Intel Core i7 4790 4.0GHz Quad Core + HT, 8GB 1600MHz, Nvidia GTX 970 4GB, 250GB SSD, Windows 8.1 64bit)
This is being pedantic, but you're using a system with acceptable specs, not optimal.
970 was min spec by Oculus standards. Only recently with ATW have they said lower can work. Similarly, the Rift is ideally run from Win 10, not 8. Not to take anything from your post, your setup should still run fine. I haven't had a chance to use even a 2 camera setup, so hopefully they can optimize for 2 while improving the experience of people with 3 and 4 camera setups.
Any sufficiently advanced technology is indistinguishable from magic.
- Arthur C Clarke
Four sensors are supported, but I think what you might be running into is USB3 bandwidth limitations. Hence why they suggest putting the third sensor onto a USB 2 port. Spread them out across USB controllers. It looks like they've found 2 sensors is fine on USB3, but 3 is too much or marginal. Most motherboards only have a USB3 controller and a USB 2, I believe.
Anyway, try moving 2 of the sensors onto USB 2 ports, see if it improves things.
Open up the Settings -> Devices menu and see if you're getting warnings on the sensors. Could well be bandwidth issues, so try moving the sensors to different USB hubs (if your motherboard has some 3.0 and 2.0, put 2 sensors in each maybe)
I hadn't used the Inatek card until my extra sensor arrived, installed the sensor but was having similar problems to those you describe, so installed the card and spread the USBs around and its been flawless ever since.
