73 replies to this topic

[EternalCore]

Elkarlo, on 21 November 2012 - 01:41 AM, said:

Srry Eternal Core didn't saw it too. Win7 x64 Pro..

Would be nice if you look into the Memory Issue, i had heavy trouble with my Gigabyte boards,
which was fixed in the last (beta) bios.
And your Memory is NOT on the tested memory page at Gigabyte. Had same Issues got G.skill Memory which was nearly the same and it was troublesome ( they testet the slower C9 1333 Mem yours). You should have the FF Bios, especially because the Fix is a Be Quiet be Cool Fix... which may cause Performance or Memory Issues.

And 1333er Memory ist often 1666er Mem which didn't pass the Specs...so a Memtest86+ should be run.

It's only a guess of a Trap i fall into too often enough. System Runs fine and suddenly with more Memory used it breaks nearly down... but still plenty of mem free... Gigabyte have Issues with 4 Banks using till newest Bios ( But never officialy admitted it) and maybe one Module is Bad when under Heavy Duty and it passed the Check because most Manufactorer Checks don't do 1 Hours testings and the warmer a Memory Cell is the more likely to fail it is.

My bios is already up to date... And My memory has been thoroughly tested and setup to remove all possible flaws and obtain speeds needed to eliminate any bottle necks without degradation.

[Quad Ace]

coolnames, on 21 November 2012 - 12:36 AM, said:

maybe include a synopsis of what you want viewers to determine after comparing both videos?

Indeed, because while I did notice a lower frame rate on the first video, it was hard to not pay attention to horrible heat management, and questionable decision making.

[EternalCore]

Quad Ace, on 21 November 2012 - 02:06 AM, said:

Indeed, because while I did notice a lower frame rate on the first video, it was hard to not pay attention to horrible heat management, and questionable decision making.

It's hard to manage your heat when your having really Low FPS and also FPS Drops...

Edited by EternalCore, 21 November 2012 - 02:12 AM.

[Demon Horde]

DrAwkward, on 21 November 2012 - 12:38 AM, said:

Yeah, my setup isn't too different from EternalCore's and I'm still averaging 35-65 FPS.

crap i wish i could get 35-65 ... currently getting 15-25 avaerage , highs in 30's and lows in 10's

[BeezleBug]

Quad Ace, on 21 November 2012 - 02:06 AM, said:

Indeed, because while I did notice a lower frame rate on the first video, it was hard to not pay attention to horrible heat management, and questionable decision making.

Off topic
This is about the FPS after this patch not about the players skill´s. Who cares how he play.
There are many people out there have the same problem. My hardware is much lower and i have the same fps, sometimes higher.
So there is someting wrong with this game. Thats all.
http://mwomercs.com/...eedback-merged/

[Ilwrath]

If the game runs worse after a patch and you have done zero changes with your
pc setup, well then it is the patch that broke the game. How hard can this be to understand?

The devs ****** up. Its that simple. Now they need to fix it and we don't need lol-kids
preaching ******** about peoples computers. Do not talk about stuff you don't understand.

[Adrienne Vorton]

seriously, i want the previous engine and my userconfig back it looked tons better while running way smoother...

[DerSpecht]

Reinstall directx from scratch... issue solved

[Soulscour]

My only framerate issue is when the memory leaks happen which is quite frequent.

[Joseph Mallan]

I been playing the game at those rates for the last 2 months! I even had a K/D of 2.96 before the 4 man team Nerf . Game looks fine to me. You just need to use Missiles more.

[EternalCore]

DerSpecht, on 21 November 2012 - 03:29 AM, said:

Reinstall directx from scratch... issue solved

That only solves issues if the directx files are either missing or corrupt/damaged... Which mine are all there and intact.

Soulscour, on 21 November 2012 - 03:55 AM, said:

My only framerate issue is when the memory leaks happen which is quite frequent.

