16 replies to this topic

[tuffy963]

Since the patch, I have made several attempts to launch and rejoin games in the new Atlas AS7-S. All attempts result in a CryEngine error and the game crashing to desktop. I can play my other mechs with no problems.

[WM Wraith]

Same - turned off PostAA, crashed. Now crash out of game to desktop every time I press OK to login.

[Alexander Garden]

tuffy963: Can you provide a screenshot of the error, or describe its contents? This crash occurs when starting a match, when re-joining a match, or both? Are you able to enter the Testing Grounds without issue?

WM Wraith: There is currently a known issue when turning PostAA Off while running in Windowed and Full-Windowed under certain resolutions. Regarding the log-in crash, is there any error being reported?

[Mal Isbad]

Mechbay area loads, lauch the round, it searches for the game, finds it then goes to the loading screen (the one with the game play tips), and then crashes to desktop. No error messages generated. I run MWO as administrator.

Basically, I can't play the game.

[WM Wraith]

Alexander Garden, on 21 October 2014 - 11:43 AM, said:

tuffy963: Can you provide a screenshot of the error, or describe its contents? This crash occurs when starting a match, when re-joining a match, or both? Are you able to enter the Testing Grounds without issue?

WM Wraith: There is currently a known issue when turning PostAA Off while running in Windowed and Full-Windowed under certain resolutions. Regarding the log-in crash, is there any error being reported?

Alexander - Not getting any warning or error message - just drops straight out of client back to desktop. No error. Repair tool did not fix. Can't log in. Get to the login screen, enter my password, hit OK to continue to launch game, then simply client goes away and I am at the desktop again Any advice on how to get client to run again?

My screen resolution was custom, running eyefinity setup under AMD....5040 x 1050

[Inveramsay]

I had the same problem with no warning but all of a sudden I was back at my desktop. I managed to log in again and rejoin at least but even so I still lost a minute in the match that may have been the end of me if it wasn't for it being right at the start

[DEATHAS]

Hello all!

Have same Problem since the Hotfix.
Got dumped to Desktop several times after Map Loading screen:

CryEngine Error
FRead did not read expected number of byte from file, only 128 of 0 bytes read

Testing Grounds is working. All of a sudden problem was gone, played 2h, now I got the CTD again.

=> FRead issue resolved by using the repair tool! Thx a lot!

Edited by DEATHAS, 23 October 2014 - 03:50 AM.

[hideyourkids]

Same error here. I login, it starts connecting then crashes, no error message or anything. I am running the repair tool now.

[Darth Futuza]

DEATHAS, on 21 October 2014 - 02:11 PM, said:

CryEngine Error
FRead did not read expected number of byte from file, only 128 of 0 bytes read

WTF? It read 128 bytes of non existing bytes? Oh dear.

[Koda Shy]

im just getting unknown error and network error, game crashes and then cant log back in. was fine before patch, I was able to finish one match then apon exit it crashed again. saying unknow error.
took several attempts to log back in.............. I am running full window, it may be the the new rewards spam in game, I don't know.

Edited by Koda Shy, 21 October 2014 - 08:54 PM.

[Mal Isbad]

I'm getting sudden crashes to desktop a lot of the time. It appears to happen with the TBR-S.

[Milandro]

I am having the cry engine 128 of 0 error as well. Testing grounds/mech lab etc works fine, it errors when loading into a match

[Rebel Ace Fryslan]

Allot more CTD's after patch 5-10 times in 3hours.

Therealways seem to be register issues in the logs.
Get it into gears, your still hiring so get some good code-slammers and plz a good database engineer.

Spoiler

<18:58:12> Material objects/mechs/skins/polygon_a/stormcrow_polygon_a not found during Unregister
<18:58:12> Material objects/mechs/skins/norn_a/centurion_norn_a not found during Unregister
<18:58:12> Material objects/mechs/skins/founders_a/atlas_founders_a not found during Unregister
<18:58:12> Material objects/mechs/skins/norn_a/atlas_norn_a not found during Unregister
<18:58:12> Material textures/mechs/cockpit/cockpit_weapondoor not found during Unregister
<18:58:12> Material objects/mechs/skins/heromechs/drg_fang_flame/dragon_drgflame_a not found during Unregister
<18:58:12> Material objects/mechs/skins/norn_a/centurion_norn_a not found during Unregister
<18:58:12> Material objects/mechs/skins/founders_a/hunchback_founders_a not found during Unregister
<18:58:12> Material objects/mechs/skins/hotrod_a/timberwolf_hotrod_a not found during Unregister
<18:58:12> Material objects/mechs/skins/vagabond_a/dragon_vagabond_a not found during Unregister
<18:58:12> Material objects/mechs/skins/invasion_a/summoner_invasion_a not found during Unregister
<18:58:12> Material objects/mechs/stalker/body/stalker_body not found during Unregister
<18:58:12> Material objects/mechs/spider/body/spider_body not found during Unregister
<18:58:12> Material objects/mechs/jagermech/body/jagermech_body not found during Unregister
<18:58:12> Material objects/mechs/stormcrow/body/stormcrow_body not found during Unregister
<18:58:12> Material objects/mechs/locust/body/locust_body not found during Unregister
<18:58:12> Material objects/mechs/direwolf/body/direwolf_body not found during Unregister
<18:58:12> Material objects/mechs/kintaro/body/kintaro_body not found during Unregister
<18:58:12> Material objects/mechs/raven/body/raven_body not found during Unregister
<18:58:12> Material objects/mechs/hunchback/body/hunchback_body not found during Unregister
<18:58:12> Material objects/mechs/kitfox/body/kitfox_body not found during Unregister
<18:58:12> Material objects/mechs/skins/norn_a/atlas_norn_a not found during Unregister
<18:58:12> Material textures/mechs/cockpit/cockpit_weapondoor not found during Unregister
<18:58:12> Material objects/mechs/cicada/body/cicada_body not found during Unregister
<18:58:12> Material objects/mechs/cataphract/body/cataphract_body not found during Unregister
<18:58:12> Material objects/mechs/awesome/body/awesome_body not found during Unregister
<18:58:13> could not free all buffers from CDevBufferMan!

[ollo]

Darth Futuza, on 21 October 2014 - 05:31 PM, said:

WTF? It read 128 bytes of non existing bytes? Oh dear.

Yeah, it should be happy to find data!

[Darth Futuza]

ollo, on 22 October 2014 - 09:14 AM, said:

Yeah, it should be happy to find data!

Unless its spilling over and reading somebody elses. That's stealing, and its punishable by unsafe memory mallocs and associated consequences.

[Alexander Garden]

Hey everyone,

Apologies for the inconvenience. The Fread errors specifically are usually due to some file corruption as a result of the patching process, so a run (or two) of the Repair Tool located in the \MechWarrior Online\Bin32 file should knock that error out.

In the meantime, I'm currently looking into the more general crashes.

[DEATHAS]

Hello again and many thanks for the quick answers!

The FRead error is now resolved!
You were right, I ran the Repair Tool, the file object.pak was inconsistent.

Runs like a dream now.

Thank you very much for helping out an addicted MWO fan!
Hope you guys resolve any other issues soon and cya in game!

Cheers

Edit: I saw this from https://twitter.com/russ_bullock, which might be helpful to you guys:

Bishop Steiner
BTW, totally separate, Nvdia update 344.48 seems to be HUGE for fixing CTDs and such. Good post PGI!

Good Luck and cya!

Edited by DEATHAS, 24 October 2014 - 04:29 AM.