Removed trackmarks still visible in find object tool - driver setup rule - solution?

[belgian46]

Hello,

I don't know if the following situation is related to the SP5 update and/or SP5 hotfix.

Here is the situation.

I'm busy with relaying track ( and other objects signals, triggers, etc ) in my Tram-Train route. I'm doing it zone by zone. I removed all tracks in the first zone, so all trackmarks were visibly gone and I saved the specific session.

However, after saving, when I go to the find object tool or to driver setup, the removed trackmarks are still visible and still useable, although they no longer exist in the session that I'm editing.

Does anyone have a possible solution?

Thank you

Kind regards

Kurt:wave:

 

[JCitron]

Hi Kurt,

Run delete missing assets and see if that cleans up the issue. I found this fixes a lot of weird things that occur when we do lots of editing.

 

[G.M.]

hi Kurt
Trackmarks can be:
-in the route
-in the route config (often renamed)
-in sessions
-in the session config
-in driver commands (stored in soup=dbase)


When do drastic editing, first thing to try is delete missing assets, after


The most drastic, but very dangerous and bad documented option is "compact route"
if you try this please do it on a clone only !
it will reset all automated ID's placed in the route,
but sadly you loose all names given to junctions signals etc.
this means all sessions ever made probably will be useless

 

[belgian46]

Hi John, G.M.

Thank you for your replies. Very much appreciated !

I will check it out and report ASAP.

Kind regards

Kurt :wave:

 

[pitkin]

From the wiki;

Soups can save items which can be represented as boolean values, floating point numbers, integers, strings, KUID references or nested SubSoups.

So, trackmark NAMES can be stored in Driver Commands and elsewhere. So if a driver command is executed and the trackmark itself has been deleted, then an error will occur unless the creator has checked for null references.

 

[belgian46]

Hi John, G.M.

I opened the config files of the route and the latest session.

I saw the tracknames in the session config.

Closed both configs - opened the route and the latest session and clicked on delete missing assets. Saved the session, closed it and re-opened it and yes, the removed trackmarks were no longer available in the find object tool and in driver setup.

I went into CM and re-opened the latest saved session config file and the removed trackmarks were still in the config file.

Do I remove them from the config file?

When restarting the placement of new trackmarks in the specific zones, is it better to use an other name strategy?

Kind regards

Kurt :wave:

 

[belgian46]

From the wiki;

Soups can save items which can be represented as boolean values, floating point numbers, integers, strings, KUID references or nested SubSoups.

So, trackmark NAMES can be stored in Driver Commands and elsewhere. So if a driver command is executed and the trackmark itself has been deleted, then an error will occur unless the creator has checked for null references.

Hello pitkin,

Thank you for the extra information - also very much appreciated .

Kind regards

Kurt :wave:

 

[G.M.]

That makes it tricky, Kurt, it is stored in so many places
just use names you want to use when placing new trackmarks
the newest(saved) should always be found

 

[pware]

I went into CM and re-opened the latest saved session config file and the removed trackmarks were still in the config file.

Do I remove them from the config file?

The kuid-table entries in the config.txt of a route is rebuilt from the map data stored in the route everytime the route is loaded into Surveyor or Driver. Deleting items from this list will not remove them unless they are deleted from the route first otherwise they will simply reappear when the route is loaded again. Items that are in the kuid-table but not appearing in the route would most likely be "missing assets" and are best deleted, as John pointed out in post #2 above, is to run the Delete Missing Assets command (but this is not guaranteed).

 

[belgian46]

That makes it tricky, Kurt, it is stored in so many places
just use names you want to use when placing new trackmarks
the newest(saved) should always be found

Hi G.M

Ok - I will continue to use my trackmarks naming convention.

Kind regards

Kurt :wave:

 

[belgian46]

