399 replies to this topic

[AdmiralBeran]

[Error] [UIAction] HUD (0): UIElement does not have object _root.mcMain.mcCurrentLayout.mcSpecHud.SetCount

Spoiler

Intel Core i7 950 @3.07Ghz, 8Gig RAM, windows 7, ATI HD5830 with current drivers

[Pz_DC]

Right before I post it got 4 games with 3 (!!!) dc... Its unplayable atm... All the time has same type of error, but 2 times it closes too fast before I as able to read it and last time it stay for longer time - "cry engine error - memory allocation for 44698328 bytes failed". Wtf have You done with this game guys? Is it bad 1st aprils fool's joke?.. Looks so - "we will give players a lot of new content but they will not be able to try it!.."

Edited by MGA121285, 04 April 2013 - 01:37 AM.

[Fides]

• Was any error message provided with the crash, if so, which? - Nope no error message, just straight crash
  
• Where in the game or menus did the crash occur? - Have had this in several places now, all ingame not in mechlab, just launched in a drop and it bombs to desktop, midgame, same, or end of match and bam it crashes to desktop.
  
• What steps had been taken prior to the crash occurring? - Well its a random occurrence so when I crash I restart my client and get a fresh invite into the group.
  
• Does the crash re-occur for you if repeating those same steps? - One guy in our guild crashed 12 times at the end of every match, so it closes your client down and you have to restart anyway. He still crashed at the end of every match. I did find when he crashed, I stopped crashing.
  
• What are your video settings, did you change them since last patch? Recently changed my drivers because of the polygon bug, to the latest ones, it was crashing before I changed them and still crashing after I changed them

Edited by Fides, 04 April 2013 - 05:51 AM.

[Karl Split]

Also myself and several of the unit still have the match freeze bug. This is where the client freezes dead and is completely unresponsive. Alt tabbing in and out of client will not fix it. HOWEVER if you ctrl alt del and bring up task manager the client miraculously unfreezes and you can carry on the match.

Personally this smells like a game resource being locked by the OS bug, Ive had to fix a few in my time and they are an absolute PITA to find. Im running win7 64bit ultimate or whatever the most expensive version is.

[CutterWolf]

Since the last two patch's (but a lot more with since the last patch) I have had the following along with several of my team mates:

1. Random hard vid lockup at end of match. Have to hit alt F4 to get out of the game and then mech stays locked in that game for several mins.

2. Random crash to desktop during game play.

3. Game will spawn us into a conquest match even tho assault match type was selected. Once in the that conquest match for 3 to 4 mins a screen will appear showing the "Match not found" screen. Hitting "enter" clears that screen and you can keep playing as normal. Once match is over and you return to the lab you can see that the game type selected was "assault"

4. Mini-map back ground is kaleidoscopic in color.

5. Mini-map has no background at all, does not display friend or foe targets, or grid lines, and directional arrow stays in a fixed strait ahead.

6. Mini-map spins 180 degrees back and forth non stop. Compass heading also spins with it.

7. Mini-map shows, grid lines, friend and foe, and directional arrow works but you have no friend or foe indicators over any mechs on your screen. You can not get any info on any mech what so ever.

System: Win 7 64bit, Intel i5 3570K, 16gig Ram, Nvidia GTX 660 Ti, Running game in "very high" settings

Edited by CutterWolf, 04 April 2013 - 08:46 AM.

[Taron]

Well, let me give the PGIs an overview. Thats the real issues we have since that patch:

1. Not working map/minimap
2. No IFF-Function
3. Crash to Mechlab
4. Crash to desktop
5. Not working Heat-View
6. Way to bright Night view
7. Multicolor Minimap
8. Damage from "Ghost-Mechs"

Edited by Taron, 04 April 2013 - 10:00 AM.

[Space Odin]

I played a game of conquest on caustic valley. When I went to the gamma point as soon as I started capping I crashed to desktop no error message. Since my brother was playing with me I was watching him play to see how the match played out.

Three of our other teammates went to cap the gamma point, each person that made contact with it either disconnected or stopped responding and ran off the map and died, which makes me assume they crashed.

Im not gonna bother posting my system specs since it happened to 3 other people in the same game.

Edited by Space Odin, 04 April 2013 - 10:06 AM.

[Moscito]

• Was any error message provided with the crash, if so, which?

CryEngine Error - *** Memory allocation for 7824100 bytes Failed
CryEngine Error - *** Memory allocation for 11141848 bytes Failed

• Where in the game or menus did the crash occur?

just before entering the battlefield

• What steps had been taken prior to the crash occurring?

changing Mech Loadout

• Does the crash re-occur for you if repeating those same steps?

Yes...very often

