Retain My Asset Names
(→Other Features) |
m (→Screenshot) |
||
| (24 intermediate revisions by one user not shown) | |||
| Line 1: | Line 1: | ||
== Summary == | == Summary == | ||
| − | '''Retain My Asset Names''', abbreviated as "'''RMAN'''", is a third party Trainz Asset Name management tool by '''Deneban Software'''. It is a shareware program for Windows 64-bit Desktop and is hosted on a node of SourceForge, where resides its documentation exclusively. Version 1.00 was rolled out on May 21, 2020. The current release is 1.01, February 18, 2021, where two bugs were corrected. Currently it is applicable to TS12, TANE, and TRS19, up until TRS19SP3. Version 2.00 is under development and will include substantial improvements and TRS19SP4 compatibility. As of Summer 2023, | + | '''Retain My Asset Names''', abbreviated as "'''RMAN'''", is a third party Trainz Asset Name management tool by '''Deneban Software'''. It is a shareware program for Windows 64-bit Desktop and is hosted on a node of SourceForge, where resides its documentation exclusively. Version 1.00 was rolled out on May 21, 2020. The current release is 1.01, February 18, 2021, where two bugs were corrected. Currently it is applicable to TS12, TANE, and TRS19, up until TRS19SP3. Version 2.00 is under development and will include substantial improvements and TRS19SP4 compatibility. As of Summer 2023, Version 2.0 is still under active development.<br><br> |
| − | + | * <i>Unfortunately, due to the unprecedented revisions to Asset Status Flags made in TRS19SP4, it and its successors are not compatible with Versions 1.x.</i> | |
| − | < | + | * <i>See the table below for major RMAN links</i><br><br> |
| + | |||
| + | == Screenshot == | ||
| + | Main Window and Transaction Window<br> | ||
[[File:Both-Windows-CP.png|750px]]<br><br> | [[File:Both-Windows-CP.png|750px]]<br><br> | ||
| Line 34: | Line 37: | ||
<tr> | <tr> | ||
<td>[[File:RedSquarePoint.jpg]]</td> | <td>[[File:RedSquarePoint.jpg]]</td> | ||
| − | <td><b>[https://forums.auran.com/ | + | <td><b>[https://forums.auran.com/forums/blogs.122/?starter_id=41964 Blog]</b></td> |
</tr> | </tr> | ||
</table><br> | </table><br> | ||
| Line 40: | Line 43: | ||
== Concept Evolution == | == Concept Evolution == | ||
| − | Although RMAN was inspired by merely attempting to restore the user capability of assigning custom asset names within a users local asset collection (a capability furnished with TS12 but disconcertingly dropped with the advent of TANE), the final product is fairly robust in concept, aimed at providing a total name management solution; one that gains virtually absolute control of a users local asset names, never to be lost again to revisions or reversions. An example of the robustness of its concept is best seen in the breadth of data it will handle (and promises to handle): it can reach back to collect TS12 data while reaching forward across decades, managing TANE/TRS19 names, and claims it will project a users "permanent" customized names forward into future N3V Trainz releases that haven't entered their conceptual phase.<br> | + | Although RMAN was inspired by merely attempting to restore the user capability of assigning custom asset names within a users local asset collection (a capability furnished with TS12 but disconcertingly dropped with the advent of TANE), the final product is fairly robust in concept, aimed at providing a total name management solution; one that gains virtually absolute control of a users local asset names, never to be lost again to revisions or reversions. An example of the robustness of its concept is best seen in the breadth of data it will handle (and promises to handle): it can reach back to collect TS12 data while reaching forward across decades, managing TANE/TRS19 names, and claims it will project a users "permanent" customized names forward into future N3V Trainz releases that haven't entered their conceptual phase.<br><br> |
== Main Window Overview == | == Main Window Overview == | ||
| Line 46: | Line 49: | ||
[[File:Main-Window-CP.png|750px]]<br><br> | [[File:Main-Window-CP.png|750px]]<br><br> | ||
RMAN's Main Window is where the user sets up the paths to Trainz folders, the originating Trainz version to import asset names from (optional), and the destination Trainz version where the customized names will be implemented. Contained here are the very important buttons where the user collects their originating Trainz version asset names and destination Trainz version asset names, thereby setting up the bulk of their data sets before renaming work begins. There are buttons for the user to load and save their custom asset names such that it is possible to import and export to other RMAN data sets / installations, including future Trainz versions. A name filter for certain operations is also available. | RMAN's Main Window is where the user sets up the paths to Trainz folders, the originating Trainz version to import asset names from (optional), and the destination Trainz version where the customized names will be implemented. Contained here are the very important buttons where the user collects their originating Trainz version asset names and destination Trainz version asset names, thereby setting up the bulk of their data sets before renaming work begins. There are buttons for the user to load and save their custom asset names such that it is possible to import and export to other RMAN data sets / installations, including future Trainz versions. A name filter for certain operations is also available. | ||
| − | <br> | + | <br><br> |
== Transaction Window Overview ( & Single Asset Editing Tab ) == | == Transaction Window Overview ( & Single Asset Editing Tab ) == | ||
| Line 59: | Line 62: | ||
'''''As a result, any name applied to the "Destination Version Name" field causes RMAN to change the name in the Destination Version of Trainz actual user data, thus making that name appear on the Surveyor Palettes when installed assets are listed.'' | '''''As a result, any name applied to the "Destination Version Name" field causes RMAN to change the name in the Destination Version of Trainz actual user data, thus making that name appear on the Surveyor Palettes when installed assets are listed.'' | ||
| − | ''' | + | '''<br><br> |
== Asset Update Tab == | == Asset Update Tab == | ||
| Line 68: | Line 71: | ||
'''''As a result of the name being applied to the Trainz destination version asset library, that name will appear on the Surveyor Palettes when installed assets are listed.'' | '''''As a result of the name being applied to the Trainz destination version asset library, that name will appear on the Surveyor Palettes when installed assets are listed.'' | ||
| − | ''' | + | '''<br><br> |
== Asset Deletion Review == | == Asset Deletion Review == | ||
[[File:Found-deleted-asset.png|750px]]<br><br> | [[File:Found-deleted-asset.png|750px]]<br><br> | ||
| − | Similar to "Asset Update" there is an "Asset Deletion" review process, although its execution is not as pressing or important as Asset Update. This process seeks out KUID versions that appear in RMAN but not in the user's current Trainz installation. It is located in the "Multi-asset Transactions Tab" of the Transaction Window. This facility can remove kuid versions from the 3 data streams RMAN carries, so the name is no longer carried. Alternatively, as a deleted asset is discovered and presented to the user, he/she can elect to keep the KUID version record and annotate what appears in their "My Name" data set for future reference. Here for example, the users customized names data set will retain the annotation shown, one indicating the asset is obsolete and what the DLS (i.e. originating author) calls the asset. In this case however, the destination Trainz version record for this specific KUID version will be deleted to reflect its deletion in the user's current Trainz installation. The process continues until all the deleted assets are dispositioned or the user aborts the operation. | + | Similar to "Asset Update" there is an "Asset Deletion" review process, although its execution is not as pressing or important as Asset Update. This process seeks out KUID versions that appear in RMAN but not in the user's current Trainz installation. It is located in the "Multi-asset Transactions Tab" of the Transaction Window. This facility can remove kuid versions from the 3 data streams RMAN carries, so the name is no longer carried. Alternatively, as a deleted asset is discovered and presented to the user, he/she can elect to keep the KUID version record and annotate what appears in their "My Name" data set for future reference. Here for example, the users customized names data set will retain the annotation shown, one indicating the asset is obsolete and what the DLS (i.e. originating author) calls the asset. In this case however, the destination Trainz version record for this specific KUID version will be deleted to reflect its deletion in the user's current Trainz installation. The process continues until all the deleted assets are dispositioned or the user aborts the operation.<br><br> |
== Bulk Asset Rename == | == Bulk Asset Rename == | ||
[[File:Bulk.png]]<br><br> | [[File:Bulk.png]]<br><br> | ||
| − | Version 2.0 will introduce a "Bulk Asset Rename" facility allows users to make multiple asset renames in a single operation and immediately appear on the Surveyor asset palettes. | + | Version 2.0 will introduce a "Bulk Asset Rename" facility allows users to make multiple asset renames in a single operation and immediately appear on the Surveyor asset palettes. |
| + | <br><br> | ||
== Other Features == | == Other Features == | ||
| Line 95: | Line 99: | ||
* Query listing of assets with same root KUID to provide similar naming carry-over | * Query listing of assets with same root KUID to provide similar naming carry-over | ||
* Saving of CDP files for renamed assets | * Saving of CDP files for renamed assets | ||
| + | * Ability to bypass "Base" assets during Asset Update operations | ||
* Improved documentation Wiki | * Improved documentation Wiki | ||
* Improved handling of problematic assets | * Improved handling of problematic assets | ||
Latest revision as of 11:22, 2 September 2023
Contents |
[edit] Summary
Retain My Asset Names, abbreviated as "RMAN", is a third party Trainz Asset Name management tool by Deneban Software. It is a shareware program for Windows 64-bit Desktop and is hosted on a node of SourceForge, where resides its documentation exclusively. Version 1.00 was rolled out on May 21, 2020. The current release is 1.01, February 18, 2021, where two bugs were corrected. Currently it is applicable to TS12, TANE, and TRS19, up until TRS19SP3. Version 2.00 is under development and will include substantial improvements and TRS19SP4 compatibility. As of Summer 2023, Version 2.0 is still under active development.
- Unfortunately, due to the unprecedented revisions to Asset Status Flags made in TRS19SP4, it and its successors are not compatible with Versions 1.x.
- See the table below for major RMAN links
[edit] Screenshot
Main Window and Transaction Window
[edit] Links for Retain My Asset Names
| Important Links for Retain My Asset Names | |
 |
Main Landing Page and Executable File Download |
|
Wiki |
|
Bug Reports |
|
Release Thread in Trainz Forums |
|
Customer Service Thread in Trainz Forums |
|
Blog |
[edit] Concept Evolution
Although RMAN was inspired by merely attempting to restore the user capability of assigning custom asset names within a users local asset collection (a capability furnished with TS12 but disconcertingly dropped with the advent of TANE), the final product is fairly robust in concept, aimed at providing a total name management solution; one that gains virtually absolute control of a users local asset names, never to be lost again to revisions or reversions. An example of the robustness of its concept is best seen in the breadth of data it will handle (and promises to handle): it can reach back to collect TS12 data while reaching forward across decades, managing TANE/TRS19 names, and claims it will project a users "permanent" customized names forward into future N3V Trainz releases that haven't entered their conceptual phase.
[edit] Main Window Overview
The balance of this page has summaries of RMAN's main features. Refer to the RMAN Wiki for complete documentation.
RMAN's Main Window is where the user sets up the paths to Trainz folders, the originating Trainz version to import asset names from (optional), and the destination Trainz version where the customized names will be implemented. Contained here are the very important buttons where the user collects their originating Trainz version asset names and destination Trainz version asset names, thereby setting up the bulk of their data sets before renaming work begins. There are buttons for the user to load and save their custom asset names such that it is possible to import and export to other RMAN data sets / installations, including future Trainz versions. A name filter for certain operations is also available.
[edit] Transaction Window Overview ( & Single Asset Editing Tab )
The Transaction Window is used once the user has imported the asset name data sets from the originating (optional) and destination Trainz versions. The Transaction Window has several tabs along its bottom border where asset names are edited, updated, deleted, and the data otherwise maintained. The window is opened by double clicking on the grid in the Main Window. It is always opened below the Main Window, for easy reference, and both windows travel together if either is dragged.
Here shown is the Single-asset Transactions Tab. From here the user can move the grid in the Main Window to any asset in the 3 data sets (originating, customized, and destination). RMAN operates on an asset KUID version basis. The KUID text box can be used to find an asset and set the grid to that position or can be set to any asset by double-clicking in any grid row in the Main Window.
Once the asset to be worked is set in the window, the presence of that asset in the originating and destination Trainz versions can be seen. The originating Trainz version name can be copied to both the user's permanent custom name and the destination Trainz version name. If the user wants a different name, it can be entered into the "My Asset Name" text box and copied to the destination Trainz version name. If the asset is present in the originating version, but not the destination version, the "Attempt to Download from DLS" button can be used to download the asset.
To help the user in the naming process, the asset's preview and config.txt buttons provide full information on the asset.
As a result, any name applied to the "Destination Version Name" field causes RMAN to change the name in the Destination Version of Trainz actual user data, thus making that name appear on the Surveyor Palettes when installed assets are listed.
[edit] Asset Update Tab
Because a Trainz user is constantly adding assets to their local asset library, RMAN provides an "Asset Update" facility, shown here, to maintain the RMAN data sets current. This is located on the "Asset Update Tab" of the Transaction Window, but it can also be launched from the Main Window using the "Refresh..." button.
The user can choose from reviewing each new asset name individually, or having RMAN do a bulk update. Which method is determined by the "Options" checkbox. Here is shown a new version of an asset has been discovered by RMAN, but new KUIDs also appear in the same manner. The name appears in red and is editable. The "Copy Name from Previous" button can be used to carry forward the name used in the prior version, if a version update appears. Asset previewing and config.txt viewing buttons are also provided to help the user disposition the new asset's name. The user can either save the name and continue the process or save the name and quit the process. If the user quits, any non-dispositioned KUID versions will appear next time an Asset Update is invoked. The saved name is used both in the users custom names and the Trainz destination version asset library.
As a result of the name being applied to the Trainz destination version asset library, that name will appear on the Surveyor Palettes when installed assets are listed.
[edit] Asset Deletion Review
Similar to "Asset Update" there is an "Asset Deletion" review process, although its execution is not as pressing or important as Asset Update. This process seeks out KUID versions that appear in RMAN but not in the user's current Trainz installation. It is located in the "Multi-asset Transactions Tab" of the Transaction Window. This facility can remove kuid versions from the 3 data streams RMAN carries, so the name is no longer carried. Alternatively, as a deleted asset is discovered and presented to the user, he/she can elect to keep the KUID version record and annotate what appears in their "My Name" data set for future reference. Here for example, the users customized names data set will retain the annotation shown, one indicating the asset is obsolete and what the DLS (i.e. originating author) calls the asset. In this case however, the destination Trainz version record for this specific KUID version will be deleted to reflect its deletion in the user's current Trainz installation. The process continues until all the deleted assets are dispositioned or the user aborts the operation.
[edit] Bulk Asset Rename
Version 2.0 will introduce a "Bulk Asset Rename" facility allows users to make multiple asset renames in a single operation and immediately appear on the Surveyor asset palettes.
[edit] Other Features
RMAN contains several other useful features which are fully documented in the Wiki. Here is a sample list by version:
Versions 1.x:
- Designed for highly reliability in maintaining data
- Asset Grid tabulation displaying all asset names per a given asset number
- Asset Preview or Config.txt display
- User choice to revert or modify assets turned faulty by rename
- Two methods of loading Originating Version assets
- Output Files tabulating all KUID Name data for user's use external to RMAN
- Data Saving On Demand, via an AutoSave interval, or manually
Version 2.0:
- Query listing of assets with same root KUID to provide similar naming carry-over
- Saving of CDP files for renamed assets
- Ability to bypass "Base" assets during Asset Update operations
- Improved documentation Wiki
- Improved handling of problematic assets
- Much improved "Sailor-proofness", avoiding crashes from user mis-operations
- Startup and Import Data Integrity Checks and Automatic Corrections
- Numerous visual and interface improvements
