Watching Drone Wars, a particular blue print creates a lot of NaN errors when you launch it might demonstrate the issue really well.
After launch my game crashed.
Also found here: https://starmadedock.net/content/dwr_gregolegomonkey_prates-drone-rack.5369/
see tester information
Docking something to this basic rail should results in a NaN error.
A single shoot out rail that changes the plane a rail is moving on will always cause this (can only be 1 long, it has to undock immediately).
[2016-09-23 00:11:22] java.lang.IllegalStateException: Exception: NaN position for Ship[RAIL_DOCK_1474582267712](150); PObject: {RigBExOrig@1110204336([CCS|SER Ship[RAIL_DOCK_1474582267712](150)])}
[2016-09-23 00:11:22] at org.schema.game.common.data.world.SimpleTransformableSendableObject.updateLocal(SourceFile:1183)
[2016-09-23 00:11:22] at obfuscated.Wm.updateLocal(SourceFile:2546)
[2016-09-23 00:11:22] at obfuscated.WB.updateLocal(SourceFile:389)
[2016-09-23 00:11:22] at org.schema.game.common.controller.EditableSendableSegmentController.updateLocal(SourceFile:1095)
[2016-09-23 00:11:22] at obfuscated.WJ.updateLocal(SourceFile:474)
[2016-09-23 00:11:22] at org.schema.game.server.controller.GameServerController.update(SourceFile:1355)
[2016-09-23 00:11:22] at org.schema.schine.network.server.ServerController.run(SourceFile:273)
[2016-09-23 00:11:22] at java.lang.Thread.run(Unknown Source)<replace this line with the file content>
<replace this line with the file content>
-feedback-
Forgot to comment but can't reproduce this, the blueprint appears fine to me. Launches without a problem and looking at the rails themselves, I have no idea how that would cause this.
It's not a duplicate of T1422 at least.
Can you still reproduce this? Anything in specific you have to do besides spawning in the blueprint and launching the ships?
This bug can be reproduced by the following. All rails will be pointing up(the y) for this example and in the same x-z facing unless stated otherwise.
Have a basic rail with your docked entity on it. Place a downward pointing(in the y) green rail so movement is stopped of the entity. Use the standard activation method(button or activation block) to replace the green rail with a red shootout rail in the same orientation as the basic rail.
Trigger the button and you'll get the nan every time.
Workarounds are adding an extra green rail inbetween the basic rail and the toggling green/red rail
I see, only happens if you want to undock immediately after a dimension change. Thanks for the feedback!
Not sure if this is related but I'd had an issue before where launching a ship off a rail with shootout turned caused the ship to glitch into a zone where there were no stars and all around is just solid grey background.
Would look at the distances from anything and it looked like it was NaN, pretty much fixed mostly reconnecting to the session though, although you might be a few km away.
Yes, Shoot out rails will put you into NaN-space if you are on the entity If not crashing you outright. This can occur when your shootout rails "point" into eachother, or if there are multiple change in direction on the rail If I recall correctly
Hm not fixed, example blueprint that has it (to check it out later), seems it can still happen if you replace the rails while they're moving on it.