13 replies to this topic

[HaXX0r1337]

I'm being desperate... This bug exists since closed beta and is still present. Even using a different computer by now.

At a random given point, this game crashes when the power up sequence is commencing. Just right after the game has been loaded completely and the 75 second timer run out. What the hell does this game which is intermittently causing a crash?

It happens about 1/10 matches. Does anyone else have the same issue?

...can one disable the boot-up sequence after the timer ran out?

HaX

Edited by HaXX0r1337, 27 July 2017 - 02:45 AM.

[Tarl Cabot]

Send a ticket to the support, though I will say this is the first time I have seen some post about crashing at power up sequence.

Meantime, you said new system. Is everything new? If not what was carried over?

Post your dxdiag if you would.

[HaXX0r1337]

well the support will tell me the usual stuff like updating drivers or reinstalling the game which usually wont help (all done btw).

I am using 64 bit client.

anyone experience with this bug?

HaX

[NARC BAIT]

are you using a user.cfg / tuning.cfg file, because that point that you described, is when the sys_spec cvars are applied, if they are deemed to be required, because the 'current' values don't match what the system expects ....

[HaXX0r1337]

nope, I don't use either. What bugs me is that the game is fully loaded, and right after the timer ends and power up sequence triggers, it crashes in about 1/10 of the matches.

[NARC BAIT]

how high do you have the video settings, the point that you say it happens, suggests to me that its still related to re-loading those settings ...

what sort of network latency do you get, because also at that point is when the network comms really start up, and your pc starts the battlegrid ...

are you running low on memory ? or perhaps free space on the primary disk ?

[HaXX0r1337]

So you are saying that high video settings causes the game to crash? oO The latency should be a random event and not to be correlated to the initial power up sequence at the beginning of each match?

I have 16 GB ram. The weird thing is, it was completely gone prior the last patch but was present before the previous patch and is present now again.

The repair tool does not find errors. I have reinstalled the game too.

I don't think there will ever be a workaround. I will try to use the 32 bit client.and keep you guys posted.

HaX

[NARC BAIT]

HaXX0r1337, on 27 July 2017 - 05:19 PM, said:

So you are saying that high video settings causes the game to crash? oO The latency should be a random event and not to be correlated to the initial power up sequence at the beginning of each match?

well, not exactly, when the timer ends, the first thing that happens is it tests what it believes the current values are (high,med,low) and checks if that matches what they are meant to be, if the two are considered to not line up, then it 'applies' the settings to all of the 'normally' controlled values, which tends to result in a large, but consistent to the machine, stall ... most of the time equivalent to the time the machine seems frozen and unresponsive during the match load up ... when this happens from a dropship launch, players will feel as though they have been 'delayed' from being dropping like everyone else, and their client will jump around a bit catching up on delayed packets ...

after that, the preload the textures around the 'camera', and the instant you are released into play, the network system starts communicating, and the battlegrid starts to become inefficient ... if your crash is always at this point, and not later during the match, its almost certainly related to one of these things ... could try changing the way some of the systems interact within a user.cfg file ... but it could just not be worth it if you don't see the problem in 32 bit mode ...

I mention latency because not all packets are equal ... and if your client doesn't receive a couple of the golden ones, the game wont progress ... and the packet isn't resent ... sometimes with wifi the golden packet might get swatted out by other noise ...

[HaXX0r1337]

I don't use the user.cfg file. TCIP is a protocoll that checks wether the packet was arrived or not. If not, the layer 4 of the network system resends it. I think you mix it up with UDP. I cant believe that a temporary lost packet causes the entire game to crash tho it might be a reason for temporary drop issues.

Yep, i never, never have ever crashed at any other given point.

My bet is it attempts to load something that causes a code violation. This must have something to do with the (pointless) power up sequence.

PGI, CAN ONE DEACTIVATE THE INITIAL POWER UP SEQUENCE PLEASE?

Edited by HaXX0r1337, 27 July 2017 - 06:50 PM.

[Tarl Cabot]

Are your soundcard drivers up to date? Besides the video side, there sounds, the commander's voice.

With that said, if you have had this problem since beta, then looking at other things. You never did say whether or not every component was new, and if not which components have been carried over?

After that, reviewing what programs you are using that the general layman may not install.

And post your dxdiag.

Edit.

Are you always on the MWO screen or are you tabbing in/out? Running full screen, full windowed or windowed mode? Again, this is the first I have seen posted where the player indicates it is at the start up sequence and has had this issue since beta......

Edited by Tarl Cabot, 29 July 2017 - 11:17 AM.

[FrontlineAssembly]

I get this Bug as well. about 2x per week. Dont use the above mentioned files. also am not on Wifi. Have plenty of excess ram as well. So not sure whats up with this.

[NARC BAIT]

bit random, but do you have virtual memory disabled ?

[Drunkenseagull]

Yes I have this problem as well. Happens for me about 1/5 matches now that it will crash at match start. It got even worse after the patch. This **** has been going on for years and nothing has been done about it, despite all the crash reports, complaints and ruined matches. Fresh install of windows and mwo plus the latest graphics driver makes no difference.

[NARC BAIT]

smells like this thread https://www.reddit.c...om_dcs_finally/ ... where its claimed to be 'fixed' ...