• What are your video settings, did you change them since last patch?

All on High - No

• What are your System specs?

AMD FX Quad Core 4100
4 GIG Ram
Nvidia GeForce GTX 650

[Morang]

PGI - you sick!

Each gaming session attempt results in soon ragequit. It hangs terribly.

Here just one example of task termination report:


Problem Event Name: AppHangB1
Application Name: MWOClient.exe
Application Version: 3.4.1.4418
Application Timestamp: 5159ffd5
Hang Signature: d11b
Hang Type: 2048
OS Version: 6.0.6002.2.2.0.256.1
Locale ID: 1049
Additional Hang Signature 1: a3586038613f4317d9d4b6b51aed45df
Additional Hang Signature 2: 7617
Additional Hang Signature 3: be55a196c16458b3841e877f88b37bd1
Additional Hang Signature 4: d11b
Additional Hang Signature 5: a3586038613f4317d9d4b6b51aed45df
Additional Hang Signature 6: 7617
Additional Hang Signature 7: be55a196c16458b3841e877f88b37bd1

[Lugh]

"As for the remaining Black Screen issue we ask that you file a support ticket and give as much detail to help us isolate the underlying cause. We also continue to add more and more telemetry in the background on a number of these issues that help us to identify their severity and where they occur."

You have three months of data from me proving it isn't a connection issue. Unless you are admitting that you're data center guys have no idea what they are doing and are losing packets on your internal network.

That is 100% on YOU! Not anyone else.


To prove it again for you
>pathping mwomercs.com

Tracing route to mwomercs.com [70.42.29.74]
over a maximum of 30 hops:
0 Highlander.hsd1.de.comcast.net. [192.168.1.111]
1 192.168.1.1
2 76.124.88.1
3 te-7-4-ur01.uofdelaware.de.panjde.comcast.net [68.85.79.201]
4 te-9-1-ur02.limestonedr.de.panjde.comcast.net [68.86.209.109]
5 te-9-3-ur01.limestonedr.de.panjde.comcast.net [68.85.35.37]
6 xe-2-0-2-0-ar03.coatesville.pa.panjde.comcast.net [68.86.209.77]
7 ae-8-0-ar03.newcastle.de.panjde.comcast.net [69.139.193.213]
8 pos-5-14-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.95.145]
9 be-11-pe04.ashburn.va.ibone.comcast.net [68.86.84.206]
10 xe-11-2-0.was10.ip4.tinet.net [173.241.131.61]
11 xe-1-3-0.tor10.ip4.tinet.net [141.136.110.5]
12 internap-gw.ip4.tinet.net [77.67.71.62]
13 border1.te7-1-bbnet1.tor001.pnap.net [70.42.24.132]
14 * * *
Computing statistics for 325 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Highlander.hsd1.de.comcast.net. [1
92.168.1.111]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 10ms 0/ 100 = 0% 0/ 100 = 0% 76.124.88.1
0/ 100 = 0% |
3 12ms 0/ 100 = 0% 0/ 100 = 0% te-7-4-ur01.uofdelaware.de.panjde.comcast.net [68.85.79.201]
0/ 100 = 0% |
4 12ms 0/ 100 = 0% 0/ 100 = 0% te-9-1-ur02.limestonedr.de.panjde.comcast.net [68.86.209.109]
0/ 100 = 0% |
5 11ms 0/ 100 = 0% 0/ 100 = 0% te-9-3-ur01.limestonedr.de.panjde.comcast.net [68.85.35.37]
0/ 100 = 0% |
6 15ms 0/ 100 = 0% 0/ 100 = 0% xe-2-0-2-0-ar03.coatesville.pa.panjde.comcast.net 68.86.209.77]
0/ 100 = 0% |
7 15ms 0/ 100 = 0% 0/ 100 = 0% ae-8-0-ar03.newcastle.de.panjde.comcast.net [69.139.193.213]
0/ 100 = 0% |
8 19ms 0/ 100 = 0% 0/ 100 = 0% pos-5-14-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.95.145]
0/ 100 = 0% |
9 17ms 0/ 100 = 0% 0/ 100 = 0% be-11-pe04.ashburn.va.ibone.comcast.net [68.86.84.206]
0/ 100 = 0% |
10 17ms 0/ 100 = 0% 0/ 100 = 0% xe-11-2-0.was10.ip4.tinet.net [173.241.131.61]
0/ 100 = 0% |
11 49ms 0/ 100 = 0% 0/ 100 = 0% xe-1-3-0.tor10.ip4.tinet.net [141.136.110.5]
0/ 100 = 0% |
12 46ms 0/ 100 = 0% 0/ 100 = 0% internap-gw.ip4.tinet.net [77.67.71.62]
0/ 100 = 0% |
13 47ms 0/ 100 = 0% 0/ 100 = 0% border1.te7-1-bbnet1.tor001.pnap.n
et [70.42.24.132]

