Why doesn't automatically naming of junctions follow Junction 1, 2, 3 etc?

Red_Rattler

Since 09 May 2003
How are junctions automatically numbered?

For example, I put the first junction on a test layout, it starts with Junction 242, instead of Junction 1, 2, 3 etc. Only vary rarely do they follow a number-in-order pattern.

And that's for all versions and builds.

Why don't they start with 1, 2, 3 etc, and if you add a junction on another route, start off from where the numbering may end?
 
What a good question.

I've often wondered about that. Could it have something to do with the physical locations of the junctions on the route, rather than the order in which they are laid, possibly based on some kind of unseen underlying mapping matrix. It could, perhaps, be related to the numerical value of the nearest grid intersection.

It would be interesting to know the actual answer.
 
Just did a test with a Create New Route, and the first junction was named 0, went a bit further along, and the next number generated was 2. Went in between those two junctions, and the it was named 4.
 
Just did a test with a Create New Route, and the first junction was named 0, went a bit further along, and the next number generated was 2. Went in between those two junctions, and the it was named 4.

Related to grid squares maybe ?
 
Just tried it myself. Grid squares are not it. I put down one length of track and 10 junctions. Sure enough, started from 0 and finished at 18. Quirk of the programming that I had never noticed before.
 
Good Morning,

Good question Red ---

A junction fan here -- In my massive Desert route, junctions begin with 3 digitals -- I, do, however name each junction, since I do this for any junction rule anyone uses! Still, I must agree -- it would have been much easier if the 1,2,3 etc system would have been implemented here!

Ish
 
G'day!

I think this has been an issue since TS2009, as the previous versions of Trainz, eg TRS2004/6 TC, retained the 1, 2, 3, 4 etc on junctions, turntables, trackmarks and many other trackside objects.,

Cheers!

jake.
 
I am getting the impression that every (nameable) object in a route gets an (even) number, starting at 0. That means switches, but also building. Now it does not show in any way for building, but it does for switches.

I just did a simple test to proof this:
I put a stretch of rail on an empty baseboard. I then created 3 switches which got the names "Junction 0", "Junction 2" and "Junction 4".
I then put 2 building on that baseboard. The game counts these and gives them not visible numbers, which in this case would be 6 and 8.
I then created another switch, which then got name "Junction 10".

So if your first switch gets number 500, you probably have put 500/2 = 250 objects on the route before that.
 
That's an interesting observation, but I don't see the purpose of it other than how the object is referenced in the program.

It would be nice if we could specify a series for our junctions, objects, etc., and have the program follow that for the route. All junctions for example could begin with jct-000- and then Surveyor automatically append a number to this prefix. This prefix could be changed at any time during the route building process.

John
 
I wonder what influence that would have, John, as you (generally speaking) end up having to rename the junctions to give them a fitting (location? role?) name anyway.
If the name is not relevant, I don't see how having them in connection order has any value.

But how you like your naming of things, like all things artistic, is always the result of personal taste / preference of course.
 
I wonder what influence that would have, John, as you (generally speaking) end up having to rename the junctions to give them a fitting (location? role?) name anyway.
If the name is not relevant, I don't see how having them in connection order has any value.

But how you like your naming of things, like all things artistic, is always the result of personal taste / preference of course.

True, but some people use a prefix of some sort and this could be set automatically. The number that follows could be the even number anyway, or if N3V fixed this, could be something that the user set. Personally I don't name a junction unless I need to. I did that routine once and went batty as I forgot where I was in my sequence. :)

John
 
I usually use city abbreviations (if I try to build a fictional or real route) or position (like the level in my multi-level layouts) as start of the name. I noticed that when running sessions you can sometimes get messages about trains waiting for junctions (or signals). In those situations just the number of a junction does not help me; I'm getting to old to remember the location of each number :hehe:.

some people use a prefix of some sort and this could be set automatically
I like that idea!
That would help a lot as it would already do half of the (otherwise having to do) rename work for me.
 
I guess any new junction number supercede the last number of track graph elements (nodes or edges, depending on how the graph is presented). For example, if you have the simple straight track, it may have such nodes: 0 - track(no number) - 1. Then, when you add a junction in the middle of it, the graph changes: 0 - track - 2 (junction) - track - 1. The next junction, as you may guess, will have the number 3. If you add another track section and then add a junction to it, you will get this layout: 0 - 2j - 3j - 1 - 5j - 4. I hope I got it right. At least that's how I'd implement it :)
 
Back
Top