Jump to content



Photo
* * * * * 1 votes

Newbie Guide to VPX Performance and Ball Stutter


  • Please log in to reply
133 replies to this topic

#1 Drybonz

Drybonz

    Really bad at pinball, but having fun.

  • Members
  • PipPipPipPip
  • 1,538 posts

  • Flag: ---------

  • Favorite Pinball: Theatre of Magic

Posted 26 July 2016 - 10:06 PM

I noticed a lot of similar questions popping up on the forums about VPX performance and eliminating ball stutter.  I thought I would attempt to write a guide that would capture answers to a lot of those questions and create a central hub for related discussion.  Please note that this guide is based on my personal experience and opinions.  It is likely that other opinions will emerge when the discussion starts, and I would encourage anyone using this guide to consider the following discussions as part of the guide.

 

This Guide is aimed at achieving optimal performance in Visual Pinball 10.  There is a gap in the required computer specs for VP9 and VP10 (or VPX).  Good performance in VP9 does not mean that your computer will be able to achieve optimal performance in VPX.  Let's look at the specs you need for VPX:

 

Intel i5 processor or better

4GB ram or more

nvidia 750 graphics card (or equivalent ATI/AMD card)

 

If your computer does not meet these specs, you may still be able to physically start and play a table in VPX, but you may not be able to be able to achieve optimal performance.  If your computer does not meet these specs, you should assume that any of the following tips may not help you eliminate your performance problems and that you should first address hardware specs to do so.

 

Video Options.  The video settings are found under the "Preferences" menu in the VPX editor.  This is the first and easiest place you should check to make adjustments.  These options are global, and some of the settings can be further at the level of individual tables, which we will discuss later.

 

Video%20Options.jpg

 

1)  Make sure that, not only the resolution, but the "refresh rate" (the Hz number) matches your monitor's.

 

2)  Unless you are wanting to run desktop tables (landscape) leave this checked.

 

3)  Leave the anti-aliasing options unchecked for now.

 

4)  Leave this as "don't stretch the ball"... otherwise, your ball may sometimes look egg-shaped.

 

5)  Stereo 3D settings... leave these alone.

 

6)  Ambient occlusion has to do with shadow and lighting.  Leave this unchecked for now.  This option can cause performance issues quickly as it is resource hungry.  The graphical improvement is minimal, so you may want this to be off always if you are having any kind of performance issues.

 

7)  Ball Rendering... leave these all unchecked for now (even though I have one checked in the picture).

 

8)  Set these both to "1" for now.

 

9)  Force Anisotropic Filtering is a graphics boost at minimal cost to resources, so let's leave it on unless you are still having issues down the road.

 

10)  Desktop composition stays checked.  Please note that "Force exsclusive fullscreen mode" is the options to turn on true fullscreen mode (like you play most 3D games).  We are going to leave it off and talk more about it later.

 

11)  Maximum textures is a limiter for how much ram you are going to allow VPX to use for playing tables.  We definitely want to leave this on "unlimited" unless we run into weird issues down the road, like crashing tables.

 

12)  The elements slider we will leave all the way to the right (max) for now.

 

Our basic strategy is to turn off all the quality controls in the main video option window... leaving the element detail slider to full  and textures to unlimited (which we walked through in the detailed, numbered steps above).  These will be our default settings for each table we open.  In the next section we will open a table and "tweak" the settings so that we have optimal performance for that table.

 

Table Options.  Open a table through the file menu in the editor.  Next press the "options" button on the left and the "table options" will open on the right.  We will play test the table (play button on the left) and see how the table performs.  If we find that it has some stutter, or is not as smooth as we want it, we will close the table and adjust the "elements slider" in the table options.  Making sure to check "override global setting", so that we are using this slider for the table, and not the one we set in section 12 in the global video options, above.  Now it is trial and error.... move the element detail slider to the max setting (full right)... now test the table... you should see its a bit better... if its not completely gone... move the slider to left one tick at a time.... test until the it feels like the stutter is gone.... *(thanks to Ben Logan for suggesting this method, and HauntFreaks for the recent write-up which I basically plagiarized for the last few sentences)* 

 

After you have found the sweet spot for the slider (and this may be different on every table, depending on how demanding the table is), you can try to add in other effects in the table options to see if your system can handle them with the given table.  Add them one at a time, testing after each change, so that you know what effects are having the most impact on performance.  After you do this for a few tables, you will quickly learn what the best approximate settings are for your system and VPX.

 

Here is a picture of the VPX editor with a table open, displaying the table options bar on the right side.  I used the Embryon table by ICPJuggla as an example (because it is awesome) but it will be the same for each table.

 

