57 replies to this topic

[Al Bert]

I decided to post this, since I came across this now for the second time - it happened after the patch Nov 20th and also now after Nov 27th patch: when in game the first time after patching, the FPS in the "Home", the "Mechlab" and the "Pilotlab" section is a constant 60 - which I like. With the second and (subsequent) launches of the game, the FPS in the "Mechlab" is still 60 FPS, but in "Home" and "Pilotlab" it seems fixed to 40 FPS no matter what.

Of course FPS in pre-game is fine anyway, I don't bother. So I am not posting this because I see it as a real issue, but maybe the underlying reason is a hint to other FPS issues?

I REALLY like the possibility now to rotate my mech in the "Loadout" section (finally I can see the hitting zones) and in the Camo section - in contrast to what some people report in the forum, I do see NO FPS drop while doing this at all (so: a fixed 40 FPS)

No settings changed, no fiddling with the user.cfg, in-game FPS around 35 in general (all settings "medium", motion blur & V-sync off, post AA)

regards,
Al Bert

[yashmack]

dropping from 60 fps to 40 fps between mechlab and in a match i would think it normal
gameplay is a lot more intense and uses a lot more power when youre actually playing as compared to static models being rotated in the mechlab...

[Al Bert]

just to clarify (again): i am not complaining about an issue but i think it is rather odd tat FPS in mechlab is 60 while in home and pilotlab its 40. and that it is 60 right after patch.

[Sayyid]

Two patches ago this game ran fine on my system, I was getting between 20-40FPS on an Athlon 5600+ x2 Dual core 2.8GHZ CPU and a 260GTX GPU with 6GB of RAM. Now I am getting between 5-15.

I have uninstalled and reinstalled after the 20th patch and it made no difference, the next uninstall most likely will be the last and I will ask for a refund on my remaining MC.

[Kill Dozer]

The move to the newer cryengine is what killed your FPS, it did mine as well and I'm running a Q6600. I lost 10-20 FPS when the engine changed.

[sycocys]

What all have you tried as far as system tweaks?

[Morang]

Aye, two patches ago it was nice, now it's the slideshow even despite costom user.cfg. C2Duo at 3600 MHz. Looks like Frozen City is the worst map for me - prolly because of these skyscraper tops or blizzard effects. I also noticed that FPS drop is much worse when I turn my whole mech, but not when I twist my torso (though my field of view moves in both cases) - dunno why.

[Kerjhr]

im running an old core2 quad q6600. and its barely playable. 50-20 fps jumps on low. 40-15 fps on very high tho. no idea why they borked the engine that hard.

Edited by Kerjhr, 28 November 2012 - 07:57 AM.

[Warenwolf]

I am playing this on a tri-core 720 Heka and FPS is all over the place. I don't get certain values consistently but rather dip down to 15-20 FPS and up to 50-60. Forest Colony and Frozen City seem to get biggest drops (subjective - it is the two maps I get 90% of time - better than two patches ago when it seemed like I played Caustic Valley Online)

[Sayyid]

I have left the config file alone because the game ran fine after the patch two weeks ago. Now the game is running worse than Planetside 2 in early beta on my system.

[Depe]

Did anyone find a custom user.cfg that could help running the game a little smoother? Maybe we could tweak a bit the cpu related features.

Edited by Depe, 28 November 2012 - 08:58 AM.

[sycocys]

Can anyone who is having issues please let us know what you have been trying to locate/solve them? Otherwise all we can assume is that you're doing nothing, and for that no one can help you.

What settings are you changing in the .cfg? Have you tried drive roll backs or new beta drivers for your card? Bumping it down to 1 core to focus the processing power?

[TheFace Asano]

running a regor amd dual core 2.8 with nvidia 550ti and 8 gigs 1600 ram. 30+ fps before 2 patches ago, and still at 5-15 in action. out of action probably 20-30. This is also with everything on low. FPS before was 30+ at medium and textures on high. tried reinstall several times, tried messing with the 3d settings in the nvidia control panel. so far nothing is working.

[TehArgz]

Sayyid, on 28 November 2012 - 05:35 AM, said:

Two patches ago this game ran fine on my system, I was getting between 20-40FPS on an Athlon 5600+ x2 Dual core 2.8GHZ CPU and a 260GTX GPU with 6GB of RAM. Now I am getting between 5-15.

I have uninstalled and reinstalled after the 20th patch and it made no difference, the next uninstall most likely will be the last and I will ask for a refund on my remaining MC.

I wouldn't hold your breath on your refund. It's not their fault you have dated hardware.
Have you taken any steps to help your system, yourself? I can sympathize with you. I'm running a c2d e8400 and a 460gtx with an older mobo, performance has been a serious issue for me in the past few patches, specifically forest colony. That being said there are some things you can do to give your system a fighting chance. Run a clean os install or at least clear out your startup items. Make sure steam/skype/anti-virus/ect are off. Close open programs. Run in a smaller window. Overclock your hardware.
If most of these things have not been done, then asking for a refund is just silly, and even if they have been done it's merely rediculous.

I have done all these things and have slightly better specs than you, and still have playability issues, so I don't expect everything to work well for you, but you never know.

Good luck!
With the game, not with the refund.

Edited by TehArgz, 28 November 2012 - 10:02 AM.

[Bagheera]

TehArgz, on 28 November 2012 - 09:59 AM, said:

