What exactly is 'saved' in a session save file?

[Xengeance]

Exactly what the thread says on the box. What all exactly is saved on a route when you save the progress of your session in Driver (i.e. not the actual Session itself Surveyor) and is there a way to extend that capability to things like scripts and third-party content. Like, for example, if someone were able to somehow implement a 'campaign mode' route which would obviously necessitate the ability to keep track of data over multiple instances of a session as one plays through it, but this could also extend to less complex areas like preserving soup tables in a script across multiple playthroughs of the same session, or maintaining consistent weather between saves - as in ' Hey, why is it sunny now? Last time I saved it was black as pitch and pouring rain?!')

 

[shaneturner12]

Usually, a Driver 'session' (actually, it's known as a saved session in the main menu) usually stores information on where trains are and industry status etc.

I would advise caution if you are using portals though - the state of these will not be saved as expected - the portal usually resets when loading the saved session back in, which may cause unexpected behaviour (this may also apply to any scripts that use the 'soup' feature - it usually resets each time the saved session is loaded - this is due to a limitation in Auran's scripts.

Shane

 

[trev999]

Session Variables are also saved in a session. Some rules will automatically restart after saving e.g trigger rule, while others do not. It depends whether the rule has a thread which can be properly restarted

Cheers - Trevor

 

[Xengeance]

Session Variables are also saved in a session. Some rules will automatically restart after saving e.g trigger rule, while others do not. It depends whether the rule has a thread which can be properly restarted

Cheers - Trevor

So you mean session variables as those variables stored in the scripts of session rules? What if the rule didn't rely on a thread and simply acted as some kind of database to store various information in to be accessed/changed by other assets in the route?

 

[danny5]

Then that may explain why some of my switch levers were missing after i had run thur them the night before.

 

[Dap]

If an asset is properly scripted, it will be able to save all it's variables and then restore them when the session is resumed. It just takes more code writing and some asset creators do not take the time to do it. I know, because I used to be one of those script writers. But now that I know how to do it, I'll never create another scripted asset that does not save and restore it's variables