track-condition fiasco.

[b9k9kiwi]

The really useful track-condition config.txt setting has been obsoleted ... no announcement, no reason given.

It seems that any routes built or edited before this event will retain the track-condition set in the config.txt of any track used, but
editing or building a route now is a fraught process with every separate section having to be set individually.

I understand that there is a form of bulk track-condition updating in surveyor 2, but I really don't want to go anywhere
near that thing.

 

[pware]

The really useful track-condition config.txt setting has been obsoleted ... no announcement, no reason given.

The track-condition tag is alive and well and is still part of the config.txt file for procedural track assets. See https://online.ts2009.com/mediaWiki/index.php/KIND_Procedural_track.

Track condition for older (non-procedural) track has, as far as I am aware, always been handled by using the Track Bump object (<kuid:401543:3120> Invisible Track Bump). All my track is procedural so I have never had to resort to using that asset.

I understand that there is a form of bulk track-condition updating in surveyor 2, but I really don't want to go anywhere
near that thing.

Why not? I use it regularly and do not have any issues.

See Set_Track_Condition_and_Superelevation.

 

[b9k9kiwi]

The track-condition tag is alive and well and is still part of the config.txt file for procedural track assets. See https://online.ts2009.com/mediaWiki/index.php/KIND_Procedural_track.

Track condition for older (non-procedural) track has, as far as I am aware, always been handled by using the Track Bump object (<kuid:401543:3120> Invisible Track Bump). All my track is procedural so I have never had to resort to using that asset.


Why not? I use it regularly and do not have any issues.

See Set_Track_Condition_and_Superelevation.

Mixed messages? I have read other threads that state that the track-condition setting has been obsoleted.

go figure.

Anyway, it doesn,t work for me.

 

[pware]

Anyway, it doesn,t work for me.

Perhaps you could describe what you are doing and what you expect to happen. As I stated above, the Track Condition setting in the Surveyor 2.0 Tool Options Palette is working fine for me with an obvious "sway and bump" present in consists moving over the track.

 

[b9k9kiwi]

Perhaps you could describe what you are doing and what you expect to happen. As I stated above, the Track Condition setting in the Surveyor 2.0 Tool Options Palette is working fine for me with an obvious "sway and bump" present in consists moving over the track.

Thank you for your patience.

I'm still in standard surveyor mode - using track-condition tag in config.txt at this stage.

If I lay new track, or replace existing track - the track condition defaults to 0 (although default is supposed to be 50%).

Existing routes using procedural track with track-condition set in config.txt are not affected, providing I don't try to replace or update the track.

 

[pware]

I'm still in standard surveyor mode - using track-condition tag in config.txt at this stage.

I would steer clear of editing the config.txt files of the track because that will set the track condition for every instance of that track asset in the route including those track sections where you do not want that track condition set. So the track used in an old shunting yard can be given a poor track condition while the exact same track asset used on a running line can have a better track condition.

A bit of experimenting has revealed the following points:-

• In Surveyor Classic you can set the track condition of any track segment (between the end circles) for both procedural and non-procedural tracks. Just open the properties window of a track segment and set the required track condition value.
• The disadvantage of this in Classic is that you have to set this for every segment individually. In Surveyor 2.0 you can select all the track segments between junctions and/or track ends and set them all at once.

 

[b9k9kiwi]

I would steer clear of editing the config.txt files of the track because that will set the track condition for every instance of that track asset in the route including those track sections where you do not want that track condition set. So the track used in an old shunting yard can be given a poor track condition while the exact same track asset used on a running line can have a better track condition.

A bit of experimenting has revealed the following points:-

• In Surveyor Classic you can set the track condition of any track segment (between the end circles) for both procedural and non-procedural tracks. Just open the properties window of a track segment and set the required track condition value.
• The disadvantage of this in Classic is that you have to set this for every segment individually. In Surveyor 2.0 you can select all the track segments between junctions and/or track ends and set them all at once.

I clone procedural tracks so as to have the same track with a variety of conditions ... I don't intend to upload any of my routes so I won't be upsetting the relevant creators.

I've fiddled around with track condition in surveyor 2.0 with no success ... but I'll re-read the instructions and go back and try again.

In the meantime I am replacing the track in the troublesome route one section at a time (which is quicker than setting the track condition one section at a time), and this is fixing the issue at least for the
route I'm working on.

Thanks for your help.

 

[JCitron]

The old track-condition tag doesn't work with Pro-track but it still works with the non-procedural track. I also made some really, really, rough track for my own use by cloning and editing the config.txt files for the track I wanted to use.

This visual appearance only still looks pretty neat as coal hoppers and boxcars bob and weave as they're pushed down a decrepit branch line or yard track.

While I welcome the ability to change track on the fly using the properties, having the ability to create a fixed set of rotten or pristine track made it a lot easier when building routes.