Trace complete.

C:\Users\Shawn>

Using the pathping command you can see zero packet loss all the way to you.

C>net stat
The syntax of this command is:

NET
[ ACCOUNTS | COMPUTER | CONFIG | CONTINUE | FILE | GROUP | HELP |
HELPMSG | LOCALGROUP | PAUSE | SESSION | SHARE | START |
STATISTICS | STOP | TIME | USE | USER | VIEW ]

>netstat

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:5354 Highlander:56796 ESTABLISHED
TCP 127.0.0.1:27015 Highlander:56835 ESTABLISHED
TCP 127.0.0.1:27015 Highlander:57134 ESTABLISHED
TCP 127.0.0.1:55321 Highlander:55322 ESTABLISHED
TCP 127.0.0.1:55322 Highlander:55321 ESTABLISHED
TCP 127.0.0.1:56796 Highlander:5354 ESTABLISHED
TCP 127.0.0.1:56835 Highlander:27015 ESTABLISHED
TCP 127.0.0.1:57134 Highlander:27015 ESTABLISHED
TCP 127.0.0.1:60611 Highlander:60612 ESTABLISHED
TCP 127.0.0.1:60612 Highlander:60611 ESTABLISHED
TCP 192.168.1.111:58140 a23-57-16-60:https CLOSE_WAIT
TCP 192.168.1.111:60627 a23-3-13-217:http TIME_WAIT
TCP 192.168.1.111:60630 208.71.123.66:http TIME_WAIT
TCP 192.168.1.111:60631 208.71.123.66:http TIME_WAIT
TCP 192.168.1.111:60633 OCSP:http ESTABLISHED
TCP 192.168.1.111:60635 addons-versioncheck-single2:https TIME_WAIT
TCP 192.168.1.111:60637 OCSP:http TIME_WAIT
TCP 192.168.1.111:60639 70.42.29.74:http CLOSE_WAIT
TCP 192.168.1.111:60640 a23-67-251-66:http ESTABLISHED

>tracert 70.42.29.74

Tracing route to 70.42.29.74 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 31 ms 29 ms 30 ms 76.124.88.1
3 13 ms 9 ms 10 ms te-7-4-ur01.uofdelaware.de.panjde.comcast.net [6
8.85.79.201]
4 11 ms 11 ms 9 ms te-9-1-ur02.limestonedr.de.panjde.comcast.net [6
8.86.209.109]
5 10 ms 12 ms 10 ms te-9-3-ur01.limestonedr.de.panjde.comcast.net [6
8.85.35.37]
6 13 ms 12 ms 11 ms xe-2-0-2-0-ar03.coatesville.pa.panjde.comcast.ne
t [68.86.209.77]
7 13 ms 13 ms 12 ms so-10-1-0-0-ar03.newcastle.de.panjde.comcast.net
[68.86.208.125]
8 18 ms 19 ms 18 ms pos-5-15-0-0-cr01.ashburn.va.ibone.comcast.net [
68.86.94.249]
9 15 ms 14 ms 16 ms be-11-pe04.ashburn.va.ibone.comcast.net [68.86.8
4.206]
10 14 ms 16 ms 14 ms xe-11-2-0.was10.ip4.tinet.net [173.241.131.61]
11 45 ms 45 ms 45 ms xe-1-3-0.tor10.ip4.tinet.net [141.136.110.5]
12 40 ms 39 ms 40 ms internap-gw.ip4.tinet.net [77.67.71.62]
13 43 ms 41 ms 41 ms border1.te7-1-bbnet1.tor001.pnap.net [70.42.24.1
32]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Everything is sub 50ms. The only obscured parts of the route in tracert are on the canadian side at about your network.

Edited by Lugh, 04 April 2013 - 12:49 PM.

[Taron]

Well, what ever: You can say what you want, but this last patch was a step back:

it's more unstable now, some older bugs are back, the new modes on heat view or night view are.... stupid. As i said.... this patch was a clear step back.

[Sammael55]

CryEngine Error - "FRead did not read expected number of byte from file, only 128 of 0 bytes readashesI havent been able to play a game yet. Crashes everytime I try and launch,

[Mothykins]

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

It'll enter the map loading screen before crashing.

[miabenet]

Greetings:

I hope you can help me in regards to the latest patches from tuesday. First my specs which I am not computer savvy:

i7 Vista
8 gig ddr 3 ram
ATI Radeon HD 5700
Anything else I have no clue

I have 2 issues since patch:

