Agreed. I sooo want to download Fallout 4 today but can't stand the idea of not playing a game like that in VR. With all the light colored texts though, I bet it's going to be a challenge to read stuff.
Oculus runtime switcher... Finally setup today - Great!
- Thread starter grammatonfeather
- Start date
Agreed. I sooo want to download Fallout 4 today but can't stand the idea of not playing a game like that in VR. With all the light colored texts though, I bet it's going to be a challenge to read stuff.
Fallout 4 won't display in stereoscopic 3d on vorpx until Ralph does the coding for it. The game can be played with the headtracking on vorpx but it will display in 2d flat pancake mode. You could play it on the virtual cinema screen that comes with vorpx and see what u think. Still very impressive playing a game on a massive screen.
So the demo scene works... can you try a few other demos and see if they work in extended? So presumably you're able to run Elite D without the switcher on 5.0.1 and your current ATI driver?
Yup, you need a combination of game set to 120 FOV and the vorpx in-game settings. I set every game to 120 fov either manually or with the vorpx game optimiser... then in game press DEL key and adjust reduce the 3d zoom just short of seeing the blank bars at the top and bottom of the screen. Sometimes I also adjust the stereoscopic depth from the vorpx in-game menu. Lastly it's important to set the correct IPD and Vorpx can take this setting from the oculus profile settings based on your calibration.
Indeed. Its a great feeling when you get it right the first time, and then you realise how many cool games you can now potentially play in VR. I think it was Skyrim when I got it right first time round.
Funnily enough, I find FOV set to 110 works best for me usually.
Any word if and when Ralf will get Fallout4 working in stereoscopic 3D? I havent been on the forums for a while.
Last edited:
Agree. The vorpx recommendation is for 120 but sometimes that's not enough and sometimes too much.
I had a lot of issues the first 3 or 4 days with vorpx. The game optimiser wasn't actually setting any of the games to 120 (except Dishonored for some reason). Took me days to get Metro last light playable because I didn't really know what I was doing.
Arma 3 had default FOV after using vorpx optimiser so I found an FOV calculator online and edited the xml manually. From that point on the game looked good.
My antivirus was interfering with vorpx (I didn't figure this out for a few days).
Skyrim looks amazing especially since it was unplayable with vireio perception.
The Battlefield games are kind of a waste of time since u can't get the wide FOV in any vehicle. You could use edge-peak for flying and zoom back in for foot stuff.
Really all of these user findings should be added to vorpx website. Ralph has a game settings sub-forum but it's mostly for problems.
Ralf has released a new update for vorpx bringing 3d support to Fallout 4. You might want to check that out. Your vorpx has probably already updated to .091?
You guys have stoked my interest in Vorpx for various games now! Quick question though when speaking of minimum FPS for it to work well....
What is the target FPS needed first *without Vorpx* so that it will work well with it? I know the DK2 likes to be at 75 so do I need to carry two times that in 2d mode so that it splits into two 75FPS images in the rift or is something lower acceptable? Thanks.
What is the target FPS needed first *without Vorpx* so that it will work well with it? I know the DK2 likes to be at 75 so do I need to carry two times that in 2d mode so that it splits into two 75FPS images in the rift or is something lower acceptable? Thanks.
You need much more than two times that I'm afraid. The rendering is one thing, the tracking and latency stuff all pays a price.
I believe vorpx has an FPS indicator so I might turn it on and check what I'm getting. I must say though that I don't have the judder issues with games on vorpx like I do with same native VR ones.
Also that 75 refresh thing isn't something my GPU can maintain all the time but the oculus runtime allows for that to a certain extent. On FSX with the amazing Flyinside plugin my FPS would often drop to about 40 but the sim still ran smoothly (no judder). Judder is absolutely intolerable as far as I'm concerned. That's the reason I uninstalled DCS world because it's just not optimised at all and so many people complain about the judder.
My GTX 680 is pretty old now but I guess the overclock helps (gives me an extra 20 frames per second) together with CPU overclock.
Also that 75 refresh thing isn't something my GPU can maintain all the time but the oculus runtime allows for that to a certain extent. On FSX with the amazing Flyinside plugin my FPS would often drop to about 40 but the sim still ran smoothly (no judder). Judder is absolutely intolerable as far as I'm concerned. That's the reason I uninstalled DCS world because it's just not optimised at all and so many people complain about the judder.
My GTX 680 is pretty old now but I guess the overclock helps (gives me an extra 20 frames per second) together with CPU overclock.
Thanks for all the answers guys. Here's my story which leads to the next question...
I had a DK2 when Elite launched and played with it exclusively, never using the monitors. Some time later I got bored and sold the Dk2 and took a break from Elite. I recently decided to start up again and scored another DK2 which arrives tomorrow. I understand the switching between the .7 and .5 runtimes to get Elite working, but I have also since upgraded to Windows 10. I tried to install .5 today but Oculus won't do it giving an error. Am I screwed for now with Windows 10 or is there a workaround? Thanks.
I had a DK2 when Elite launched and played with it exclusively, never using the monitors. Some time later I got bored and sold the Dk2 and took a break from Elite. I recently decided to start up again and scored another DK2 which arrives tomorrow. I understand the switching between the .7 and .5 runtimes to get Elite working, but I have also since upgraded to Windows 10. I tried to install .5 today but Oculus won't do it giving an error. Am I screwed for now with Windows 10 or is there a workaround? Thanks.
Last edited:
I never had probs with win10 on .5 (upgraded from win8). The switcher has its own .5 driver which works for me so you should be ok
OK, so it sounds like I should first install the latest oculus software and then using the switcher will get the .5 working on it's own?
Yes. You simply install 0.7 or 0.8 runtime. Do not download or install 5 or 5.0.1. Not necessary.
When you extract the zip file... Copy the Windows folder (from the extracted zip) to the root of your C: drive.
Then copy the Oculus_0500 folder to program files (x86)
Then you can go into the program files (x86)/Oculus_0500/ folder and send create desktop icons to launch the 0500 and 0700 easily.
Whenever you run the 0500 command the oculus panel should say that the oculus is switched off but the tracker is working. That is normal. Just run Elite.
That was VERY easy to understand. Thanks and have some rep. Just installed it and tested to be working perfect. So easy!!! DK2 should be arriving any time today!!!
Last edited:
Don't forget to run the 2 .cmd as Administrator. I had some scary times before I remember this point. You can set them definitively to run as Adminstrator by right-clicking on them and select Properties. Also, I suggest to edit both .cmd to study all path used on them. My version had some quotes missing around path and as I had space to reach the Runtime 0.8.0.0 it failed until I modified them lightly.
In any case, this switcher run perfectly for me between 0.5 and 0.8 on my Win 10 64bits, great little things
In any case, this switcher run perfectly for me between 0.5 and 0.8 on my Win 10 64bits, great little things
Don't forget to run the 2 .cmd as Administrator. I had some scary times before I remember this point. You can set them definitively to run as Adminstrator by right-clicking on them and select Properties. Also, I suggest to edit both .cmd to study all path used on them. My version had some quotes missing around path and as I had space to reach the Runtime 0.8.0.0 it failed until I modified them lightly.
In any case, this switcher run perfectly for me between 0.5 and 0.8 on my Win 10 64bits, great little things
Yes, did that straight away and had no troubles. Working perfectly on my system which is the same as yours. Now to just get my X52 configured back to wherever I had it before and learn how to fly again. It was glorious to see the DK2 fire right up and load Elite without a hitch! Now I have to fight myself on whether to play this or Fallout. 1st world problems!!!!
Thanks! A point to note is that whenever you change your main runtime you will need to drop the switcher's Windows folder back in to your C: root again. I changed from .7 to .8 runtime last night so I had to do that.
I also switched to the very latest Nvidia driver 358.91 and I swear I've never seen Elite so smooth!
I've been very impressed with how good Fallout 4 looks on vorpx.
Have you found it to be a problem that Fallout 4 doesn't have geometry based 3D and uses z mode instead? Some people say it's fine and others hate it.