BAM FP Future Pinball - BAM OpenVR on Meta (Oculus) Quest 1/2 and Rift / Rift S

Future Pinball

TerryRed

Pinball Master
Future Pinball-BAM OpenVR on Meta (Oculus) Quest 1/2, and Rift / Rift S

1653862409213.png


This page is dedicated to try to get FP-Bam OpenVR working on Meta (Oculus) Quest 1/2. We'll talk about using Oculus Link, Air Link and the Virtual Desktop wireless solutions.

Much of what is on this page also applies to Rift and Rift S users as well. Ignore the Wireless / Link sections, but apply the rest of the settings you see.

For other headsets such as the Vive and Index, I don't cover any SteamVR settings (I don't have one of these headsets), but the other settings should still apply to you.





I assume you are already familiar with VR as well as Future Pinball and BAM.

Nothing on this page is set in stone! Windows updates, VR hardware, GPU drivers, Steam VR, Oculus desktop app, etc change regularly which can have an effect on required settings... as does your PCs hardware.

What I'm posting here is based on my own experiences. Yours may vary.





Examples of FP-BAM in VR can be seen in these videos:







Last Guide update: May 30 - 2022

No more stuttering head movement!


The latest BAM Open VR (1.5-346 or higher) has fixed the awkward head stutter and table movement that we've been seeing for quite a while.





===== BAM OpenVR Intro =====

So far in testing (with BAM OpenVR 1.5-346 or higher), as long as BAM / Steam / Quest / Oculus / VD / Link (whatever you use) is setup correctly... most everything runs great as long as your PC is fast enough to handle it well. I cannot emphasis that last part enough.

VR is MUCH more demanding than normal desktop / cabinet gameplay.

You need a "fast" PC to handle "all tables" at good fps / Hz / ss and run them properly.

When I talk about running "correct" and "good" and "proper"... I am referring to "minimum" fps and constant "smooth" VR gameplay. The ideal target is a minimum of 60 fps "in VR" at all times when using Virtual Desktop's 60Hz option, which is what I recommend everyone start with, as FP tends to run best at that (and 60Hz requires less CPU / GPU). If you are trying to run at 80Hz, you need minimum 80 fps, etc. Keep in mind though... you basically need "twice" that fps in normal desktop mode, as VR is in 3D so you are rendering double the normal amount.

Older tables are less demanding, but newer BAM based tables... especially my own PinEvent releases like Star Wars DSA or Sonic Pinball Mania require a faster PC to run smoothly. If you enable PinEvent PUPDMD / PUP Stream, then you need an even faster PC.

SLAMT1LT's Ultimate Pro tables are great examples to start with and get a good idea of how things can run. Blade Runner, Indy Stern, Aliens Legacy (with BAM's Post Processing set to 1.00) looks amazing in VR. I have a temporary Mega link to his Ultimate Pro tables (currently not on his site) in my most current FP and BAM Mega Guide.

So I highly recommend starting with less demanding tables first (and PUP Stream and PUPDMD disabled. for PinEvent tables) Once things seem to be running well and "proper", then try newer more demanding tables.





===== Future Pinball and BAM Mega Guide =====

For information on Future Pinball and BAM (not VR specific) consult my Mega Guide for the latest info.






===== REQUIREMENTS =====

Future Pinball and BAM installed and setup. You can get the 2 in 1 installer at ravarcade's site


Latest version of BAM OpenVR installed in the Future Pinball folder (some tables need the newest version)


ALL Visual C++ updates are needed for BAM to work correctly! Install them and reboot afterward. Use an easy all in one installer at this link:


4 GB patch may be needed for some tables to work. You can apply this after FP and BAM are installed and updated. More info here:


AntiVurus / Defender "might" need an exception added for the Future Pinball folder to allow BAM and the 4GB patch to work correctly! FP / BAM / 4 GB patch are all safe to use!

Other things needed:
  • AC1200 5GHz (or faster) router if using Virtual Desktop wireless or Air Link (ideally with your PC connected to the router with a network cable, not using a wireless connection)
  • Link cable if using Oculus Link (I use a cheap 20 ft USB C to USB B cable)
  • a fairly fast PC with a good video card (GPU) that can handle high quality VR games and apps




===== Future Pinball settings =====


1653835075338.png


1653838004414.png



The above FP settings are what you need to use. If you have a multiscreen cabinet, then you would enable and setup the backbox resolution / monitor as required. The items circled in green can be changed if needed.
  • keep reflections off until you have all tables running properly / smooth. You need a fast PC for these options in VR
  • the resolution isn't going to affect the VR resolution in-game (that is handled on the VR end)
  • keep it set to Full Screen so FP stays in focus (especially when opening the BAM menu!)
  • texture compression may help with video cards that have lower VRAM
  • trilinear filtering can help the table look nicer, but it makes some tables take a VERY long time to load
  • keep all other settings the same, as its required for all tables to run properly!
