TerryRed
Pinball Hall of Famer
Future Pinball-BAM OpenVR on Oculus Quest 2
This page is dedicated to try to get FP Bam OpenVR working on Oulus Quest 2. We'll talk about using both the Oculus Link and the Virtual Desktop wireless solution.
Using Virtual Desktop (VD) Wireless for PC VR!
Great success! Mostly.
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:
*************** 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!
Oculus Quest 2 using Link Cable
****** Using a decent quality Link cable and Open Composite DLL *****
Great success! Mostly.
OK.. after some testing, here’s what I find works very well for me on my system to get smooth gameplay, and a very nice SS / clean image. No funky ball judder, etc.
Your CPU and GPU will greatly determine how well everything can run. Some tables may run really well… whereas others may be much more demanding (newer tables).
My PC Specs:
Not used:
Future Pinball:
Oculus Desktop App
This is used to change settings for Oculus PC VR without dealing with the Oculus Debug Tool. It can be found here:
Settings:
For testing, I enable the Visual HUD and set to Performance
BAM:
BAM VR settings:
BAM Table position:
BAM Lighting and Post Processing
Default and Table CFG files:
Note: that the tables may not seem smooth until AFTER you have all these settings “correct”, and you’ve exited and reloaded FP-BAM!
Exiting a table and Starting another table:
Tables:
PinEvent PuP-Packs and PUP Stream:
Once you are all setup… then running the tables is pretty normal.
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!
BAM OpenVR FAQ
I run the table from BAM-OpenVR\FPLoader.exe, and it loads and runs. I see the VR options in the BAM menu on the FP window, bit it’s not displaying in VR…
I think it’s running and working in VR but I can’t see the table…
This page is dedicated to try to get FP Bam OpenVR working on Oulus Quest 2. We'll talk about using both the Oculus Link and the Virtual Desktop wireless solution.
Using Virtual Desktop (VD) Wireless for PC VR!
Great success! Mostly.
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.
*************** Settings ******************
Steam VR:
- set to 100% resolution
- no super sampling / AA, smoothing, etc
- buy Virtual Desktop (VD) for Quest (not the Rift Store version!)
- 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 Medium
- 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!
Oculus Quest 2 using Link Cable
****** Using a decent quality Link cable and Open Composite DLL *****
Great success! Mostly.
OK.. after some testing, here’s what I find works very well for me on my system to get smooth gameplay, and a very nice SS / clean image. No funky ball judder, etc.
Your CPU and GPU will greatly determine how well everything can run. Some tables may run really well… whereas others may be much more demanding (newer tables).
My PC Specs:
- i5 9600K CPU
- 16 GB DDR4 ram
- nVidia GTX 1080
Not used:
- SteamVR is completely bypassed when using Open composite DLL
- don’t enable PinEvent PuP-Packs / PuP Stream (at first). These can cause a heavy judder and need a powerful PC. Wait until you have tested all tables and have them running smoothly, and then try enabling this to see if your system can handle it for those tables
- I have attached the openvr_api.zip (at the bottom of this post)
- extract the DLL file from the zip into the BAM Open VR plugins folder
- overwrite the DLL file already in there (you can backup if you want)
- use the settings in the pics below for FP
- you could try enabling the nvidia Low Latency mode as well
- 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
- keep vsync OFF and fullscreen enabled
- you can lower the resolution down to 640×480, since this has no effect on VR, but can affect your GPU performance

Oculus Desktop App
- be sure your Quest 2 has good and fast USB 3.0 connectivity
- you can set the resolution and Hz (72 / 80 / 90) in the device settings
- the higher the Hz and resolution… the better your CPU and GPU needs to be
- start at resolution 1.0 and 80Hz as a nice middle ground. You can always come back and go higher (if your system can handle it) or lower (if your system can’t handle it) as needed.
This is used to change settings for Oculus PC VR without dealing with the Oculus Debug Tool. It can be found here:

Settings:
- Super Sampling 0 (this comes down to how fast your system is if you want it higher)
- ASW = Off (though I find if your fps go really low this will still turn on)
- GPU Scaling = Off
- Oculus Homeless = Off (no need for this anymore, as you can disable the Home in the desktop app…very recommended!)
For testing, I enable the Visual HUD and set to Performance
- this shows a real time graph so you can see the Hz and fps
- it shows on the left what you have Link set to (72, 80, 90)
- on the right it shows how much headroom you have left for your cpu / gpu
- if the right side falls too low, then your fps / performance on the left will drop as well
- If your system is fast… then the left “should” be steady at 72 / 80 / 90 (whatever Link is set to)
- as long as the left is solid… then the game / head movement / ball movement “should” be nice and smooth!
- if your fps shows 45 constant while playing… then that means ASW is turning on (your system may be to slow for the table, etc)
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
BAM VR settings:
- 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
BAM Table position:
- 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
BAM Lighting and Post Processing
- 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)
Default and Table CFG files:
- 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
Note: that the tables may not seem smooth until AFTER you have all these settings “correct”, and you’ve exited and reloaded FP-BAM!
Exiting a table and Starting another table:
- when you exit a table, you must close FP and reload BAM Open VR and load your next table
- you may need to press the BAM HOME / Reset key each time a table loads to center it
Tables:
- once you get everything running nice, I suggest trying SLAM’s Ultimate Pro tables, and my PinEvent updated tables, as they are set for proper lighting and look really good in VR! There are many older tables that do look amazing (polygame, blindmankind,etc)
- Star Wars DSA: Epic Space Battles looks particularly cool if I do say so myself (but it’s VERY demanding and needs a FAST computer and gpu to run smooth)
- older tables should run really well. If needed they can be set to FP Original in BAM settings for it’s renderer to run much better, and use Default Preset for Lighting
- New Tables (Ultimate Pro, PinEvent, etc) MUST use New Renderer, or they will look like ass!
PinEvent PuP-Packs and PUP Stream:
- 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! If the table doesn’t run well for you, then keep pup and pup stream disabled!
Once you are all setup… then running the tables is pretty normal.
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!
BAM OpenVR FAQ
I run the table from BAM-OpenVR\FPLoader.exe, and it loads and runs. I see the VR options in the BAM menu on the FP window, bit it’s not displaying in VR…
- make sure that the Mode is set to “OpenVR” and not one of the other options like Static CAM, HappyCab, etc
- make sure in the Addons menu that “Force Arcade Mode” is ON
- you may need to exit and restart FP after making these changes
I think it’s running and working in VR but I can’t see the table…
- try looking around
- try BAM’s “HOME” key to Reset View
- try ~ or Q to bring up the BAM menu
- you may need to choose Reset View in your VR headset
Attachments
Last edited: