36 replies to this topic

[Smitti]

I've never had an issue with gpu heat in the mechbay... or ever, really. Would like to see it back at 60fps.

+1 for the option to select the mech bay FPS however, for the sake of people to do have said heat issues.

[MrBlonde42]

I too would like the option to limit the fps to 30 vs. 60 fps.

[Black Templar]

my GPU sits at 34% load with 60°C in the mechlab screen. it is nice, because my cooler is much more quiet at these temperatures. however, spinning the mech model in the mechlab causes a blurry and stuttering image now.

an option to assign "foreground" and "background fps caps to the game would be nice. during a match i want the engine to use the full power of the system anyways. when i alt+tab out on the the other hand, i would like to see an option to cap the FPS so i can finish whatever task that is keeping me from playing asap.

Edited by Black Templar, 18 December 2013 - 01:27 AM.

[1Sascha]

Quote

I've never had an issue with gpu heat in the mechbay... or ever, really. Would like to see it back at 60fps.

Same here. I'm in the low/mid 40s (°C) in Mechlab and under 60°C in-game. So I wouldn't mind the the smoother handling of 60 FPS in Mechlab.

But since other guys with hotter running cards may have problems here, why not put an option in there to cap at 30, 40 or 60?
Perhaps with a disclaimer popping up if you set it to 60, warning the user that some video-cards may be running hot at that setting.

Although I don't quite understand why running the Mechlab at 60 FPS would put any significant strain on today's cards in the first place - but that's just me.

S.

Edited by 1Sascha, 18 December 2013 - 01:49 AM.

[Yaros525]

Magic string sys_MaxFPS = 60 sits forever in my user.cfg,
and I have zero problems with GPU heat.

[Bromineberry]

Yaros525, on 18 December 2013 - 05:14 AM, said:

Magic string sys_MaxFPS = 60 sits forever in my user.cfg,
and I have zero problems with GPU heat.

This, but sadly it's not working anymore. For the same reason (and to avoid big drops in the framerate= I set this variable to 50. But since this patch, like I said, it's not working anymore.

[Magos Titanicus]

same here. straight after the new patch my fps in Mechlab went down to round about 30 fp/s
(check your fps with F9)
running the repairtool changed nothing.

Edited by Magos Titanicus, 18 December 2013 - 06:21 AM.

[Colonel Tequila]

Running at 70C in windows - 70C on MWO frontend. No heat change for me - just a choppy front end - would be nice to have a smooth front end mechlab again

[Brian Windover]

If we had no sort of cap some users could get into the 5000 FPS range which would cause GPUs to overheat and die. This was a similar problem when the new Battlenet was release with StarCraft II.

[Deathlike]

It would've been nice had this info been in the PATCH NOTES.

[Bromineberry]

Brian Windover, on 18 December 2013 - 09:12 AM, said:

If we had no sort of cap some users could get into the 5000 FPS range which would cause GPUs to overheat and die. This was a similar problem when the new Battlenet was release with StarCraft II.

Is there a way, that you can make the "max_fps" command work again?

[P e n u m b r a]

is 30 fps not a bit extreme though? i mean most cards can easily handle 200fps without overheating if you cap it at 30 why not at least 120?

[Fooooo]

Brian Windover, on 17 December 2013 - 08:17 PM, said:

Our old system was enabling vsync in the front end this is why a lot of users were seeing 60 FPS, the reason we did this was to prevent huge frame rates which could cause your video card to overheat and die . Enabling the vsync was the incorrect way of doing this so we made a change to cap the FPS in the front end. Right now we cap the FPS to 30 when you are in the front end, however seeing as people are seeing some issues we will increase the FPS to 60 the next patch.

Capping the FPS in the front end will not affect the FPS in game.

Thank you for this.

I hate the jerky movement that happens in the mechlab now that its limited to 30.

To add to this, can we get the option to limit the frames with sys_maxfps back as well ??

I could always limit it to 40 or 50 via keybinded cfg in the mechlab (as the mechlab seemed to run my gpu near 100% usage at 60, but in a match was just over 50% at 60...) ...now I cant.


Maybe also having an option in the options menu for mechlab frame limits would be useful ? one for 30 and one for 60? (for those that dont wish to use V-sync and dont want to use a cfg to limit etc)

Edited by Fooooo, 20 December 2013 - 09:56 PM.

[Martin Oberhofer]

Brian Windover, on 18 December 2013 - 09:12 AM, said:

If we had no sort of cap some users could get into the 5000 FPS range which would cause GPUs to overheat and die. This was a similar problem when the new Battlenet was release with StarCraft II.

as i appreciate a frame cap (why letting the gpu run at 100% when it make 0 difference), it saves a bit of power too -> nice
but...
To cause a GPU to overheat and die requiers a horrible setup, and it cannot be done by software alone.
All modern GPUs have an overheat protection -> throtteling or stop

I understand the need (or better usefullness) of a limit or cap in some sort, but 30 is way to low, and i dont buy the excuse of prevent gpus from death for a second -> that would even be assured by a cap at 60-100-120 even 200.

Lets not forget, there are people out there crunching numbers with desktop gpus - we talk about 24/7 use of everything the gpus has to offer.

[Matta]

All I can say is:



Seriously guys, was this the right way to handle FPS lock ?
Instead of almost negligible chance for some GFX card to die now we have jerky Mechlab where shuffling parts and weapons is a pain to watch. What's even best, now we have to wait for the next patch to solve the issue.
Sometimes I wonder do you even test things you touched before releasing live...

[Gremlich Johns]

Thorqemada, on 17 December 2013 - 09:24 PM, said:

I would like to have a Setup Option for that.
At 60 fps my GPU runs hot and i am very happy with 30 fps!

Pretty Pls

After market cooler!!

[Darth Futuza]

Matta, on 21 December 2013 - 07:34 AM, said:

Seriously guys, was this the right way to handle FPS lock ?
Instead of almost negligible chance for some GFX card to die now we have jerky Mechlab where shuffling parts and weapons is a pain to watch. What's even best, now we have to wait for the next patch to solve the issue.
Sometimes I wonder do you even test things you touched before releasing live...

Count yourself lucky I'm still getting 9fps...