1) I go to click "launch" with the trial mech and I get the pretty picture and loading bars on the world but then get booted back to the launch screen with the mech "in game"

2) Once in awhile I will get booted out of game entirely.

Both instances are sudden and the game worked flawlessly before it.

PS: I dont know if it is relevant but there is a mech missing from the 4 listed and in the box it reads: "@ml_Unknown"

PPS: Please help because I have been waiting for this game like nobodys business

Thank you very much and have a great day

[frag85]

Frozen

• Was any error message provided with the crash, if so, which?

No. Just frozen.

• Where in the game or menus did the crash occur?

Combat.

• What steps had been taken prior to the crash occurring?

Playing the game as normal.

• Does the crash re-occur for you if repeating those same steps?

No reproducible steps to make it happen.

• What are your video settings, did you change them since last patch?

Effects - Medium


Object Detail - High
Particles - Low
PP - Low
Shading - Low
Shadows - Low
Texturing - Medium
Envi - Low
AA - Off

Same settings I have been using since closed beta.

• What are your System specs?

[spoiler]


Win7
3570k
Gigabyte Z77x-UD3H
G.Skill 1866mhz DDR3, 16GB 8x2
GTX275 SLI Driver v.301.42
Intel 520 SSD
Various 1TB drives[ /spoiler]


This freeze has not happened in several weeks. Now it happens once an hour, mostly on Tourmaline.

Edited by frag85, 04 April 2013 - 05:33 PM.

[Lightfoot]

Okay, I can run the Test Maps all day with no crashing or freezing, but if I launch into a game, MWO crashes/FREEZE in about 2-4 minutes. Occasionally I can complete a match.

Now these crashes and freeze started on the 2/12/13 patch, no crashes before that. Wasn't this when the State Rewind was added? If so that seems to be the cause of the Freeze bugs. Why else would MWO never crash on Testing Grounds, but crash in a few minutes of combat in a Live game?

Yes, current drivers. All latest today.

Nvidia 550TI, AMD Phenom X3 (3 cores, one disabled), Gigabyte mobo, Realtek sound. Windows 7 64 bit Pro, all current updates.

Also, prior to the 2/12/13 patch MWO never crashed, ran all settings on high or higher. This since June 2012.

Edited by Lightfoot, 04 April 2013 - 07:57 PM.

[Lugh]

Lightfoot, on 04 April 2013 - 07:55 PM, said:

Okay, I can run the Test Maps all day with no crashing or freezing, but if I launch into a game, MWO crashes/FREEZE in about 2-4 minutes. Occasionally I can complete a match.

Now these crashes and freeze started on the 2/12/13 patch, no crashes before that. Wasn't this when the State Rewind was added? If so that seems to be the cause of the Freeze bugs. Why else would MWO never crash on Testing Grounds, but crash in a few minutes of combat in a Live game?

Yes, current drivers. All latest today.

Nvidia 550TI, AMD Phenom X3 (3 cores, one disabled), Gigabyte mobo, Realtek sound. Windows 7 64 bit Pro, all current updates.

Also, prior to the 2/12/13 patch MWO never crashed, ran all settings on high or higher. This since June 2012.

Sadly these were happening as early as the 1-5(?) patch.. state rewind likely only added to the problem.

[Theevenger]

CTD on Tourmaline Desert. No error message; I got dumped to the MechBay.

[Pz_DC]

Sorry for some "trolling" but today I got 70% crashes. That's not playable. All the time same thing - "cre engine error - memory allocation" with different adresses.

[Xelchon]

Fides, on 04 April 2013 - 04:44 AM, said:

• Was any error message provided with the crash, if so, which? - Nope no error message, just straight crash
  
• Where in the game or menus did the crash occur? - Have had this in several places now, all ingame not in mechlab, just launched in a drop and it bombs to desktop, midgame, same, or end of match and bam it crashes to desktop.
  
• What steps had been taken prior to the crash occurring? - Well its a random occurrence so when I crash I restart my client and get a fresh invite into the group.
  
• Does the crash re-occur for you if repeating those same steps? - One guy in our guild crashed 12 times at the end of every match, so it closes your client down and you have to restart anyway. He still crashed at the end of every match. I did find when he crashed, I stopped crashing.
  
• What are your video settings, did you change them since last patch? Recently changed my drivers because of the polygon bug, to the latest ones, it was crashing before I changed them and still crashing after I changed them

No change whatsoever to anything since three months; constantly using the latest driver, as is now. Graphic Card: Nvidia GTX 580. Same thing happens. When in combat, just crashing to desktop without any error, even closes the client and all that. 4 times its happening today, was fine until yesterday. The game is unplayable right now as far as Im concerned.