Yea I Found a Major UI Memory leak 2 patches ago which is still yet to be fixed....
The Memory leak Causes issues like this: http://mwomercs.com/...-a-peek-inside/

Edited by EternalCore, 21 November 2012 - 09:05 PM.

[Insidious Johnson]

I'm with ya EC, I just posted a performance issue in patch feedback. I get frame rate drops with missiles of any kind are directed at me, to as low as 8 fps on ultra high and 15 fps on low. I normally run 60+ on ultra high. Just started this patch. Only answer is it is this patch that did it. Quit telling BETA testers to take a month off. PGI is getting the feedback it needs. It isn't keeping pace with the demands created by their own hands for new and constant bug fixing.

[Arthur Heath]

lol I was pretty excited to see the game look so nice watching the 1st video. Much nicer than what mine has turned into, my fps seems to be on a wave cycle it pulses slowly from 5fps - 30fps. Just a steady rolling surge up and down, some almost locking spikes here and there. I even turned all the graphic setting down to "Atari" setting. I figure at the rate of deterioration I will be out of luck in 3 more patches at best. Considering my actual account is a leg. founder this will be Bad...I am bad.

[Roni]

i7 3970x with 2 gtx 690 cards in sli. On graphics heavy games its consistently 65+ fps on max settings.
In Mwo the graphics arn't that great but it goes to even 25-45 during activity, so it's definately something wrong on their end needs to be optimized or fixed..
On the bright side once it's fixed it will only get better.. Cough.. i mean return to what it actually should be.. The 4 fps bug hasn't happened in a while though.

[JebusGeist]

Reoh, on 21 November 2012 - 12:51 AM, said:

I think the reason you're not hitting anything is because you couldn't even aim properly at a stationary target. You then overheated while overextended and got beat down for playing in a risky manner. While you did encounter the occasional overheat HUD bug, you were basically already dead at that point anyway and your mech just hadn't cottoned on to it yet. If your HUD had come back as it normally does then you'd still have died anyway.

Framerate directly affects the ability to judge cursor positions.
You realise that at 11-15fps, compared to say, 24-30fps, you have to seriously adjust the way in which you move your mouse, as the game will poll your mouse movements faster than it actually renders them. It will take twice as long to visually confirm that "yes, im now pointing at thier center torso" which generally means you will overshoot your target. This gets progressively harder to compensate for as your framerate drops, all the way down to 1 or less frames per secont, at which point you will have only slightly more precise movements than a blind man would.

[EternalCore]

The hot fix that they implemented has done nothing to fix the FPS for me....

[Taizan]

I guess I'm in the same boat with the FPS. Every match where I don't get disconnected its either one of the three:

1) Normal game start
2) Power down bug (yellow screen remains, no HUD)
3) Black screen

If its 1) again three things may happen:

1) All systems nominal 45 - 55 FPS. Yay! i can play!
2) 4 FPS bug
3) Wonky FPS dropping down to around 10-15 FPS, if I "look" away from any other mechs or structures, it goes up a bit to 25 FPS (the regular FPS difference when having mechs/objects in sight).

The only thing I noticed and thought was really peculiar is that when I die and I go into spectator view all FPS issues sometimes seem to be gone, not like in the first video.

In the meantime I'm so happy when I can play a match at all, I don't even care at all how the match is going to end up.

Edited by Taizan, 24 November 2012 - 03:39 PM.

[Laokin]

MoonUnitBeta, on 21 November 2012 - 12:41 AM, said:

I'm getting around 40fps....

I don't know why you're having issues. I'm running 550ti @ 1680x1050. Maybe update drivers? Otherwise if it was the patch, it'll get fixed. Everyone's pulling old man gramps on PGI because they were "promised"(? as if things are subject to change..) this and that, and that the patch is bad... give it some time. copy your dxdiag and e-mail to them so they can sniff out the problems.

Edit: settings are on high, but my shadows slider is at the min. I don't notice a difference with it on graphically, same with fxaa or w/e that edge smoothing stuff is called nowadays... too many abbreviations for me to care about - the point is, you know what I'm talking about .

