Does the re-rail portal actually work? kuid2:116387:6:1 by Maggs.

[Dinorius_Redundicus]

In TS2010, CM says this asset has this fault "Error: Unable to link compiled script class."

It is a built-in so I suppose I can "revert to original" but this may only suppress the error message without fixing the fault.

Anyone else see the same problem? Anything I can do about it?

 

[fran1]

Mine has no errors, but I also have the :5 version which is re rail portal (not built in ), yours is the basic re rail portal. Get the :5 version and see if the error goes.
If not use disable the built in one and use :5.

 

[Dinorius_Redundicus]

Where is the :5 version?

CM tells me the :1 version is the only one it can find. Remember I don't have TS12.

 

[shaneturner12]

I would advise doing a database repair and see if that fixes it. Failing that , revert it to original.

Shane

 

[Dinorius_Redundicus]

I've already done a database repair and it fixed nothing. The fault and lack of other versions seems real. Reverting is a false fix as you know, it just disguises the fact that kuid2:116387:6:1 has something wrong with it. Never mind, no big deal.

 

[fran1]

Where is the :5 version?

CM tells me the :1 version is the only one it can find. Remember I don't have TS12.

Sorry about that, been reminicing, kuid 2:116387:5:1- re rail portal by maggs build 2.0.

 

[dragonharh]

Re-rail Portal,<kuid2:116387:5:1>
download this one is works fine in TR10 I been using it for years and never had errors.

 

[Dinorius_Redundicus]

Then I wonder what this script fault is all about?

 

[Azervich]

I've seen this error before, it's to do with the Class name in the script and the class name linking it in config.txt, they both have to be the same or that error comes up, even an upper case latter in script and lower case letter in config throws that error too, it need to be exact... here's an example

config.txt

script "loco"
class "Loco"

loco.gs

Loco is class locomotive

as you see I used a uppercase 'L', if you type a lower case instead on just one of those you'll get that error.

Cheers.

 

[Dinorius_Redundicus]

I thought it might be that too, especially since the cases in config.txt don't match that of the script file;

script "PortalTunnel"
class "PortalTunnel"

script filename = portaltunnel.gs

However, when I changed the 2 config.txt entries to all-lowercase, exactly matching the script name, the 'link' error was still there.

I reverted to original, which unsurprisingly eliminated the error report. I then Opened for Edit, still no error (which was surprising). I was even able to make the following edits and re-commit without causing the error to return;

- removed the messy looking foreign language descriptions and string-table tags.
- removed the Type tag.
- converted category-era-x tags to one category-era tag with "1800s" as the only value.
- converted category-region-xx tags to one category-region with "UK" as the only value.
- added a category-keyword tag with some keywords.
- changed username from "Re-rail Portal Basic" to "Portal re-rail basic".

Note that the script/class tags, with their mixed lower/uppercase letters were left untouched, and as I said, the fault did not reappear.

I am not sure what to conclude from all this, apart from thinking that I must have previously made some edit other than the ones mentioned above which triggered the fault. And it seems that you can actually get away with mismatching cases between the config and script filename.

 

[p-dehnert]

The script filename isn't casesensitive, it's the class entry which must exactly match the classname in the scriptfile.

Peter

 

[Dinorius_Redundicus]

The script filename isn't casesensitive, it's the class entry which must exactly match the classname in the scriptfile.

Peter

And that leaves me even more puzzled.

The script filename, the internal contents of that script, the class and script tag values - none of those were changed. But CM was initially detecting a fault and later no fault.