June 17, 2015, 09:28:18 am
To add to what Peter said, the GFX Score is also affected by whatever the CPU is doing while you're running the benchmark test.
If your CPU is busy rendering in another application or the anti-virus software is scanning files in the background, the CPU will act as a bottleneck for the graphics card. The result is subpar performance and a low GFX score. The same principle applies to the frame rate in
Build mode as well as to previews in
Photo &
Movie mode.
In other words, you need to be sure that the CPU isn't doing a lot of other stuff in the background when you run the benchmark test.
This is especially the case if you run the benchmark test right after booting Windows as many applications and background processes are still being loaded and initialised during the first few minutes after the boot procedure.
You can check if the CPU is using a lot of resources just before running the benchmark test again by pressing CTRL + ALT + DELETE and selecting the
Task Manager.
If you keep getting 4,500 points, even when your CPU is idle, the DXDiag_Lumion.txt document may help us identify the bottleneck in your system.
And lastly I would highly recommend that you
click here to run the PassMark performance test application so that we can see if the low score is only in Lumion or if it's system-wide.