I wouldn't hold your breath on your refund. It's not their fault you have dated hardware.

Perhaps not, but it IS their fault for misleading people to believe the game would run on Core2Duo machines:

Quote

Core 2 Duo E6750 2.66GHz
Athlon II X2 245e
GPU:
GeForce 8800GT
Radeon HD 5600/5700
RAM: 4 GB
OS: Windows Vista 32-bit
DirectX: DX9
HDD Space: 4 GB

Specs taken from here:

http://mwomercs.com/...eveloper-update

Pretty sick and tired of hearing people blame us for PGI's inability to support their own published minimum spec.

PGI either needs to fix the problem, or change the published spec with a great big apology. It is long past time for this to happen.

Also no, CryEngine version is not the problem. There was no engine version update on 11/20. MW:O went to 3.4 before that and ran just fine. Not the peak of performance for me, but just fine. Go back and read through the performance feedback thread from the 11/20 patch. Several Dev posts explaining the problem. I already copied them into one thread on this subject.

I'm not doing it again.

11/20 was bad. 11/27 is just utterly unplayable.

In closed beta this ran with 40 fps on an e8400 with 12GB of ram and a GTX 560. All of which surpass their minimum spec quite nicely.

Edited by Bagheera, 28 November 2012 - 10:22 AM.

[TehArgz]

Bagheera, on 28 November 2012 - 10:21 AM, said:

Perhaps not, but it IS their fault for misleading people to believe the game would run on Core2Duo machines:



Specs taken from here:

http://mwomercs.com/...eveloper-update

Pretty sick and tired of hearing people blame us for PGI's inability to support their own published minimum spec.

PGI either needs to fix the problem, or change the published spec with a great big apology. It is long past time for this to happen.

Also no, CryEngine version is not the problem. There was no engine version update on 11/20. MW:O went to 3.4 before that and ran just fine. Not the peak of performance for me, but just fine. Go back and read through the performance feedback thread from the 11/20 patch. Several Dev posts explaining the problem. I already copied them into one thread on this subject.

I'm not doing it again.

11/20 was bad. 11/27 is just utterly unplayable.

In closed beta this ran with 40 fps on an e8400 with 12GB of ram and a GTX 560. All of which surpass their minimum spec quite nicely.

Minimum spec is the minimum spec to load the software. Performance will be minimal. Go load up any version of windows with min specs, tell me how well it works.

Again, I sympathize with the OP, and your specs are slightly better then mine. Similarly I have experienced degraded performance progressively with the last few patches. However I understand that my specs are near enough minimum that I WILL HAVE PROBLEMS. Additionally I do everything that I can to give my system a fighting chance to run this game as smoothly as possible. I don't have any reason to believe the OP has done so much as close his browser window in an effort to help his system, and for that part of it I have 0 sympathy.

edit: furthermore the paragraph directly below the specs on the link you posted.

Quote

Right now a duo core system is our minimum spec machine but it is also our main focus of concern. It is playable on those specifications and I have tested it myself but it is currently very much a minimum spec type of experience running on low-detail settings. It’s obvious that a Quad core system is the key as even the earliest Core 2 Quad systems run the game very well and it is our goal (since there are still so many out there), to optimize the Core 2 Duo systems to run much faster.

bolded are my emphasis.

Edited by TehArgz, 28 November 2012 - 11:20 AM.

[WardenWolf]

I may go home and install MWO on an old dual-core AMD setup to see if I can recreate any of these problems (though obviously I won't be able to check for a dip in performance vs previous patches). Niko, if I find anything in regards to task manager I will PM you.

[Col Forbin]

I have some system advice that may help you get better performance for all games; one is easy, one a little more difficult.

1) Use GameBooster. This hands down a no-brainer. Setup is a breeze, but a little hands on tweaking will yield better results.
Basically, it is a program that will shut down unnecessary (for gaming) programs and services running on Windows that eat up CPU cycles. You can set it to automatically do this when you start a game, and it will automatically restore everything when you exit the game. Oh, and it's FREE.

http://game-booster.en.softonic.com/


2) Overclocking. Some processors won't allow you to do this, but with a $20-30 fan/heatsink and a little elbow grease, you could probably get a halfway decent overclock that will affect your performance positively. Proper case airflow is needed for this and you might need to add some $5 case fans to achieve this....

[puratech]

Same problem on similar setup. Core2Duo @ 3.5ghz, gf260gtx, 4gb ram. I have near identical framerates to you, it was awesome and playable 2 patches ago, then fps has left.

I've tried fresh MWO install, the Windows7 install is only a couple of months old anyway, closed all non essential programs, turned off unimportant services and it is very marginally better like 8-9fps rather than 5-6. CPU is just constantly maxed out ingame appears to the the bottleneck. I appreciate my hardware isnt amazing, but it runs other games I want to play fine and it ran this one well before that patch.

My friend who also doesnt play since said patch cant play on his q6600 laptop anymore very well, but works alright on his i7. It seems that it needs more processing power than dual cores and maybe stock quads can provide.

Did that patch (110mb i think) change to a different version of the CryEngine then?

Edited by puratech, 28 November 2012 - 12:32 PM.

[Col Forbin]

This game is such a beast right now, that in order for me to not experience any CPU bottlenecking I have my i5 2500K overclocked from 3.3Ghz to 4.95Ghz.... I am playing on the highest graphics settings....