Table%20Options.jpg

 

- 4x Anti-Aliasing - Removes "jagged" edges - Hi impact

- FXAA - another form of Anti-Aliasing (AA)... can be used together with 4x AA.  Less graphical and resource impact (Medium)

- AO (Ambient Occlusion)... as discussed above... minor graphical enhancement... very high resource impact.

 All of the three above settings will override the global in video options.

- Vsync - this will be -1 probably, by default.  -1 means it will use the default we set in the video options.  You can leave it or change it to 1 here also.

- Under "playfield options" you can uncheck reflect elements on playfield, or change the strength of the reflection.  You can leave these on or reduce or remove them for a very minor resource improvement, or if you just have a personal preference on how it looks.

- Under ball, you may actually gain a bit of a "perceived" performance improvement by reducing the amount/stregth of reflections of light and objects on the ball.  When the ball is moving quickly, less reflections may make it look like it is rolling more smoothly, or you may even gain an actual minor improvement.  Test it out and see what you think.  Try a setting of 0.5 or 0.3.  Zero to remove completely.

 

Those are all the settings we will be changing in the table options.  At this point your table should be pretty well optimized... however, we can discuss some other popular techniques.

 

True Fullscreen.  In section 10 of the video options, we left "force exclusive fullscreen mode" unchecked.  Now we are going to decide if we want to try it out.  Almost every 3D game you play (Call of Duty, Dark Souls, etc) offer a fullscreen video mode and that is how they are intended to be played on today's computer hardware.  They are optimized to be played this way, and you will get the best performance in fullscreen mode.

 

VPX also offers the same fullscreen mode, and you can turn it on by checking "force exclusive fullscreen mode" in the video options.  You may have steered clear of this option because of the warning "less compatible" next to the option.  In reality, the "true fullscreen" mode is commonly used and most players on the forum who try it find that there are no compatibility issues, and that it does offer a snappier performance over windowed fullscreen mode.

 

Playing in true fullscreen does take a bit of extra setup work and reading.  I'm simply going to link, here, to a useful thread on the forum that answers every question about setting it up and troubleshooting any problems that arise.       http://www.vpforums....rue +fullscreen

 

Additional Tips.  I am going to compile as many additional tips as I can in this last section.  I'm sure that, through discussion, we will come up with new tips and standards, and I will try to keep this document updated as much as possible.  Anything that you can think of adding is most welcome.

 

- In general, modern tables with more lighting effects, models, etc... are going to use more resources than older tables, such as a EM.

 

- Some users suggest, that if you are still running Windows 7, you should disable "aero" from the windows desktop to improve performance.  I do not use Windows 7 and have not tested this.

 

- Some Windows 10 users report Windows Defender as the source of their slowdown and stutter.  Turn off your Windows Defender.  Read here for related info:  http://winaero.com/b...ith-few-clicks/

 

- Backglass settings... I originally got this great tip from Allknowing, and if you have a tricky table that doesn't quite want to smooth out, this can really help with some fine tuning.  Right click on your backglass raise the numbers in the four lighting and solenoid, etc boxes by a few digits.  Just go a few at a time as you test them.  Sometimes they will be greyed out on some backglasses and this is not an option, but if you can adjust them it's worth a try.  This works best on a backglass with a lot going on (lots of lighting, moving parts, etc).

 


Edited by Drybonz, 15 September 2016 - 11:53 PM.


#2 StevOz

StevOz

    Pinball Fan

  • VIP
  • 1,721 posts
  • Location:Nirvana

  • Flag: Australia

  • Favorite Pinball: Scared Stiff



Posted 26 July 2016 - 11:11 PM

A core i5 or better is a complete falsehood, I have a 3.4 GHz core i3 haswell with a GTX660 2Mb and it runs VPX no problem at all, with almost every VP setting enabled.

 

vps_t.jpg


Edited by StevOz, 26 July 2016 - 11:24 PM.

Files I have uploaded here...

 

http://www.vpforums....ownloads&mid=34


logoshort.gif


#3 Noah Fentz

Noah Fentz

    'Rasslin' Fan

  • VPF Administrator
  • 12,271 posts
  • Location:South Lyon, MI

  • Flag: United States of America

  • Favorite Pinball: Whitewater

  • PS3 Gamer Tag: noahfentz


Contributor

Posted 26 July 2016 - 11:38 PM

A core i5 or better is a complete falsehood, I have a 3.4 GHz core i3 haswell with a GTX660 2Mb and it runs VPX no problem at all, with almost every VP setting enabled.
 
vps_t.jpg


