Jump to content

1.5 , sending wingman on reconnaissance can crash the game


Recommended Posts

Posted (edited)

Sending a wingman on reconnaissance can sometimes crash the game to desktop. There is a freeze first and then crash to desktop. This seems to be an issue ever since 1.5 was released.

 

I have this in the logs:

# -------------- 20151109-203803 --------------

# C0000005 ACCESS_VIOLATION at A3BE4167 00:00000000
00000000 00000000 0000:00000000
A3BE4167 009CF0F0 0000:00000000
A3BC522D 009CF380 0000:00000000
A3BEABA3 009CF3C0 0000:00000000
4D3472DF 009CF440 0000:00000000
4D347825 009CF490 0000:00000000
A3E7DAA8 009CF500 0000:00000000
A3E81592 009CF530 0000:00000000
A3E97904 009CF560 0000:00000000
A3E97854 009CF590 0000:00000000
A3F41E2C 009CFC40 0000:00000000
A3F43CB5 009CFC80 0000:00000000
57B713D2 009CFCB0 0000:00000000  BaseThreadInitThunk()+22
59795454 009CFD00 0000:00000000  RtlUserThreadStart()+34

I have 3 crash logs so far with this RtlUserThreadStart()+34 related to this crash.

I also have a .dmp file, but I don't know where to send it

 

This one is a bit strange and I sadly have not found a reliable way to reproduce it. It has happened several times now, it only seems to happen when I have played for a while. It has happened in the campaign, the insurgent instant action. As I said I have nod been able to reproduce it reliably. It does not seem to be related to the distance the wingman needs to travel.

 

So far I have :

play for a while

send wingman to reconnaissance

crash to desktop.

 

Edit : I managed to reproduce the issue:

In the Deployment Campaign:

Narzan Valley mission

fly to the ingress point

shoot a few trucks and AAA

command wingman to scout 2 km ahead

player pilot speaks the commands

the AI does not respond

crash to desktop

 

This issue is not tied to this mission. however I have only been able to reliably reproduce this in this mission, mostly due to the easier timing.

Edited by nitrodust
Posted

I had this crash two times yesterday in the last mission of the Deployment campaign. It's not really reproducable for me either, but if it happens it happens directly after my Pilot gives the Radio command, when the Wingman would normally acknowledge.

  • 2 weeks later...
  • 3 weeks later...
Posted

I'm experiencing the same crash with the Ka-50 module in 1.5.1. It doesn't happen all of the time, so it took me a while to figure out that sending a wingman on recce was the trigger for the crash.

 

Here's my crash log, for whatever it's worth:

 

 

# -------------- 20151204-033434 --------------

 

# C0000005 ACCESS_VIOLATION at 3FD74057 00:00000000

00000000 00000000 0000:00000000

3FD74057 0013F350 0000:00000000

3FD5512D 0013F5E0 0000:00000000

3FD7AA93 0013F620 0000:00000000

F35F72DF 0013F6A0 0000:00000000

F35F7825 0013F6F0 0000:00000000

4000DD28 0013F760 0000:00000000

40011C42 0013F790 0000:00000000

40027E74 0013F7C0 0000:00000000

40027DC4 0013F7F0 0000:00000000

400D279C 0013FEA0 0000:00000000

400D5955 0013FEE0 0000:00000000

77A05A4D 0013FF10 0000:00000000 BaseThreadInitThunk()+D

77B3B831 0013FF60 0000:00000000 RtlUserThreadStart()+21

 

In my case it tends to only happen on missions with long flights before engagements. Fortunately the flying part is just as fun as the weapons part, so redoing missions isn't a big deal :).

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...