VSync OFF is needed if you are trying to use 72Hz, 80Hz, 90Hz, 120Hz, as enabling Vsync will lock FP into whatever Hz your monitor uses, and won't allow FP in VR to run at the higher Hz (and higher fps). So if your monitor only runs at 60Hz (most TVs and monitors), then enabling vsync will never allow FP to run higher than 60 fps in VR (so it will never reach 72, 80, 90, 120Hz).

If you are only using 60Hz (and your monitor runs at 60Hz), then you can try to enable vsync to see if it helps with performance and stability.

Remember.... the higher the Hz you set for VR settings, the faster your PC needs to be to keep smooth gameplay / fps at that Hz!





Set FPLoader.exe (BAM) in BAM-OpenVR folder to Windows 8 compatibility
  • this is needed to prevent FP from crashing (required because of Win 10/11 updates)
  • you "may" also need to run FPLoader.exe as Administrator "one time" to create BAM's cfg files (not normally needed). After that set FPLoader back to not run as Administrator

1653958406676.png






===== nVidia Driver settings =====
  • use the settings in the pics below for FP
  • when you have everything running really nice, you can always come back here and increase the transparent AA if your system can handle it (I wouldn't go higher than 4). This setting may improve the jaggies on things like wire ramps and certain transparent items (depending on other settings and options used).... but it needs a fast PC.
1653840064912.png


1653840119597.png







===== Virtual Desktop (VD) wireless =====

I had the best overall success using Virtual Desktop wireless app on the Quest 2.

Virtual Desktop for Quest:
  • buy Virtual Desktop (VD) for Quest (not the Rift Store version!)
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 DLL! It won't work with Virtual Desktop wireless and will cause FP-BAM to crash!

****** Settings *******

Steam VR:

  • set resolution to auto-change (to allow VD to change the resolution settings as needed)
  • no super sampling / AA, smoothing, etc

Virtual Desktop Streamer app settings:

1653841376443.png



Virtual Desktop settings:
  • start using Streaming Settings at Mid, or whatever matches your hardware. This setting is what will change Steam VR's settings for resolution, etc. You can try a higher setting later (after everything is running smooth) if your PC can handle it
  • start with 60 fps (Hz). Once you have everything running smooth, then you can come back and try a higher fps if your PC can handle it
  • the Bitrate should be enough to handle the fps / resolution you are using. I usually use around 100 for Streaming
  • sharpening should be set to a higher value
  • you can enable the performance overlay to show what your fps is running at and other helpful stats. You want FP-BAM to match your Streamer settings while playing at all times. So if set to 60fps in settings, your overlay should show 60.... if set to 80 fps, then it should show 80, etc.

VirtualDesktop settings 1.jpg



VirtualDesktop settings 2.jpg







===== Oculus Link and Air Link =====

If you can get Link to work well, it can be more solid and stable compared to a wireless option, and you can change the resolution to a higher setting (supersampling) and increase BAM's AA to make the table look much crisper and much nicer! (similar to VD wireless VR Settings).

Not used:
  • SteamVR is completely bypassed if you use Open composite DLL with BAM OpenVR

Install the Open Composite DLL and ini into the "BAM-OpenVR \ plug-ins" folder
  • I have attached the "Open Composite DLL.zip" (at the bottom of this post)
  • extract the DLL file and ini file from the zip into the BAM Open VR plugins folder
  • overwrite the DLL file already in there (back it up first if you want)

Oculus Desktop App
  • be sure your Quest 2 has good and fast USB 3.0 connectivity if using Link cable
  • you can set the resolution and Hz (72 / 80 / 90) in the device settings
  • the higher the Hz and resolution… the faster your PC needs to be
  • start at resolution 1.0 and 72Hz. You can always come back and go higher if your system can handle it.

Oculus Tray Tool

This is used to change settings for Oculus PC VR without dealing with the Oculus Debug Tool. It can be found here:


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 too slow for the table, etc)

