Noel Hibbard
Registered
I made a new tool for building packages. It looks a lot like the MAS2 tool after clicking the package button and then the create single cmp button. My tool has a few advantages. One is it lets you setup some defaults like Author and URL so you don't have to type them every time. It also can save a .cmpinfo file with all the package details which you can open later to repackage another time without having to type all the info again. Once you save a .cmpinfo file you can just double click on it to open it in my tool. Or you can right click on it and select Package and it will package without even prompting for any info. The tool can also open .MFT files. MFT files can be found in your Installed folder. So for example you can install Sebring.. Then open explorer and go to:
In there you will see all the mas files and an MFT file. You can double click on the MFT file and it will come up in my tool and show all the details about the component. From there you can change the GetMod URL and then click package and it will spit out a new rfcmp file (in the same folder) with your changes.
The tool also has some command line options which will help with batch rfcmp creation.
Here are the options:
--package tells the tool to open the cmpinfo file specified by with the --file option and then package it and close. --version=<version> tells the tool to update the version number when creating the new package and it also saves the new version number in the cmpinfo file.
The tool probably has some bugs so maybe you guys could mess around with it and report any problems you find.
This tool along with the new ModMgr command line options should allow modders to fully automate the packaging process. I was able to fully script the process on a 900MB mod and it takes about 1min to run through the whole process of updating the MAS files with the latest files and then building the individual rfcmp files and all I have to do is double click on a single batch file.
Here is a download link:
http://www.mediafire.com/download/o614b7rdl4zo7dn/cmppack.exe
You must save this file into your Core folder right beside the other EXE files (rFactor2.exe, ModMgr.exe, ect). The first time you run the tool it pops up the setting dialog where you can type your default Author, URL, output path (where you want it to place the rfcmp files) and the path to the MAS2.exe file. You can leave all of these blank except for the path to the MAS2 Tool. On first run it will also build file associations and context menus for .cmpinfo and .mft files.
Also check out my MAS extraction tool in this thread:
http://isiforums.net/f/showthread.php/18947-MAS-file-extractor-rfcmp-Installer
With the combination of these two tools and the new ModMgr.exe command line options you can script full builds with ease.
Here is a screenshot of me going into the Installed folder for ISI's Camaro and then double clicking on the camaro_car.mft file. From here I could change details about the car and then click Package to create a new rfcmp file.:

Change Log:
1.0.0.0: First release
1.0.0.1: Some error checking for stuff like missing mas files ect. Also added a "Save As" button so you can open a .cmpinfo file for one car, change the MAS list, name, ect and then save it with a new filename. The date field shows a real date now rather than an epoch date. When you create a new component it defaults to today's date. I also rearranged some buttons and changed some verbage a little.
1.0.0.2: Switched output path and mas file paths to be relative to the working directory of cmppack.exe. This makes it easier to create a more portable built environment that can be shared with other team members.
1.0.0.3: Added an option to the settings dialog to turn relative paths on or off. By default relative paths are disabled.
1.0.0.4: Fixed bug which was causing the tool to not create correct relative paths.
1.0.0.5: Fixed bug when saving cmpinfo files without having a catagory and/or origin set.
Click here to donate
Code:
<datapath>\Installed\Locations\Sebring_Virtua_LM\1.90
In there you will see all the mas files and an MFT file. You can double click on the MFT file and it will come up in my tool and show all the details about the component. From there you can change the GetMod URL and then click package and it will spit out a new rfcmp file (in the same folder) with your changes.
The tool also has some command line options which will help with batch rfcmp creation.
Here are the options:
Code:
--file=<mft or cmpinfo file> [--version=<version>] [--package]
--package tells the tool to open the cmpinfo file specified by with the --file option and then package it and close. --version=<version> tells the tool to update the version number when creating the new package and it also saves the new version number in the cmpinfo file.
The tool probably has some bugs so maybe you guys could mess around with it and report any problems you find.
This tool along with the new ModMgr command line options should allow modders to fully automate the packaging process. I was able to fully script the process on a 900MB mod and it takes about 1min to run through the whole process of updating the MAS files with the latest files and then building the individual rfcmp files and all I have to do is double click on a single batch file.
Here is a download link:
http://www.mediafire.com/download/o614b7rdl4zo7dn/cmppack.exe
You must save this file into your Core folder right beside the other EXE files (rFactor2.exe, ModMgr.exe, ect). The first time you run the tool it pops up the setting dialog where you can type your default Author, URL, output path (where you want it to place the rfcmp files) and the path to the MAS2.exe file. You can leave all of these blank except for the path to the MAS2 Tool. On first run it will also build file associations and context menus for .cmpinfo and .mft files.
Also check out my MAS extraction tool in this thread:
http://isiforums.net/f/showthread.php/18947-MAS-file-extractor-rfcmp-Installer
With the combination of these two tools and the new ModMgr.exe command line options you can script full builds with ease.
Here is a screenshot of me going into the Installed folder for ISI's Camaro and then double clicking on the camaro_car.mft file. From here I could change details about the car and then click Package to create a new rfcmp file.:

Change Log:
1.0.0.0: First release
1.0.0.1: Some error checking for stuff like missing mas files ect. Also added a "Save As" button so you can open a .cmpinfo file for one car, change the MAS list, name, ect and then save it with a new filename. The date field shows a real date now rather than an epoch date. When you create a new component it defaults to today's date. I also rearranged some buttons and changed some verbage a little.
1.0.0.2: Switched output path and mas file paths to be relative to the working directory of cmppack.exe. This makes it easier to create a more portable built environment that can be shared with other team members.
1.0.0.3: Added an option to the settings dialog to turn relative paths on or off. By default relative paths are disabled.
1.0.0.4: Fixed bug which was causing the tool to not create correct relative paths.
1.0.0.5: Fixed bug when saving cmpinfo files without having a catagory and/or origin set.
Click here to donate
Last edited by a moderator: