Video settings

[Frankwurst]

I tried to tweak my video settings, but cannot get rid of horrible pixelation.
Moving objects like flippers and naturally the ball look really terrible (like pixel ball on the Doom table). Which settings should I got for?

[Powaplaya27]

What resolution are you playing in? Try 1440p for a start

[Junker-2047-]

Are you using a scaling method such as Intel XeSS, Nvidia DLSS, or AMD FSR?

These will make your image look pretty bad in order to maintain adequate FPS. Unfortunately the game is so poorly optimized that, if you disable these scaling methods, your FPS will tank at higher resolutions and you will be left with Stutterball FX.

[Frankwurst]

Thanks for the replies. My standard resolution is 1080p. I tried different settings with scaling method (have a GTX 10060), without any good balance of results (I'm noobish with fine tuning anyway).
Trying to like FX for the new William tables, but I think I will simply stick to FX3 for a little bit longer.

[C²C^Guyver |NZB|]

I am also running 1080p and everything looks fine. However, my graphics card is a little bit newer than yours, an RTX 2060

If everything looks pixelated, the card could be dying. Is it only doing it in FX?


Junker, GTX cards do not have tensor cores, so they do not support DLSS. As far as enabling it making the image look worse, this is not true, at least in my case. I have everything maxed and it runs fine. I do have vertical sync disabled as I have heard that it causes flipper lag.

[Frankwurst]

Static elements look acceptable. But when moving, the ball turns into a pack of pixels and scores popping up aren't very sharp for example. I'm not sure about it, but I think it was ok when FX launched on Steam (and 1 year before when I gave it a try on Epic). I didn't really tweaked the settings (and resetting to default doesn't change anything), but I will go through them again one day... (no similar problem with other games as FX3, but I'm not playing any really recent game atm).

[exe]

My GPU card is a Nvidia GeForce GTX 1080 Ti

my settings in Nvidia Control Panel, manage 3D settings, program settings with
[Steam game install directory]\steamapps\common\Pinball FX\PinballFX\Binaries\Win64\PinballFX-Win64-Shipping.exe:
Max Frame Rate = OFF
Power management mode = Optimal power
Texture filtering - Quality = Performance
Vertical Sync = OFF

program settings with [Steam game install directory]\steamapps\common\Pinball FX\PinballFX.exe don't work because this is just a loader for the real game exe file above

in-game VIDEO settings
BASIC:
my Windowed Mode = Full Screen
my Resolution = 2560x1600
Vertical Sync = OFF
ADVANCED:
Upscaler Method = Intel XeSS (with a Nvidia RTX GPU you might want to choose Nvidia's DLSS)
Upscaler Mode = Balanced (you can try with Performance)
Antialiasing Method = TemporalAA
Antialiasing Quality = Medium (you can try with Low)
Framerate Limit = 120
Shadow Quality = Low
Motion Blur Amount = OFF
Motion Blur Quality = OFF

edit: my keyboard and mouse are both wired

[Frankwurst]

Originally posted by exe:

My GPU card is a Nvidia GeForce GTX 1080 Ti

my settings in Nvidia Control Panel, manage 3D settings, program settings with
[Steam game install directory]\steamapps\common\Pinball FX\PinballFX\Binaries\Win64\PinballFX-Win64-Shipping.exe:
Max Frame Rate = OFF
Power management mode = Optimal power
Texture filtering - Quality = Performance
Vertical Sync = OFF
,,,

Thanks a lot. I will use these as a reference.

[exe]

You can use this as a starting point. Try with these settings and experience how this works out. Ask for help if you need to.

[S.J.C. Entertainment]

Jesus this is annoying. The only way for my computer to get decent frames is to have it set to “AMD Fsr” and there’s NO way to turn off the god awful AA. It’s either the entire table is a blurry mess or all of the moving parts are. Glad to see nearly 2 years later
that Zen hasn’t fixed ♥♥♥♥.

[MikeFulton]

Probably unrelated to the OP, but I was seeing a bit of video glitching in just the last day or two, with EVERYTHING. not just FX, but an NVIDIA driver update seems to have fixed it.