Using Link and Air Link with Open Composite DLL and Oculus desktop app (Rift app) gave mostly similar results to VD wireless (and you don't deal with SteamVR), but sometimes could be a bit less in fps depending on the table.


SteamVR and it's "VR Server" process MUST be completely closed if using Open Composite DLL and Link!
  • to be sure there is no confusion or conflict, make sure that SteamVR and it's VR Server is NOT running when using Open Composite DLL
  • if left running they WILL cause problems and may cause stuttering head movement and gameplay!
  • to be sure of this, use Task Manager to close the "VR Server" process, or you can use the command: taskkill /f /im "VRServer.exe"
  • after this you should NOT see SteamVR startup or show up when running BAM OpenVR (when using Open Composite DLL only). If you do see SteamVR, then something is not setup right
  • another indicator that SteamVR is still running in the background or going to cause a problem... is when using Oculus desktop to run FPLoader and load a table, you should be seeing the FP progress screen as the table loads. If you do not see this and only see a black screen or you see a yellow circle with an exclamation mark, then chances are either SteamVR is still running or going to cause a problem with Open Composite
  • I have attached a file named "Kill VR Server.zip". In that zip there is a BAT file that (when run) will make sure that SteamVR and VR Server are closed completely. Run this BAT file before running FPLoader.exe. (it uses the command: taskkill /f /im "VRServer.exe"). To be sure it worked, open Task Manager and check to see if VR Server is still running at all.

Open Composite head movement may feel a bit "odd" for some people
  • I can get silky smooth head movement and gameplay with Open Composite, but I do find that no matter what I do, it has a bit of a delayed head movement compared to Virtual Desktop
  • you MUST adjust BAM OpenVR's Latency settings to help reduce this (read more below in BAM OpenVR settings)
  • when I use Virtual Desktop wireless... I don't get this delay at all (but I still need to adjust the Latency in BAM menu to get that)

SteamVR with Link

Using Link and Air Link with Steam VR was more of a pain (for me at least), so I didn't bother to test much with that. So I can't say if it works well yet. It may work better for you (and may not have the "odd" head movement delay)





===== BAM OpenVR =====

Download the latest BAM OpenVR from ravarcade's site. I recommend getting the zip file instead of the installer. Be sure the zip file is not blocked by Windows before extracting files.


Do a clean install of the latest BAM-Open VR into the Future Pinball folder. Do NOT mix it with normal BAM folder. This uses separate settings / cfg files than the normal BAM folder. You may want to start with no BAM CFG files so that your tables will all start with the same default settings (that you will create below).

When updating BAM in the future, you will update both the BAM folder (normal BAM) and the BAM OpenVR folder (for VR only).


1653855432558.png



Running BAM Open VR
  • run FPLoader.exe from the BAM-OpenVR folder (from your Virtual Desktop or Oculus Desktop in VR)
  • start with a simple table, or the New Table
  • once the table is loaded and starts in VR, you'll probably see the table below you
  • bring up the BAM menu with Q or ~
  • if you get a grey screen once in VR or when trying to open BAM menu (this is a VR headset model obscuring your view)...try exiting the table, close FP and try again

****** BAM VR settings ******

These are the settings I use. It's important to "first" apply "all" the settings below, then exit the BAM menu, then exit the table and close FP completely in order for the settings to be applied completely. After this, reload the table again, and make any adjustments if needed.

The Main VR settings
  • the HOME key re-centers your view. By default this is F12 (you can change it in BAM menu). you may need to use this each time you start a table, so make it something that is easy to activate while in VR!
  • 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 stutter. This setting combined with your GPU's Transparent AA settings make all the difference in FP looking crisp and nice... but it also can be a heavy hitter on fps for some tables!
  • Start Cam Position is what you adjust for a default position and height for yourself

Frame Latency is VERY important! It will sync up your head movement with the game. By default it may have a delay for you, and feel a bit odd. Each person is different. Try each value for yourself until you find the one that has no delay and feels good for you


BAM VR settings 1.jpg


Free Cam settings
  • this is very handy to allow you to move your position around in real-time easily using your gamepad and buttons or keys
BAM VR settings 2.jpg



Addons settings
  • these settings are very important to get right
  • you will need to set them, exit the bam menu, exit the table and close FP and reload before they are fully applied

BAM VR settings 3.jpg



Table and Lighting
  • here you can adjust the angle / size / position of the table itself
  • this can be handy if you like to play seated in a comfy chair and don't want to look down all the time

BAM VR settings 4.jpg



Lights
  • this is where you can make adjustments to the overall "basic" lighting of the table
  • for "older" FP tables, they are normally set to "Default" preset, but you can try Darker preset settings and see if they look better in VR.
  • for "older" FP tables, you can also try changing the "Light System" to "FP Original" if needed for better fps
  • for newer BAM based tables, you can try changing the lighting preset to Darker settings, and in many cases they may look much better. Keep in mind the table may override these settings on startup or during gameplay (as set from the code in the table's script)
  • for newer BAM based tables... NEVER change the "Light System" to "FP Original". This MUST be set to New Renderer for all the lighting and rendering to look proper and work correctly!

BAM VR settings 5.jpg



Post Processing
  • for "older" FP tables, you would typically leave these settings at default. If in doubt, you can choose Reset to Default. You can try changing the "Light System" to "FP Original" for better fps if needed
  • for newer BAM based tables, you can try changing Src Gamma to a lower value, and it may look better in VR. The "Light System" MUST be set to New Renderer for these tables!

BAM VR settings 6.jpg



BAM Menu Preferences
  • you can change where the BAM menu appears. It can be in front of you when press the menu button (DEFAULT), or it can appear to the left or right of you (what it normally is set to)

BAM VR settings 8.jpg



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

BAM VR settings 7.jpg







BAM Ray Cast Ball Shadows
  • this feature is very demanding and needs a fast GPU
  • this feature may not look good on all tables (it depends on how the table was created)
  • this feature requires that New Renderer is set for "Light System"
  • all of my newer releases and PinEvent V2 tables are designed to properly use this feature




Table / Ball / Head Movement is not Smooth?

Note: that the tables may not seem smooth until AFTER you "first" have all these settings "correct", and they won't all apply correctly until you've exited the BAM menu, exit the table, closed FP, closed / killed the VR Server process from SteamVR and reloaded BAM OpenVR!

Once you have things working well enough at lower settings, then you can work your way up from there for things like AA and SS, etc.





Exiting a table and Starting another table:
  • to avoid lots of problems, I HIGHLY recommend you completely close FP EVERY TIME you exit a table, or want to reload the same table. FP needs to start "fresh" every time
  • I HIGHLY recommend you completely close Steam VR and it's "VR Service" process every time you exit a table, or want to load a new table. (Sometimes Steam VR gets glitchy, or won't close itself properly). The best way to do this to "be sure" its closed is to use Task Manager to close out the Steam "VR Server" process, or you can use a BAT file and use a taskkill command to do this (like if running from a front-end which can do this for you easily).
  • I have attached a file named "Kill VR Server.zip". In that zip there is a BAT file that (when run) will make sure that SteamVR and VR Server are closed completely. Run this BAT file before running FPLoader.exe to be sure (it uses the command: taskkill /f /im "VRServer.exe")
  • I've ran Popper in VR to easily launch FP VR tables "in VR", and I had Popper "taskkill VR Server" on it's Close Script each time I exited a FP VR table. Steam VR will automatically start again when a new FP VR table is launched
  • you may need to press the BAM HOME key (Reset View) each time a table loads to center it!




FOCUS ISSUES
  • sometimes, depending on your system, once FP starts in VR, it "may" be out of focus, and you won't either see FP in VR yet, or your controls may not respond until FP is in focus
  • you may need to "click" into the FP window to bring it back into focus. At that point your controls should start working. When using VD wireless.... sometimes you need to bring up the VD menu, and choose "Switch to VR"
  • some tables have lots of BAM models / assets to process once the table is completely loaded and ready to start. This will cause the table to seem to not respond in VR until this is done. Be patient, and wait for any BAM yellow text messages (visible on the PC only) to be done and go away before expecting the table to appear in VR.




Performance Overlays
  • (VD) Virtual Desktop Wireless has an option in its menu to show a Performance Overlay while in VR. This is VERY handy to show you what your fps and other important info is. So for example, if you are running in 60Hz, you should be getting 60fps at all times to get a good VR experience. If running in 80Hz, you should be getting 80fps at all times, etc.
  • Oculus has a similar option that can be enabled using the Oculus Debug Tool, or you can also enable this with the Oculus Tray Tool as well if you have that installed.





Tables:
  • I suggest trying SLAM's Ultimate Pro tables, my own table releases and PinEvent updated tables, releases from GeorgeH / Gimli / wild / AnonTet and other more recent releases which tend to be set for more proper lighting and look really good in VR!
  • older tables should run really well. If needed they can be set to FP Original for it's "Light System" which will help with fps
  • New BAM based tables (Ultimate Pro, PinEvent, etc) MUST use New Renderer, or they will look like ass!
  • there are many other great FP tables that also look great in VR!

PinEvent PuP-Packs and PUP Stream:
  • DO NOT enable pup-packs or Pup Stream until you have all tables working and looking good! You need a faster PC to handle the extra demand for the videos and the streaming features it uses





===== Table Test Results =====

I had 3 PCs to test with in my house with my Quest 2 using Virtual Desktop Wireless, Link and Air Link.

"Lower end PC" : CPU = i5 4670K, 16GB DDR3, GPU = GTX 1080
"Mid Range PC" : CPU = i5 9600K, 16GB DDR4, GPU = GTX 1080
"High End PC" : CPU = i7 11700K, 32GB DDR4, GPU = RTX 3080

Perfect = smooth VR with max intended fps for the Hz being run. No stutter. Excellent VR experience.
Good = smooth most of the time, but not always staying at intended fps. Good, but not perfect VR experience.
Bad = stuttering and not smooth. Not a good VR experience.

These results were using Virtual Desktop wireless set to MID and 60Hz

"Lower end PC" Results:

Star Wars DSA - Epic Space Battles = Bad
Sonic Pinball Mania = Good
Silent Hill (wip) = Good
RetroFlair 2 (wip) = Bad
Junkyard Cats BAM = Perfect
BvP BAM = Perfect
Aliens Legacy Ultimate Pro = Perfect
Blade Runner Ultimate Pro = Perfect
F14 Tomcat Ultimate Pro - PinEvent = Bad
Jaws Ultimate Pro - PinEvent = Perfect
Halloween Ultimate Pro - Big Bloody Mike = Perfect
Indy Stern Ultimate Pro = Perfect
Jurassic Park Ultimate Pro = Perfect
Robocop Ultimate Pro = Perfect
Star Trek Ultimate Pro = Good
Strikes and Spares Ultimate Pro = Perfect


"Mid Range PC" Results
  • all tables were mostly "Perfect" except for RetroFlair 2 which still struggled on the Light Cycles
  • running some tables at 80Hz or 90Hz made them struggle , but most were at least Good, while many were perfect
  • some PinEvent tables with PinEvent PUP Stream enabled ran Perfect, but some struggled a bit and were mostly Good

"High End PC" Results
  • all tables (with or without PinEvent PUP Stream enabled) were mostly "Perfect" except for RetroFlair 2 which still struggled on the Light Cycles
  • running most tables at 80Hz or 90Hz were Perfect, but enabling PUP would make some drop to Good at times




120Hz
  • while I was able to get this working with Virtual Desktop / Link / Air Link, only a High End PC could even really handle it, and even then I think the connection is simply not keeping up well enough
  • as an example, Steam VR's "Home" would only give me max 110 fps with a RTX 3080.... so don't expect to be playing FP in VR with 120Hz most likely
  • the lower Hz settings look really good and smooth if your PC and connections can handle them.






How to improve visuals and get rid of the jaggies or use supersampling

This will vary depending on what you use.

Note, that a faster PC is required to maintain smooth gameplay when making any of these changes!
  • in nVidia Control Panel, increasing the Transparency AA "can" greatly improve the visuals and remove jaggies
  • for Virtual Desktop wireless, changing the Stream Settings to HIGH or ULTRA
  • in Oculus Desktop app (for Link and Air Link), increasing the Resolution is like supersampling
  • SteamVR has its own settings for increasing resolution / supersampling. These may or may not work well depending on what you are using.





Good luck! FP in VR is AWESOME!

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!

Just be realistic with your expectations of what your PC and other hardware may be able to handle!





===== 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, but 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 (F12 by default)
  • try ~ or Q to bring up the BAM menu
  • you may need to choose Reset View in your VR headset

I feel like there is a delay in head movement and it makes me feel a bit yucky...
  • open the BAM menu while playing, and change the Latency settings
  • everyone is different, so change this setting until you feel it works best for you

Table plays smooth, but I want to try to get rid of the jaggies
  • this will vary depending on what you use
  • Note, that a faster PC is required to maintain smooth gameplay when making any of these changes!
  • in nVidia Control Panel, increasing the Transparency AA "can" greatly improve the visuals and remove jaggies
  • for Virtual Desktop wireless, changing the Stream Settings to HIGH or ULTRA
  • in Oculus Desktop app (for Link and Air Link), increasing the Resolution is like supersampling
  • SteamVR has its own settings for increasing resolution / supersampling. These may or may not work well depending on what you are using.

I'm using Open Composite DLL with Link, and I am using all your settings and recommendations, but the head movement and gameplay is still stuttering, even on New Table...
  • it's critical that you have SteamVR and it's VR Server completely closed before running FPLoader with Open composite
  • I have attached a zip file named "Kill VR Server.zip". In that zip is a BAt file that (when run) will completely close out VR Server. To be sure it worked, open Task Manager and check to see if VR Server is still running at all.



 

Attachments

  • BAM VR settings 7.jpg
    BAM VR settings 7.jpg
    201.1 KB · Views: 19
  • Kill VR Server.zip
    200 bytes · Views: 21
  • OpenComposite DLL.zip
    319 KB · Views: 33
Last edited:

TerryRed

Pinball Master
@Gimli
@Gin
@ravarcade
@GeorgeH
@polygame
@wild

For those who are wondering.... yes the new Oculus Quest 2 is an excellent headset. Not only because its a great All in One headset (no PC required.... play games anywhere), it also has great specs (90Hz and good resolution).... but also because you can play normal PC VR games using a long USB cable (no video card needed).... or even better...use Virtual Desktop to play PC VR wirelessly!

It's also very cheap! $399 for 64GB, or $549 for 256GB (Canadian)

Quest 2 Specs:
  • Product Weight: 503g
  • Tracking: Supports 6 degrees of freedom head and hand tracking through integrated Oculus Insight technology.
  • Storage: 64GB or 256GB
  • Display Panel: Fast-switch LCD
  • Display Resolution: 1832×1920 per eye
  • Display Refresh: 90Hz
  • SoC: Qualcomm® Snapdragon™ XR2 Platform
  • Audio: Integrated speakers and microphone; also compatible with 3.5mm headphones.
  • RAM: 6GB
  • Battery Life: You can expect between 2-3 hours based on the kind of content you’re using on Quest 2; closer to 2 hours if you’re playing games and closer to 3 hours if you’re watching media.
  • Charge Time: With the provided USB-C power adapter, Quest 2 will charge to a full battery in about 2.5 hours.
  • Adjustable IPD with three settings for 58, 63 and 68mm.
  • Playspace: Stationary or Roomscale supported. Roomscale requires a minimum of 6.5feet x 6.5 feet of obstruction-free floor space.

If considering getting one, I highly recommend getting the better Elite Strap, or even better the Elite Strap with Battery (which also acts as a counter weight). The stock strap is kind of crappy... and you'll want better comfort.

Virtual Desktop for Wireless PC VR has been updated significantly... and despite there being a tiny bit of latency... I am hooked on playing my PC VR games wirelessly now and at a much better resolution!

Future Pinball BAM Open VR looks AMAZING... and on wireless it so cool!

@Gimli
@ravarcade

I remember you guys saying you play FP VR on your phones? If you were wanting a dedicated VR headset... this is the one to get (and a good wifi router). You wont regret it. The only downside is you MUST use your Facebook account to use the headset. I have no problem with this... but some do.
 
Last edited:

Gimli

Pinball Master
@Gimli
@Gin
@ravarcade
@GeorgeH
@polygame
@wild

For those who are wondering.... yes the new Oculus Quest 2 is an excellent headset. Not only because its a great All in One headset (no PC required.... play games anywhere), it also has great specs (90Hz and good resolution).... but also because you can play normal PC VR games using a long USB cable (no video card needed).... or even better...use Virtual Desktop to play PC VR wirelessly!

It's also very cheap! $399 for 64GB, or $549 for 256GB (Canadian)

Quest 2 Specs:
  • Product Weight: 503g
  • Tracking: Supports 6 degrees of freedom head and hand tracking through integrated Oculus Insight technology.
  • Storage: 64GB or 256GB
  • Display Panel: Fast-switch LCD
  • Display Resolution: 1832×1920 per eye
  • Display Refresh: 90Hz
  • SoC: Qualcomm® Snapdragon™ XR2 Platform
  • Audio: Integrated speakers and microphone; also compatible with 3.5mm headphones.
  • RAM: 6GB
  • Battery Life: You can expect between 2-3 hours based on the kind of content you’re using on Quest 2; closer to 2 hours if you’re playing games and closer to 3 hours if you’re watching media.
  • Charge Time: With the provided USB-C power adapter, Quest 2 will charge to a full battery in about 2.5 hours.
  • Adjustable IPD with three settings for 58, 63 and 68mm.
  • Playspace: Stationary or Roomscale supported. Roomscale requires a minimum of 6.5feet x 6.5 feet of obstruction-free floor space.

If considering getting one, I highly recommend getting the better Elite Strap, or even better the Elite Strap with Battery (which also acts as a counter weight). The stock strap is kind of crappy... and you'll want better comfort.

Virtual Desktop for Wireless PC VR has been updated significantly... and despite there being a tiny bit of latency... I am hooked on playing my PC VR games wirelessly now and at a much better resolution!

Future Pinball BAM Open VR looks AMAZING... and on wireless it so cool!

@Gimli
@ravarcade

I remember you guys saying you play FP VR on your phones? If you were wanting a dedicated VR headset... this is the one to get (and a good wifi router). You wont regret it. The only downside is you MUST use your Facebook account to use the headset. I have no problem with this... but some do.
Have you tried it with BAM Terry ?
 

Famine

Pinball Nudger
TerryRed,

Firstly, thank you for your numerous posts and guides regarding setup of FP, BAM, and OpenVR.

I'm running BAM-OVR on Steam VR through a wired Quest 2 on a PC with the following specs:
Windows 10
16 Gb ram
i7-9750
Nvidia RTX 2070

I've had some troubleshooting items that I have worked through that I thought you might want to see alternative solutions to as well.

In your post here: https://vpinball.com/forums/topic/future-pinball-and-bam-mega-guide-by-terryred/page/2/

You mention the possibility of experiencing a grey screen when trying to access the in game menu "Q or ~". I've been able to get past this by actually starting a game on the table, and then pressing the menu key. Restarting the table and FP does not solve this on my setup.

I did also experience the juttering issues you describe above, (which is what got me to this forum) however I don't think it has to do with the display or PC limitations. This appears to be a device tracking issue. Display works fine if I hold completely still, however the moment my head has to move, the screen bounces quite a bit. It's like the sensitivity is turned up to 100 and its predicting that the headset is still moving. I've confirmed that this occurs on the PC display as well.

Any thoughts on how to turn the tracking sensitivity down?
 

TerryRed

Pinball Master
@Famine

 

Famine

Pinball Nudger
So, that didn't work. doesn't seem to be related to eye sync. Now I'm working on getting a video capture in game... wondering if this is just default behavior and I'm just overly sensitive to the movement.
 

Gimli

Pinball Master
So, that didn't work. doesn't seem to be related to eye sync. Now I'm working on getting a video capture in game... wondering if this is just default behavior and I'm just overly sensitive to the movement.
It may be just my system but I have noticed the jitters arent present in freshly installed bam directories...so one of the config files that bam creates with gameplay is the culprate.

So I backupped a jitterfree version of bam and use that to restore my active bam folder once the jitters set in
 

Famine

Pinball Nudger
Thanks @Gimli. I'll try a reinstall then. unfortunately this was mostly a fresh install. Only changes were TerryRed's custom configs. I also tried VPX to see if I'm getting a similar playback issue on that program, but can't seem to get SteamVR to accept it... Fun times!
 

Gimli

Pinball Master
If you start with fresh bam folder...I tend to use the bam.zip that has a BAM folder and NOT the BAM install progam....start by playing the fp dummy"new table' first. do not copy any cfg files.

This will give you the simplist setup with no added complications.

See if you get jitter....

Once I am happy with that then I gradually add stuff and save and make a complete copy the current working BAM folder.
 

michel757

Pinball Wizard
Hello,

Really, well done everyone for your great work ....
Sorry for my English, but I only speak the language of the frog eaters.


Since the BAM_v1.5-318 version of 'BAM' in 'vr' with my Quest2 in wifi or link, the image is not stable, it moves a lot as soon as we follow the head.
With Fpsvr, since this version we notice that the cpu frames are in the red at more than 300.
I did a test with a Rifts, the cpu frames are still important but visually we do not feel this phenomenon

This ties in with what Famine said in another post
 

Gimli

Pinball Master
Hello,

Really, well done everyone for your great work ....
Sorry for my English, but I only speak the language of the frog eaters.


Since the BAM_v1.5-318 version of 'BAM' in 'vr' with my Quest2 in wifi or link, the image is not stable, it moves a lot as soon as we follow the head.
With Fpsvr, since this version we notice that the cpu frames are in the red at more than 300.
I did a test with a Rifts, the cpu frames are still important but visually we do not feel this phenomenon

This ties in with what Famine said in another post

see my post above yours...
 
Last edited:

Gimli

Pinball Master
Gimli,


Thank you for your reply ,I had read your post yet ...
I will redo a clean installation
It seems to be one of the BAM cfg or dat parameters that suddenly causes the shaking.
When you tweak a parameter in BAM menu or use a table developers BAM cfg file there are some things in the BAM folder that get updated. I haven't bothered to figure out which parameter is the culprit.
If you still have the problem I will try to provide a copy of my BAM folder that I am currently using that hasn't been corrupted yet :)
 

michel757

Pinball Wizard
Thank you very much for your answer.

To no longer have this jitter problem, I just need to replace 'BAM.DLL' with version 'v.1.5-317'.

What is strange

It would be super nice if you could send me your configuration
 

Gimli

Pinball Master
Thank you very much for your answer.

To no longer have this jitter problem, I just need to replace 'BAM.DLL' with version 'v.1.5-317'.

What is strange

It would be super nice if you could send me your configuration
I think rav tweaked something in the Bam.Dll recently to help the ball rolling look better in VR , maybe that is the problem

thanks for the feedback
 

michel757

Pinball Wizard
hello Gimli,

I will follow your instruction to rebuild A Fresh Bam folder.
I will tell you, if that solved my problem
This phenomenon is already present in version 'BAM_v1.5-318'

thank you
 

Gimli

Pinball Master
hello Gimli,

I will follow your instruction to rebuild A Fresh Bam folder.
I will tell you, if that solved my problem
This phenomenon is already present in version 'BAM_v1.5-318'

thank you
I think you are right it is the Bam.dll that is the culprate
The jitter is less if I wear the headset tighter but I don't think that should be the fix
 

Gimli

Pinball Master
hello Gimli,

I will follow your instruction to rebuild A Fresh Bam folder.
I will tell you, if that solved my problem
This phenomenon is already present in version 'BAM_v1.5-318'

thank you
@ravarcade

Ok I tested Bam.dlls and the last one that works without jitter on my oculus quest 2 is version 315
 

Attachments

  • BAM_v1.5-315.zip
    27.3 MB · Views: 406

AnonTet

Pinball Master
Site Supporters
Hey guys, i'm trying to setup my rig again after a longer absence than I antecipated. As i'm back to VR as well, now with a Valve Index, it has been awesome and smooth at 90Hz (higher really is unnecessary).

I do have a problem though and i'm wondering if you all are also affected and if able to be improved upon, could help with the jitter. Basically, I can't explain the high CPU frame times while the CPU is only at 60% and GPU could have another headset connected to it :)

