I tried to save the settings on ATLS from a single session to the route. I went over the tutorial and directions atleast 50 times today!!! And, regardless, the crossing signals never works. WATCH OUT CARS!!! Anyways, I'm having alot of trouble with this.And after doing this for 49 crossings, I'm quite angry. Can somebody help me with this please?:'(
ATLS settings not saving to the route
- Thread starter diesel9
- Start date
dude drop and roll..........
I just started with ATLS stuff last couple weeks and ya I did give up on it......
But I had odd ball crossings to cover so second shot got it right away..........
So you need to post exactly what you set em too.........
And I can give ya a straight shot ....these are very easy once ya get the hang of it.........
Dave =)
I just started with ATLS stuff last couple weeks and ya I did give up on it......
But I had odd ball crossings to cover so second shot got it right away..........
So you need to post exactly what you set em too.........
And I can give ya a straight shot ....these are very easy once ya get the hang of it.........
Dave =)
Gandalf0444
FVRR member
The ATLS settings need to be saved in a session, not the route itself.
Gandalf0444
FVRR member
No you can't. The settings will NOT be saved if you save it in a route and not a session. The route will save the locations of the ATLS objects but that is it.
Actually you can....sort of.
from ATLS documentation.
SAVING TO THE MAP (if required)
All the settings you make in the ATLS will be saved to a Soup, so if you are running a Session that's all you need to do. In most cases you may name an asset to your choice and it will have no impact on its working, settings still being saved to a Soup. However, if you are saving purely for identification purposes, then you must avoid using the Control Characters. These characters are [ ] ( ).
If you want to save the settings you have made to a map, (if you are a Scenario script writer for example), then this may be done by saving the name of the asset as follows, using those Control Characters.
Open the Properties Dialogue Box of the ATLS asset you want to save and set it up as required. Then, look in the top left corner and you will see something like 'ATLS1[65,E,O]'.
This is an encoded representation of all the settings you have made to the asset. If you save the name of this asset EXACTLY as shown, the settings will be retained and recovered when you re-load the map. They will also work in a Scenario.
It’s important to keep the format exactly, including the square brackets and commas or it will either just not work, or may cause errors.
On occasions you may encounter the 'That Name Is Already In Use' message. If you do, don't save it but add '(A)' to the name you are saving. So you will save: 'ATLS 1[65,E,O](A)'. Use the letter (B), (C) etc., for subsequent clashes. The brackets are important.
If you want to change the 'saved name' or delete it, its always best to save the map and re-load afterwards. Otherwise errors may occur.
Remember, you don't need to save if you are just running normal Sessions.
(Special warning for the Controller asset. The generated name in this asset will get very long if you have lots of Routes and Phases. Note also that the Phase Timing durations are 'rounded' when saving to a map.)
from ATLS documentation.
SAVING TO THE MAP (if required)
All the settings you make in the ATLS will be saved to a Soup, so if you are running a Session that's all you need to do. In most cases you may name an asset to your choice and it will have no impact on its working, settings still being saved to a Soup. However, if you are saving purely for identification purposes, then you must avoid using the Control Characters. These characters are [ ] ( ).
If you want to save the settings you have made to a map, (if you are a Scenario script writer for example), then this may be done by saving the name of the asset as follows, using those Control Characters.
Open the Properties Dialogue Box of the ATLS asset you want to save and set it up as required. Then, look in the top left corner and you will see something like 'ATLS1[65,E,O]'.
This is an encoded representation of all the settings you have made to the asset. If you save the name of this asset EXACTLY as shown, the settings will be retained and recovered when you re-load the map. They will also work in a Scenario.
It’s important to keep the format exactly, including the square brackets and commas or it will either just not work, or may cause errors.
On occasions you may encounter the 'That Name Is Already In Use' message. If you do, don't save it but add '(A)' to the name you are saving. So you will save: 'ATLS 1[65,E,O](A)'. Use the letter (B), (C) etc., for subsequent clashes. The brackets are important.
If you want to change the 'saved name' or delete it, its always best to save the map and re-load afterwards. Otherwise errors may occur.
Remember, you don't need to save if you are just running normal Sessions.
(Special warning for the Controller asset. The generated name in this asset will get very long if you have lots of Routes and Phases. Note also that the Phase Timing durations are 'rounded' when saving to a map.)
Last edited:
Approach_Medium
Trainz Addict
Mikeman; You are a programmer / scripter, and I have done some scripting myself. But I am afraid the average TS player does not have any idea of what you are talking about. Like, what the hell is a soup? I thought it was just something you eat
.
Of course, I have learned that the Soup is just a database used by Trainz to store an object's variables / properties at any point you need to save them.
I suggest a much simpler method; Always work with sessions.
When you are working on a route in Surveyor, just make sure you always load the last saved session to continue your work.
Atlas, and other assets do not normally save their data with the route. I learned this the hard way with the Junction Controller. I had the Hoboken passenger yard all set up with the junction controllers all over the place controlling slip switches, etc and suddenly realized that my switches were no longer working together as I had programmed. I then realized that I needed to save sessions every time.
FW
.Of course, I have learned that the Soup is just a database used by Trainz to store an object's variables / properties at any point you need to save them.
I suggest a much simpler method; Always work with sessions.
When you are working on a route in Surveyor, just make sure you always load the last saved session to continue your work.
Atlas, and other assets do not normally save their data with the route. I learned this the hard way with the Junction Controller. I had the Hoboken passenger yard all set up with the junction controllers all over the place controlling slip switches, etc and suddenly realized that my switches were no longer working together as I had programmed. I then realized that I needed to save sessions every time.
FW
ApproachMedium
Youtube dude
What I have done is to create a base session in which all the ATLS is configured. Then when I want to create a session to play in, I open up the base, lay our the trains, then use save as to save it under a new session with all the trains and ATLS crossings configured. The base session will stay the same, and you wont have to configure 49 crossings for every session 
-Joe
-Joe
Gandalf0444
FVRR member
That is exactly what I do.:hehe:What I have done is to create a base session in which all the ATLS is configured. Then when I want to create a session to play in, I open up the base, lay our the trains, then use save as to save it under a new session with all the trains and ATLS crossings configured. The base session will stay the same, and you wont have to configure 49 crossings for every session
-Joe
Hi Guys.....
Saving to a Session is the easiest way to save ATLS settings. The 'Soup' which undoubtedly stands for something, is as you say what the 'database' is called that saves all the settings in Trainz. It’s automatic.
However, if you want to, you can also save to the map (or Route). This is fiddly and was really put there to accommodate Scenario writers. That's the old way of controlling Trainz. Scenarios don't have Sessions so the blue coded numbers in the top left corner is the only way to save the settings for them. Even I don’t run scenarios anymore so I’ve really only kept it in, (on my Sen City Signals) so people can save to a map if they want to for whatever reason. My next project won't have that ability.
If the settings are saved as the name of the asset as shown in the top left corner then it all should work.
If Diesel posts some photos of what he’s doing we may be able to tell what’s wrong. It may be a error in the program that he’s discovered for all I know. Not many people save to a map so it’s not had a lot of testing.
Boat
Saving to a Session is the easiest way to save ATLS settings. The 'Soup' which undoubtedly stands for something, is as you say what the 'database' is called that saves all the settings in Trainz. It’s automatic.
However, if you want to, you can also save to the map (or Route). This is fiddly and was really put there to accommodate Scenario writers. That's the old way of controlling Trainz. Scenarios don't have Sessions so the blue coded numbers in the top left corner is the only way to save the settings for them. Even I don’t run scenarios anymore so I’ve really only kept it in, (on my Sen City Signals) so people can save to a map if they want to for whatever reason. My next project won't have that ability.
If the settings are saved as the name of the asset as shown in the top left corner then it all should work.
If Diesel posts some photos of what he’s doing we may be able to tell what’s wrong. It may be a error in the program that he’s discovered for all I know. Not many people save to a map so it’s not had a lot of testing.
Boat
Ya saving to a map dont do much good even with P/L industries.....
But like Boat said and I earlier need to see what he s done...........
I found it very simple to use once I took time to figure it out correctly and
I found it to work with a tricky spot of 2 line s merging into 1 with a branch line jct to boot of course in 2 different directions and only used 6 triggers
in the 2-4 set up..........
I have so far 28 crossings set up and different set ups pending double track and single and works great...........
Dave =)
But like Boat said and I earlier need to see what he s done...........
I found it very simple to use once I took time to figure it out correctly and
I found it to work with a tricky spot of 2 line s merging into 1 with a branch line jct to boot of course in 2 different directions and only used 6 triggers
in the 2-4 set up..........
I have so far 28 crossings set up and different set ups pending double track and single and works great...........
Dave =)
Actually I expect to use the save to map feature quite a lot. Firstly, it saves a lot of heartache for the large number of people who never download the basic session, and secondly it saves a huge amount of work if you have two routes you want to merge, as the session data is always lost for one route or the other.
Paul
Paul
Well, after toying with ATLS some more, I've realized that the settings I saved on the route were automatically set to LCM(Level Crossing Mode) and for the triggers, 2 way running/4 trigger setting were already implemented. Which means that all I had to do wuz click on the number I want the controller,slave,and triggers to have. So it appears that this is all that saves to a route. Pics should be on here tommorow I promise. It's been a busy day today and I only had 5 minutes of Trainz today.