Commodities and driver command setup doesn't work

[TorenHynes]

Hello there,

I have a minor problem with TRS06. When I try to open up "Add commodity" it says a nonfatal script error occured. A similar thing happens when I try to add driver commands. Any suggestions?

I can provide error codes if required.

 

[fran1]

I don't know if this applies to 2006 but check if you have a product called rusty re bar/40ft load. This causes issues in 2010+2012.
Also check if any products have a build number above 2.6, delete those also.

 

[shaneturner12]

There is also a Lime product that also causes issues.

Also check for faulty driver commands.

Shane

 

[fran1]

There is also a Lime product that also causes issues.



Shane

That I think was Dzien50's problem ages ago, a right sod to find.

 

[KenGreen]

I had this problem 2 years ago and both Fran and Shane helped me sort it out.
The problem is caused by downloading something containing a commodity with a higher build than 2.6.
My problem was Japanese passengers. I don't think Content Manager Plus has a build version column therefore you need to select commodity in CMP and view the config file (bottom option after right click) of each item to ensure that it doesn't exceed 2.6.

Ken

 

[stagecoach]

CMP has the option to add extra colomns including build version. You right click on the colomn header tab to bring up a list.

 

[shaneturner12]

That's interesting. When I last checked TRS2006, there was no such column. I believe it was added in TS2009's CM2.

Shane

 

[TorenHynes]

There are no faulty driver commands or commodities present. How, then, do I proceed?

 

[fran1]

There are no faulty driver commands or commodities present. How, then, do I proceed?

Any loads/commodities (in fact anything) with a higher build than 2.6 ? They won't show as faulty but create havoc when you run 2006.

 

[TorenHynes]

Ok, sounds like that may be the problem with both the commodities and the driver commands. How do you find the build version on an asset (other than looking in the config file of every single commodity/driver command, which would take a long time)?

 

[shaneturner12]

That is the only way of doing it for TRS2006. You only need to check non-builtin items though.

Shane

 

[dnevans8]

This problem is almost always a result of a recently downloaded commodity or driver.
In CM if you search for category - commodity then sort the list of commodites on installation time you can then disable the most recent then check in game to see if your problem is removed, if it is not then enable the ones you just disabled and disable the next few until your problem is removed. You can then home in on the problem commodity either by checking the config.txt files of the disabled assets or by reducing the number of disabled commodities until you isolate the problem asset without having to go through all of them.
You can then repeat this for category driver.
It might be necessary to disable the commodities and drivers at the same time and go through the checks at the same time.