Page MenuHome

Nvidia GT 430: Poor frame rate with Anti-aliasing set to single pass
Open, Needs Triage by DeveloperPublic

Description

System Information
Operating system: Void Linux
Graphics card: Galaxy Nvidia GT 430 1GB (GL 4.6 supported by driver 390.116)

Blender Version
Broken: (public download) 2.80 (sub 75) branch: master, commit date: 2019-7-29 14:47, hash f6cb5f54494e, type: Release
Worked: 2.79b

Short description of error
0.5FPS in all windows

Exact steps for others to reproduce the error
Based on the default startup or an attached .blend file (as simple as possible).
1: start Blender 2.8.0
2: configure preferences and set Anti-aliasing to single pass (disabling doesn't affect anything)
3: set texture management to GLSL
4: do whatever, even the preferences window displays at this framerate.

step 2 boosted the FPS from 1.5 to 0.5
step 3 doesn't seem to have done anything

my card can handle minor anti-aliasing, in fact I'm even using it in 2.79b at more than 50FPS with the default scene

my guess is poor frame-loop optimization, which I'm rather disappointed would make it into a release.

Details

Type
Bug

Event Timeline

Cannot reproduce here (linux, 970m, 430.26 drivers).
Seems like that driver is the last one provided for your card.
Not sure if there is anything we can do here...

Philipp Oeser (lichtwerk) renamed this task from Poor frame rate to Nvidia GT 430: Poor frame rate with Anti-aliasing set to single pass.

Not sure if there is anything we can do here...

I'm fairly certain my issue is not with my driver, or I'd likely be having issues with running anything at all
Xonotic, RedEclipse, and Minetest run just fine (above 50FPS) with the detail set fairly high.

also I can't quite agree with the issue rename, but I'll leave it
it's stated in the issue that even disabling anti-aliasing makes no change from 0.5FPS

check your frame loop for anything that might be using CPU
CPU use does spike to about 80% when I simply rotate the default scene
when idling CPU use is about 10%

in 2.79b this CPU spike doesn't happen