New CM "Modified" and "Open for Edit" status behaviour

[pware]

In recent days I have noticed a new Content Manager "behaviour" when downloading some assets from the DLS - not all downloads just those that have errors reported during the install procedure.

The normal download progress window will open up to give an error report (with red "x" icons) during the downloads when the installation compliance test detects an error in a downloaded asset. When all the downloads and installs have been completed, the downloaded but possibly faulty assets will have the status label "Open for Edit" despite the fact that no previous versions of the assets exist in CM. The usual label "Installed from DLS, Faulty" is not shown.

If I commit the assets the "Open for Edit" changes to "Modified" but the asset <kuid> values are unchanged from the originals therefore I have not modified them myself. Selecting these now installed and "Modified" assets and viewing their errors and warnings gives a blank report window.

Two examples from just a few minutes ago:-
<kuid2:132952:101265:14> SAM P - TRKit Track repair kit
<kuid2:132952:101201:13> PCS - Wooden sleepers stack

During the last 3 days I have accumulated 15 "modified" items from DLS downloads.

Is anyone else noticing this? Does anyone have an explanation?

Puzzled

 

[JCitron]

I've seen that in previous versions of TRS22 and Plus. The reason why the assets remain open for edit is due to fbx files in with the asset. Deleting the fbx files then allowed me to submit the asset. The status then of course is modified.

 

[pware]

Deleting the fbx files then allowed me to submit the asset. The status then of course is modified.

Thanks for that. In my cases I didn't delete anything so the "Submit" process must have deleted them automatically (I am assuming).

The next time it happens I will take a deeper look at the asset before I submit.

 

[JCitron]

That's interesting. Check faulty assets and see what comes up. I'm assuming that the open-for-edit ones disappeared and were marked as faulty and were submitted.

 

[pware]

I just deleted one of today's installed "Modified" assets and repeated the download and install operation. This is the error report during the download and install procedure

; <kuid2:132952:101201:13> : Searching asset 'PCS - Wooden sleepers stack'
; <kuid:-25:1150> : Skipping fully installed asset 'Container'
; <kuid2:132952:101201:13> : Downloading <kuid2:132952:101201:13>
; <kuid2:132952:101201:13> : Installing <kuid2:132952:101201:13>…
; <NULL> : ParseAssetDownload
; <kuid2:132952:101201:13> : TADInstallAssetPackage> <kuid2:132952:101201:13> "PCS - Wooden sleepers stack"
+ <kuid2:132952:101201:13> : <kuid2:132952:101201:13> opened for edit
; <kuid2:132952:101201:13> : Wrote <kuid2:132952:101201:13> to disk
- <kuid2:132952:101201:13> : Unexpected files encountered while creating database entry for <kuid2:132952:101201:13>. Trainz Asset Database may need repair.
- <kuid2:132952:101201:13> : Failed to submit changes to asset <kuid2:132952:101201:13> due to database access error
; <kuid2:132952:101201:13> : Commit failed for <kuid2:132952:101201:13>
; <NULL> : Installed 0 asset(s) from CDP
+ <NULL> : Complete

The emphasis above is mine.

On opening the asset in Explorer while its status was "Open for Edit" there is indeed a file of type .fbx present.

From Dr Google:-

An FBX file is a 3D model saved in the Autodesk Filmbox format. It contains a model that can be used and shared across a variety of digital modeling and content creation programs. FBX files are often used in game development and animation.

As a test I submitted the asset without deleting the .fbx file. It was labelled "Modified" despite no changes being made. On opening it again in Explorer the .fbx file was still present (so submit did not delete the file or "fix" the problem as I had originally assumed). CM did not flag the asset as faulty for having it present.

After searching the config.txt file to make sure that it was not referenced there I deleted the .fbx file and submitted. The submit was successful and it was labelled "Modified" as expected since I deleted one of its files. The <kuid> was unchanged.

 

[Forester1]

Rather than commit, can you "Revert to Original"? That has always worked for me, and they end up as "Installed from DLS".

 

[pware]

Check faulty assets and see what comes up.

The "View errors and warnings" report was blank on the unedited asset but after deleting the .fbx file it reported:-

; <kuid2:132952:101201:13> : Validating <kuid2:132952:101201:13>
; <NULL> : Performing asset precache
; <kuid2:132952:101201:13> : Loading asset <kuid2:132952:101201:13>
! <kuid2:132952:101201:13> : ProductSpec> missing 'icon-texture' tag for product '<kuid2:132952:101201:13> "PCS - Wooden sleepers stack"'

The "Revert to Original" did not revert it back so I will delete, download the original again and submit without any changes.

 

[pware]

Rather than commit, can you "Revert to Original"? That has always worked for me, and they end up as "Installed from DLS".

Trying than now.

Nope: Using "Revert to Original" deleted the downloaded and "Open for Edit" asset and it is now labelled as "Available for download"

 

[Forester1]

Odd. Is that new with 22? I have never seen that in T:ANE or TRS19

 

[pware]

Odd. Is that new with 22? I have never seen that in T:ANE or TRS19

