CTD Every time

[mjeh]

Hi.

 

Mission with 2 players in F-15C, server crashes ("DCS has stopped working") every time when we try to taxi to runway. Mission plays just fine with just me playing on the server.

 

Log folder, DXDiag and mission included, no track was created.

Logs.rar

Ganistan.miz

DxDiag.txt

Edited November 21, 2012 by mjeh

[mjeh]

A little update, the mission worked fine if I took off before player 2 entered the game. It seems the crash occurs when we're both taxing

[JABO2009]

to sum up my Weekend sessions in DCSW:

 

joined MP for about 15 times, thereof I got 9 CTDs...

[Heli Shed]

Hi,

 

Well, for a start you can help yourself by ensuring that the Aggressor groups are set to 'Late Activation'; they are called upon a condition being met - ie when part of the coalition is in Zone 'Cap'.

 

The flag settings then dicate the time span for the remaining spawning Red's. Again, they are not set to 'Late Activation'.

 

Do i think that the reason for your crash every time is due to this? no. I don't. But the point im making to you is that with a product (as glorious as it is) such as DCS World and all of it's modules that are still essentially in Beta (all be them publicly released), you 'have' to eliminate everything from a mission design as a possibility of instigating a crash.

 

Try making the mission again.

 

Start with just your F-15's and taxi together.

 

That ok?

 

Now add the next phase and re-run.

 

That ok?

 

and so on and so on.

 

With your mission, it shouldn't take that long.

 

Regards

 

'T'

 

 

PS: Welcome to the long drawn out and rarely thanked task of creating stable missions. ;-)

Edited November 26, 2012 by Tyger

[Heli Shed]

To add,

 

Also eliminate certain conditions in missions that you 'know' will instigate a crash on the server or on some clients as a CTD.

 

An example of this is AI Aircraft (not Heli's) landing and shutting down. More often than not will instigate the CTD for clients or the infamous kernal32.dll and ntdll.dll error as per crash log.

 

Good luck

 

'T'

 

 

copied and pasted from error log:

 

C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D

773FC521 0019FED0 0001:0002B521 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21

Edited November 26, 2012 by Tyger

[mjeh]

Thanks for taking the time to review and reply!

 

Aye, I suppose I should start using 'Late Activation' hooks. Old habits and all.

 

I don't think the direct cause is the activation triggers either, this has the feel of improper memory handling and my main suspect is the ATC interaction in this particular case. But then again, with memory issues it is hard to say what exactly is influencing what unless you have intimate knowledge of the engine's inner workings - so it could indeed be caused by anything in the mission.

 

For all I know it could even be that I had some memory corruption from a previous crash and that this was affecting the current sessions. I'll admit I haven't exactly bent over backwards trying to get this to work as it was just a mission I threw together for some quick fun for a buddy and myself. But I figured since it was indeed crashing consistently as we were taxiing I'd be a good lil' beta tester and submit the crash logs.

 

PS: Welcome to the long drawn out and rarely thanked task of creating stable missions. ;-)

 

Thanks, I could quote this a hundred times for truth

 

 

 

To add,

 

Also eliminate certain conditions in missions that you 'know' will instigate a crash on the server or on some clients as a CTD.

 

An example of this is AI Aircraft (not Heli's) landing and shutting down. More often than not will instigate the CTD for clients or the infamous kernal32.dll and ntdll.dll error as per crash log.

 

Well, that would certainly explain some issues we've been having. Thanks again!

 

-Mj