badhabit wrote:Dr.Disaster wrote:k, one final hint
Ok, looks like from 1 to 2 you changed the graphic settings (resolution?) as the memory load goes up (but I mentioned that before), potentially increasing by that the GPU utilization. The small CPU load variation between 1 and might be inside the fluctuation range so might or might not be indicative, not clear. (the dropping cooler load is strange)
Yes, that's all i did: reset resolution from manual 1280x720 set in "grimrock2.cfg" back to 1280x1024 via options menu so the entire desktop area is used. In return this gave LoG access to the GPU's entire RAM and +6% in load.
badhabit wrote:Third image, you increased the GPU load again by increasing the graphical load by options (fullscreen intead of windowed mode?) & "catched" the CPU load in a even lower state?
All screenshots were taken in borderless window mode.
The only difference in settings is the resolution change from 1 to 2. Between 2 and 3 none of the option were changed.
Naturally there is some jitter in the GPU load value sensor but that is present in all pictures with GPU-Z graphs inside. The difference however between pic 2 and 3 is persistent. In pic 2 the load never manages to go past 92% while in pic 3 it easily does. Enhancing the unscaled pic' 3 GPU-Z load sensor section shows that the last readings have a higher top value in general then before.
Regarding' "catched" the CPU load in a even lower state ': this would only lead to a temporary increase, not a permanent one. I could have waited several more seconds or a minute before taking pic 3 but the GPU-Z readings would still have been the same. The tool's sensor show that the pic's were taken very close together. In fact the time between pic 2 and 3 is what it took to save pic 2 to disk: screenshot to clipboard via PrintScreen key, then saving clipboard content away with Paint. Then I applied the difference and took pic 3 to show the 4% gain in load. The question remains: what was it?
