79 Script Errors in EIT AutoDriveWithmcTimetable Asset

Smileyman

Socialist Serenade
Having decided to go 100% into understanding ALL aspects of the Enhanced Interlocking Towers by @pguy , including mission codes and everything else, so that I can decide whether to implement it on my route, I have hit a snag that's not of my doing.

The AutoDriveWithmcTimetable Asset, freshly downloaded from the DLS, shows 79 script errors during compile.
I've tried a DBR and an extended DBR, as well as re-downloading the asset a couple of times.

I'm using TRS2019, fully updated, and the asset in question is <kuid2:61392:8322:76> which Content Manager implies is the latest version for TRS2019.
All dependencies are up-to-date.

The pieces are starting to fall into place for using the EIT and all it's extras, but I'm going to need this asset to be able to understand and use ALL aspects of the EITs.

A google search didn't bring up anything, or anyone having this problem with this asset, so... I don't know.

If @pguy is about, I can post a couple of screenshots of the 79 error messages if it's useful, although I'm hoping there's a simple fix.

Cheers.
 
Why not? :)

EIT-Errors.jpg
 
My guess is that the script is missing an include file or two. Perhaps a library and some helper functions?
Spot on!

As soon as you said that, I knew where to go because I was looking at the source code earlier.

At the start of the code he is initializing links to the libraries so he can use them, but of the four libraries that he's trying to connect to,
mchelper, nochelper, stthelper and esvhelper4, he only set includes for three of them, forgetting to add one for the stthelper class.

Once I added the correct include, committed the asset and rebuilt the database, zero errors.

I wonder why no-one has ever reported this?
Couldn't find a mention anywhere.
I know EITs and all the extras that are required to get them running properly have a big learning curve (I'm half way around that curve right now), and that the deeper you go, the more complex it seems (but it's not, it's just abstract without the information at hand), but were/are people giving up on using EITs before they got to the timetable part, which is further down the line, and that's why it was never reported?
And those that had cracked it had probably moved on to TRS22 by the time they got to using the timetable feature, and Pierre had probably fixed his omission in versions for TRS22 by then.

Anyway, thanks mate.
If I hadn't seen your post, it probably would have been days before I came back to it, and would have ended up scouring the source code, doing diff tests on the new and previous versions, etc., before noticing it.

Cheers.
 
Last edited:
Those sort of errors seem typical of a first compile after clearing syntax errors. I.e. forgotten includes. I was puzzled how it was uploaded like that.

I have zero experience of EITs other than a basic understanding their purpose. I did write a locked shared track asset a few years back but never released it as I didn’t know how it would interact with EITs. It was based on the system used on the IoW railway between Smallbrook Junction and Havenstreet (I think). I lived in that area as a kid a very long time ago.
 
Yes, we've all been there, forgetting includes, but usually testing brings up the mistake immediately.
So it is a puzzle how he didn't see it, how it got uploaded and accepted, and how no-one has asked for a fix when it showed up as faulty in Content Manager.

I don't have Trainz 22, so I can't see if he continued to update it with "Trainz 22 and later" versions, although I'm pretty sure I've seen it discussed here.
Maybe he noticed it, fixed it, and the fix just happened to be the first version of the "22 and later", leaving the "19 and later" version broken.
I'm sure he didn't intend that.
 
Back
Top