Closed gbl08ma closed 7 years ago
no idea. did never happen to me. If you can reproduce it, write this in lines 266 and 284 (outcomment the debug message and remove the pos_to_string calls):
266: atprint("maxn conway for ",maxn,path[maxn],maxn-1,path[maxn-1])
284: atprint("minn conway for ",minn,path[minn],minn+1,path[minn+1])
and provide the debug log
I couldn't reproduce it yet. If it doesn't happen again in a few days I think this issue can be closed, it was probably just a random thing caused by the version upgrade. The problems with itrainmap I reported on the forum, though... should I open an issue, or am I doing something wrong?
Close it yourself when you think it's gone.
I just put together two trains with 6 cars each, after much hopping on and off, I couldn't reproduce the error... let's assume it was DB migration shenanigans and forget this.
After deleting all trains (to avoid issues like #34 ...), updating to 1.6.2, migrating all the tracks to the new database, creating a new subway train with two cars, hopping on it, after just a few blocks / seconds the following error occurred:
I reopened the world, the player was still attached to the train and moving forward just like before the crash, so I left the train and entered again, moved it forward like before, and the error didn't occur again (so far).