Instead of referring to it as a 'falsehood', which to me, at least, makes it sound as if you think he's intentionally misleading people, how about suggesting that i3 works as well?

Only with comparing notes on hardware can we achieve a good suggested hardware profile.

Thanks for putting in the effort on this, Drybonz. It's a great starting point for a collaboration of successful hardware requirements.

:tup:

Sent from my SM-G930T using Tapatalk

IdleReel.gif RumbleDMD.jpg HS2-DMD.jpg SBM.jpg ww_logo.jpg EK.jpg

 
T2.jpg Sorcerer.jpg Breakshot.jpg Firepower.jpg GorGar.jpg StarTrek.jpg


My Photobucket Resources
Whether You Believe You Can, Or You Can't, You Are Right." - Henry Ford
The future of pinball lives, it just needs to be nurtured!
If you're here to stab me in the back, you're going to have to get in line.


#4 StevOz

StevOz

    Pinball Fan

  • VIP
  • 1,721 posts
  • Location:Nirvana

  • Flag: Australia

  • Favorite Pinball: Scared Stiff



Posted 26 July 2016 - 11:54 PM

Err, political correct, candy coated speech only, OK, not only does a core i3 work as well, it will save you up to $100 to spend on a better graphics card if need be...how about that. :)

 

I guess I've always been bemused by the number of posts here recommending a core i5 as minimum VP specs when I know this is not the case and are almost certain VP has fairly low CPU needs.


Edited by StevOz, 26 July 2016 - 11:58 PM.

Files I have uploaded here...

 

http://www.vpforums....ownloads&mid=34


logoshort.gif


#5 Drybonz

Drybonz

    Really bad at pinball, but having fun.

  • Members
  • PipPipPipPip
  • 1,538 posts

  • Flag: ---------

  • Favorite Pinball: Theatre of Magic

Posted 27 July 2016 - 12:04 AM

Thanks for the comments Steve... this allows me to bring up some great talking points.  I'll start by quoting myself... this comes from the very first few sentences of the OP... "Please note that this guide is based on my personal experience and opinions.  It is likely that other opinions will emerge when the discussion starts, and I would encourage anyone using this guide to consider the following discussions as part of the guide."

 

I listed an i5 because I have seen so many other people mention it before as a suggested "for optimal performance" processor.  I'm sure a lot of people are using an i3 or worse.  I'm sure people will be glad to hear it's working for you with an i3.

 

I hope that you will help contribute some useful suggestions for  performance that may help other new guys that are running an i3 as well.

 

 



#6 StevOz

StevOz

    Pinball Fan

  • VIP
  • 1,721 posts
  • Location:Nirvana

  • Flag: Australia

  • Favorite Pinball: Scared Stiff



Posted 27 July 2016 - 12:17 AM

6)  Ambient occlusion has to do with shadow and lighting.  Leave this unchecked for now.  This option can cause performance issues quickly as it is resource hungry.  The graphical improvement is minimal, so you may want this to be off always if you are having any kind of performance issues.

 

Ambient occlusion is resource hungry only when the Update in-game (quality) option is selected, selecting Enable has little to no performance hit as with this option, it is only applied to static table elements.


Edited by StevOz, 27 July 2016 - 12:18 AM.

Files I have uploaded here...

 

http://www.vpforums....ownloads&mid=34


logoshort.gif


#7 Johngreve

Johngreve

    Enthusiast

  • Platinum Supporter
  • 343 posts
  • Location:Eagle,Wisconsin

  • Flag: United States of America

  • Favorite Pinball: Star Wars TESB (sound mod),Pinball Magic,Ghostbusters,Dozers AFM,VPX table of Indiana Jones the Pinball Adventure

Posted 27 July 2016 - 12:34 PM

Thanks Drybonz

I really like this,though I'm not having any problems with VP 10 this is a nice tutorial that will let someone like myself with little or no knowledge try to help himself out. I give you an A+ for taking the initiative to put this together.
So many of those settings are a mystery to most of us, this takes some of the mystery out of it which ultimately makes it a bit easier
for someone to be willing to try some changes and see if improvements can be seen.

#8 Drybonz

Drybonz

    Really bad at pinball, but having fun.

  • Members
  • PipPipPipPip
  • 1,538 posts

  • Flag: ---------

  • Favorite Pinball: Theatre of Magic

Posted 27 July 2016 - 03:18 PM

Thanks, Johngreve... my hope is that this will benefit us guys that aren't having problems, or have already worked out our problems, by giving us something that we can easily link for new guys instead of typing out an explanation each time someone has a question about performance problems.  So, hopefully, as the discussion develops it will be useful to everyone, and save people some time as well.

 

