Why does the menu stress my GPU more than the game itself?

[lods of emone]

Seriously, I don't get it. Why does a moving image max out usage?

In the menu I'm getting 99% usage, while in game on max settings it'll be anywhere from 50 - 80%.

 

[Xendance]

Seriously, I don't get it. Why does a moving image max out usage?

In the menu I'm getting 99% usage, while in game on max settings it'll be anywhere from 50 - 80%.

The menu doesn't require as much CPU processing as levels. Meaning that your GPU has to wait less for the CPU to feed data for rendering. Thus your GPU usage is higher in the menu.

 

[Icey_Pain]

The menu doesn't require as much CPU processing as levels. Meaning that your GPU has to wait less for the CPU to feed data for rendering. Thus your GPU usage is higher in the menu.

But what exactly is so heavy about the menu that it needs to hitch before you can press any buttons while making your fans spin like crazy?

 

[hockeywarrior]

But what exactly is so heavy about the menu that it needs to hitch before you can press any buttons while making your fans spin like crazy?

Good question ... I remember before the DDE Beta there never used to be a hitch. It was introduced later, and now it's been in the game ever since.

 

[Xendance]

Good question ... I remember before the DDE Beta there never used to be a hitch. It was introduced later, and now it's been in the game ever since.

But what exactly is so heavy about the menu that it needs to hitch before you can press any buttons while making your fans spin like crazy?

Hitch? As in slow fps and lag? I don't get any of that
But generally speaking the GPU always renders as fast as it can (unless you cap the fps somehow), so if there is very low to none waiting for data from CPU it's going to utilize the GPU core more.

 

[hockeywarrior]

Hitch? As in slow fps and lag? I don't get any of that
But generally speaking the GPU always renders as fast as it can (unless you cap the fps somehow), so if there is very low to none waiting for data from CPU it's going to utilize the GPU core more.

The hitch we're talking about is when the menu first loads, it pauses for a second before you can move your mouse or click anything. It's not a bug deal, but was a "bug" I noticed introduced at some point during the DDE beta. All of my friends who play (mostly ones who used to play these days) have also brought this up.

 

[ARMY guy]

Apparently you people never played a ut3 game before. Had you actually played a ut3 game before, you would know that hitch when the menu loads happens in every single ut3 engine game i know of. *loads unreal 3 to see if it hitches, oh look at that*

But the ro2 bashers will then blame tripwire for Epic's problem.

 

[lods of emone]

Apparently you people never played a ut3 game before. Had you actually played a ut3 game before, you would know that hitch when the menu loads happens in every single ut3 engine game i know of. *loads unreal 3 to see if it hitches, oh look at that*

But the ro2 bashers will then blame tripwire for Epic's problem.

Congratulations, you win the award for "Worst member of the month".

 

[Nik21]

Same in Minecraft. lol.

 

[hockeywarrior]

Apparently you people never played a ut3 game before. Had you actually played a ut3 game before, you would know that hitch when the menu loads happens in every single ut3 engine game i know of. *loads unreal 3 to see if it hitches, oh look at that*

But the ro2 bashers will then blame tripwire for Epic's problem.

Not that I really care that much about this, but what part of "this didn't happen until one of the DDE beta builds" don't you understand? I was in the beta since late July, and played RO2 just about every day, and I can tell you that it didn't exist.

I have also played UT3 and many other UE3 engine games and never noticed this. Again, I really don't care about this issue because its so inconsequential but I do care about being called an idiot essentially.

 

[Fedorov]

I wonder how many GPUs have TWI fried for not capping the FPS on their menus. I know Killing Floor fried my 9800GTX+.

 

[Lavalampdrinker]

Apparently you people never played a ut3 game before. Had you actually played a ut3 game before, you would know that hitch when the menu loads happens in every single ut3 engine game i know of. *loads unreal 3 to see if it hitches, oh look at that*

But the ro2 bashers will then blame tripwire for Epic's problem.

That Hitch is there since ut2004.

 

[hockeywarrior]

I wonder how many GPUs have TWI fried for not capping the FPS on their menus. I know Killing Floor fried my 9800GTX+.

Yep, this remains a major reason I don't play Killing Floor often. Almost every time I get past the splash screen my PC either locks up completely or I get a blue screen (on multiple PCs). I have heard this is due to the infinite FPS allowed which freaks the hell out of my graphics card. Turning on vsync didn't do anything either. I can only join Killing Floor games through the Steam browser.

 

[Cpt-Praxius]

Apparently you people never played a ut3 game before. Had you actually played a ut3 game before, you would know that hitch when the menu loads happens in every single ut3 engine game i know of. *loads unreal 3 to see if it hitches, oh look at that*

But the ro2 bashers will then blame tripwire for Epic's problem.

Who here was bashing RO2 or Tripwire?

People were asking why this happens.... that's it.

Talk about jumping the gun.

That Hitch is there since ut2004.

I never experienced it in UT2004, or the RO Mod, or RO1, or even Killing Floor.... RO2 is the only one that seems to do this for me.

It's not any issue for me and my system handles the game and the menu just fine..... but I was wondering about this stall at startup as well.

 

[lods of emone]

I wonder how many GPUs have TWI fried for not capping the FPS on their menus. I know Killing Floor fried my 9800GTX+.

That isn't really their fault. NVIDIA should have better thermal management so their cards shut down at dangerous temps, throttle, etc.

 

[wazups2x]

100% GPU usage won't kill your GPU unless something is already wrong with it. That's what they're meant to do.

Also, yes there was no small menu hitch at the begging of the beta. It changed with one of the patches. It's not bad, just a tad annoying.

 

[Shadrach]

There might be several causes for this:
1: Background playing of BIK files have been known to cause GPU load, for instance I had it in both Medieval and Empire TW before disabling the videos.

Solution: Allow to either disable menu videos or delete them, and fall back to a static image. If you delete the video now the screen just flashes red+yellow

2: No framerate cap on the menu and loadscreen, causing the GPU to think "WAHEY I CAN OUTPUT 250 FPS LETS START THE FANS!"

Solution: Let the default FPS cap of 62 also apply to menus and loadscreens.

 

[Machete234]

Your FPS are probably not capped in the menu

 

[Icey_Pain]

Your FPS are probably not capped in the menu

It's not capped on a low value from what I can see, I can easily measure over 230 FPS in the menu.

 

[lods of emone]

Your FPS are probably not capped in the menu

In-game FPS isn't capped either (or at least not a level it ever reaches for me). If a menu utilises the GPU more than the game itself, then that is a problem.