18 replies to this topic

[Grothanol]

Hi there. I dont know if thats the right topic but i ask here for now.
I bought a new graphics card, 670 GTX OC gygabyte. The 3 windforce model. And i have FPS issue. My FPS is unstable, they move beetween 70 to 30 sometimes (with very high setting, without vertical synchro and 1920 x 1080 resolution.)
Rest of my computer is not so bad... Intel core I5 3570K IvyBridge and 8 GB ram and running on windows 7 64.
I asked some people and they told me game still at 60 FPS for them. Any idea?

[Mrhitla]

I have same problem. And yes, i have just same hardware, as the OP.

[Morikuro]

That's pretty strange. I have your processor/OS/ram, and an OCed GTX 670, only mine is a Galaxy (67NPH6DV5ZVX) and not a Gigabyte. Stable frames from 55ish to 60 almost all the time with everything maxed at 1920x1080, except for motion blur (on low because I don't care for heavy amounts of it).

Edited by Morikuro, 30 October 2012 - 01:05 PM.

[Stickjock]

Only thing I can think of off the top of my head is...

Turn off Ambient Occlusion for MW:O in your Nvidia Control Panel... patch before last that helped a lot of Nvidia GPU users fix FPS loss problems...

AO support for MW:O was added by Nvidia in the last few Driver updates, but don't think MW:O fully supports it yet... that would be my guess why it causes some problems...

Good luck!!

[AllGamer]

The CryEngine is simply not fully optimized yet.

it doesn't matter if you are on nVidia, ATI or Matrox, none of them runs at a stable frame rate.

with any other game (also sporting CryEngine), i pull over 100 fps

but in this game it barely keeps up at 24 fps

[christophermx4]

I have nearly the same specs, and I turned V-Sync on, and it helped keep my frame rate around 60 FPS. This game engine needs more work - hopefully DX11 will iron out some of the issues.

[Thelamon]

I have the same problems with my GTX 670 OC windforce (Gigabite 3 Fan).

With the MWO settings all at very high (as they should be) I get gyrations from 60 fps down to 13 fps and the like (with second long screen freezes in that FPS drops).

This all started to happen with the Cryenginge upgrade patch, that also happened to suck so bad as to get the Open Beta delayed. Before they upgraded the cry engine I could play with no issues.

--------------------------
Something is really cheesy here. (And the game unplayable for me right now with these slide-show intervals.)

I have tried to switch the settings in the Nvidea driver profile (set to maximum performance etc. - It says Ambient occlusion not supprtet by the application, so no use turning that of), have checked the latest driver, the latest beta driver and have freshly reinstalled the game.
All to no avail.

When I run GPU-Z to check what is going on I can see that the card isn't running at its regular 3d performance clock @ 980 + MHz or even the boosted frequency, but rather around 800ish in average.
The temperature stays around 40° C - so by all accounts MWO somehow doens't trigger the card to go on full-power 3D application mode. It looks like the card causes thes FPS dips by powering down to 2d mode or something.

There was a thread out there suggesting just that and to work around using an MSI OC tool to force it to continuously run at a set (performance) frequency via profile for the MWO application. (Haven't checked that yet and cant find the thread right now)

The Gigabyte OC tool that came with the card doesn't cut it for me (or I'm too stupid), as I cant find the right options.

[evilC]

MWO is currently very heavily CPU bound, you will notice very little difference between a GTX 260 and a GTX 660 ti (I just upgraded and saw next to no improvement).

This is borne out by the MWO Benchmarking Project results - the only people getting high FPS (ie minimum of 60FPS) are the ones with beastly CPUs.

[ThreePi]

Its definitely very CPU-bound. I have an older i7 920 with a 7970 and there's virtually no FPS difference between medium and very high settings. The thing I don't really understand is that this why performance wasn't like this earlier in closed beta? I remember playing a month or so ago and performance was lightyears better, now the game is just unplayable at times.

[Erasus Magnus]

about 2 patches ago they introduced an updated version of the engine, with tons of new or improved graphic effects.

since then a lot of people started to have severe problems with the performance of this game.

