PC Story Mode Chapter 14 - Crash to Desktop - when sabotaging a trip wire

On what platform did the bug occur?
PC

On which Game mode did the bug occur?
Story

If the bug occurred in Story, on which chapter did it occur?
CHapter 14

If the bug occurred during a mission, what Objective and Map were you playing on?
Story Mode chapter 14

What were you doing before reproducing the bug?
Sabotaging a TipWire

Were you able to reproduce the issue multiple time ? If so, does it occur all the time (100%)?
(will update wanted to complete report before retrying)

For each bug reported, it would be highly appreciated if you can share any of the files below with us.

Logs: You can share with us the Necromunda.log file. Don't relaunch the game before taking the logs, otherwise the logs will be overwritten. To locate the game log files: C:\Users[your computer name]\AppData(*)\Local\Necromunda\Saved\Logs
Necromunda.log

Saves: You can make a .zip/.rar of the save folder. To locate the save folder, with .sav files: C:\Users[your computer name]\AppData(*)\Local\Necromunda\Saved\SaveGames
Commander_-942146763.zip
A Screenshot / Video showing the issue will be appreciated and help us reproduce the issue. Using a file sharing site like WeTransfer.com is fine.
(https://youtu.be/OS_h7k4dk1Y)

If the game crashed/closed to desktop, here are the additional files needed (+ the one above) that will help us fix the bugs.

Callstack: You should have a "Callstack" automatically copied after this happens. Try creating a new .txt file and ctrl+v to reveal the Callstack. Save it and share it with us with the name "Callstack_yourname".
Callstack_hysnap.txt

Crash files: You can make a .zip/.rar of the crash reports folder. To locate the crash reports folders, with 4 files (.dmp / .log / .ini / .runtime-xm) for each crash: C:\Users[your computer name]\AppData(*)\Local\Necromunda\Saved\Crashes
UE4CC-Windows-87BBAE824D669F3C70A6E69284C201C6_0001.zip

the error did not repeat when I wen back into the game and returned to the chapter...

Hi Hysnap, thank you for your report and and sorry for the inconvenience.

If I get you right, you were trying to sabotage a zip line and the game crashed when you confirmed?
And could you confirm it happened only once?