Anyways, runs nice. I only got the 4fps bug a few times so far.

If the patch IS bad [which it is] then what is giving it "time" supposed to do exactly?

It's certainly not going to change the focus of next patch unless I voice how unpleased I am with the current patch -- including the reasons why.

This is called a feedback.

Here is the problem with feedback in the modern world;

There exists three kinds of people when Giving[G] feed back, and two types of people when Receiving[R] feedback;

People G-A. Who give feed back whether it's good or bad, unbiased feedback.
People G-B. Who give phoney feedback and complain about things that don't exist.
People G-C. Who give ungodly biased positive feedback to largely negatively received implementations.

People G-C, commonly use the lines "Give it time" or So and So is exceptional, I love every bad change they've made for the game because it was made by "X" and I love them.

People G-B, commonly use the lines "BlahXblah needs a nerf because blahYblah is better" when ultimately they just haven't figured out how to play yet.

People G-A, commonly produce threads of both types but consider all the rules of the game as well as their personal opinions in a rational and mature way.

Then there are 3 different types of receivers of feed back.

People R-A. People who understand when feedback has solid merit, or when feedback is disproportionate to the core of the game.

People R-B. People who ignore all the negative feedback their product receives while glorifying the positive feed back, often times embracing People G-C.

You will see games like Tribes:Ascend -- their developers are part of "People R-B" which is why their game is crashing and burning hard as we speak.

In fact, all developers who are from the mind of People R-B fail inevitably to provide a really entertaining product.

Why is this so? Because they pick and choose which feedback to listen to based on the concept of not compromising their "original vision" even if the original vision is fundamentally flawed and doesn't work.

A AAA title can never succeed without a solid "vision" for the product. Laid out BEFORE all the hard work goes into making the product, because if you are forced to changed your vision mid product it will suffer from the core missteps of the original vision unless you have the luxury to essentially start over.

F2P crowd funded projects cannot afford to change their vision mid way. Once people are playing it, making erratic changes will upset and segregate players -- so much so, that the players themselves have no clear indication of what the game is really trying to be, often times resulting in a tug of war over the direction the game should take.

Developers then have to try to converge those differing opinions which often times succeeds at driving the final nail in the proverbial coffin, since it's likely to not please either side of said tug of war -- which results in a profuse bleeding of players.

If you'd like examples of both devs that understood this principle, or devs that failed to acknowledge this principle, here are some that follow;

Understand this principle;
Riot Games [League of Legends]
Valve [Half-Life Series]
Blizzard [War/Starcraft/Diablo Series]

Didn't understand this principle and failed because of it;

Flagship Studio's [Hellgate: London]
Hi-Rez Studio's [Global Agenda, Tribes: Ascend]

And it's looking like we're going to be adding PGI to this list with MechWarrior Online.

[Click]

Posting videos demonstrating it is useless. Making separate threads from performance feedback is useless. Thinking your hardware is the problem when you're easily above minimum specs is dumb. From a previous post I made:

Quote

This is a software problem, for the love of god just realize that already and let the devs work. My advice is do what I did: drop the game for a while, just keep checking on progress regularly.

[Fiachdubh]

Internet too slow too watch the videos at moment but I seem to have opposite experience of many. In closed beta I had an fps of 11 to 18 and played the game no problem. Post open beta I have an fps between 30 and 50.

Cinema and TV are traditionaly 24 fps (new fancy technology is raising that)
HALO 3 and many next gen console games are locked at 30 fps

At around 20 fps the eye sees it as running smoothly, with low resolution and blurry picture it can go much slower with sharper images such as games it needs to be a bit higher but if you have got 30 fps in game it is perfectly good and anything above is just extra icing. It is lag that is the real problem in game not fps (once you're staying 30+ of course).

Edited by Fiachdubh, 24 November 2012 - 04:32 PM.