

#61
Posted 16 November 2012 - 12:59 AM
#62
Posted 16 November 2012 - 02:06 AM
ultra high settings
never recognized the framebug
30-50 fps, very rare more or less, depends on map, direction, mechs in sight path.
never below 25fps
Maybe the game doesn't like nvidia cards ?
#63
Posted 16 November 2012 - 08:08 AM
#64
Posted 16 November 2012 - 10:05 AM
Have Nvidia GTX 570 1.25 gig ram
8 gig ddr3
intel i7 quadcore 3.6 ghz
And running Ultra at 1280x720 with 60+fps ( for recording sake. Do have 60+ fps even with 1920x1080 )
Today after a long secession I got fps hit to a point it was unplayerble ( under 5fps )
So think if we dont reboot the client at all we will run out of memory and it will start to decrease in fps.
At least that is my theory, because I usually dont get it. And my usual play time is 30 minutes to 1 hour normally. But today I did a marathon and thats where I got it.
Edited by Anariaq, 16 November 2012 - 10:08 AM.
#65
Posted 16 November 2012 - 10:36 AM
Edited by fxrsniper, 16 November 2012 - 10:37 AM.
#66
Posted 16 November 2012 - 01:53 PM
Max pre-rendering
Set to single monitor performance
Set to max performanceI(dont use Adaptive)
In game settings:
Reduce resolution to the 1280 range(I think its 1280), you shouldnt notice much of a reduction in visual quality, it at all
Use the USER.cfg to turn off Shaders and Shadows
These are the changes I can remember that significantly improved frequency of FPS spikes, and a moderate increase in FPS.
#67
Posted 16 November 2012 - 02:43 PM
A race condition in a runaway thread. When it happens you will see that your CPU usage is pegged in at least one of your cores.
Edited by xenoglyph, 16 November 2012 - 02:43 PM.
#68
Posted 16 November 2012 - 04:36 PM
I never saw this issue until I turned off V-Sync as a test.
#69
Posted 16 November 2012 - 05:08 PM
The Cheese, on 16 November 2012 - 04:36 PM, said:
I never saw this issue until I turned off V-Sync as a test.
I experienced the same issue, and I have Vsync active (60 fps) just to avoid the noising rows on the monitor.
But effectively I had some problem sometimes with this totally decrese of FPS and is not my pc
(intel I7 970i.e, 2x 670GTX sli, 8 gb ram).
thanks for the sugestion I will try to deactivate vsync.
#70
Posted 16 November 2012 - 05:36 PM
CocoaJin, on 16 November 2012 - 01:53 PM, said:
Max pre-rendering
Set to single monitor performance
Set to max performanceI(dont use Adaptive)
In game settings:
Reduce resolution to the 1280 range(I think its 1280), you shouldnt notice much of a reduction in visual quality, it at all
Use the USER.cfg to turn off Shaders and Shadows
These are the changes I can remember that significantly improved frequency of FPS spikes, and a moderate increase in FPS.
Nvidia said to leave it on default not single performance I've tried both not real noticeable difference
#71
Posted 16 November 2012 - 06:16 PM
If it happens to me again I'll take a look at the affected thread and get a stack dump. Out of a couple hundred matches it's only happened to me twice though...
I'm pretty sure it's something that happens as the client is setting up a match. Both times it happened to me I started the match at 4 fps.
#72
Posted 16 November 2012 - 09:42 PM
xenoglyph, on 16 November 2012 - 06:16 PM, said:
If it happens to me again I'll take a look at the affected thread and get a stack dump. Out of a couple hundred matches it's only happened to me twice though...
I'm pretty sure it's something that happens as the client is setting up a match. Both times it happened to me I started the match at 4 fps.
I think you could search and find the thread about the 4fps bug (assuming it's only one bug). Basically, one member found that mechs weren't clearing from video memory properly, eventually completely filling up your cards mem and causing the 4fps. It varies from system to system, and happens more quickly on XP than 7 64-bit. You can adjust how soon it happens by raising or lowering your graphics settings, but it should happen consistently. You just have to restart after so many games; for me, on XP, I have to restart after every 4 games, while my friend on 7 gets it after ~8 games.
Of course, this may not be the only bug around that does this...
Edited by Indeed, 16 November 2012 - 09:46 PM.
#74
Posted 17 November 2012 - 03:43 AM
FroBanger, on 16 November 2012 - 12:45 AM, said:
12 Gigs or Ram
Nvida 560 Ti Hawk
I used the MSI somthing or other to see how much of my cpu the game was using at MAX it was using 50 percent of my GPU and 800 megs of its memory but I was only getting 30fps .. Yes I know that doesnt sound all that bad since I never get the FPS bug that drops me to 1or 2 fps and I do not get random crashes. I'm more so asking whats causing this game to not function at 60 FPS? it is my CPU? is it bad Game play optimization in MWO? Or does the game just not like the 560 Ti hawk, or am I not doing somthing correct in my NVIDIA profile?
IF its bad optimization in the game or the game specificalyl hates my graphics card cool let me know I shant ask again.
If its somthing I can change in my NVIDIA profile or my user config file please let me know I know someone has to be playing this game at 60 FPS stable at all times. Oh I run the game at 1920x1080 all settings low.
If anyone knows any Nvidia profile things I should have on instead of off please do tell. Thanks.
Hi Mate I have a very similar build and avarage 40-50fps max 60fps min 25fps, it depends on which map I am on. I have all settings on high, Vsync checked and screen res at 1600x900 full screen. I do get crash back to desk top but only after about 7-8 hours of play....there still seems to be a memory leak in game somewhere. Hope this helps matey

#75
Posted 17 November 2012 - 06:47 AM
Don't run Vsync unless your FPS is over 60 and you have an issue with tearing.
#77
Posted 17 November 2012 - 02:01 PM
xenoglyph, on 16 November 2012 - 06:16 PM, said:
If it happens to me again I'll take a look at the affected thread and get a stack dump. Out of a couple hundred matches it's only happened to me twice though...
I'm pretty sure it's something that happens as the client is setting up a match. Both times it happened to me I started the match at 4 fps.
4 FPS bug is a shaders cache issue supposedly(memory leak?). No fix except to restart the client. Its not a hardware issue or driver issue, etc...the devs screwed the pooch in the code somewhere. Nothing to be done until they find it and fix it in house.
#79
Posted 29 November 2012 - 11:24 AM
#80
Posted 29 November 2012 - 12:03 PM
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users