TRS2006 built-in asset corrupted by its new version

legia

New member
I have a problem with an asset built into TRS2006, "Point Motor WH63" <kuid:33572:24000>, which has been corrupted by its new version available at DLS, <kuid2:33572:24000:1>.

This new version, <kuid2:33572:24000:1>, does not show up in surveyor's asset window and cannot be used as a junction (no red-green direction arrows are visible). However, in CMP it does not display any errors. I believe CMP automatically replaced the built-in version with the new one in all dependant assets, including many of my routes, rendering them non-functional.

Even after I manually replaced reference to <kuid2:33572:24000:1> with <kuid:33572:24000> in config files, CMP still attempts to use the new version. When I deleted the new version, CMP shows it as a missing dependency, available on DLS.

I opened for edit the built-in version, <kuid:33572:24000>, then selected option "Revert to original", but this didn't help. It looks to me that some irreversible operation took place while I was downloading the new version. Since then, no matter what I do CMP refuses to use the built-in version. Is there any way to remedy this situation? I used original version of "Point Motor WH63" as the default junction in many routes and it would take much time to restore these routes to their original functionality.

I believe problems like this were discussed on this forum in many places, but unfortunately I was not able to find a hint which could help me to solve my problem.

I would much appreciate any assistance I could get.
 
The updated ones are designed for Trainz Classics or above usually (if they have been repaired as part of the DLS Cleanup)

You may have to reinstall.

Shane

P.S. You do not seem to have any serial numbers registered on that account.
 
Just Thinking Out Loud

Just thinking out loud here, but if I were to find myself in this position one sneaky thing I might try is to open the :1 asset and eviscerate it by removing the "Obsoletes" section, then commit the nobbled asset. No guarantee, I haven't tried this.
 
The updated ones are designed for Trainz
P.S. You do not seem to have any serial numbers registered on that account.

In fact I have 2 accounts: one for TRS2006 and another for TC1 and TS2009. At the time of creating these accounts I was not aware they will have impact on the way I use DLS or this forum. I send a formal request to AURAN to merge the accounts or delete and start fresh, but nothing has been done. The price paid for these games plus FCT seems to be nothing compared with the time spent on fixing problems, looking for missing dendencies, etc. But all this is part of life experience to enrich us.
 
Fair enough - just be prepared for people asking that question in future, or asking which Trainz version you are referring to.

Shane
 
In fact I have 2 accounts: one for TRS2006 and another for TC1 and TS2009. At the time of creating these accounts I was not aware they will have impact on the way I use DLS or this forum. I send a formal request to AURAN to merge the accounts or delete and start fresh, but nothing has been done. The price paid for these games plus FCT seems to be nothing compared with the time spent on fixing problems, looking for missing dendencies, etc. But all this is part of life experience to enrich us.

Re your last sentence "enrich" could easily be replaced with enrage or frustrate in relation to trainz.
 
Built-in asset obsoleted by new version

Just thinking out loud here, but if I were to find myself in this position one sneaky thing I might try is to open the :1 asset and eviscerate it by removing the "Obsoletes" section, then commit the nobbled asset. No guarantee, I haven't tried this.

I'm not sure if I understand you. Do you mean to open config file for <kuid2:33572:24000:1> and remove a section labelled "obsolete"? There is no such label there.

But I think you are leading me in right direction - there must be a piece of information stored somewhere on my local folder telling TRS to use <kuid2:33572:24000:1> instead of built-in <kuid:33572:24000>. The only question is where this file is located and how to change it back?

I believe this isn't a minor problem as it affects not only routes which you made, but changes behaviour of the original simulator (by deprecating built-in asset). It also crashes all driver sessions which were saved before replacement took place. The fact that the new asset is not designed for your version of Trainz is not so obvious; some new assets deployed after 2009 works well in TRS2006. CMP does not have mechanism to guard against the potential risk that a new version will render built-in version useless. If this can happen it will happen, it is only matter of time when.

I will keep trying and I hope my case is interested enough for others to come up with an advice. I do not expect perfect solution to this problem, but I much appreciate any feedback.
 
Have you tried changing the build number in the config file to 2.6 or lower? It would cause a problem if you were to share your route with other TRS06 users (they would have to do the same thing), but it should get you running again.

Paul
 
Obsolete-table

I'm not sure if I understand you. Do you mean to open config file for <kuid2:33572:24000:1> and remove a section labelled "obsolete"? There is no such label there.

But I think you are leading me in right direction - there must be a piece of information stored somewhere on my local folder telling TRS to use <kuid2:33572:24000:1> instead of built-in <kuid:33572:24000>. The only question is where this file is located and how to change it back?

