Infinite save new route and session loop

constar261

Active member
Hi I'm going here to get advice and hopefully a solution to something I've only seen to routes I regularly use. The 2 routes in question are Mayfield - Davenport by and1 and the Indiana Western revamps by BBarnes. Whenever I try to create a session and save it with no rollingstock as a base I get the save new route and session loop where I can't save just a session. On the Mayfield to Davenport route if I use the original version of the the route I can load make and save a session with out having the save new route and session occur. Trying that on the rest of the updated versions nothing and I've never had any success with the Indiana Western revamp. I'd like to know if anyone else has experienced this on other routes and what solutions or work arounds are available?
Note have tried just to save a session no rollingstock, locomotives, etc.

kuid:293137:105463> Mayfield - Davenport

<kuid2:293137:105463:4> Mayfield - Davenport
 
That is normal. You can not save a session to someone else's route, only your own. The route and session must have the same creator's number in order to be worked on. If you want to upload the session as an add-on to the original route, you need to change the map-kuid in the session config to that of the original
 
You can load in a DLS route and a session into Surveyor and then select Save As... from the Surveyor Main menu. You will be given two options..
  1. Save new route and session and both will be saved using your <kuid> identity and will be independent of the original route and session. You can then, if you wish, delete both the original route and session.
  2. Save new session. Only the session will be saved. This will also be saved with your <kuid> identity and will be an independent session from the original session but it will still be dependent on the original route. This means that if you delete the original route you will also delete your new session.
As @stagecoach points out above, you cannot save your copy of the route and/or session so that it will overwrite and replace the originals. Likewise, if you make any changes to your versions of the route/session you cannot upload them to the DLS without the permission of the original route/session creator.

You can however, create a brand new totally original session for the route and upload that to the DLS but I would put in an acknowledgement to the original creator of the route.
 
I was trying option 2 that pware describes to only save a session after going thru train selecting the route and selected create a new session. However every time I attempt to do that it greys that out when I attempt to save and wants to save as a new route and session even if no editing has occurred.

As for what stagecoach is explaining I’ve been saving sessions to routes that are not my own years like UMR series Sherman hill, BN Oasis, and more only the 2 routes mentioned above have ever done this
 
Indiana Western version from MSgt that I cloned always prompts a route save; have not figured that out but maybe something in the original (gfisher?) route is triggered when cloned.

I also have many sessions for dl'd routes that don't require changing the route. In fact, the use of layers in sessions can adapt a route for use such as hiding assets or adding scenic interest.
 
Yeah I'm trying to save just a created new session no route edits whatsoever Saving an Edited Session Only and make a blank base session. Something is constantly triggering the save as new route and session dialogue prompt. I'm trying to figure out why that is when on other routes I can do that just fine.
 
Something is constantly triggering the save as new route and session dialogue
My immediate suspicion is that something in the route is being edited. To test this lock all your route layers and then edit your session. Does it tell you that the layer of the object being edited is locked?
 
Are you using a version of Trainz that has the UDS interface? Are you during session creation every going into driver? It is my experience that doing something as simple as changing a turnout while driving can trigger a route save when you flip back into Surveyor and the switch is still at the changed position. This might also be true for any asset that changes while in Driver. At least, that is my guess.
 
My immediate suspicion is that something in the route is being edited. To test this lock all your route layers and then edit your session. Does it tell you that the layer of the object being edited is locked?
Layers are locked above its still doing the same thing.
I've also tried the trick of saving new route and session then taking the new session and switching to the dls'd downloaded route.
 
If you are trying to edit a session that is linked to the original, it will still want to save the route under your kuid on exiting.
 
If you are trying to edit a session that is linked to the original, it will still want to save the route under your kuid on exiting.
I've also just now save new route and session then went into the new route and session to create another new session on that version of the route and it does it again wanting to save new route and session.
 
Mayfield - Davenport by and1
I have just downloaded and installed this route and it does have "issues"
  1. 2 of its assets (<kuid:95230:100021> and <kuid:95230:100801>) are no longer on the DLS as they had been removed - possibly copyright violations or for repairs.
  2. The route itself is classified as "Third Party" - not always a good sign.
  3. A large number of assets have warnings - mostly because they contain .FBX files which are remnants of the creation process using 3D software and are not needed in Trainz assets. Warnings are not errors but the FBX files should have been removed.
  4. CM report that 208 assets are missing - the route description does indicate where these can/might be found.
Testing the creation of sessions confirms your problem that you cannot simply save the new session without also saving the route. I saved the route using a new name and repeated the process using my newly saved route (which now has my <kuid>) and the result was the same.

I then created a clone of the route and repeated the process with the same result.

The two route layers are both locked and unlocking them made no difference.

So I am at a loss to explain this. Its large number of missing/unknown assets (208) immediately activates my firm policy of deleting the route as I am not into playing the "hunt the missing asset" game.
 
Last edited:
I have just downloaded and installed this route and it does have "issues"
  1. 2 of its assets (<kuid:95230:100021> and <kuid:95230:100801>) are no longer on the DLS as they had been removed - possibly copyright violations or for repairs.
  2. The route itself is classified as "Third Party" - not always a good sign.
  3. A large number of assets have warnings - mostly because they contain .FBX files which are remnants of the creation process using 3D software and are not needed in Trainz assets. Warnings are not errors but the FBX files should have been removed.
  4. CM report that 208 assets are missing - the route description does indicate where these can/might be found.
Testing the creation of sessions confirms your problem that you cannot simply save the new session without also saving the route. I saved the route using a new name and repeated the process using my newly saved route (which now has my <kuid>) and the result was the same.

I then created a clone of the route and repeated the process with the same result.

The two route layers are both locked and unlocking them made no difference.

So I am at a loss to explain this. Its large number of missing/unknown assets (208) immediately activates my firm policy of deleting the route as I am not into playing the "hunt the missing asset" game.
I just ran into the same situation with one of my own routes. I set up some consists on the route and saved. In the olden days the prompt would be to save the session. I got the save route and session and had to save both to keep my changes. I then moved a consist and when I saved this time, I got the expected save session only box.

I think this is a bug introduced by UDS.
 
I just ran into the same situation with one of my own routes. I set up some consists on the route and saved. In the olden days the prompt would be to save the session. I got the save route and session and had to save both to keep my changes. I then moved a consist and when I saved this time, I got the expected save session only box.

I think this is a bug introduced by UDS.
I think I can confirm this as I decide to attempt to find a work around and after messing around with the route and got the save box to appear. I'll have to consult the route maker on that front.
 
I think I may have tracked down the problem with the save loop error. Something happened btwn this version <kuid:293137:105463> Mayfield - Davenport and this version <kuid2:293137:105463:3> Mayfield - Davenport. The orginal version of the route doesn't have this problem but the 3rd version did have a problem this may have occurred because of a UDS error when saving the route that must have triggered it. During any point in time during the making of the update to the route did you see something funky or not normal happen during the save or use the UDS the go from driver to surveyor then back to driver and a glitch occur? Second option could be an error occur because of an asset script getting messed up due to the UDS functionality.
 
Back
Top