New Crash on MP DS server
15:46:55.5508 [FATAL] Initializer: System.Runtime.InteropServices.SEHException (0x80004005): External component has thrown an exception.
at Sandbox.Engine.Platform.Game.RunLoop()
at Sandbox.MySandboxGame.Run(Boolean customRenderLoop, Action disposeSplashScreen)
at Torch.VRageGame.DoStart()
at Torch.VRageGame.Run()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
System.Runtime.InteropServices.SEHException (0x80004005): External component has thrown an exception.
at Sandbox.Engine.Platform.Game.RunLoop()
at Sandbox.MySandboxGame.Run(Boolean customRenderLoop, Action disposeSplashScreen)
at Torch.VRageGame.DoStart()
at Torch.VRageGame.Run()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
Same bug here, don't know how to reproduce. Happens at random.
Same bug here, don't know how to reproduce. Happens at random.
Make sure you guys try to replicate the crash in vanilla, because Keen will probably dismiss anything with Torch in the stack trace. If you can't replicate it in vanilla let me know because it'll probably be my job to fix whatever it is.
Make sure you guys try to replicate the crash in vanilla, because Keen will probably dismiss anything with Torch in the stack trace. If you can't replicate it in vanilla let me know because it'll probably be my job to fix whatever it is.
I highly suggest reproducing this in the vanilla DS before reporting.
It not likely a problem with Torch, but we don't want to scare the devs away from fixing this because they see "Torch" in the stacktrace.
I highly suggest reproducing this in the vanilla DS before reporting.
It not likely a problem with Torch, but we don't want to scare the devs away from fixing this because they see "Torch" in the stacktrace.
Left a creative mode, vanilla DS server up all night with a dozen or so players and was unable to recreate this issue. My torch server with roughly the same amount of players experiences this crash at least once an hour. So far, any evidence I've gathered makes this a torch issue. So far.
Left a creative mode, vanilla DS server up all night with a dozen or so players and was unable to recreate this issue. My torch server with roughly the same amount of players experiences this crash at least once an hour. So far, any evidence I've gathered makes this a torch issue. So far.
I'm getting the same error on my DS but I don't use torch. I was told it happened to someone flying into space from earth and leaving the cockpit but when we tried to reproduce it nothing happened.
I'm getting the same error on my DS but I don't use torch. I was told it happened to someone flying into space from earth and leaving the cockpit but when we tried to reproduce it nothing happened.
RRRRRRRRRREEEEEEEEEEEEEEEEEEEEEE UNPLAYABLE -_-
RRRRRRRRRREEEEEEEEEEEEEEEEEEEEEE UNPLAYABLE -_-
Experiencing this so frequently, it makes my brain hurt :/ It's making me paranoid to the point where I'm backing up whatever I'm working on to my blueprints every 5 minutes or so.
Experiencing this so frequently, it makes my brain hurt :/ It's making me paranoid to the point where I'm backing up whatever I'm working on to my blueprints every 5 minutes or so.
Frequent crashes, must be fixed
Frequent crashes, must be fixed
RAAAAAAAAAGGGGGGEEEEEEEEEEEEEEEEE FIIIXXXXXXXXXXXXXXXX PLZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ :D :D :D
RAAAAAAAAAGGGGGGEEEEEEEEEEEEEEEEE FIIIXXXXXXXXXXXXXXXX PLZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ :D :D :D
This issue has been resolved in hotfix v187.204.
This issue has been resolved in hotfix v187.204.
Replies have been locked on this page!