CC breaks more than it fixes

[Approach_Medium]

Everyone knows that a lot of older content comes into (from DLS) TS2010 (and TS2009) with warnings and errors.
For example, a lot of old content uses a different mesh type. You get a warning (not an error) about "progressive meshes". When possible, I will convert the .pm to .im using PevSoft, but when there is no .pm file to convert, that is not an option.
The content will function and look fine in TS2010 so it's not an issue.

However, if there are errors, such as "tag not permitted...", these must be removed for the asset to work.
I like to use Content Creator to do this, rather than edit the config.txt file.
At the same time, I usually change the bogies to ones that look much more authentic.

Often, after making changes in CC and then re-committing, there are new errors. The progressive meshes warning is now an error. Other errors may pop up as well.

So, I have reverted to editing the config.txt file instead of using CC. This prevents the new errors from popping up, and allows me to use the content.
It's not as clean as using CC, but until Auran fixes this issue with CC, is there any choice?

Can anyone give me some idea of why this is happening, and whether there actually is a way to use CC without creating new errors?

Thanks

FW

 

[tomurban]

Everyone knows that a lot of older content comes into (from DLS) TS2010 (and TS2009) with warnings and errors.
For example, a lot of old content uses a different mesh type. You get a warning (not an error) about "progressive meshes". When possible, I will convert the .pm to .im using PevSoft, but when there is no .pm file to convert, that is not an option.
The content will function and look fine in TS2010 so it's not an issue.

However, if there are errors, such as "tag not permitted...", these must be removed for the asset to work.
I like to use Content Creator to do this, rather than edit the config.txt file.
At the same time, I usually change the bogies to ones that look much more authentic.

Often, after making changes in CC and then re-committing, there are new errors. The progressive meshes warning is now an error. Other errors may pop up as well.

So, I have reverted to editing the config.txt file instead of using CC. This prevents the new errors from popping up, and allows me to use the content.
It's not as clean as using CC, but until Auran fixes this issue with CC, is there any choice?

Can anyone give me some idea of why this is happening, and whether there actually is a way to use CC without creating new errors?

Thanks

FW

CC is intended for the creation of new assets, not repairing them as you found out. CC has a built-in error checker that alerts the asset creator that his masterpiece does not meet current standards for uploading to the DLS.

tomurban

 

[clam1952]

You may be interested in Asset-X which is a stand alone fixer being worked on, currently in beta.

http://forums.auran.com/trainz/showthread.php?t=63264

 

[Approach_Medium]

I guess that's why they call it Content Creator, not Content Editor
Sometimes though, it does work very well for repair, such as when I use PevSoft first to create the .im files from the .pm. It saves me the trouble of searching through the sometimes lengthy config file to find what I need to change.

I'll check out the Asset-X beta if it's available for DL.

Thanks

FW

 

[clam1952]

I guess that's why they call it Content Creator, not Content Editor
Sometimes though, it does work very well for repair, such as when I use PevSoft first to create the .im files from the .pm. It saves me the trouble of searching through the sometimes lengthy config file to find what I need to change.

I'll check out the Asset-X beta if it's available for DL.

Thanks

FW

It's on PEV's site, been playing with it and it looks quite useful.

 

[paulzmay]

The main reason CC causes issues is that it updates the asset's build number to the current build, and error checking uses different standards for some issues between trainz-build numbers (e.g. checking for .pm meshes). Using CC, and then reverting the build number of the asset manually may work in some cases.

Paul

 

[Approach_Medium]

The main reason CC causes issues is that it updates the asset's build number to the current build, and error checking uses different standards for some issues between trainz-build numbers (e.g. checking for .pm meshes). Using CC, and then reverting the build number of the asset manually may work in some cases.

Paul

I usually cancel the update when CC opens. Does it still update the build #?

 

[Approach_Medium]

It's on PEV's site, been playing with it and it looks quite useful.

I have checked it out. Agree that it seems useful, but I haven't really tried to fix anything yet.

FW

 

[paulzmay]

I usually cancel the update when CC opens. Does it still update the build #?

It won't save the config with the new build number, but it will list errors based on the latest build error checking.

Paul

 

[Jananton]

It won't save the config with the new build number, but it will list errors based on the latest build error checking.

Paul

Hmm, in my experience if you cancel the build number upgrade it will nevertheless update to 2.9
After that the CMP will check against that set of config rules. This indeed will sometimes introduce new errors.
In such cases I revert the build number manually to the original and that seems to do the trick.

Greetings from overcast Amsterdam,

Jan