It seams the reason I couldn't find the pkginfo.dat. is because it doesn't exit. Instead I've found these two, Seams to be the same thing but are named cmpinfo, Not pakinfo. I'll delete these two and have another try after work tonight. Let you know what happens.
As i explained in my previous post #20 that it's no longer present or used from the Roaming directory. I doubt deleting the "cmpinfo" files will fix your unique issue but you have nothing to lose so i do hope i'am wrong. Good luck!! Edit: @D.Painter ...Contact Support from your Launcher with your "PerfLog" file explaining the issue which might be your best solution!
When I open them in notebook all the entries listed were relevant to what I have been doing so they are current. I truly hope it does fix my problem! Haha..
I am not an expert but after several attempts I got it. I updated the version of the update on the official update of the mod (I could not make it work on the base version) The new skins were added to the original skins. the most important thing ... the new package https://velaqui.gal/link/TVRJNE56UTJNell5T1E9OjpoYXNoOjowLjE0NTcxNzAwIDE1NjAwNzAzMTk-/ P.D.: I suppose it stops working when Studio updates the mod
In my 3+ years of packaging it has always been the "Base" directory so the "update from" knows the proper directory to sync with. I see no VEH files listed but in it's place using RCD files in your package so perhaps being unconventional is why it works for you.
Well ... I see that it works in both ways. The new skins are added but the version does not change when it is updated on the base version. On the other hand when the update is made on the next version it becomes a new version. I'm sorry I can not explain myself better, I use a translator and I hope I'm doing it right (G ... Translator)
It's too late for me and I'm going crazy If I update on the base (v1.72) the result is a white skin instead if I update on version v1.73 the new skin looks good P.D.: I hope not to infect my madness
The reason why you're experiencing the white car skin effect when using the correct base directory is bacause you're not including the necessary VEH file for each one of your skins so the game knows which car number or naming matches it's proper skin. The advantage to using the proper Base directory is that it seperates your 3rd party skins from S397 default skins by their version numbers which is great if you only want 3rd party skins in some races or perhaps only S397 default skins in other races!
Hi all. See you've been having some fun while I've been at work. I'm going to step by step this post as I go through the packaging. First thing is I've delete those cmpinfo.dat file. Now opening the Mas. tool, going to "create Single cmp Package" The first thing is it's a clean skin, No entries. Probably a good sign. I'll use the BMW M6 as that's the one I've been showing the most here. Open the installed location folder, find the BMW M6 Still no joy. Want work with Update from. Want package. Mas. tool exe is the latest one in the rF2 directory.
I doubt it will change anything but, what happens if you open the mas tool through the launcher and not through the exe?
Thank you for that. It actually work!!! as strange as it may seem using the launcher to open the Mas tool did make the difference. Cheers guy's.
Glad you finally sorted! Quite strange btw, through the launcher you basically open the exe, i thought they are the same but apparently there are differences.
I use the MAS2.exe to do my packaging so you probably have a corruption or wrong file location for it not to work directly from the EXE. Be sure the MAS2.exe path location is: rFactor 2/Support/Tools/MAS2
@D.Painter I don't think you've shown a screenshot of your main MAS tool window, which might show any issues with which folders are being used. As an outside chance.