[RESOLVED] CTD when pressing cycling waypoints with NSEQ boxed

[Rob]

Hello,

 

I can reproducibly get DCS to crash when cycling through waypoints in the EHSD, with NSEQ boxed, and a TERMINAL (TERM) waypoint selected.

 

To reproduce: enter DATA mode, box NSEQ, using the Option Display Unit (ODU), press TERM, using the UFC keypad enter 4, Enter. Return to the EHSD by pressing Data, rebox NSEQ, and press the OSB buttons to cycle forwards and backwards through waypoints.

 

Because it crashes, there is no track. Here is a video of a crash. Here is a video. It only takes a few seconds to test yourself and recreate.

 

 

Attached is the .miz file that I was flying. It contains a single air start AV8B carrying JDAMS with 6 waypoints programmed in the mission editor, and some unarmed transport targets. dcs.log also attached.

 

Once again, there is no track produced by DCS because it crashes, so I cannot add a track because there is no track to add.

Edited October 11, 2020 by [Rob]
grammar

[RAZBAM_ELMO]

;4520903']Hello,

 

I can reproducibly get DCS to crash when cycling through waypoints in the EHSD, with NSEQ boxed, and a TERMINAL (TERM) waypoint selected.

 

To reproduce: enter DATA mode, box NSEQ, using the Option Display Unit (ODU), press TERM, using the UFC keypad enter 4, Enter. Return to the EHSD by pressing Data, rebox NSEQ, and press the OSB buttons to cycle forwards and backwards through waypoints.

 

Because it crashes, there is no track. Here is a video of a crash. Here is a video. It only takes a few seconds to test yourself and recreate.

 

 

Attached is the .miz file that I was flying. It contains a single air start AV8B carrying JDAMS with 6 waypoints programmed in the mission editor, and some unarmed transport targets. dcs.log also attached.

 

Once again, there is no track produced by DCS because it crashes, so I cannot add a track because there is no track to add.

 

If it is a CTD then we need a .log file as explained in the HOW TO REPORT posts stickied at the top.