unusual cpu and gpu usage and stuttering in BGE #44032

New Issue

Daedalus · 2015-03-17T22:55:22+01:00

Daedalus commented

2015-03-17 22:55:22 +01:00

System Information
CPU: Intel i3-3220 3.3Ghz
GPU: EVGA GTX 570 1280 MB (Driver 337.88) (will update driver and check again)
RAM: 12 GB
OS: Windows 7 Home Premium 64bit

Blender Version
2.73 and 2.71

Short description of error
when running the game engine from blender, either standalone or viewport, after a few seconds the cpu and gpu usages begin to steadily climb and then near the peak the frame rate drops(stutters madly) for a few seconds then the usages drop back to normal, then begins climbing again.

turning off vsync in blender seems to prevent the usages from climbing, but the stuttering still occurs at about the same time. rivatuner/afterburner shows 60 fps even with vsync off and during the stuttering.

Exact steps for others to reproduce the error
start the blender game engine. seems to be indifferent to resolution or anti-aliasing. no interaction with game still produces issue.

{F152470}(game started at the yellow line)

blend file
Game_Demo.blend (happens on an empty game/startup file too)

**System Information** CPU: Intel i3-3220 3.3Ghz GPU: EVGA GTX 570 1280 MB (Driver 337.88) (will update driver and check again) RAM: 12 GB OS: Windows 7 Home Premium 64bit **Blender Version** 2.73 and 2.71 **Short description of error** when running the game engine from blender, either standalone or viewport, after a few seconds the cpu and gpu usages begin to steadily climb and then near the peak the frame rate drops(stutters madly) for a few seconds then the usages drop back to normal, then begins climbing again. turning off vsync in blender seems to prevent the usages from climbing, but the stuttering still occurs at about the same time. rivatuner/afterburner shows 60 fps even with vsync off and during the stuttering. **Exact steps for others to reproduce the error** start the blender game engine. seems to be indifferent to resolution or anti-aliasing. no interaction with game still produces issue. {[F152470](https://archive.blender.org/developer/F152470/BGE.bmp)}(game started at the yellow line) blend file [Game_Demo.blend](https://archive.blender.org/developer/F152475/Game_Demo.blend) (happens on an empty game/startup file too)

Daedalus commented

2015-03-17 22:55:22 +01:00

Changed status to: 'Open'

Daedalus commented

2015-03-17 22:55:22 +01:00

Added subscriber: @Daedalus_MDW

Daedalus commented

2015-03-18 00:26:37 +01:00

updating graphics driver(uninstalling old in safe mode and driver sweep) didnt changing anything. turns out after having more time to mess with settings, the "use framerate" under System in the Render tab caused the frame capping without vsync (sounds normal), but also was the cause of the odd usage and stuttering. with vsync ON and Use Framerate OFF, the game now runs constantly smooth (and at a playable speed :) )

Daedalus commented

2015-03-22 20:52:03 +01:00

this still happens on 2.74 RC2.

as a side note, "Use Framerate" causes the mouselook to bug out and get laggy, regardless of on or off. but turning "Use Framerate" OFF and Vsync OFF always returns mouselook functionality to normal.

built and tested in 2.74 RC2 starter_game.blend

this still happens on 2.74 RC2. as a side note, "Use Framerate" causes the mouselook to bug out and get laggy, regardless of on or off. but turning "Use Framerate" OFF and Vsync OFF always returns mouselook functionality to normal. built and tested in 2.74 RC2 [starter_game.blend](https://archive.blender.org/developer/F154152/starter_game.blend)

Daedalus commented

2015-03-24 23:32:24 +01:00

however, the unusual usages are still present. after turning on the stats, i noticed the "GPU Latency" % started to drop and the "Outside" began increasing at the same time the usages begin to climb. once the GPU Latency reaches about 5% and the Outside reaches about 90%, it stutters for a few seconds and the usages drop back to normal, GPU latency returns to about 95%, and the outside returns to 0%. all while the frame rate reads ~60 fps.

the laggy mouselook occurs when the Outside is about 90% and the GPU Latency is about 5%-0%.

this doesnt happen when "Use Framerate" is unchecked.

NOTE: i have no background processes running, i only install the necessary software/drivers to get the computer functional. the only other program i run besides blender is MSI Afterburner for temps and fan curve. closing Afterburner didnt help.

however, the unusual usages are still present. after turning on the stats, i noticed the "GPU Latency" % started to drop and the "Outside" began increasing at the same time the usages begin to climb. once the GPU Latency reaches about 5% and the Outside reaches about 90%, it stutters for a few seconds and the usages drop back to normal, GPU latency returns to about 95%, and the outside returns to 0%. all while the frame rate reads ~60 fps. the laggy mouselook occurs when the Outside is about 90% and the GPU Latency is about 5%-0%. this doesnt happen when "Use Framerate" is unchecked. NOTE: i have no background processes running, i only install the necessary software/drivers to get the computer functional. the only other program i run besides blender is MSI Afterburner for temps and fan curve. closing Afterburner didnt help.

Daedalus commented

2015-04-07 04:33:01 +02:00

The climbing usages also happens on:

System Info:
Intel Core 2 Duo E7600 3.06Ghz
Asus P5G41T-M LX Plus
4GB RAM
AMD/ATI Radeon HD 5770 (13-12 Driver)
Windows 7 Home Premium 64bit

The climbing usages also happens on: System Info: Intel Core 2 Duo E7600 3.06Ghz Asus P5G41T-M LX Plus 4GB RAM AMD/ATI Radeon HD 5770 (13-12 Driver) Windows 7 Home Premium 64bit

Daedalus commented

2015-05-13 05:24:42 +02:00

theres a script (for cycles) in the attached file that seemed to be causing the issue. whether that is normal or not, i dont know, but deleting it fixed the issue of stuttering and climbing usages.

Jorge Bernal commented

2015-05-15 15:47:10 +02:00

Added subscriber: @JorgeBernalMartinez

Jorge Bernal commented

2015-05-15 15:47:10 +02:00

In linux I can not repeat the same behaviour.

Anyway, the script that you are referiing is the related one to setting the sky texture to the vector?

In linux I can not repeat the same behaviour. Anyway, the script that you are referiing is the related one to setting the sky texture to the vector?

Sergey Sharybin commented

2015-05-18 14:18:51 +02:00

Added subscriber: @Sergey

Daedalus commented

2015-05-18 23:17:40 +02:00

In #44032#308847, @JorgeBernalMartinez wrote:
In linux I can not repeat the same behaviour.

Anyway, the script that you are referiing is the related one to setting the sky texture to the vector?

yes, that is it.

> In #44032#308847, @JorgeBernalMartinez wrote: > In linux I can not repeat the same behaviour. > > Anyway, the script that you are referiing is the related one to setting the sky texture to the vector? yes, that is it.

Jorge Bernal self-assigned this 2015-05-19 08:01:03 +02:00

Jorge Bernal removed their assignment 2015-05-19 08:02:05 +02:00

Jorge Bernal commented

2015-05-19 08:04:42 +02:00

Added subscriber: @ideasman42

Jorge Bernal commented

2015-05-19 08:04:42 +02:00

It is very strange that a bpy script that it is not attached affects this way to bge. Maybe it is related to blender too.

I add to @ideasman42 waiting for his advice.

It is very strange that a bpy script that it is not attached affects this way to bge. Maybe it is related to blender too. I add to @ideasman42 waiting for his advice.

Jorge Bernal commented

2015-05-19 11:36:11 +02:00

In #44032#309784, @JorgeBernalMartinez wrote:
...that it is not attached ....

not attached --> not linked to a python controller

> In #44032#309784, @JorgeBernalMartinez wrote: >...that it is not attached .... not attached --> not linked to a python controller

Daedalus commented

2015-05-20 21:15:10 +02:00

i decided to go back and try it again. turns out i couldnt get the uploaded file to show the bug either. after messing around with lots of blender settings and lots of nvidia settings, still no bug.

turns out its the 1280x1024 screen resolution causing the bug. not the script, i just had coincidentally tried deleting the script after i got a new monitor with a 1440x900 native. in the properties/render tab of Game_Demo.blend uncheck "Desktop" under "Standalone Player". that should cause the game to run at the set 1280x1024 which the bug presents itself. if you turn on framerate and profile, you can watch the Outside and GPU Latency dance.

havent tested any other resolutions.

i decided to go back and try it again. turns out i couldnt get the uploaded file to show the bug either. after messing around with lots of blender settings and lots of nvidia settings, still no bug. turns out its the 1280x1024 screen resolution causing the bug. not the script, i just had coincidentally tried deleting the script after i got a new monitor with a 1440x900 native. in the properties/render tab of *Game_Demo.blend* uncheck "Desktop" under "Standalone Player". that should cause the game to run at the set 1280x1024 which the bug presents itself. if you turn on framerate and profile, you can watch the Outside and GPU Latency dance. havent tested any other resolutions.

Sergey Sharybin commented

2015-05-25 21:52:27 +02:00

Doesn't seem to be a generic blender bug then. Either video mode is not set correctly so software scaling is needed or so.. BGE guys will know better :)