I am running on Trainz Plus (the Train Railroad Simulator 2022 forum is the de-facto Trainz Plus forum as well). I only just noticed it happening these past few days.

 

[pware]

I have submitted a bug report

 

[frogpipe]

(Based on my TRS19 experience) These days trainz ingests an FBX file and spits out a TRAINZMESH file. After that the FBX is extraneous.

 

[p-dehnert]

I just did a quick test in Trainz+, and it downloaded without any problems. These were the messages in the download panel:

; <kuid2:132952:101201:13> : Searching asset 'PCS - Wooden sleepers stack'
; <kuid:-25:1150> : Skipping fully installed asset 'Container'
; <kuid2:132952:101201:13> : Downloading <kuid2:132952:101201:13>
; <kuid2:132952:101201:13> : Installing <kuid2:132952:101201:13>…
; <NULL> : ParseAssetDownload
; <kuid2:132952:101201:13> : TADInstallAssetPackage> <kuid2:132952:101201:13> "PCS - Wooden sleepers stack"
+ <kuid2:132952:101201:13> : <kuid2:132952:101201:13> opened for edit
; <kuid2:132952:101201:13> : Wrote <kuid2:132952:101201:13> to disk
; <NULL> : sleepers.fbx
! <kuid2:132952:101201:13> : Warn, T7852: FBX-DOM (TOK_KEY, offset 0x42a3) shading mode not recognized: Phong
+ <kuid2:132952:101201:13> : <kuid2:132952:101201:13> submitted
+ <kuid2:132952:101201:13> : Installed asset <kuid2:132952:101201:13>
; <NULL> : Installed 1 asset(s) from CDP
; <kuid:-3:10042> : Searching asset 'Container'
; <kuid:-25:1150> : Skipping fully installed asset 'Container'
+ <NULL> : Complete

I quick test in TRS22 wasn't possible, it's packaged in "Datsun Junction Model Railroad" and "Coal Country".

Peter

 

[pware]

Thanks for that p-dehnert.

Just out of curiosity (or because I like living dangerously ) I repeated my experiment with downloading and installing <kuid2:132952:101201:13> PCS - Wooden sleepers stack in TRS22 (Standard) instead of Trainz Plus. It downloaded and installed with no errors and is now happily classified as "Installed from DLS".

I quick test in TRS22 wasn't possible, it's packaged in "Datsun Junction Model Railroad".

I don't have that DLC package (or any DLC assets) in TRS22.

Go figure

 

[pware]

N3V QA have responded stating that they have been unable to fully reproduce the issue but do get error messages - for example about shading on the PCS - Sleeper Stack not being recognised. They also report that after installing the asset is labelled as "Modified", as I reported.

They asked if the problem still occurs after doing a DBR. I was able to test this by performing a DBR and then downloading the assets again. They installed without errors and were labelled as "Installed from DLS".

 

[pware]

Further news from N3V QA.

I suspect something causes some form of breakage in the DB, which leads to the assets installing incorrectly, rather than the assets themselves having a fault. I suspect it isn't the assets with .fbx file in them itself the issue, but rather the state the DB was in when they were being installed.

Some of the issues could have been caused by the state of the DB when the SP update to build 123794 was installed.

 

[ianwoodmore]

Paul,

Can you clarify whether you can see the asset in Preview Viewer.
I'm finding that some of Samplaire's assets that are KIND 'product' files are turning up blank with most of the parameters showing 0 (zero). Some of MSGSapper's as well.

None that I have include FBX files in them.
But they did have *.texture files as they are 'packaged' assets.

I thought it might be the product-category asset kuid -3 10042 as I can't find it amongst Auran's assets.
And there doesn't appear to be anything equivalent in kuid -25.

Ian

 

[p-dehnert]

Product-category <kuid:-3:10042> Container has been obsoleted by <kuid:-25:1130>, which has been obsoleted by <kuid:-25:1150>.

TRS19 and later have a problem with "List Asset Versions", they seem to ignore the obsolete-table. Requesting the versions of <kuid:-3:10042> shows all 3 versions, for <kuid:-25:1150> only this kuid is shown.

Peter

 

[pware]

<kuid:-3:10042> is listed an an <unknown asset> in my Trainz Plus CM, so it has never been installed.

When I right click on it and select List Asset Versions I get the following.

<kuid:-3:10042>
<kuid:-25:1130> Container Available for download, obsolete
<kuid:-25:1150> Container Built-in

Going backwards by listing the asset versions for <kuid:-25:1150> only shows <kuid:-25:1130> because <kuid:-3:10042> is an <unknown asset>. That is not a problem for me.

 

[ianwoodmore]

No wonder I couldn't find it in category 'commodity'.
category 'product-category' assets are in TYPE 'Misc' for which there is no default CM filter.

Common practice among many of us is to delete assets with status 'obsolete' to save space on HDD and SSD drives, and then forget about them.

Incidentally, the thumbnail.jpg associated with these builtin product-category assets is a white uniform colour 240x180 pixel image which is as useful as tits on a bull.. There is, of course, no tag 'product-texture' hence no preview image for the viewer.