i for myself have pretty stable frames at 20-30 fps, but after 3-5 matches, the fps suddenly drops down to 4 fps and stays like this until i restart the game.
even in mechlab i have **** poor performance.

i guesss its partly because of this array of new and imprpoved effects and the fact that the game is still only dx9 and not dx11. i also read that this game game also doesnt make use of 64 bit systems. dont know if this is true, but it would mean that it only supports a max amount of 4 gis of ram.

im wondering that it still performs and looks so good while still using this old tech.

[Thelamon]

Hi there has anybody found a workaround or gotten a response from support yet?

My problem with the random fps drops is the slideshow with short screenfreezes that results and eventually gets me killed in game...


I have followed all I could find on this matter, including this thread:
http://mwomercs.com/...ormance-issues/
But all there is to find is, that plenty of people have serious fps problems since the cry engine upgrade patch two or three weeks ago...
A friend of mine runs the exact Gigabite 670 GTX OC Windforce and gets really good results though (and I don't really think it is the card, as I get really nice performance in any other game and on all the bench marks like Futuremark 3d 2011, Furmark etc. - the card runs nice and stable at 1100 MHz on the Furmark Stresstest).

I have tried out all the workarounds that I could come up with:

1. Full reinstall and clean update of MWO
result: problem persists unchanged

2. Try out all the different Nvidea drivers
310 beta - no improvement
306 - latest regular driver - no improvement
301 - the driver I was on when closed Beta was still fun - no improvement

3. lowering the the grafic settings in Game from very high down to medium with AA and shadows of
- no difference in FPS at all!

4. created an MWO profile in the Nvidea Driver setup, set everything to maximum performance etc.
- no improvement
-----------------------------------------------------------------------------------------------------

I checked the systems performance while running MWO using GPU-z and CPU-z and the performance display of my g14 keyboard displaying the load of the 4 CPU cores.

The findings:
1. The CPU load is between 40% and 55% running the game - the CPU load is no where near max on any of the cores.

2. The memory usage (of my 8 Gb RAM) is at max 39%. It doesn't look like MWO use the 64 bit engine and the higher available memory that comes with it.

3. Most baffling: MWO somehow throttles down the GPU of my 670 GTX
Once starting the game and in te Mechlab the GPU core goes from low 2D up to a medium frequenzy of 780 MHz and then stays there with some lower dips after launching into the game.
The card never runs its nominal 980 MHz nor its 3D boost of 1100 MHz with the current MWO build!
It is as if the computer doesn't truly recognize MWO as a high performance 3D aplication and tries to save energy by running at a lowered GPU clock.
(The card alse never gets warm/ hot the Temp stay around 40° C without the fans ever throttling up.)

Looking at 1. to 3. the system feels passive - not even trying hard to run MWO and getting defeated while really struggling, but rather like treating MWO like a low priority app.

--------------------------------------------------
I then tried to force the card to go full power by using the MSI Afterburner tool.
I configured a profile for MWO and set the GPU to 1100 MHz for all 2D and 3D applications.
(Eg. the regular frequencies the card usually auto-boosts to when running 3D performance programs) - I could see that these profile specs were then run when testing with 3D benchmark tools.

However Win 7 seems keen on energy-saving and turns down the "not-so-forced" frequency of the afterburner profile, while on the Desktop... (That was better back in the day with the regular Rivatuner - if you chose to heat your room with your GPU you could )

Same happened in MWO - profile or not - ~780 MHz or lower for my GTX 670 while running MWO

Maybe the flash-based Mechlab doesn't feature as a full grown 3D app and the driver/card/system (?) then don't get the difference once the real game using the cry engine is launched?

-------------------------------------------------
Any Ideas?
Again: I could run this game with all settings maxed till that patch came and screwed things up. Now these FPS freezes kill the game for me.

Thanks
Thelamon

PS - System specs:
Win 7 64
8 Gb RAM (@800 matching the FSB 400 of the CPU)
Intel Core 2 Quad 9550 (E0) @ 3,4 GHz with FSB 400
Nvidea 670 GTX OC Gigabite Windforce

Edited by Thelamon, 06 November 2012 - 02:35 AM.

[GL Chozo4]

Yo might also find it helps to disable processor throttling. This can often be done so by setting your power-profile in your control panel to 'performance' mode or 'always on' depending on your system.

[GrimmwolfGB]

To add to the confusion, I have the same card and I am on a similar setup and it works flawlessly.

[AC Rimak]

It's already a well known fact that MWO has huge performance issues on good machines.
Seems like cryengine optimizaton problems, no fix yet.

Edited by AC Rimak, 06 November 2012 - 07:22 AM.

[Flapdrol]

evilC, on 01 November 2012 - 10:29 AM, said:

MWO is currently very heavily CPU bound, you will notice very little difference between a GTX 260 and a GTX 660 ti (I just upgraded and saw next to no improvement).

This is borne out by the MWO Benchmarking Project results - the only people getting high FPS (ie minimum of 60FPS) are the ones with beastly CPUs.

Agreed, the only way to keep fps on 60 is to overclock a sandy/ivy bridge cpu close to 5 Ghz.

Also, you have to force vsync off in the nvidia control panel to actually turn it off.

[GrimmwolfGB]

btw, Thelamon "fixed" his problems with the game by upgrading to a bigger display (1920*1080, 24''). His FPS problems are gone.

[Swiss Beats]

I am not sure how a bigger display would affect things? I have three 24 inch monitors in surround mode at 5760 x 1080 on a 660Ti card and whether I am in full screen maxed out or even dropping down to one monitor I get the same FPS regardless. With the graphics on low I peg the FPS at 60+, both medium and high settings yield 30-50 FPS consistent with some random drops depending on the map. These are the same areas in Forest Colony, River City and Caustic where most people report problems so I attribute that to being the MWO graphics equivalent of the Bermuda Triangle.

This is a new build but even on my old POS dual core AMD I was getting consistent 30-40 FPS most maps unless it was a mess of mechs all alpha striking each other at close range making a hot mess of things then it would **** the pooch on me.

I'll run some FPS tests later using MSI Afterburner to see if I spot anything unusual but the larger monitor improving things does not make sense to me.

[GL Chozo4]

demonr6, on 13 November 2012 - 01:07 PM, said:

I am not sure how a bigger display would affect things? I have three 24 inch monitors in surround mode at 5760 x 1080 on a 660Ti card and whether I am in full screen maxed out or even dropping down to one monitor I get the same FPS regardless.

The reason a larger monitor/res affected such a case is only when the persons CPU is bottlenecking/choking-out their graphics card. Smaller scenes being rendered increase the load on the CPU whereas larger strain the GPU more. Usually such a system bottleneck can often being somewhat overcome with higher-quality/resolution so that the CPU itself ends up with far less work to do when it couldn't handle a higher load otherwise. This works because with a higher load on the GPU - the CPU ends up waiting on the GPU to finish rendering a scene more often. It may 'lower fps' a bit on the higher resolutions but one will find that their significant FPS drops during the game are minimized or gone altogether as a result of the CPU being more free to load more data.

SRC: Experience from past setups (mine or otherwise) trying to play at bare minimum requirements@highres. Same result when having played MWO-CB on my last system (was cpu choked on 2.71ghz dual-core). Used to also find it amusing I was able to play MechWarrior 4 on my old 350mhz AMD/7.5MB AGP S3-Savage back in the days too (but only if it was right in the middle of quality there, would choke out on one or the other otherwise).

Edited by GL Chozo4, 13 November 2012 - 02:50 PM.

[SerpentrasD]

ThreePi, on 01 November 2012 - 07:22 PM, said:

Its definitely very CPU-bound. I have an older i7 920 with a 7970 and there's virtually no FPS difference between medium and very high settings. The thing I don't really understand is that this why performance wasn't like this earlier in closed beta? I remember playing a month or so ago and performance was lightyears better, now the game is just unplayable at times.

Not. Or do you wanna say that my old phenom 9950B is good like the i5 3570k? Same GPU 7870 dc II v2 and I could run at max with the old cpu without getting bad frames.
MWO dont need much performance to run and don't need much ram because the maps and all the other crap is not so big.

I have games where you really need cpu power but this game don't need it.