how I still have the Adlers on my route. I disabled them. I deleted them from the config file of the route. They do not show up on the dependencies list. I made sure I did the delete missing items. They are still there and all attempts to find the source on the route itself to delete have proved fatal. I strongly believe I should have the right to delete them from my content if I don't want them.
Please Explain
- Thread starter Mr_D
- Start date
Even if you disable something, if it is already on the a route, it will still show up. Those birds are very annoying. The easiest way that I have found to get rid of them on a route is find where they are, go to a straight overhead view, switch to wireframe mode. Look for a point in their flight where they change direction and doubleback, that is where you want to try to delete them.
stagecoach
75377
Have you rebuilt the data base? they may still be on it.
I have run the quick database repair and now running the extensive repair. What I don't get is how do they get loaded when I deleted them from the kuid table in the config file. What is the source that the program is loading them from? I have tried the overhead shot and deleted everything in a square block radius but the birds are still there.
The config kuid list is just a 'quick reference', the program is calling the asset from the .gnd and or .obs file which are to all intents and purposes un-editable.
Disabling assets won't stop Trainz from using them if a route wants them...
Andy
In my opinion the Adler qualifies as malware. It didn't help me that as it starts with an "A" and is at the top of the list (intentional maybe?) I would have them dotted all over my route, as a result of accidentally "adding" instead of "moving" an object.
But they went away for good when I moved my route into TC3.
Mick Berg.
In my dealings with 2004 and TrainzObjectz, content details for layouts is store in the Config file and also the Map file (forget its name). Removing the items from the Config file (the actual kuid number) will not remove them from the Map file and this is where the problem is. When the Map file is opened, the content is still there and (from memory) is re-written into the Config file. I imagine from this thread this has not changed in all/any versions of TRS.
So the only way to remove them is to do it manually, again to my knowledge.
Hope this helps.
Craig
So the only way to remove them is to do it manually, again to my knowledge.
Hope this helps.
Craig