My rig is a 8600k@5GHz with 16GB RAM DDR4 @2400Mhz CL15 and a MSI gtx1080 at default factory speeds (it is factory OC though).

I'm using BAM 327 but 315 makes no difference either to me.

I've played BAM VR before on lower spec'ed rig with an MSI GTX1050Ti that's not even VR Ready and I don't recall this issue. Granted it was with a VIVE not an Index but it still had to maintain 90FPS.

So, question, are you all also experiencing high CPU frame times when the CPU is far fom 100%? If so, lowering settings or super sampling helps with the jitter? I don't seem suffer from jitter but frame times are frame times and still indicate something is not quite right in this case.

Anyone tried some windows settings like power management and c states disabling... anything you might have found that helped even if only a bit. Example, having vsync helps reducing the CPU frametime for me although I can't correlate this with CPU.

cheers.
/edit
Forgot to mention, i've played other vr games and the high cpu times don't exist. just in BAM VR.
 
Last edited:

Gimli

Pinball Master
Hey guys, i'm trying to setup my rig again after a longer absence than I antecipated. As i'm back to VR as well, now with a Valve Index, it has been awesome and smooth at 90Hz (higher really is unnecessary).

I do have a problem though and i'm wondering if you all are also affected and if able to be improved upon, could help with the jitter. Basically, I can't explain the high CPU frame times while the CPU is only at 60% and GPU could have another headset connected to it :)

