Sessions & scenarios problems

[Kevin_Beresford]

Hello to all
While I appreciate all the work everyone puts into making sessions/scenarios, I don't have the skills to do them myself, it is very frustrating to spend a lot of time to download & install on my computer when 9 out of 10 of them don't work for various reasons. Missing dependencies, script errors, etc. I am always having to delete them after downloading because most of them don't run.
Without wishing to be rude or offensive to anyone, why can't they be tested more thoroughly before being submitted so they work without all the errors. It is very frustrating to drive anything if they don't work. I am sure there are many others who face the same problems.
Regards trainman :'(

 

[JackClare1995]

Script errors could be down to your content. Same for missing dependencies, make sure everything on your end works properly

I had a problem with the AJS stations at one point. They were all marked as faulty and everytime I stopped at one I got a script error. Turns out the script had disappeared! Try redownloading a session's dependencies

 

[Pendolino]

Hello Kevin,

I have made, released and tested many sessions for Italian and U.S. routes: 99% of the issues are due to missing dependencies. Even script errors are often due to missing dependencies (e.g.: if you have a portal set for emitting a train containing a car you have not downloaded, the dreaded red dot (or bug) will appear).

It is imperative that the route, the session and the locomotives and rolling stock have zero missing dependencies.

There are also some issues with some Trainz versions that make the problem worse:

1) TS2010 does not write the KUIDs rules and orders used in the session into the kuid-table of the session. If the author has used a rule or order that is not built-in in TS2010, CM will not report missing dependencies, but as soon as the rule/order is activated the session will crash. As far as I know there is only a way to avoid this issue: the author must take note of the rules/orders he used as the session is created and then must manually add their KUIDs to the kuid-table of the session. This bug has been removed in TS12 (thanks, N3V!) and this has been the main reason I switched to TS12. When a script error appears, click on the red bug and then click on the "More" button: if a KUID is listed, take a note and download it.

2) The KUIDs of the locomotives and cars generated by portals are not written into the kuid-table of the session. This can cause the generation of incomplete or engineless consists (with unpredictable results) or straight "red bug" errors. There is a rule (I don't remember its name now) that should automatically add them to the kuid-table of the session, but I have not yet tested it, so I can't tell how it works. If the author has not added the kuids of the locomotive and cars to the kuid-table of the session, this is a perfect recipe for failure, with no possibility of identifying the missing assets. So far, I have solved this issue by preparing the portal-generated consists in advance and then manually adding their KUIDs to the kuid-table of the session. In this way, if the user does not have a required piece of rolling stock, CM will report that the session has a dependency (the consist) with missing dependencies, which can therefore be located and downloaded. I hope this issue is solved in TANE...

While I found the creation of sessions one of the strong points of Trainz, testing them is a very time-consuming affair, especially when you run the same session dozens - literally - of times to check out that anything works as intended. It is essential to have a dedicated team of beta testers to find out bugs before the session is released.

 

[shaneturner12]

The rule Pendolino is referring to ref: portal trains is called Portal Dependencies and is on the Download Station. Be aware though that if two portals have the same name, it will cause a script issue.

Sgabe

 

[oknotsen]

Try these sessions:

• Woodridge switching
• Woodridge logs run
• Coal for Charlescrossing
• Headenburg airport shuttle

They are made with built-in (or updates of those) assets only.
Support topic.

 

[philskene]

Hi Kevin --

Like you I too get very frustrated by routes and sessions with missing and unknown dependencies.

Which is why with my sessions I use built-in or Download Station content and, with any external content, always give a direct link to the download site in the description under the thumbnail.

I also now give a link to a post in the Forums where additional details of the session can be found.

Search the DLS with "philskene" as the author.

Phil

 

[Kevin_Beresford]

To JackClare1995
Thanks for your response, I have redownloaded the dependencies on all the the maps more times than I can count, but still end up with missing items.
Regards trainman

 

[Gary_Evans]

Kevin:
In your post that opened this thread you stated that you are frustrated with missing dependencies

etc. and wondered why sessions are not tested before being uploaded. In this post you imply that

creators do not test thoroughly before uploading. I deeply resent the implication. I am sure that all

session creators test thoroughly before they upload. I certainly do, almost to the point of nauseam.

Do you not realize that if you can't run a session because of missing dependencies the creator

could not have run it either? The creators ran and tested the sessions successfully because all of

the dependencies were in their system. If as you stated in your last post, you have downloaded

several times to no avail, then the assets you seek are not on the DLS if in fact you are

downloading from the DLS. If you opened the dependencies file and found that they are all on the

DLS, then you are having a problem with your system. If however, some or all the missing

dependencies are listed as unknown, then they are from a third party site. If that is the case,

shame on the creator for not issuing a warning but it does not mean they didn't test before

uploading. In my years with Trainz, I have uploaded nearly a hundred scenarios/sessions and

found that most problems arising with missing dependencies were due to errors originating with the down loaders who were far too quick to pass blame.

Gary