The kuid-table entries in the config.txt of a route is rebuilt from the map data stored in the route everytime the route is loaded into Surveyor or Driver. Deleting items from this list will not remove them unless they are deleted from the route first otherwise they will simply reappear when the route is loaded again. Items that are in the kuid-table but not appearing in the route would most likely be "missing assets" and are best deleted, as John pointed out in post #2 above, is to run the Delete Missing Assets command (but this is not guaranteed).

Hi Pware,

Thank you for the extra info ( very much appreciated ! )

Although, the trackmarks are no longer part of the specific session, I can still find the names within the config file of the session/route.

Within my Tram-Train route I also use tramstop assets and they are also removed ( and will be put back again, only it is a different tramstop asset ). The names, I used for the platforms of the tramstop can still be found in the config file of the session.

Nevertheless, after executing delete missing assets, using the find object tool or within the driver setup rule, the removed trackmarks are no longer available.

Perhaps, I should be clicking on the delete missing assets multiple times in order to synchronise the files involved. I will give it a try and see what is happening.

Kind regards

Kurt:wave:

 

[belgian46]

Hello,

I'm getting the same warnings as yesterday, after clicking on delete missing assets.

The warnings are

; <NULL> : Deleting missing ground textures
; <NULL> : Deleting missing/invalid objects
; <kuid2:342053:25212:1> : Loading asset <kuid2:342053:25212:1>
! <kuid2:342053:25212:1> : MapObjectSpec::LoadDefaultMeshes> missing 'night' tag in <kuid2:342053:25212:1> "DS Apartment Block 05"
; <kuid2:342053:25154:1> : Loading asset <kuid2:342053:25154:1>
! <kuid2:342053:25154:1> : MapObjectSpec::LoadDefaultMeshes> missing 'night' tag in <kuid2:342053:25154:1> "DS Warehouse 01"
; <kuid2:342053:25156:1> : Loading asset <kuid2:342053:25156:1>
! <kuid2:342053:25156:1> : MapObjectSpec::LoadDefaultMeshes> missing 'night' tag in <kuid2:342053:25156:1> "DS Warehouse 02"
; <kuid2:37028:27001:1> : Loading asset <kuid2:37028:27001:1>
! <kuid2:37028:27001:1> : MapObjectSpec::LoadDefaultMeshes> missing 'night' tag in <kuid2:37028:27001:1> "tank amoco"
; <kuid2:342053:25159:1> : Loading asset <kuid2:342053:25159:1>
! <kuid2:342053:25159:1> : MapObjectSpec::LoadDefaultMeshes> missing 'night' tag in <kuid2:342053:25159:1> "DS Office Block No3"
; <NULL> : Deleting missing/invalid splines
; <kuid2:9000:38001:2> : Loading asset <kuid2:9000:38001:2>
! <kuid2:9000:38001:2> : zero-length normal for chunky track
! <kuid2:9000:38001:2> : zero-length normal for chunky track
; <NULL> : Validating object/spline layer IDs
; <NULL> : Rebuilding named object table
; <NULL> : Process complete with 0 errors and 7 warnings

No warnings about trackmark names, platform names.

Refering to G.M. reply #3 - I will not execute the option - compact route - ( to risky ).

Kind regards

Kurt

 

[pware]

I have just downloaded and installed those assets:-

<kuid2:37028:27001:1> tank amoco
<kuid2:9000:38001:2>
<kuid2:342053:25156:1> DS Warehouse 02
<kuid2:342053:25212:1> DS Apartment Block 05
<kuid2:342053:25159:1> DS Office Block No3
<kuid2:342053:25154:1> DS Warehouse 01

<kuid2:9000:38001:2> is listed as an <unknown asset> so I was unable to investigate that one further.

The other 5 installed without any errors but when selected each one and opened the View Errors and Warning command I received the following messages for each of them (but only one shown below - color and bold emphasis is my editing).

