33 replies to this topic

[Saybrook]

I have micro stutter on most of the more demanding tables (like VPW).  I have an Intel i5 12400 and NVIDIA RTC 3060ti.  I have a 2k 144Hz Gsync monitor and a 75Hz back glass.  Some of the micro stutter I believe is being caused by the B2S (at least tested on Earth Shaker VPW, hauntfreaks backglass).  I do not believe B2S is all of it, however.  I have tried so, so many suggestions.  I'm running VPX (64-GL) 10.8.0 2051, and B2S server 2.1.6.  Best performance is Windowed, Vsync on.  I've tried checking full screen optimization stuff, Windows Defender, NVIDIA app settings, etc.   Does anyone else have this issue?  Suggestions?

[digitalarts]

Set b2s in b2s-setting (right-click at the b2s) to "use as exe" (or similar wording...)

[Saybrook]

Set b2s in b2s-setting (right-click at the b2s) to "use as exe" (or similar wording...)

Thank you for the reply.  I have this set already.

[deadmanworking]

Might be mismatched Hz-rate did you try it without the second monitor plugged in?

Also you tried "so so many suggestions" - what exactly? 
We can hardly drop more suggestions if you might have tried them already 

[Emanoel299]

Hi

 

Open task manager. Always on top on back glass monitor.

Go to performance and see what happen whit CPU clock and GPU memory

I had a similar issue and the problem was not enough fan cooler operation.

Bootleneck happens

I fixed change the Fan cooler

Also, take a look in your power supply.

I have one system just like you for VR only and works fine. My PS is 850 W.

Edited by Emanoel299, 03 August 2026 - 10:07 PM.

[TT11]

I have a similar system to yours.  I run 1080p on a 2 screen setup.  No stutter at all on VPW, Pup packs etc.  Is there stutter when the Backglass is not loaded and you have the PF running only?  I found that happened on my DE Guns & Roses from VPW.  It was the version of Backglass I was running.  A new one fixed it......

[Saybrook]

Hi

 

Open task manager. Always on top on back glass monitor.

Go to performance and see what happen whit CPU clock and GPU memory

I had a similar issue and the problem was not enough fan cooler operation.

Bootleneck happens

I fixed change the Fan cooler

Also, take a look in your power supply.

I have one system just like you for VR only and works fine. My PS is 850 W.

This is an interesting idea!  The CPU maxed out at 17% and the GPU at 27%.  GPU memory looks OK I think.

I have a similar system to yours.  I run 1080p on a 2 screen setup.  No stutter at all on VPW, Pup packs etc.  Is there stutter when the Backglass is not loaded and you have the PF running only?  I found that happened on my DE Guns & Roses from VPW.  It was the version of Backglass I was running.  A new one fixed it......

I tried an older back glass and a newer one.  Both have stutter.  When I disable the back glass the ball is much smoother but still occasional stutter so not perfect.  I wonder if an older B2S would make a difference?

[Saybrook]

Might be mismatched Hz-rate did you try it without the second monitor plugged in?

Also you tried "so so many suggestions" - what exactly? 
We can hardly drop more suggestions if you might have tried them already 

Maybe I will try to set the playfield to match the back glass to see what happens.

[Koplings]

I had the same problem when B2S was running on a small number of newer higher end tables.  What worked for me after a lot of trial and error was to open the table editor,  make your way to the properties editor window (the window where you can adjust the night-day cycle under the "User" tab).  I changed the "FPS Limiter/VSync (-1=def)" in there from -1 to 0 for the problematic tables and the problem went away.  I have no idea why or whether that might work for you but somehow that solved the problem for me. Worth a try.

[Flying Dutchman]

Table specific:

Add the following lines to your specific ´table-name´ .ini

[Video]
DynamicFramePacing = 0
MaxFramerate = 0

Global VPX settings:
Turn these specific heavy features OFF manually. 
In VPX go to ´Preferences´ / ´Video/Graphic Options´.
Check the middle column (Performance and Troubleshooting):

- Max. Ambient Occlusion: Set this to Disable AO (turns off shadows between objects).
- Max. Reflection Mode: Set this to Disable reflection (removes heavy reflections from the playfield).
- Force Bloom Filter off: Check this box (turns off the heavy light glow).
- Elements Detail Level: Drag this slider all the way to the left (fewer unseen details in 3D objects).
- Right Column SettingsAnti-Aliasing: Turn off Anti-Aliasing. 
- Look under Anti-Aliasing for Post-processed AA and set it to Disabled (this removes jagged-edge filtering, which saves a lot of processing power).

 

