No rolling stock list in Surveyor??

rrfoose

Trainzer/Aviator
Hi all! The last couple of days, when I go into Surveyor, if I want to place rolling stock, and click on the wheel tab, it comes up and the list is blank. Both the individual locos/cars list and the consists list have no text, so I can't find/select/place a piece of rolling stock. Other tabs, such as track & buildings, show normally and have all items listed. Anyone know why this might be happening? More importantly, is there a fix for it?? Thanks for the help!
Chase
 
I saw this soon after patching to HF3. It is possible that merely closing and relaunching Trainz is enough to populate the list. However, just to be safe I performed a DB rebuild first. On relaunch, the list was there.

Might point to an issue with HF3.
John
 
I recommend closing Trainz and letting the database validate after the HF3 install. You can see this happening by opening up the log. To access the log click on the Launcher and on the Developer menu item then click on Show log.

You'll see stuff scrolling up quickly as the database data is being validated. Eventually the assets will appear in Surveyor.
 
I tried both solutions - it seems as though the database had already validated. However, rebuilding the database did fix the issue. Thanks for the help guys!
 
Is the forced rebuild a 1-time thing or should it be done periodically? Of course it should not be required at all but, if needed, done at load time.
 
Is the forced rebuild a 1-time thing or should it be done periodically? Of course it should not be required at all but, if needed, done at load time.

I think it occurs periodically and I've noticed it appears to be related to the filters and indexing in Content Manager, and probably T:ANE its self. This makes sense if we've installed new content or made changes to any content since the index has to be rebuilt so the queries include that data. The same validation and indexing seems to take place when switching from online to offline mode for those of us who can work offline. I think the code might need some optimization because the larger amount of content, and some of us have a lot of content (ahem), can cause a substantial re-indexing process to occur when assets are added or removed.

A periodic rebuild probably isn't a bad thing since this appears to remove any empty tables in the index and speeds up the queries and performance overall once the validation and index-tables are rebuilt.

John
 
Back
Top