This problem is annoying for playing Trainz. Sometimes I can just install an asset which is totally fine. Sometimes, the creator can release an update for the asset, like adding a new locomotive variant and stuff. If I want to update it, I have to get the cdp again, and reinstall it. But when I install it, ones that are already installed gets Open for Edit status. It's so annoying!!! I literally have to go to the Open for Editing section and revert unsubmitted edits almost every single time I install a package. Coal and Water even is included in there!!!
(Frustration) Why does something have to stay open for edit when that asset gets installed???
- Thread starter screecher
- Start date
The "Open for Edit" after an install normally means that the same asset (with the same kuid code, including update number if any) is already installed in your Content Manager. It allows you to "back out of the install" by selecting the asset, opening its drop down menu and selecting the option "Revert to Original". At least that is my experience every time I have seen the "Open for edit" label after an install.
Your statement...
Your statement...
... indicates to me that that is exactly what has happened. You had installed the update and then reinstalled it again "I have to get the cdp again". Why the "double install" I do not know as I have never had that experience. Did you install the update unknowingly via a DLC update?
This is a safety net so that assets aren't overwritten by accident. Sometimes, assets can have the same kuid number. This is common when assets are exported to cdp files and then removed from Trainz. At some point, there's a possibility that the same kuid can end up being used again at some point because Trainz no longer has any reference to the one that was deleted. What you don't want to do, for example, is to import a building you have created that has the same kuid as a route you've been working on for ages and end up losing the route! To get around that, Content Manager is configured so that if the SAME kuid exists, the asset is left open so you can check first and use your thinking cap and brain to think before blindly overwriting your already installed assets.
What I do when installing cdp files is open up the view in Content Manager with Open for Edit showing instead of Installed Content. I then drag in my cdp files and once everything is installed, I then revert all the open assets to original unless the content creator says specifically that there's an update for something. I got into this habit years ago and it has worked perfectly.
@pware
Sometimes there are asset dependency packages for various locomotives, for instance that use the same components or are included in various downloads. A good example is some of the diesel locomotives where the same components such as sand, diesel fuel, cab interior, and bogies are commonly used across multiple models. Some authors will create a dependency pack while others will put all the assets in a single pack. While that's convenient in some ways, it can cause the open for edit issue if there are multiple models of the same locomotive since each pack that's installed contains the same dependencies.
What I do when installing cdp files is open up the view in Content Manager with Open for Edit showing instead of Installed Content. I then drag in my cdp files and once everything is installed, I then revert all the open assets to original unless the content creator says specifically that there's an update for something. I got into this habit years ago and it has worked perfectly.
@pware
Sometimes there are asset dependency packages for various locomotives, for instance that use the same components or are included in various downloads. A good example is some of the diesel locomotives where the same components such as sand, diesel fuel, cab interior, and bogies are commonly used across multiple models. Some authors will create a dependency pack while others will put all the assets in a single pack. While that's convenient in some ways, it can cause the open for edit issue if there are multiple models of the same locomotive since each pack that's installed contains the same dependencies.
I don't follow that. When I download a loco, for example, that has dependencies that are already installed then those dependencies are skipped during the download and install process for the new loco. If one of the dependencies has a different (new) kuid then it will be downloaded and installed with the loco and the new dependency is submitted (not left "Open for edit"). During an install I usually fully open the download window to display the progress data as the assets are downloaded and installed.
The only exceptions to this have happened when an error was detected during the install. One such mysterious case I posted about last December in these forums at new-cm-modified-and-open-for-edit-status-behaviour where a newly installed asset from the DLS is labelled as "Modified".
That at least is my experience.
Last edited:
Correct with the faulty meshes. That was an issue with FBX files and I've had that as well.
Maybe this will 'splain it better.
The Scenario is the following:
You've purchased a bunch of Conrail B40-8s from Jointed Rail.
You install the first cdp that has the weathered version.
This puts in horns, engine sounds, and animated fans.
The fans, horns, and engine sound already exist because they are built-in or come from previously installed DLC. The fans and engine sounds are now open for edit. You revert any open assets to original...
You repeat this with another cdp of the un-weathered Conrail B40-8s.
This cdp contains the same meshes as the previous one you just installed as well as the same horns, fans, and engine-sounds.
The B40-8 mesh is now open for edit along with the horns, fans and engine sounds.
This will repeat for every install of similar assets because they share the same mesh, horns, engine sounds, and animated fans.
What I do is change the view in Content Manager to Open for Edit assets and install my content from cdp files. Once everything is installed and the birds have roosted properly, I'll then revert the opened assets.
I hope this makes sense now.
I installed it again because I want to get the new engine
They can possibly check to see if it's the same asset. If it's detected to be the same, it should stay in the normal status. This is my idea
The problem there is that while an asset may have the same KUID it may not be exactly the same asset. And then how should the new imported version be labelled and treated?
As an example: I am currently working on a route and session using my working copy of Trainz Plus. I regularly save the route and session as .cdp files and I periodically import those .cdps into my beta version of Trainz Plus (on several different computers) and my copy of TRS22PE. In each case the imports appear as "Open for Edit" because the previous versions of those assets, with the original KUIDs, are already installed. How then is CM supposed to tell the difference between the original and new versions? In many cases the changes I have made are very minor, insignificant, in a very large route. Will CM have to spend a lot of time and resources doing a byte by byte comparison between the two assets?
I get that, but say: If I install an asset, say a whistle or horn. Totally unchanged after I installed it. I use the same cdp it was in. The properties of the whistle/horn is the same as the one as the one I installed before. If it detects its the same properties, it should stay in its current status. The only time it can be open for edited, is when that whistle/horn is a locomotive in a different cdp, but have the same exact kuid.
That isn't the way the database works. It stores assets based on the primary key of the KUID. It doesn't know anything about what is inside an asset. Databases work on primary keys and secondary keys, that is how they maintain the integrity of the database. What you are suggesting is well beyond the capabilities of any database system that I am aware of today. It is also counter to good database design principles.
Here's something on database basic. Content Manager and Trainz uses a Relational Database Mangement System or RDBMS
%201.png)
www.lido.app
The examples refer to company-related things such as HR employee numbers, etc., but substitute this with Trainz data-types and you'll see it works the same.
Database Basics: Concepts & Examples for Beginners - Lido.app
Get started with relational databases by understanding organized data storage and how it effects efficiency.
www.lido.app
The examples refer to company-related things such as HR employee numbers, etc., but substitute this with Trainz data-types and you'll see it works the same.
stagecoach
75377
All downloads and imports are opened for edit during installation. Once installed CM will commit them. If CM detects an identical kuid installed it leaves it open. CM only checks kuid numbers. If CM has to check the contents matched for every asset your DBR could take a week to sort out.
Can you be more specific? Examples?
I just tried that with some randomly selected assets (Open --> Edit Config File Text) and they all opened the config.txt file in a my text editor. The assets remain "Open for edit" until they are submitted (if you have changed the text file) or reverted (if it has not been changed).
View errors and warnings. Some assets will remain open for edit, if the .fbx files are still in the folder. The fix is to delete the .fbx files and submit the asset.
Okay just picture this. I want to open the config txt of an asset. I right click it, and click edit config text file. In some cases, all it does is just open it for edit, which literally (in this case) acts like the same function for the open for editing button. It forces me to open the config txt manually by "Open with Explorer." Is there a reason as to why this happens? You probably are lucky to be able to open the text without it just opening for edit.
Ok. But what are fbx files?
From Dr Google:-
They are not needed in Trainz assets but sometimes an asset creator forgets to remove them from the asset before it is uploaded to the DLS.
There are a few threads in these forums on this matter.
https://forums.auran.com/threads/new-cm-modified-and-open-for-edit-status-behaviour.176243/
https://forums.auran.com/threads/warning-message-when-importing-assets.177793/
What if there are no FBX files inside that loco?
Apart from the rare FBX issue I have never experienced a new install with a different kuid to those already installed, not even those with KUID2: codes with the update number trailing at the end, to show the "Open for Edit" status label after installing the update.
I would have to experience it myself to be able to come up with a theory.
Just a thought. Does this occur when updating assets that are labelled as "Modified"?
I would have to experience it myself to be able to come up with a theory.
Just a thought. Does this occur when updating assets that are labelled as "Modified"?