AdvancedApproach
Well-known member
Good Afternoon AdvancedApproach
This generally occurs if a scripted object that is placed in the route is configured by the creator of the object to save/change settings when creating a session, resulting in the route needing to be saved as the changes are attempting to be saved to the route itself. Unfortunately it can be difficult to find what asset is causing this, as there are currently no tools provided to see which assets are making changes that require saving.
The best option is to look at what objects you placed into the route around the time that this issue started occurring, to see what may cause this issue.
Given this revelation now I've got to find the guilty party which is a tall task.
This generally occurs if a scripted object that is placed in the route is configured by the creator of the object to save/change settings when creating a session, resulting in the route needing to be saved as the changes are attempting to be saved to the route itself. Unfortunately it can be difficult to find what asset is causing this, as there are currently no tools provided to see which assets are making changes that require saving.
The best option is to look at what objects you placed into the route around the time that this issue started occurring, to see what may cause this issue.
Given this revelation now I've got to find the guilty party which is a tall task.