Autocommit at Trainz launch vs commit in CM

[schweitzerdude]

I successfully imported an archived route from TC1&2 into TS2010 as an archive (*.cmpa) file, although some assets didn't survive the trip but I expected that to be the case. (I chose not to run in capatability mode). After reading the manual re committing imported content (page 45), in CM I did a search and found that all my DLS-imported content from my imported route is uncommitted, found by doing a search: location=local, open for edit=true. But CM has a default setting: file/settings/miscellaneous/when launching Trainz=automatically commit assets, but they don't stay committed apparently. Assets from the DLS into TS2010 seem to be committed, contrary to what the manual says. This may be due to the default setting in CM: "automatically commit when installing CDPs".

My question is would I benefit performance-wise by committing in CM approximately 250 open for edit assets from my imported route or just let them commit at Trainz launch, as is now the case?

 

[Euphod]

I don't think there is a performance penalty, per se, but I try to commit when it's called for, and just use the setting as a backup. There may be a wait when Trainz launches if you let the program commit at that point considering the number of items open.