Questions About Route Sharing Your Routes

GN1996

Not a real user title.
If you build a route and would like to share it with others or use it for multiplayer, what do you have to do? Do you have to ask people if you can use their content in your route, or does that matter if the content was built in? What other guidelines does a person have to follow if they wish to share thier route?
 
None!

The only restriction you face is that for multiplayer ALL route and session assets MUST be built-in or DLS. No exceptions.

For a non-multiplayer route you can use anything. Distributing a route in no way compromises the license of any asset used in the route. The way Trainz works you distribute ONLY the route and/or session you created, you are not distributing the dependant assets used....
 
Okay, so I could just upload my route and session if the assets follow those criteria, then call it good?
 
Hmmm...that seems odd. If the route and session are already on my hard drive, why would I have to download them?
 
It actually makes a certain amount of sense. MP requires everyone to be on the same page, to be using the exact same route, content, etc. If it comes straight from the DLS, then the program can be (reasonably) sure nothing's been modified.
 
I noticed that when I look at asset details for routes, it gives a list of people who contributed dependencies. When my route is uploaded, does CM automatically do this or do I have to it?
 
CM will do that automatically for you.

Sometimes CM will not list all dependencies. An example is trains that are emitted from portals, CM will not list them as dependencies. There are a few other instances which I can't remember off hand.
 
If you don't intend to run multiplayer sessions on your route then I don't see why you should download it from the DLS once it's available and overwrite your original copy.
 
A good rule to follow is not include rolling stock in a session that's going to be uploaded. The reason is the rolling stock can easily be downloaded and also not everyone may want to run the same trains on their copy of your route.

John
 
A good rule to follow is not include rolling stock in a session that's going to be uploaded. The reason is the rolling stock can easily be downloaded and also not everyone may want to run the same trains on their copy of your route.

John

John,

I think you meant to say do not include rolling stock on a ROUTE that is to be uploaded.

A SESSION, on the other hand does need to have cars and engines installed before uploading the SESSION.

CM will do that automatically for you.

Sometimes CM will not list all dependencies. An example is trains that are emitted from portals, CM will not list them as dependencies. There are a few other instances which I can't remember off hand.


When I create a session that uses a Portal, I always add the consists that will be emitted to the SESSION Config file kuid table. Easy to do manually. And t makes sure the SESSION user has everything needed to run the SESSION.


David
 
Last edited:
Back
Top