Validating... Again?

Now will these validation "features" be available in the new modern program that is in the wings?
 
How do I get this extended validation? I started CM with the Installed filter active. After successfully validating my user name with Planet Auran, nothing else is happening.

Taddaemon reports it deleted some cached files and a backup folder, did a PlantAuranLogin and is writing the AssetIndex about every 2 minutes. If that's it, it doesn't even register in Task Manager.
 
I have also noticed this while working on scripts. I will install and test revisions to a script rule and on some occasions about 12000 assets are re-validated regardless of having anything to do with the script asset I installed. It doesn't happen every time it gets installed but every 3rd or 4th time. This greatly slows down the process because of having to wait for the items to validate as there is no true responsiveness to driver or surveyor until there are only about 32 assets left to validate.

steps:

session already exists with rule as a dependency.

1. modify session rule script
2. install in cmp and commit
3. right click session asset in cmp and view in driver to test

every few times i do this apparently the same 12000 or so assets are re-validated. these are not dependencies of the route or the session rule. this causes driver to load in several minutes rather than a few seconds.
 
Thanks for tracking down some of the triggers of this problem p-dehnert and norfolksouthern37.

Is there any hope that this bug in HF4 will be fixed or do we have to wait a year for T2?

(I know, I know it is not a bug it is a feature.)
 
I had this happen last night after some asset updates and then again this morning after I downloaded some assets off of the DLS. Right now I'm still validating over 15,000 assets and won't do anything in Trainz until this finishes.

The validation to me seems to indicate some kind of database integrity issue as I've seen this in the past when opening and closing CM and Trainz in succession multiple times when I've been modifying and testing assets. Perhaps the message is incorrect as to what the application is actually doing and the wording needs to be changed.

John
 
Still can't get this extra validating to kick-in. I've closed and reopened Trainz, rebooted, even re-installed a recent building object I was working on to see if I could trigger the validation routine. Nada.

Feeling kind of left out of all the fun.
 
Mine seems to have settled down again and isn't now doing it, installed a few things and it just validated them pretty much straight away without going into an extended validation, perhaps it got out of sync with something somewhere.
I will keep watching it though.
 
Arrrrgggghhh!!!

Again! WTH. another 12,000 asset validation.

Grrrrr!!!

I did happen to notice that as the tadeamon was closing it announced that it was flushing the database. which really had me worried.

How often is this going to keep happening?

Edit: In recent days I've imported two very long (+100mile) DEM maps and today just prior to this mess I imported about 20 cdps of rolling stock as well as downloading about 12 assets that I knew were probably in need of repair. FWiiW
 
Last edited:
Arrrrgggghhh!!!

Again! WTH. another 12,000 asset validation.

Grrrrr!!!

I did happen to notice that as the tadeamon was closing it announced that it was flushing the database. which really had me worried.

How often is this going to keep happening?

This is probably incorrect wording or maybe not. In database terms, a database is dumped when the application or server is closed.

Most databases today use what is called journaling and transaction files. All of the data stored is written to transaction files and the activity is stored in journals. Think of it as having a list and a box with stuff in it. When the program is closed, the data is moved to the database for final storage. The purpose of this is to prevent catastrophic damage to the information and to allow multiple actions to be completed at the same time. With the logging and transactions separate, it will help prevent data corruption should the database be open when there is a crash, or worse an unexpected system shutdown (crash). When the system comes back up, or the application starts again, the data is then "played back" and imported loaded to the last place you were prior to the crash. You may lose some latest transactions, but not everything is gone. In the old days, databases were open all the time so if you were to crash, you'd lose everything. This also allows for more efficient searching and data handling because the whole database isn't open for read or write. If the whole database has to open, then we'd have to wait forever for each transaction to complete before we could do something else. The way things are now, we can actually, within limits, search and download content at the same time.

So Content Manager's underlying utilities appear to work in this fashion using the SQL-Lite database engine. If you look at your Userdata folder while you are running Content Manager, you'll see .sql, .sql-wal, and .sql-shm files. To us they mean nothing, but to Content Manager, they are the temporary holding the information. Once you close Content Manager, TADDaemon does a bit of cleaning up and this data is flushed to its proper spots in Assets.tdx and these files are deleted.

I hope I explained this right!

John
 
OK, but this is the first time I've seen the flushing message and, as soon as I attempted open trainz again, it immediately started the validation process. I thought there might be a correlation.

The flushing message came after the TADDDaemon shutting down due to inactivity message which also surprised me. Only 5500 to go... <sigh>
 
OK, but this is the first time I've seen the flushing message and, as soon as I attempted open trainz again, it immediately started the validation process. I thought there might be a correlation.

The flushing message came after the TADDDaemon shutting down due to inactivity message which also surprised me. Only 5500 to go... <sigh>

I've seen that validation message too after reopening. But then again there have been a lot of updates. I too had over 15,000 assets to go the other day. I let it run and practiced the piano instead.

John
 
Hi Guys,

This has been happening to me since I got TS2012! It used to be just me or my computer at one time (that's what the fanboi's said at the time!) but at least now it seems to be effecting more and more people. Welcome to me world, friends :p:hehe:.

I seem to get it happening after downloading more than a weeks worth of downloads. Also, on the re-validation, it seems to stop at 33. Is this normal?

Hopefully one day (later this year, ;)) this will be sorted.

Regards.
CaptEngland (ps. doing a re-val again right now).
 
I seem to get it happening after downloading more than a weeks worth of downloads. Also, on the re-validation, it seems to stop at 33. Is this normal?

Stops or ends at 33 here as well, validating, when it happens, is not so painful on an SSD drive.
 
Thanks for confirming that Malc.

On next years new P.C. I am going to make sure that I will add a big SSD drive just for trainz. Hopefully that will sort a lot of time wasting, out.

Regards.
CaptEngland.
 
Time wasting indeed, my entire 4 hour window for working on trainz shot on this housekeeping stuff. Grrrrr!

I wanted to accomplish so much today, instead, nada. Rats!
 
I think I've managed to work out now what causes the higher validation numbers (and the repeated validations in some cases, usually when installing assets). As it validates an asset, it also validates it's dependencies. If an asset has few dependencies, then it usually have a low number of assets to validate. However, if it's a dependency that has other dependencies, it goes on and on until it's checked them all (as well as assets that depend on those dependencies and their dependencies as well in some cases), which for assets that use a popular built-in, that can stretch into the thousands quite easily.

Shane
 
It's not only checking the dependencies, but rebuilding the obsolete/version history. Installing new assets usually gives me only a few asset to validate, but deleting obsolete assets gives quite an amount of assets to validate. My system (Athlon dual core, no SSD) needs about 15 to 30 minutes to validate 1000 assets.

Peter
 
I decided eventually to patch to 61388.
There are stacks of errors - most of them "the tag 'image' in 'o' points to a nonexistant file .jpg " and then sound wav and texture errors. I will have to learn how to fix these errors, from scratch as I have not the faintest - many of the assets are great stuff that I enjoyed like Bjorns Mallet etc. The game itself works ok by me, now and then a stutter is all.
 
Back
Top