reported Embark to transport from start with more than three vehicles embarking causes CTD (with crash report)

[Rolds]

The attached mission is an example of the problem. I discovered there is an embark to transport "from start" checkbox which is awesome, finally you can start a mission with infantry in a helicopter or vehicle!

There are a couple of problems however. It only appears to work reliably with 1 or 2 vehicles embarking troops. 3 or more and often one of the groups of infantry will not be embarked at the mission start, they will instead appear on the map wherever you've placed them.

Worse, exiting such a mission and then running it again from the mission editor often causes DCS to crash (typically it does bring up the crash report system). Attached mission is an example. Running this mission a second time after exiting it will crash DCS.

The embarking (and towing and cargo transport) options that you guys are putting into the game are cool it would be great if these were robust, stable features!

Test Syria.miz

debrief.logdcs.log-20230205-024526.zipdcs.log

[Drewbacca]

I’m having the same issue.

In the attached mission, trimmed down to just the units that are causing the crash, I can sometimes run it for 10 minutes, sometimes run it to completion. But if I run it to completion, the next mission I run, whether it's this mission or something else, I’ll get a CTD on the “Net Start” portion of the mission load screen.

For reference, I’ve also run this mission but removed “At Start” or even just “Embark” entirely, and no crash occurs.

As mentioned before, about half the units don’t embark to their transport on start. Instead, they begin the embarkation procedure on mission start. I tried removing the units that did not embark correctly, thinking it was a pathing issue, and then a different batch of units failed to embark.

At first I thought it might be a conflict with my mods. But I sent this mission to two of my friends who have no mods and they got the same results. All the same, I have the following: TacView; Civilian/Military Aircraft Mod; Su-30MKI; A-10, F-16, F-18 default countermeasures programs; Loadouts (e.g. AIM-9X for F-15C and HARM for MiG-29); Various skins such as liveries and English cockpits.

 

My computer specs are as follows:

Processor: 12th Gen Intel Core i9-12900K 3.19 GHz

RAM: 16 GB

GPU: GeForce RTX 3080

OS: Windows 11 Home

dcs.log dcs.log-20230207-042044.zip Only Offenders.miz

[silverdevil]

On 2/4/2023 at 9:48 PM, Rolds said:

The attached mission is an example of the problem. I discovered there is an embark to transport "from start" checkbox which is awesome, finally you can start a mission with infantry in a helicopter or vehicle!

There are a couple of problems however. It only appears to work reliably with 1 or 2 vehicles embarking troops. 3 or more and often one of the groups of infantry will not be embarked at the mission start, they will instead appear on the map wherever you've placed them.

Worse, exiting such a mission and then running it again from the mission editor often causes DCS to crash (typically it does bring up the crash report system). Attached mission is an example. Running this mission a second time after exiting it will crash DCS.

The embarking (and towing and cargo transport) options that you guys are putting into the game are cool it would be great if these were robust, stable features!

your crash happens right after these lines

Quote

2023-02-05 02:45:25.828 INFO    APP (Main): MissionSpawn:initScript
2023-02-05 02:45:25.828 INFO    APP (Main): MissionSpawn:spawnCoalition neutrals
2023-02-05 02:45:25.828 INFO    APP (Main): MissionSpawn:spawnCoalition red
2023-02-05 02:45:25.828 INFO    APP (Main): MissionSpawn:spawnVehicles 47
2023-02-05 02:45:25.917 INFO    APP (Main): MissionSpawn:spawnVehicles 81
2023-02-05 02:45:25.930 ERROR   WEAPONS (Main): Invalid connector name (POINT_GUN_01): unit type = Soldier RPG, ws id=1, ln id=1, br id=1
2023-02-05 02:45:25.994 WARNING LOG (7708): 9 duplicate message(s) skipped.
2023-02-05 02:45:25.994 ERROR   WEAPONS (Main): Invalid connector name (POINT_GUN_01): unit type = Paratrooper RPG-16, ws id=1, ln id=1, br id=1
2023-02-05 02:45:26.000 WARNING LOG (7708): 2 duplicate message(s) skipped.
2023-02-05 02:45:26.000 INFO    APP (Main): MissionSpawn:spawnCoalition blue
2023-02-05 02:45:26.000 INFO    APP (Main): MissionSpawn:spawnVehicles 17
2023-02-05 02:45:26.074 ERROR   WEAPONS (Main): Invalid connector name (POINT_GUN_01): unit type = Soldier RPG, ws id=1, ln id=1, br id=1
2023-02-05 02:45:26.101 WARNING LOG (7708): 5 duplicate message(s) skipped.

 

[Rolds]

16 hours ago, silverdevil said:

your crash happens right after these lines

 

Thank you for looking at this! But I don't know what these lines mean, are you able to interpret them?

[silverdevil]

6 hours ago, Rolds said:

Thank you for looking at this! But I don't know what these lines mean, are you able to interpret them?

hello. i am not real sure what it means. however it appears on this post and @BIGNEWY replied that it was reported. the topic was locked without much ceremony. i am not sure if this is what caused your crash. are other missions ok? if so it points to a mission issue.

 

[BIGNEWY]

this is a different issue. 

I have reproduced and reporting the crash now. 

thanks for the data