This is true on MFT files. I guess I could make MFT files work just like cmpinfo files. I was just trying to keep it simple on MFT files because I figured this would be the more novice use of the tool. Maybe I will change this behavior.
I was just expecting the generated rfcmp package to be written in the output folder specified in options. May be I don't know how to use the tool efficiently. When I test physics I make a version, let's say 0.49 (from 0.48 version mas files) that I package, I try the car, and make some changes to files in the mas files. If I open the cmpinfo file, when I want to pack version 0.5, the cmpinfo has still stored the mas files from the 0.48 version, not of the previous build 0.49, so I have to delete all mas files in your tool and select manually the mas files from verson 0.49, before building version 0.5. That is why I prefer to click directly on the MFT, there the mas files are current, but the output folder has to be changed. Are my explanations clear for you? Thanks again.
Since a few day i always get an error starting the tool. I tried this fix but it is still not starting. https://support.microsoft.com/en-gb...he-net-framework-version-and-platform-support So far it always worked perfect.
Tried this but it does help. I know this works when the mas tool is crashing. But here the cmppack.exe does not start.