SENTRY
Game crash immediately after ending a level
After getting in the pod at the end of a level there seems to be maybe a 25% chance seemingly at random of the screen going black with no way to continue. Music continues to play but nothing on screen, clicking anywhere on the display causes the windows "exe not responding" popup with no apparent resolution other than ending the game process. Reloading the game puts you right back at the ship screen before the mission just completed (as in the game didn't save the level just completed).
< >
Showing 1-5 of 5 comments
Gary  [developer] Feb 4 @ 10:00am 
Could you send your log files to me at support@firebladesoftware.com please?

They're located here: %USERPROFILE%\AppData\LocalLow\Fireblade Software\SENTRY\

This sounds like an infinite loop rather than a crash, but just in case there's a crash dump I'd like that too please! If there is one, it'll be here: %TMP%\Fireblade Software\SENTRY\Crashes

There's been some other reports of this in another thread and it's our number one priority to fix, it's just proving tricky for us to reproduce (which likely indicates it's network-related). If it happens again, it'd be good to know if you can reload the campaign in Singleplayer and try to beat the level to progress.
Originally posted by Gary:
Could you send your log files to me at support@firebladesoftware.com please?

They're located here: %USERPROFILE%\AppData\LocalLow\Fireblade Software\SENTRY\

This sounds like an infinite loop rather than a crash, but just in case there's a crash dump I'd like that too please! If there is one, it'll be here: %TMP%\Fireblade Software\SENTRY\Crashes

There's been some other reports of this in another thread and it's our number one priority to fix, it's just proving tricky for us to reproduce (which likely indicates it's network-related). If it happens again, it'd be good to know if you can reload the campaign in Singleplayer and try to beat the level to progress.

Can do - I think you're right, it doesn't necessarily crash you just can't do anything without quitting and restarting the game. I should have noted I actually have only been playing single player, that's where the error is occurring for me so I'm not sure my problem is network related (but then again I'm no dev!)
Last edited by Farmer Pickles; Feb 5 @ 11:42am
Gary  [developer] Feb 5 @ 12:17pm 
It seems to be more commonly reproduced in co-op, but there have also been reports of it happening in singleplayer too. Out of interest, were you using turrets at all? That seems to be another common link between players that have had it happen.
Gary  [developer] Feb 5 @ 2:48pm 
We've put a fix for this in version 0.7.25505, which Steam should auto-update to.

Let us know if it turns up again, and thanks for the info in helping to track it down.
Seems to be completely fixed!
< >
Showing 1-5 of 5 comments
Per page: 1530 50