I believe this isn't a minor problem as it affects not only routes which you made, but changes behaviour of the original simulator (by deprecating built-in asset). It also crashes all driver sessions which were saved before replacement took place. The fact that the new asset is not designed for your version of Trainz is not so obvious; some new assets deployed after 2009 works well in TRS2006. CMP does not have mechanism to guard against the potential risk that a new version will render built-in version useless. If this can happen it will happen, it is only matter of time when.

I will keep trying and I hope my case is interested enough for others to come up with an advice. I do not expect perfect solution to this problem, but I much appreciate any feedback.

Sorry, I wasn't at my system so did not have the correct phraseology. The one asset I've personally obsoleted was an enginespec. This was done by creating the updated version kuid2:520526:1241:1 and adding the following to it (the *new* KUID):

obsolete-table
{
0 <kuid:520526:1240>
}

(end of added material). The observed effect was to cause all instances of locomotives having this enginespec to use the updated one even though their KUIDs still contained the old one and were not physically changed. I thought your situation might be that the downloaded version contains an obsolete-table causing all instances to use the new (updated and non-working) version, and that you might be able to fix it by removing the "obsolete-table" entry in the new (for your purposes, bad) version. This should (?) cause your system to use the old version in-game again since the actual records calling for the old version have not changed. That, anyway, was the theory. If your new (bad) vesion doesn't have an "obsolete-table" then the theory is wrong.
 
Changing trainz-build value

Have you tried changing the build number in the config file to 2.6 or lower?
Paul

Config of built-in asset , <kuid:33572:24000>, has line:
trainz-build 1.3

Config of new version, <kuid2:33572:24000:1> has:
trainz-build 2.7

Which one should I change?
 
I've just opened my 2006 and run a saved session from 12 months ago, the only rolling stock left on the route are coal hoppers. I have 3 and 4 loco sets running to a schedule with no wagons.
I'm begining to think updated versions get transfered to all versions of trainz regardless.
 
Have you tried changing the build number in the config file to 2.6 or lower?
Paul

I lowered value for trainz-build from 2.7 to 1.3 (as in the built-in asset), but this have no effect.

With both versions installed and enabled, "Point Motor WH63" is listed in Surveyor, "Tracks-add object", but there is no corresponding picture in the track viewer and I can't place this object on a track junction.

When I delete the new version, "Point Motor WH63" is removed from the list of the tracks objects that can be added.

There is no table in the config file to tell CMP to make built-in version obsolete, so how come CMP attempts to use the new version and disregards the built-in one?

This question I should perhaps direct to Auran help desk, only I am not sure if there is anyone to listen.

Anyway, it is good to know that trainz community is caring and ready to help, even old-fashioned folks like me, who still uses TRS2006.
 
Anyway, it is good to know that trainz community is caring and ready to help, even old-fashioned folks like me, who still uses TRS2006.

As always, dear Legia. Auran was before and N3VRF41l is lucky now. They keep having the most loyal customers in the world of leisure software. Maybe their problem lies on how to keep them. Some facts are not helping.

Take care, (BTW your city's football team played here in Vigo once in the past, Celta de Vigo won, I think ;) )

The loyal Sixer side of Alberte :wave:
 
If you would like to PM me your e mail address I have a wh63 asset which works ok for 2006.
Can you send me one too please as i am having the exact same problem, although i am having more problems as a lot more items that were in my lovely TRS2006 are now, like legia, unusable and unsee-able in game now:'( and the list as follows:

GWR steam driver
GWR steam fireman
hump_backed_bridge
Point Motor WH63
LMS_gantry
LMS Combined Gantry
LMS Dual 3 Combined Bracket (basically nearly all LMS signals, both semaphore and shunting)
Mk1_second
GWR_Newbury_ftbridge
GWR Large prairie 51xx
hedgerow_spline
Pajero
waterfall_sample
SR 13ton 5 plank open wagon
GWR pannier Interior
School_1942
Brick_Arch_Bridge
Brick_Arch_Bridge 1T

Thats all i can find at the moment, the list is long i know but if anyone can help get my beloved TRS2006 working like it should do then i would really be grateful:D

I really want my '06 back, it's the best.
 
Last edited:
I really want my '06 back, it's the best.

Hi guy,

Being this your first post with this account, you prove to be a trainzer showing good taste... ;) :D if not the best, -sometimes the best is not the most suitable-, the most sensible of the bunch, the cleverest kid at the block.

The agreeing side of Alberte :wave:
 
Hi guy,

Being this your first post with this account, you prove to be a trainzer showing good taste... ;) :D if not the best, -sometimes the best is not the most suitable-, the most sensible of the bunch, the cleverest kid at the block.

The agreeing side of Alberte :wave:
Thanks, nice to be accepted on my first post.

Names Stephen by the way.
 
Back
Top