can not reproduce SLAM ER triggers game/server crash by (almost) hitting the water

[MorrisMessing]

Hi, we recently had 2 server crashes when a SLAM-ER, which was programmed to fly towards a steerpoint, headed towards the sea surface. As mentioned this happened 2 times in a row. Multiplayer track files did not generate so the only things I can provide are the TACVIEW Files, the DCS log file and the mission briefing (for the Steerpoint coordinates)

DCS SLAM ER BUG.rar

[BIGNEWY]

Hi, 

I have been unable to reproduce so far on my system, if possible the next time it happens you should get a zip folder created in your dcs log folder in saved games please attach. 

 

[MorrisMessing]

@BIGNEWY

 

Hi,

Same BUG as mentioned above occured today (for the 3rd time in total)

 

DCS did not create a zip file in the logs directory in saved games, but I will try to give you as much input as we can provide below.

 

Shared between all 3 occurences:

- marianas map

- we were on a server hosted by myself

- a client (not me) dropped the SLAM-ER

- the SLAM was given a STP1 which was (N11°27’ E144°40’). Steerpoint was entered with following 0s to complete the full (D)DDMMSS.SS format. (there was no specific altitude assigned to the steerpoint)

- after release the SLAM turned towards the steerpoint but failed to maintain its assigned altitude (through FLT HIGH setting)

 

Differences between the cases:

- during the 3rd occurence the SLAM-ER that is believed to trigger the crash was dropped by a different client than the first two times.

- the game did not always crash with the slam beeing on the same alt, but it was below 1000ft in all three cases.

- the SLAMS were fired from different aircraft (not the sam unit, but the same flight)

 

Additional information:

- a SLAM-ER drop was tested yesterday (one day before the third case) in singleplayer using the same coordinates and it worked without any problems. It was a different mission file though (& not on my system)

 

What we think it is:

We strongly assume the crash has something to do with the Steerpoint coordinates messing up the guidance of the SLAM-ER. Because any other SLAM-ER fired in the same mission (&mission file) worked as advertised.

 

I hope you can get something figured out with that information.

 

I would ba able to send over the server trk file but is is to big to upload it here.

 

SAME_BUG_14_12_2022.rar