#Crash with possibly unique circumstance

2 messages · Page 1 of 1 (latest)

ashen mulch
#

So last night while I was mid mission with one other player I had to step away for family related reasons. The friend I was playing with decided to disconnect as I was not sure how long I would be. One thing led to another on my end and I was away from my computer and the game for a little more than 9 hours. This was not planned and I do not know how soon the game would have reached this crashing state but when I returned the game was still running and I was still sitting in a passenger seat so I thought why not continue.

I played for an additional 30 minutes taking out threats and looting. During which time I noticed a visual bug. The bug consisted of two floating rings that looked to be ship thruster visuals that were not attached to the ship but hovering in line with the thrusters that should be present. That was not really a concern so I ignored but did take screen shots in order to make a post about seeing that.

During a landing sequence the game booted me to the main menu unexpectedly. Now this technically would be expected as the game had ran on my mission instance for an extended time well exceeding the 1 hour estimation for the total mission time of my gameplay loop.

I am aware that the crash should be expected but I thought passing the information along might be helpful since I would expect that solo gameplay on higher difficulty missions may start to take more and more time for players. Maybe not 9 hours worth of time but as I do not know exactly how long it really took to happen perhaps a dev can spend some time testing to be sure this only happens in extreme enough cases like mine not far sooner.

peak grove
#

looks like part of the inside thruster asset slowly moved outward from the ship body 🤔