Cheers,

FD.

[deadmanworking]

Table specific:

Add the following lines to your specific ´table-name´ .ini

[Video]
DynamicFramePacing = 0
MaxFramerate = 0

Global VPX settings:
Turn these specific heavy features OFF manually. 
In VPX go to ´Preferences´ / ´Video/Graphic Options´.
Check the middle column (Performance and Troubleshooting):

- Max. Ambient Occlusion: Set this to Disable AO (turns off shadows between objects).
- Max. Reflection Mode: Set this to Disable reflection (removes heavy reflections from the playfield).
- Force Bloom Filter off: Check this box (turns off the heavy light glow).
- Elements Detail Level: Drag this slider all the way to the left (fewer unseen details in 3D objects).
- Right Column SettingsAnti-Aliasing: Turn off Anti-Aliasing. 
- Look under Anti-Aliasing for Post-processed AA and set it to Disabled (this removes jagged-edge filtering, which saves a lot of processing power).

 

Cheers,

FD.

 

Good performance tips but a 3060 should be able to run the tables at 2K no problem. So instead of switching to low end graphic fidelity I'd be first looking for a different bottleneck. 
(my cab is also on 3060 12GB and runs VPWs heaviest tables on 2K at 232fps with everything set to high-end video in settings)

[Flying Dutchman]

 

Table specific:

Add the following lines to your specific ´table-name´ .ini

[Video]
DynamicFramePacing = 0
MaxFramerate = 0

Global VPX settings:
Turn these specific heavy features OFF manually. 
In VPX go to ´Preferences´ / ´Video/Graphic Options´.
Check the middle column (Performance and Troubleshooting):

- Max. Ambient Occlusion: Set this to Disable AO (turns off shadows between objects).
- Max. Reflection Mode: Set this to Disable reflection (removes heavy reflections from the playfield).
- Force Bloom Filter off: Check this box (turns off the heavy light glow).
- Elements Detail Level: Drag this slider all the way to the left (fewer unseen details in 3D objects).
- Right Column SettingsAnti-Aliasing: Turn off Anti-Aliasing. 
- Look under Anti-Aliasing for Post-processed AA and set it to Disabled (this removes jagged-edge filtering, which saves a lot of processing power).

 

Cheers,

FD.

 

Good performance tips but a 3060 should be able to run the tables at 2K no problem. So instead of switching to low end graphic fidelity I'd be first looking for a different bottleneck. 
(my cab is also on 3060 12GB and runs VPWs heaviest tables on 2K at 232fps with everything set to high-end video in settings)

 

 

I posted above not only for Saybrook´s setup but for people in general that experience stutter & flipper lag ..     

 

Cheers,

FD.

[Saybrook]

I had the same problem when B2S was running on a small number of newer higher end tables.  What worked for me after a lot of trial and error was to open the table editor,  make your way to the properties editor window (the window where you can adjust the night-day cycle under the "User" tab).  I changed the "FPS Limiter/VSync (-1=def)" in there from -1 to 0 for the problematic tables and the problem went away.  I have no idea why or whether that might work for you but somehow that solved the problem for me. Worth a try.

Thank you for the tip.  I am not able to locate what you are suggesting.  I've unlocked the table but don't see a User tab?

Thank you all for the suggestions.  I'll be away from my table for a few days but will try all these when I get back!

[Tesla]

I had the same problem when B2S was running on a small number of newer higher end tables.  What worked for me after a lot of trial and error was to open the table editor,  make your way to the properties editor window (the window where you can adjust the night-day cycle under the "User" tab).  I changed the "FPS Limiter/VSync (-1=def)" in there from -1 to 0 for the problematic tables and the problem went away.  I have no idea why or whether that might work for you but somehow that solved the problem for me. Worth a try.

 

Sounds like maybe you are still running VPX v10.7.x

 

AFAIK, in VPX v10.8.0 ... there is no User Tab on Tables themselves any more.

 

Generally, seems like those kind of options have been moved to VPX-Editor / Prefs / Video (and per Table is now done with INI files).

 