Thanks for the comments... I appreciate it.



#9 cenutrio

cenutrio

    Neophyte

  • Members
  • Pip
  • 9 posts

  • Flag: Spain

  • Favorite Pinball: whitewater

  • 360 Gamer Tag: ATRAKAVIEJAS

Posted 01 August 2016 - 09:32 PM

thanks, i  search a similar guide .

now a have to translate ,becouse my englih is like a monkey



#10 DJRobX

DJRobX

    Pinball Fan

  • VP Dev Team
  • PipPipPipPip
  • 941 posts
  • Location:Valencia, CA

  • Flag: United States of America

  • Favorite Pinball: F14 Tomcat

Posted 03 August 2016 - 09:19 PM

I just wanted to add a couple bits of experience to this discussion.  My cab came with two video cards, a GTX 650ti and a lower end GTS 210 for the backglass display.  That GTS card destroys VP performance if a B2S backglass is updating frequently.   The solenoid/lighting polling settings don't seem to matter much.   Some B2Ses are much "heavier" than others and it rarely seems to matter how much visible activity there is.    Unfortunately, source code to B2S isn't available, so I've never been able to identify why some perform so poorly.    A workaround that I use most of the time is just to use a static backglass, which is easy since HyperPin leaves the picture up there if it exists, I assume PBX does also. 

 

Unfortunately my GTX only came with 1GB, so performance suffers in different ways on other tables if I hook the backglass up to the same card. 

 

My i3 4340 + 650ti seems to ALMOST handle VPX tables pretty well with the higher quality settings disabled.   I still get stutter around the inlane on a few tables.  I've read in a few places that this may be CPU related due to the collision detection.    

 

My new GTX 970 and i7 4790k will be here Friday.  I will hook up all 3 displays to the new card.   Hopefully this new combo will hold me for a while. 



#11 roar

roar

    Enthusiast

  • Members
  • PipPipPip
  • 462 posts

  • Flag: Canada

  • Favorite Pinball: TOM

Posted 13 August 2016 - 02:18 AM

I continue to struggle with ball stutter. Trying lots of things I've read online but I can't figure it out. Lots of horse power here, i5, 8GB RAM, GeForce 960 with 2GB RAM running on an SSD. Everything was running fine for the better part of a year and then windows update in Windows 7 started chewing resources up, I got that all sorted but couldn't fix the stuttering and lag so I blew my install away and installed Windows 10 and the lag is still there... Crazy part is the games often play fine for the first couple of minutes and then the chugging starts. I've stripped this thing down as bare bones as I can, running latest VPX and later VPinMAME and one table, a VPX version of AFM. I even unplugged my Pinscape tonight and was just using the keyboard. I'll sit down again with it and step through these directions again tomorrow... I think I just wanted to vent somewhere :)

#12 StevOz

StevOz

    Pinball Fan

  • VIP
  • 1,721 posts
  • Location:Nirvana

  • Flag: Australia

  • Favorite Pinball: Scared Stiff



Posted 13 August 2016 - 11:06 AM

roar if you are using windows defender, then be sure to exclude all VP folders from being scanned.


Files I have uploaded here...

 

http://www.vpforums....ownloads&mid=34


logoshort.gif


#13 wrd1972

wrd1972

    Authoring Padawan

  • Platinum Supporter
  • 2,265 posts
  • Location:Central KY. USA

  • Flag: United States of America

  • Favorite Pinball: Funhouse

Posted 13 August 2016 - 01:21 PM

Great post.

 

Drybonz,

Why dont you establish an "official" test table and DB2S that everybody can run to benchmark performance. I would like to see folks be able to compare results in a meaningful way. Maybe folks can offer candidates.


My VP Pincab /MAME Arcade  Specs: Dell T3400 workstation with Core2 Quad core 3.0GHZ (Q9650) CPU - 8GB of RAM - Nvidia  GTX 970

40" PF Sony gaming LED TV, Dual 21" Dell monitors in the backbox - Pinscape dual boards - Full DOF - Full MAME arcade support.


#14 Drybonz

Drybonz

    Really bad at pinball, but having fun.

  • Members
  • PipPipPipPip
  • 1,538 posts

  • Flag: ---------

  • Favorite Pinball: Theatre of Magic

Posted 13 August 2016 - 03:17 PM

Hey wrd, that is a good idea.  I would recommend Demolition Man as a very demanding table with which to benchmark (Incredibly beautiful and nicely made table by Knorr and Kiwi but pretty demanding on resources).  I'm sure there are a bunch we could come up with... that's just the one that comes to mind, to me, that if I can run it at full speed, no stutter, I can run anything else... it's also in the downloads section here at VPF, so easy for everyone to acquire.



