Updating old double track and bridges

[Pendolino]

Hello,

I am upgrading an old route to TRS19, but I have got a problem with an old asset. The darker tracks in this picture are double tracks (technically, a "bridge" with tracks only, and no bridge mesh). I would like to replace them in place, since there are a lot of trackside catenary poles attached to them and there are few things I hate more than laying catenary.

This is the double track: it uses two chunky-mesh tracks. Since I made the asset (one of the glorious results of a misspent youth ), I thought "Great, I only have make a new version, replacing the chunky-mesh tracks with procedural tracks"

So I made a new version, and it worked... to a point. If I lay the object, it shows the new tracks (on the left in the image below). But the track that was already laid in this test map still shows the old tracks. If I pick the two assets with the dedicate tool, the KUID appearing in the bottom right corner is the same (version :3)

Since the same track is also used in some "real" bridges used in the same route, I also checked their status: the bridges on the map still show the old tracks, but I lay down a new instance of the bridge the latter shows the new tracks.

Is there some way to solve this issue, or should I rip off all the old double tracks and bridges?

I have not tried using the "attached-splines" technique, since I am not sure whether it is applicable to this situation.

Thanks in advance for any advice!

 

[TSwenson]

Right of the top of my head, did you obsolete the old asset?
If you only cloned your own asset and it has the same Kuid it doesn't know to render the new one, if you made a newer version then it should automatically update (i.e. 123:123 for both, or 123:123 for the old and 123:123:1 for the new track).
Just my first instinct fix, I hope this helps...
Thor

 

[Pendolino]

Thanks! Yes, the old double track with chunky-mesh track was <kuid2:69593:31003:2>, the new one is <kuid2:69593:31003:3>. As soon as I committed version :3, version :2 was marked as "obsolete".

The track specified in the "bridgetrack" tag is, of course, totally different: for <kuid2:69593:31003:2> it is a chunky-track of mine, for <kuid2:69593:31003:3> it is a built-in procedural track.

The game should replace the old version with the newer one, and it actually does so: picking the asset after I loaded the new version shows <kuid2:69593:31003:3> in the bottom right corner. The existing asset, however, is still rendered with chunky-mesh track.

I also tried using the pick up tool and placing the selected asset on the map: the newly laid track correctly shows the procedural track (as it should).

 

[TSwenson]

Drat... so much for the easy fix.
Sounds like the program isn't recognizing the update right, I have a few suggestions, after the age old "log out completely and restart the machine and log back in" process.
Try bulk updating the asset by selecting on of the old ones in the bulk tool and then finding the existing one in the track menu on the right and updating it to itself...
You can try moving a spline point on the affected "track" bit and then undo the move (ctrl-z) and see if that does anything... I use this for graphic glitches on procedural track.
Basically, you're trying to make the game look at the asset at that point and get it to use the new one, and remember, if it works it's not dumb.

 

[JCitron]

You can try bulk-updating the track. I've done that before with double-track assets. The track changes to the newly chosen track the route, but the problem is it's still going to be the wrong ones if you are going to upload a route or the assets.

Another thought is this might be a caching issue with TRS22 we've run into. You can try exiting completely and then running a DBR. That might fix the problem, but I'm not sure.

 

[stagecoach]

Will updating the asset also update the mesh? I have found that assets once placed do not update automatically. All my ships once placed and then corrected for angle, height etc only applied to newly placed assets, the already placed assets remained unchanged. This goes back to very early versions of trainz when you could roll a car on its side and upload the route with it on and it remained on its side until you replaced it and reverts to the original.

 

[Pendolino]

Thanks for your replies, gentlemen!

I have not attempted to bulk-update the tracks because, as far as I know, this operation cannot be performed on "kind=bridge" assets since the time bulk-updating was introduced back in TS2009. In fact, I tried it just now, and a popup appeared in the center of the screen, stating: "Bridges, tunnels, multiple tracks and trains are not allowed". Is this allowed in TRS22?

Then I attempted to bulk-update the individual track and it worked!!

This is the test map with the two "identical" double tracks:

And this is the result of bulk-updating the single track called in the config of the previous version with the procedural one: it worked like a charm!!!

Thanks a lot, you all have been very helpful!!!

 

[TSwenson]

Yeah! victory!
Oh, do I feel dumb.... it's a simple solution, and it was what I was trying to remember in my previous post (I'll blame it on my new puppy distracting me). It seems dumb but it works. I use this trick all the time, particularly with things like replacing old style tracks in industries.

 

[Pendolino]

As you said above "If it works, it's not dumb"!