TerryRed
Pinball Hall of Famer
Future Pinball-BAM on Oculus Quest 2 in VR
OK.. after some testing, here's what I find works very well for me on my system to get very smooth gameplay, and a very nice SS / clean image. No funky ball judder, etc.
My System: i5 9600K CPU, 16 GB ram, GTX 1080, 5GHz router
Not used:
Note: FP-BAM Open VR does NOT work well with Oculus Link (so far)
Does this make sense? The Oculus Quest 1 Link is running at 72Hz, and the Rift S at 80 Hz and Rift CV1 at 90HZ... so maybe that is the reason they don't work well with BAM Open VR with terrible judder problems. I've tried all settings of FP and GPU driver, Windowed, Fullscreen, vysnc on and off, etc. Maybe also running on Oculus API on top of Steam VR is causing problems.
Is it possible to get BAM to work with Oculus API directly...or have a more direct control over the Hz and sync settings?
*************** Settings ******************
Steam VR:
Future Pinball:
BAM:
Exiting a table and Starting another table:
Not sure what other solution to use for a table switching method without using a typical front-end. I'm open to ideas!
Good luck!
I'm so happy many of you guys will finally be able to enjoy some of my table updates, and the MANY FP tables out there that work completely in VR (no changes or updates needed) and simply look amazing!
- Using Virtual Desktop (VD) Wireless for PC VR!
OK.. after some testing, here's what I find works very well for me on my system to get very smooth gameplay, and a very nice SS / clean image. No funky ball judder, etc.
My System: i5 9600K CPU, 16 GB ram, GTX 1080, 5GHz router
Not used:
- Oculus tray Tool is not running
- no special settings with Oculus Debug Tool (most of what we do is handled by Virtual Desktop)
- DO NOT use Open Composite for FP! It won't work with Virtual Desktop wireless (so far)
- normal front-ends to launch tables in VD. While I do have this working... it always causes judder problems. Probably due to VD also capturing my cabinets 4 monitors.
- PinEvent PuP-Packs (at first). These can cause a heavy judder. Probably due to VD capturing the monitors that the pup-packs are displayed on.
Note: FP-BAM Open VR does NOT work well with Oculus Link (so far)
- for whatever reason Oculus Link causes terrible judder in FP BAM Open VR, no matter what settings are used
- when running FP in VR on non Oculus headsets like Index (which can run at 120hz)... there seems to be no problems
- my guess is that FP needs to be running in either 60Hz or 120Hz in VR (even multiple of 60hz) to get a good judder-free experience
@ravarcadeDoes this make sense? The Oculus Quest 1 Link is running at 72Hz, and the Rift S at 80 Hz and Rift CV1 at 90HZ... so maybe that is the reason they don't work well with BAM Open VR with terrible judder problems. I've tried all settings of FP and GPU driver, Windowed, Fullscreen, vysnc on and off, etc. Maybe also running on Oculus API on top of Steam VR is causing problems.
Is it possible to get BAM to work with Oculus API directly...or have a more direct control over the Hz and sync settings?
*************** Settings ******************
Steam VR:
- set to 100% resolution
- no super sampling / AA, smoothing, etc
- buy Virtual Desktop (VD) for Quest
- patch virtual desktop for wireless PC VR using Side Quest
- only use 60Hz for now (FP seems to need 60 or 120Hz to run nicely)
- get VD working nicely with a good 5G router or better
- I have my stream and VR settings set to High
- I have my stream and vr bitrate set to the lowest
- use the settings in the pics below for FP
- when you have everything running really nice, you can always come back here and up the transparent AA if your system can handle it (I wouldn't go higher than 4)
Future Pinball:
- the pic below shows my FP settings
- I recommend starting with this at first to be sure you'll have good smooth gameplay
- when you have everything running very nicely, you can always come back and try enabling reflections if your system can handle it
BAM:
- do a clean install of the latest BAM-Open VR (do NOT mix with normal BAM folder). you may want to start with no BAM\CFG files so that your tables will all start with the same settings (that you will create below)
- now you run FPLoader.exe from BAM Open VR folder from your Virtual Desktop in VR. Try running a table
- you'll probably see the table below you. Bring up the BAM menu with Q or ~
- if you get a grey screen...try exiting the table, close FP and try again
- by default the HOME key (re-center) is F12 (you can change it in BAM menu)
- In Add-ons: Hide FP logo = true, Hide Overlays = always, Frame Limiter = Off (important)
- Vsync = OFF
- AA = x2 or x4. Can be set higher if your system can handle it...but keep it low at first or you may get judder. This setting combined with GPU Transparent AA make all the difference in FP looking crisp and nice... but it also can be a heavy hitter on fps for some tables.
- Frame Latency = Important! Try each value for yourself. Each person is different. This will help with the table not being in sync with your head movement
- you can adjust the table's position and size and angle in the usual BAM Table menu
- you can also setup your gamepad to move around in VR in real-time
- older tables would benefit from Presets: Default or Night.
- newer tables like Ultimate Pro and PinEvent will set this for you per table
- set what you like for a default setting
- be sure to use New Renderer only (though "old" tables will look fine with FP Original, don't set that as your default)
- once you have everything looking the way you want, go back to the main menu and make sure you "Save as Default"
- now ALL tables will use these settings the first time they load
- you can always choose "Reset to Defaults" for any table at any time (if you mess up another table)...or you can delete their BAM\CFG file
Exiting a table and Starting another table:
- when you exit the table, you'll see you are still in Steam VR. This is ok, and you want to leave it there
- press the left Oculus controller's Menu button twice to go back to your virtual desktop
- close FP and reload BAM Open VR and load your next table
- once the table is loaded, its possible it may not kick into VR, and you may only hear it or see the FP window. If this is the case, then just press the left Oculus Controller's menu button twice to go back into VR
- enjoy another table!
- you may need to press the BAM HOME / Reset key each time a table loads to center it
- repeat the above for exiting and starting a new table (or take off your headset and look at your monitor)
- once you get everything running nice, I suggest trying SLAM's Ultimate Pro tables, and my PinEvent updated tables, some of GeorgeH's updates, Gimli and wild's updates... as they are set for proper lighting and look really good in VR!
- Star Wars DSA: Epic Space Battles look particularly cool if I do say so myself!
- older tables should run really well. If needed they can be set to FP Original for it's renderer (which will help with fps)
- New Tables (Ultimate Pro, PinEvent, etc) MUST use New Renderer, or they will look like ass!
- DO NOT enable pup-packs or Pup stream until you have all tables working and looking good!
- once you do... then you can try to enable ONLY the PuP FullDMD and the PUP Stream FullDMD option! Disable the others so VD isn't over burdened! (The table is smart enough to make the Backbox and FullDMD look correct) If the table doesn't run well for you, then keep pup and pup stream disabled!
Not sure what other solution to use for a table switching method without using a typical front-end. I'm open to ideas!
Good luck!
I'm so happy many of you guys will finally be able to enjoy some of my table updates, and the MANY FP tables out there that work completely in VR (no changes or updates needed) and simply look amazing!
Last edited:
ps I only read the second post and it looked like spec sheet only ...
