51 replies to this topic

[htamas]

Ryzen is much better than FX. Unfortunately, my MoBo in the cabinet cannot run that. All I could upgrade to is something much more power hungry which I won't do, and it would still not excel at single-core performance that VP mostly needs. In that case, I should rather rebuild the whole system, but I'm dragging my feet, LOL. Most things run very well with what I have, save for the occasional stutter, but it's quite rare.

 

I didn't try too much troubleshooting to pinpoint what may be the reason... not quite certain what is the best tool for this. Will try to poke around.

[wiesshund]

Most you could upgrade to, would for you, actually be a downgrade
at the cost of more cooling needed, maybe more PSU depending on what you have now
only to actually run slower for things that only use 1 or 2 cores.

 

be different if pinball could sit there and leverage 6 or 8 cores

 

Not to mention, the prices on that CPU line are just silly
It costs more to buy one of those, than a ryzen that can dance circles around it and use less power.

And you still have money left for a motherboard

if nothing else, try using performance monitor built into windows

[lukpcn]

 

I finally had time to test the experimental registry hack @Thalamus mentioned at VPinball.

Hi Dkong, can You tell me the link to it ?

[kiwi]

 

 

I finally had time to test the experimental registry hack @Thalamus mentioned at VPinball.

Hi Dkong, can You tell me the link to it ?

 

Is here in post 15

[lukpcn]

 

 

 

I finally had time to test the experimental registry hack @Thalamus mentioned at VPinball.

Hi Dkong, can You tell me the link to it ?

 

Is here in post 15

 

Thanks

[BleedinFingers]

Thought I would share my experiences too being new to VPX

 

Just changed graphics card from Radeon 550 as it was struggling with a few tables to a 1050Ti (I know not the best but it should do me in the cab with 1080p and limited on power / thermals) and the improvement was disappointing.  This started my experiments with the settings

 

Started with changing to exclusive fullscreen and disabling almost all effects

 

FPS showing 130+ but visually there was tearing and the ball chopping along the table on some tables, not always the ones I would expect. Some EM tables were worse than something like Addams Family??

Setting B2S to EXE mode fixed this

 

Locking to VSync 60Hz stopped the tearing but fast moving balls were choppy as they moved aroound the table. Then I looked at my monitor which for some reason was set to 59Hz but was capable of 75

 

Changing the monitor refresh to 75Hz and setting the VPX refresh to the same frequency worked like magic, now I have turned back on pretty much all effects and all tables locked at 75Hz and playing smooth as silk that I have tested so far

 

So check your monitor settings

[goodtwist]

Thought I would share my experiences too being new to VPX

 

Just changed graphics card from Radeon 550 as it was struggling with a few tables to a 1050Ti (I know not the best but it should do me in the cab with 1080p and limited on power / thermals) and the improvement was disappointing.  This started my experiments with the settings

 

Started with changing to exclusive fullscreen and disabling almost all effects

 

FPS showing 130+ but visually there was tearing and the ball chopping along the table on some tables, not always the ones I would expect. Some EM tables were worse than something like Addams Family??

Setting B2S to EXE mode fixed this

 

Locking to VSync 60Hz stopped the tearing but fast moving balls were choppy as they moved aroound the table. Then I looked at my monitor which for some reason was set to 59Hz but was capable of 75

 

Changing the monitor refresh to 75Hz and setting the VPX refresh to the same frequency worked like magic, now I have turned back on pretty much all effects and all tables locked at 75Hz and playing smooth as silk that I have tested so far

 

So check your monitor settings

I agree. Making sure the hz and fps matched really smoothed things out for me. In my case it is a 60hz LG tv and 60fps cap set in the nvidia graphics options.

[Robsoie]

Maybe it can help someone somewhere about performance.

For a long time on some table (the one i got it most prominently was "24" ) when using VPX i had some bizarre "visual lag" when the ball was hitting some bumper.

When it happened, the video seemed to freeze for half a second but the ball was apparently still moving even if not showed as once the freeze disappeared the ball was where it should have been without the freeze.

Was very annoying to me as even when lowering every option it still happened. So i thought it was one of those VBS issue with window 10 own defender.

I also noticed that while i was halving the resolution of every textures files used, that visual lag was lowered.

 

I finally found out what was the source of the problem : "Texture Compression" , as in games that featured this option it was always a good one to improve performance, i had this enabled all the time when using VPX.

 

For some reason after testing with it disabled, no more "visual lag", even when playing the version of the table that had its texture at full size.

So in case you run into similar problem, check if you have "Texture Compression" enabled, if so disable it.

 

Interestingly i had a similar problem with  "Texture Compression" enabled  with Future Pinball , though unlike VPX it was not a visual lag, but some noticable slowdown on some busy tables.

[clyptos]

Hi all, sorry to bump an old thread, but I just wanted to thank you all for helping me solve a long standing framerate issue I was having. This seemed to affect all tables, with some far more noticeable than others, but I just realized at last week o'clock that any table I started without a backglass ran at rock solid framerate, even with settings maxed. But as soon as the backglass was enabled, framerates were all over the place. After some time trying to solve this on my own I ended up finding this thread and I'm glad I did! I had been trying to adjust graphical settings, both in VPX and my NVIDIA drivers, which made near zero difference at all to performance. What did make a difference though, and I did not know this at all, was to run all backglass in EXE mode. So, following suggestions in this thread, I ended up editing the b2stablesettings.xml file in notepad++ and did a find and replace to enable the backglass to start in exe mode flag, then saved. Holy cow that fixed everything!!! All my tables now run extremely smooth. I know this may be common knowledge to all the old schoolers here, but you'd be surprised how many people do not know to check this and instead go in circles with tweaking graphics settings in VPX etc. (Like ME! lol) Anyhow, thank you all. I hope some others in the future will also find this useful. It's one setting that has a pretty significant impact on framerate that is not really talked about much!

Cheers

[sdivodul]

@clyptos You can also try raising the "Skip ... frames" values in the b2s settings if you are still seeing some ball stutter.

[clyptos]

@clyptos You can also try raising the "Skip ... frames" values in the b2s settings if you are still seeing some ball stutter.

So far I haven't had to mess around with that but I will absolutely keep that in mind if I start having issues. Thank you!

[clyptos]

@clyptos You can also try raising the "Skip ... frames" values in the b2s settings if you are still seeing some ball stutter.

Sorry for the 800 year delay in replying to this, but I did mess around with this and it has def helped with some performance issues with some tables. Thanks!
Cheers!