Backdating
- Thread starter Kris94
- Start date
hauntedclipp
copper-crowned
For some reason, this doesn't quite work for me. I mean, it does, but only after I uninstall Trainz, reinstall it, and wait a couple of days for my installed content to reappear.
I discovered that completely by accident when I had to uninstall and reinstall 06 and found North Western Railway 3D's 09 content working! But I wouldn't recommend doing that for every model you backdate. :hehe:
I discovered that completely by accident when I had to uninstall and reinstall 06 and found North Western Railway 3D's 09 content working! But I wouldn't recommend doing that for every model you backdate. :hehe:
The quick way. After you backdate it save it as a cdp to the desktop and re-import it into Trainz letting it over write the original. This will update the data base for this one asset.
Or the long way. After back dating re-build the data base which could take 30 min to an hour depending on how many assets you have.
Don't try backdating a route as they are none back datable.
Or the long way. After back dating re-build the data base which could take 30 min to an hour depending on how many assets you have.
Don't try backdating a route as they are none back datable.
Retro00064
New member
It is not always as easy as just changing the value of the "trainz-build" field in the asset's config.txt file. Doing that is a given mandantory procedure, but assets for newer versions of Trainz can have features/configurations that are not supported in older versions, or might be missing features/configurations that older versions require. Config.txt fields are a major part of this, but scripts and what have you can also be involved. Some content creation knowledge is a must when back-dating assets that need more than just a "trainz-build" value change.
Some times, content creators make assets for newer versions that are actually completely compatible with older versions except for the "trainz-build" value. I kinda remember what might have been an old principle to make assets for the lowest version of Trainz that they will work in (with my personal opinion also adding: "without missing out on too many features from a newer version that would benefit the asset's quality"). I think that that is a good principle. However, I have seen several instances where assets were made for a newer version when there was no need to, due to the asset technically being compatible with earlier versions of Trainz. There might be a possibility that Content Manager/Content Creator Plus has something to do with this, since it appears that it automatically sets the "trainz-build" field to the program's Trainz version, unlike TRS2004 and earlier where the creator basically filled most/all of the stuff in manually. Still, the creator using such newerr versions of Trainz could probably set the "trainz-build" value to a lower one manually. It is up to the end user to back-date such assets as needed.
Regards.
Some times, content creators make assets for newer versions that are actually completely compatible with older versions except for the "trainz-build" value. I kinda remember what might have been an old principle to make assets for the lowest version of Trainz that they will work in (with my personal opinion also adding: "without missing out on too many features from a newer version that would benefit the asset's quality"). I think that that is a good principle. However, I have seen several instances where assets were made for a newer version when there was no need to, due to the asset technically being compatible with earlier versions of Trainz. There might be a possibility that Content Manager/Content Creator Plus has something to do with this, since it appears that it automatically sets the "trainz-build" field to the program's Trainz version, unlike TRS2004 and earlier where the creator basically filled most/all of the stuff in manually. Still, the creator using such newerr versions of Trainz could probably set the "trainz-build" value to a lower one manually. It is up to the end user to back-date such assets as needed.
Regards.
NSWGR_46Class
Just call my Captain Rude
Intresting point of view that is until you try to unload the item to the DLS - its now refusing to take items that may be fine to run under 2004 standards but would be rejected due to the build number alone.
Remember there will come a time when 2004 and UTC content will be removed from the DLS its just that the time line has no been set yet.
Yes 2004 and UTC are dead products
http://online.ts2009.com/mediaWiki/index.php5/Trainz_Life-Cycle_Policy
cascaderailroad
New member
Pre SP1 may be dead (as they are unavailable), but 04 and 06 assests run in compatability mode, are still the backbone of 09/10/12.
There are only 1991 TS10 assets
And 9840 TS09 assets
There are well over 14115 assets below 09/10/12 that you use everyday, and you rely on them. Without them, your version would be dead !
There are only 1991 TS10 assets
And 9840 TS09 assets
There are well over 14115 assets below 09/10/12 that you use everyday, and you rely on them. Without them, your version would be dead !
Last edited:
Retro00064
New member
And just having assets on the DLS under a later build number is enough to make it a bit harder for users of older versions to get them. It is/was actually possible to grab assets off of the DLS for a later version of Trainz than what you own by using the direct FTP address of the asset. The original SP3/UTC Downlaod Station (located at http://www.auran.com/trainz/downloadst.htm, which got removed (redirected to the TRS2004 "Black Pages" DLS) soon after I posted about its existence in one thread here on the public forums (N3V must have seen it)
:'() made it easy to copy and paste the FTP address of such assets (instead of you having to figure it out manually), since the old Download Station software there did not know to put a "Serial Number Required" message on assets for Trainz versions TRS2004 and later that you did not have a suitable registered version to run them. I understand that being true for those legacy assets that went through the DLS Clean-up, but what about those that did not? Will N3V make the remaining legacy assets go through an other sort of "clean-up" to increase the version of Trainz that they are set up for, to clear them of the warning about a low "trainz-build" number that TS12 gives them? That might be the way to go, to preserve them for TS12 and future versions of Trainz.
Regards.
Retro00064
New member
And TRS2006 and earlier assets presumably (?) will run in native mode if they are error-free.
Regards.
NSWGR_46Class
Just call my Captain Rude
There is no compablity mode in TS12 its gone.....
cascaderailroad
New member
Then you have lost over 14115 assets 
It will take quite awhile to re-manufacture all those lost assets
It will take quite awhile to re-manufacture all those lost assets
Retro00064
New member
Then you have lost over 14115 assets
It will take quite awhile to re-manufacture all those lost assets
Did you see me post? It appears that legacy assets will work in native mode as long as they do not have errors (though they might even still work if they only have warning). I do not think that I have read otherwise. Besides, if no legacy asset works in the newer versions, then it would be likely that there would be piles of posts around here by users who did not like it.
Regards.
Last edited:
NSWGR_46Class
Just call my Captain Rude
Warnings yes - errors noDid you see me post? It appears that legacy assets will work in native mode as long as they do not have errors (though they might even still work if they only have warning). I do not think that I have read otherwise. Besides, if no legacy asset works in the newer versions, then it would be likely that there would be piles of posts around here by users who did not like it.
Regards.