#15 wrd1972

wrd1972

    Authoring Padawan

  • Platinum Supporter
  • 2,265 posts
  • Location:Central KY. USA

  • Flag: United States of America

  • Favorite Pinball: Funhouse

Posted 13 August 2016 - 10:58 PM

Just benchmarked DM with my setup:

98FPS with DB2S and FXAA and 4XAA disabled

72FPS with DB2S and FXAA and 4XAA maxed out

 

This is with a dinosaur Core2 Quad 3.0Ghz and a GTX760 video card. I would say that I dont have any stutter issue with any tables at all.


My VP Pincab /MAME Arcade  Specs: Dell T3400 workstation with Core2 Quad core 3.0GHZ (Q9650) CPU - 8GB of RAM - Nvidia  GTX 970

40" PF Sony gaming LED TV, Dual 21" Dell monitors in the backbox - Pinscape dual boards - Full DOF - Full MAME arcade support.


#16 viktory2k1

viktory2k1

    Autistic Genius

  • Platinum Supporter
  • 986 posts
  • Location:Waukesha Wisconsin

  • Flag: United States of America

  • Favorite Pinball: Tales of the Arabian Nights

Posted 13 August 2016 - 11:30 PM

HI, I am running an i5 4690, GTX660, MSI H81M-E33 micro-ATX mobo, 600watt PS, 240GB SSD, 8GB RAM, and running 3 monitors and I blew the extra $$ on the i5 because I was unsure of what I needed but I am running windows 10 and never saw a stutter or any type of slowdown on vp9 and VPX so I know this setup works but not sure how low is really "required". I am amazed at how many posts I see about slowdowns and ball stutter with PC's better then this. I have everything maxed out too, Maybe I will mess with settings and see if I can get a stutter or slowdown. I am pretty much just breaking into VPX so maybe there is a really demanding table we should all use and report our results. The proc is 3.5 GHz. I think and stutter or slowdown has to be software related because I have seen posts with way higher specs then mine with slowdown issues, Just my opinion.


logo.png

 

If it ain't broke, it's probably a good idea to take it apart anyway!

I just post here to hear myself type.


#17 Drybonz

Drybonz

    Really bad at pinball, but having fun.

  • Members
  • PipPipPipPip
  • 1,538 posts

  • Flag: ---------

  • Favorite Pinball: Theatre of Magic

Posted 14 August 2016 - 03:55 AM

If you guys have tips for people with better specs that are still getting stutter, that are not included in the tutorial, please share... I'm sure it will be helpful to new guys especially!  Thanks.   :)



#18 viktory2k1

viktory2k1

    Autistic Genius

  • Platinum Supporter
  • 986 posts
  • Location:Waukesha Wisconsin

  • Flag: United States of America

  • Favorite Pinball: Tales of the Arabian Nights

Posted 14 August 2016 - 06:41 AM

I really can't say I am new but I have probably less knowledge of this the a brand new member, there are alot of things I just don't get. I am getting help though. I really like the "benchmark" test table idea though.


Hey wrd, that is a good idea.  I would recommend Demolition Man as a very demanding table with which to benchmark (Incredibly beautiful and nicely made table by Knorr and Kiwi but pretty demanding on resources).  I'm sure there are a bunch we could come up with... that's just the one that comes to mind, to me, that if I can run it at full speed, no stutter, I can run anything else... it's also in the downloads section here at VPF, so easy for everyone to acquire.

Should this be the official testing table? Is it in vpx without looking? I'm in. Maybe put a link up so everyone reading this has the exact same table.


logo.png

 

If it ain't broke, it's probably a good idea to take it apart anyway!

I just post here to hear myself type.


#19 viktory2k1

viktory2k1

    Autistic Genius

  • Platinum Supporter
  • 986 posts
  • Location:Waukesha Wisconsin

  • Flag: United States of America

  • Favorite Pinball: Tales of the Arabian Nights

Posted 14 August 2016 - 06:57 AM

This one?

Demolition Man (Williams)(1994)(Knorr-Kiwi)(FS-DT)(VP10) 1.2

logo.png

 

If it ain't broke, it's probably a good idea to take it apart anyway!

I just post here to hear myself type.


#20 Drybonz

Drybonz

    Really bad at pinball, but having fun.

  • Members
  • PipPipPipPip
  • 1,538 posts

  • Flag: ---------

  • Favorite Pinball: Theatre of Magic

Posted 14 August 2016 - 07:08 AM

Yes sir.