https://www.vpforums...=56351&p=549605

Edited by Tesla, 04 August 2026 - 03:57 PM.

[Emanoel299]

@saybrook

 

I am talking about the CPU clock and not CPU usage. If clock went down, you will have performance issues.

 

And the Backglassfile must have the same name of playfield if not, dependding on the table, you will run the VR backglass and not the real backglass file.

[Saybrook]

 

Table specific:

Add the following lines to your specific ´table-name´ .ini

[Video]
DynamicFramePacing = 0
MaxFramerate = 0

Global VPX settings:
Turn these specific heavy features OFF manually. 
In VPX go to ´Preferences´ / ´Video/Graphic Options´.
Check the middle column (Performance and Troubleshooting):

- Max. Ambient Occlusion: Set this to Disable AO (turns off shadows between objects).
- Max. Reflection Mode: Set this to Disable reflection (removes heavy reflections from the playfield).
- Force Bloom Filter off: Check this box (turns off the heavy light glow).
- Elements Detail Level: Drag this slider all the way to the left (fewer unseen details in 3D objects).
- Right Column SettingsAnti-Aliasing: Turn off Anti-Aliasing. 
- Look under Anti-Aliasing for Post-processed AA and set it to Disabled (this removes jagged-edge filtering, which saves a lot of processing power).

 

Cheers,

FD.

 

Good performance tips but a 3060 should be able to run the tables at 2K no problem. So instead of switching to low end graphic fidelity I'd be first looking for a different bottleneck. 
(my cab is also on 3060 12GB and runs VPWs heaviest tables on 2K at 232fps with everything set to high-end video in settings)

 

This is interesting.  I turned off Vsync and I am seeing fps in the 260's on Earthshaker.  I can't seem to run frame pacing on the GL version of VPX.  The table will run at 30-something fps.  I'm guessing there is something with the sync type, where it is set (NVIDA app or in VPX), GL vs non-GL VPX, Gsync on one monitor, etc.  Are you running VPX GL version?

[deadmanworking]

maybe you should reset Nvidia settings and go about them again. Ultra low latency, High Performance the usual stuff and then take a look at the frame pacing FAQ: 
https://docs.google....IQ/edit?tab=t.0

[Saybrook]

maybe you should reset Nvidia settings and go about them again. Ultra low latency, High Performance the usual stuff and then take a look at the frame pacing FAQ: 
https://docs.google....IQ/edit?tab=t.0

Thank you for linking.  I am trying some of the suggestions but others seem like they don't apply any more (Set your table fps limiter/v-sync settings on the default -1 else it overrides your general settings. There is a potential bug where setting it to 0 or 1 lets the frame-rate run unlimited.)

 

I am not able to run frame pacing in full screen exclusive (both GL and DX run at around 32fps). It seems to run in Windowed but still stutters. I think that might be a clue somehow?

[deadmanworking]

Important takeaway from the FAQ is setting the stage for frame pacing: 

Disable v-sync in your GPU drivers or any other user sync including your monitor's Free-/G-Sync (VPX will not use it). + use windowed, not exclusive fullscreen. 
As for GL vs DX you'll need to try both. On my cab GL is way better, on my gaming laptop DX wins out. 
+

You didn't tell us any result what happens if you unplug the backglass monitor, or what happens when you set the refresh rates in different combinations. (60/120 might be a first try)

[Saybrook]

 

Important takeaway from the FAQ is setting the stage for frame pacing: 

Disable v-sync in your GPU drivers or any other user sync including your monitor's Free-/G-Sync (VPX will not use it). + use windowed, not exclusive fullscreen. 
As for GL vs DX you'll need to try both. On my cab GL is way better, on my gaming laptop DX wins out. 
+

You didn't tell us any result what happens if you unplug the backglass monitor, or what happens when you set the refresh rates in different combinations. (60/120 might be a first try)

 

I tried disabling Vsync on the monitors but did not make a difference.  I unplugged the back glass and no difference there either.  I tried 120/75 and no luck.  I am not able to change the back glass monitor from 75Hz.  What's interesting is that when I enable the frame rate monitor (F11), I will get flashes of red while testing both the 120Hz and 144Hz playfield rates.  Given the un-synced high frame rates that my system seems to be able to achieve, not sure what is happening there.