I'd put this down to him not knowing how to use it. Many games run quite well with vorpx. They might have gameplay issues in VR, but technically many work well.
I'd put this down to him not knowing how to use it. Many games run quite well with vorpx. They might have gameplay issues in VR, but technically many work well.
He does seem to be fairly uniquely challenged getting stuff to work. Best to start with easy stuff first, then move into harder things like Bioshock. He doesn't even say he ran HL2, which is a must to be sure things are working properly.
Still, the takeaway message is still valid- it takes nearly endless jacking around to get things to work. Which pretty much reminds me of 3D Vision.
He does seem to be fairly uniquely challenged getting stuff to work. Best to start with easy stuff first, then move into harder things like Bioshock. He doesn't even say he ran HL2, which is a must to be sure things are working properly.
Still, the takeaway message is still valid- it takes nearly endless jacking around to get things to work. Which pretty much reminds me of 3D Vision.
Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607 Latest 3Dmigoto Release Bo3b's School for ShaderHackers
I read that article this morning on the bus and immediately thought he is not the man for that job.
He fails to mention that most of the busywork actually only involves about 20 seconds to switch the Rift orientation and set it to 75hz, and possibly set the Rift as the main monitor.
I tried Outlast and Borderlands 2 with VorpX without any issues at all - other than the fact that software does not conform to the IPD measurements from the Oculus profile and I had to spend roughly 5 seconds to change the parameters.
I read that article this morning on the bus and immediately thought he is not the man for that job.
He fails to mention that most of the busywork actually only involves about 20 seconds to switch the Rift orientation and set it to 75hz, and possibly set the Rift as the main monitor.
I tried Outlast and Borderlands 2 with VorpX without any issues at all - other than the fact that software does not conform to the IPD measurements from the Oculus profile and I had to spend roughly 5 seconds to change the parameters.
Note that some of the games work with much tinkering, but NOT IN STEREO!
Still, the takeaway message is still valid- it takes nearly endless jacking around to get things to work. Which pretty much reminds me of 3D Vision.
Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers
He fails to mention that most of the busywork actually only involves about 20 seconds to switch the Rift orientation and set it to 75hz, and possibly set the Rift as the main monitor.
I tried Outlast and Borderlands 2 with VorpX without any issues at all - other than the fact that software does not conform to the IPD measurements from the Oculus profile and I had to spend roughly 5 seconds to change the parameters.
i7 4790k @ 4.6 - 16GB RAM - 2x SLI Titan X
27" ASUS ROG SWIFT, 28" - 65" Samsung UHD8200 4k 3DTV - Oculus Rift CV1 - 34" Acer Predator X34 Ultrawide
Old kit:
i5 2500k @ 4.4 - 8gb RAM
Acer H5360BD projector
GTX 580, SLI 670, GTX 980 EVGA SC
Acer XB280HK 4k 60hz
Oculus DK2