If you pause the game while you're flying the aircraft, then attempt to Alt+Tab out of the game, the game will crash.
Description
Description
Details
Details
- Legacy ID
- 2805764132
- Severity
- None
- Resolution
- Fixed
- Reproducibility
- Always
- Category
- Game Crash
Steps To Reproduce
- Open Editor on Stratis
- Place the player as BLUFOR > NATO > Air > A-164 Wipeout and set special to Flying
- Preview
- Let the aircraft fly for 5 seconds
- Pause the game
- Alt+Tab out of the game
- The game will freeze and crash
Event Timeline
Comment Actions
Hello Sniperwolf,
could you please confirm this behaviour on current Steam Stable or Steam Dev 1.16 and 1.18?
I was unable to reproduce it.
Thank you.
Comment Actions
Current dev build: 1.19.123679 - Crashes with the repro steps (alttab_flying_paused_crash2.zip)
Current stable build: 1.16.123633 - Crashes with the repro steps (alttab_flying_paused_crash3.zip)
- The Steam overlay is running
- GPU drivers are NVIDIA GeForce drivers 337.50
Comment Actions
Also to mention, with 1.19.123679, I don't even have to Alt+Tab out of the game anymore. Pausing the game will crash the game.
Comment Actions
Ok, figured it out, there is another step. It has something to do with "currentZeroing player" in the watch fields
I had the following in the watch fields:
- cursorTarget
- currentZeroing player
- "abcde"
Removing the "currentZeroing player" fixed the crash, putting it back, crashed the game again on pause, it crashes even when editing the watch field to type it in.
Executing it from the pause console while flying in the plane crashes the game as well, so it's not just the watch fields.
Comment Actions
Thank you for finding this one. The repro steps worked (it seems that "currentZeroing player" is causing the crashes. Our programming team will look into it.
Comment Actions
Hello,
this issue has been fixed (locally) and should appear on Steam Dev in couple of days.
Thank you
Comment Actions
Mass closing tickets marked as resolved more than 1 month ago.
If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.