1
It was admitted during the height of the HUD bug, it was noted that hand optimizations were used and not tested thoroughly enough, causing the massive annoyance of a missing or generally non-properly working HUD.
When done correctly, the results are great.... but when done w/o testing the consequences, it causes major unintended side effects.
The memory leak problem still exists in MWO. I'm not sure if it's a memory leak or memory corruption... but whatever the problem actually is, it's bad. I moved from XP to Win7, hoping for improvement in MWO stability, but it's gotten far worse. I noticed a major difference back a while ago, from moving from WIn95 to 98, and 98SE to 2K. The differences are much more noticeable when you feel it. The thing is, Win7 is not the problem, but MWO is exacerbating the problem due to my OS change. Whereas Win7 is a lot more sensitive to changes over XP (like 2K was over 98SE), MWO has accelerated weirdness in file corruption AND memory oddities (like Windows and other apps acting strangely). I should probably run a few memory tests in the meantime (and I'm sure the hard drive isn't acting up - there would be more obvious signs), but MWO is doing a really poor job of it.
With that said, many of those godawful crashes involving "fread could read X of 0 bytes", it is because the game tries to extract some data, but manages to fail. In reading the logs, I never understood why EVERY file is opened (outside of security reasons) and then closes when MWO is closed. This "memory corruption" that MWO seems to cause on its own does so many other things that make or break stuff in Windows, and it would not surprise me if there was stuff corrupting the MWO dev's computers due to it. It may be subtle (just one byte changed, especially while downloading MWO files) but sometimes it's enough to take down Windows or some other app in the background.
Just remove any hand optimizations (meaning full assembly) related to file handling in MWO, that's all I'm asking. It never ceases to amaze me how MWO and the frontend seem to go on its merry way with corrupted files, only to self crash early and often. Yet, when MWO has not been run during a session, and the MWO Repair Tool is in use, so many files (particular Objects.pak due to obvious reasons) gets corrupted so trivially easy. It's almost as if you're tempting fate, when the only thing that works consistently well is the MWO Repair Tool ONLY when MWO has not been run previously (because, everything after MWO runs, including the MWO Repair Tool, behaves strangely).
No, this does not need a support ticket, because frankly the entire file corruption thing happens w/o rhyme or reason to anything. WHAT IS CLEAR from my experience is that once I have played MWO, the only way I can properly maintain my system is to IMMEDIATELY reboot or shutdown and hope MWO doesn't take windows with it. This is getting worse before it gets better, and PGI needs to address it at some point because it would not surprise me if PGI's development poops on itself because of this serious bug that never gets resolved. It happens with NO OTHER GAMES/APPS/STUFF... it's SPECIFIC TO MWO. There's no other thing that generates such bad behavior (Firefox at times is bad, but not MWO terribad).
So please fix this for the good of the game or don't be surprised if it comes back to haunt you.
Edited by Deathlike, 13 December 2013 - 12:27 AM.
