Bezier curves turn into reverse connections that are randomly connected to other nodes

[waluda]

I edited a pre-made route config (in AutoDrive Course Editor v.1.0.9) > saved that and entered the game.
The routes I added where shown ingame with some reverse lines being thrown in sometimes. So I removed a couple of nodes (2-3 max.) and ALT+F4ed the game. Loading config via Course Editor again, all standard quadratic bezier curves were turned into reverse connections (to random points of other bezier curves). This issue applies to all backups of my savegames AD config.

At the same time, waypoint nodes have also moved.

[KillBait]

This is sign of network corruption, it's a bug that has been around for a while now and it's proved to be near impossible to fix as i don't have a re-producible case to figure it out, but i have a strong suspicion that it is undo/redo related.

The only course of action if this happens is to go back through the last few autosaves until you find one that is not corrupted.

I'm currently re-doing the entire network building/modifying code ( a major task in itself) to try a kill this bug once and for all.

[whitevamp]

This is sign of network corruption, it's a bug that has been around for a while now and it's proved to be near impossible to fix as i don't have a re-producible case to figure it out, but i have a strong suspicion that it is undo/redo related.

The only course of action if this happens is to go back through the last few autosaves until you find one that is not corrupted.

I'm currently re-doing the entire network building/modifying code ( a major task in itself) to try a kill this bug once and for all.

I had forgotten to post to this thread after posting my crash report, but your assumption is most likely correct. After hitting the undo button and experiencing a crash, I encountered the same issue—reverse lines appearing and the AD config file becoming corrupted.

It definitely seems to be tied to the undo/redo functionality. Hopefully, the ongoing rewrite of the network building and modification code will help eliminate this bug once and for all. Let me know if there's anything I can do to assist with troubleshooting or testing!

[KillBait]

Just a bit of context i want to add to this, i'm 95% sure the corruption is undo/redo related, the code for each of the buttons undo is not consistent and uses different approaches depending on the action, it wasn't until i was going step by step through each buttons undo/redo that i started to notice a few possible issues.

(1) There are basic checks done, but a lot use direct manipulation of the network with no checks which leaves no room for errors.
(2) There is at least one that can trigger during an autosave, while it's extremely unlikely to happen, it's still a possibility.
(3) Even similar functions use different approaches, this should not be the case, this one falls on me.
(4) The underlying code is fine, just the way it's used isn't great.

I've tried a few different approaches to fix this over the last few weeks and i finally settled on a single class that is responsible
for all manipulation of the network be it add/remove nodes/connections or any cut/copy/paste function. I'm currently modifying
each buttons undo function to use this new class, this is having a side effect of me catching a few bugs i didn't know existed and
will eliminate many potential errors.

The modifications will be in the next release and i'm hoping this bug is killed for good. If not, i have only one place to look for the errors instead of 30 different class files and a maze of code to trace through.