; <kuid2:342053:25156:1> : Validating <kuid2:342053:25156:1>
! <kuid2:342053:25156:1> : VE48: This asset uses an obsolete trainz-build number. Trainz-build numbers below 3.5 are no longer supported.
; <NULL> : Performing asset precache
; <kuid2:342053:25156:1> : Loading asset <kuid2:342053:25156:1>
! <kuid2:342053:25156:1> : MapObjectSpec::LoadDefaultMeshes> missing 'night' tag in <kuid2:342053:25156:1> "DS Warehouse 02"

Conclusion: the problem is with those assets, not with your route, CM or Trainz build. The fact that they are warnings only and not errors means that they can be ignored - for now but in a future release of Trainz the warnings could become errors. It will be up to the original creator (if he/she is still active) to fix these problems.

 

[stagecoach]

In my TRS22 those DS assets show as packaged with no faults. DLS upload 22 Jan 2015 version 1.3. The config is

kuid <kuid2:342053:25156:1>
kind "scenery"
region "Test"
type "Trackside"

obsolete-table
{
}
trainz-build 1.3
category-region-0 "IE"
category-era-0 "2000"
category-class "BR"
nightmode "home"
asset-filename "DS Warehouse 02"
username "DS Warehouse 02"
description " "

thumbnails
{
0
{
image "screenshot.jpg"
width "240"
height "180"
}
}
author "DomSarto"
contact-email "southwelldom@eircom.net"
contact-website "n/a"
license "may not be used as part of any payware route or included on any payware CD/DVD for which payment is required."
username-pl "DS magazyn 02"
username-cz "DS Skladiště 02"
description-cz " "
username-es "Almacén DS 02"
username-jp "DS 倉庫 02"
username-de "DS Warehouse 02"
username-fr "Entrepôt DS 02"

kuid-table
{
}

 

[belgian46]

Hello Pware, Keith

Very interesting.

In my TRS19 Platinum edition build 117009 ( Sp5 hotfix ) - all those DS assets show no warnings or errors in CM.

<kuid2:9000:38001:2> Invisible track ( created by weevil - also packaged ).
@pware : if necessary, I can send you the asset ( download via dropbox link )

Kind regards

Kurt :wave:

 

[pware]

In my TRS19 Platinum edition build 117009 ( Sp5 hotfix ) - all those DS assets show no warnings or errors in CM.

My version is Trainz Plus build 117092.

Part of the problem may be that those assets are old - Trainz Build 1.3 and at least one of the tags shown in the config.txt file in the post from stagecoach is now obsolete ("asset-filename"). The "night" tag, which my version reports as missing from the config.txt file, is an environment control to identify the night sky. Not sure why it would be needed in a scenery asset.

The warnings may simply be due to a difference in the asset compliance checking between the different builds, not helped by the ages of the assets. It is also possible that because the assets in TRS22 are "packaged" and therefore came from the DLC and not the DLS then they may have different compliance tests when installed.

<kuid2:9000:38001:2> Invisible track ( created by weevil - also packaged ).
@pware : if necessary, I can send you the asset ( download via dropbox link )

Thanks for the offer but not necessary.

 

[belgian46]

Hello Pware,

I only hope that those older assets will not become a major problem .

Kind regards

Kurt

 

[stagecoach]

I have two installs of TRS22 both at 117092. The main one I use for most work (updated from earlier versions) shows the asset as packaged with no errors. The second install is the EA updated and this had to have the DLS version of the asset downloaded. This shows the errors that pware stated earlier.

 

[chili46]

The most drastic, but very dangerous and bad documented option is "compact route"
if you try this please do it on a clone only !
it will reset all automated ID's placed in the route,
but sadly you loose all names given to junctions signals etc.
this means all sessions ever made probably will be useless

Yeah, I did that once without cloning (only ONCE). It does create a mess! Fortunately I export all my routes/sessions to .CDP files on a regular basis. If I'm doing major edits, I try to remember to make a backup copy first (emphasis on "try to remember"). If things get totally munged, I have can restore from previous edits.

 

[belgian46]

Hello Keith, Chili46

Thank you for the extra information -

Kind regards

Kurt :wave: