First off, thanks for spending your time creating this video to help others get the most out of their VP experience. You do a nice job too on the presentation and the format of the tutorial - it feels like I could be attending a formal webinar
However, there are definitely a few things in there that could / should be scrutinized and may even lead some people astray. One main thing at the moment is that “Maximum pre-rendered frames” should be set at 1, not 4 as you have in your tutorial, as the higher the level the more perceived input / video update lag will be present and will affect more delicate flipper work. This item has resurfaced and been further reinforced in the Pinball Arcade forums with the recent PC versions release and is discussed over in their forums.
Also, from the video it appears that you are on Windows 7 and at the moment / with any nVidia driver versions, FXAA does nothing and has no point in being turned on (with or without regular AA being enabled). The levels you suggest for both “Anisotropic filtering” and Antialiasing – Setting” are considerably above the range of perceivable difference within VP (much above 8X for either will only further performance drops on most systems, some more observable during in high demand alpha / lighting sequences vs. regular FPS monitoring with the "ball in launch lane" tests).
Good suggestion on the “Antialiasing – Transparency” setting to be turned off, however, I personally did not experience the issues you refer to experiencing (ball on flipper for one) with merely toggling this option. What I have seen and tested around this setting in particular was that it can improve FPS slightly yet without any apparent adverse affect any of the “transparency” aspects (alphas ramps / primitives) within VP – probably does not relate the same way for any number of reasons (DX7 aspects being a potentially good candidate).
The VP preferences as well that you suggest may not be at all about reducing ball stutter from both enabling RU and RO (although occasionally that can be table specific) and in having the alpha slider all the way to the right as it will only drop FPS and burden performance further). Often, I have seen people refer to, and use myself, the “one tick left from the middle” setting as that seems to be a sweet spot for performance combined with the lack of smoothing from higher settings. However, when editing / creating a table it’s best to work with the setting on full so the ramps do not get distorted but then also try other settings before releasing it to see how it may affect other user’s systems when the have it differently (ramps will change reasonably in there shape with this and it sometimes opens up decent graphical anomalies that might have to be dealt with in the editor to ultimately resolve in a more global way).
No disrespect intended and the effort is appreciated, but as the title of the post suggests in all this information being a “Ball Stutter Fix”, you definitely have some suggestions in your video that will actually increase it. If nothing else, the main point and purpose for me posting a response was to inform you and others at least about the Maximum pre-rendered frames and it’s impact on flipper lag. Everything else, as with anyone’s suggestions / experience should still always be confirmed on everyone’s own particular systems.
Edited by jimmyfingers, 06 November 2013 - 02:53 AM.