My rig is a 8600k@5GHz with 16GB RAM DDR4 @2400Mhz CL15 and a MSI gtx1080 at default factory speeds (it is factory OC though).

I'm using BAM 327 but 315 makes no difference either to me.

I've played BAM VR before on lower spec'ed rig with an MSI GTX1050Ti that's not even VR Ready and I don't recall this issue. Granted it was with a VIVE not an Index but it still had to maintain 90FPS.

So, question, are you all also experiencing high CPU frame times when the CPU is far fom 100%? If so, lowering settings or super sampling helps with the jitter? I don't seem suffer from jitter but frame times are frame times and still indicate something is not quite right in this case.

Anyone tried some windows settings like power management and c states disabling... anything you might have found that helped even if only a bit. Example, having vsync helps reducing the CPU frametime for me although I can't correlate this with CPU.

cheers.
/edit
Forgot to mention, i've played other vr games and the high cpu times don't exist. just in BAM VR.
Welcome back AnonTet.
I am using Quest2 with virtual desktop so I can 't really comment on your system but Terry likely could as he has used other setups tethered and untethered
 

AnonTet

Pinball Master
Site Supporters
Thanks @Gimli.

The problem doesn't affect the game visually for me but seems to affect the physics. If the Quest2 had the same problem of high CPU frame time I though it could be connected albeit affecting in different ways our headsets.

Anyway, i'll keep trying on my side and post if I find something, just in case it can help with Quest2.
 
General chit-chat
Help Users
  • No one is chatting at the moment.
  • @ freebird1963:
    *** ******* ** *** **** **** ** **** ** **** *** *** **** * * ***** *** *** ***** ** ******** ***** **
    Quote
  • Chat Bot Mibs:
    ***** *************** *** ****** *** *****
  • (Guest) fuckedupthemath:
    ****
    Quote
  • (Guest) fuckedupthemath:
    ****
    Quote
  • (Guest) fuckedupthemath:
    *****
    Quote
  • (Guest) fuckedupthemath:
    ***********************************
    Quote
  • Chat Bot Mibs:
    ***** **** *** ****** *** *****
  • (Guest) test:
    **
    Quote
    (Guest) test: **
    Top