-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Thank you for your work that creating a easy way to pack files.
And I wonder where can we found its data folder?
That's what I faced:
-
I used other model swapping F-22. That was my mod files: D:\Nimbus\Content\Blueprint\Player\Pawn\AcePlayerPawn_f22a.uasset & uexp.
-
I moved D:\Nimbus to D:\acmi-pack.exe, named it 0 and successfully created a Pawn_0_P.pak.
-
Pawn_0_P.pak tested well in game, thx.
-
I didn't want to test F-22 any more. instead, I wanted to test F-35. So I deleted D:\Nimbus...\Pawn\AcePlayerPawn_f22a.uasset & uexp, and created D:\Nimbus...\Pawn\AcePlayerPawn_f35c.uasset & uexp.
-
Again, I moved D:\Nimbus to D:\acmi-pack.exe, named it 0 and successfully created a Pawn_0_P.pak.
-
Here comes the problem: the new-built Pawn_0_P.pak contains both AcePlayerPawn_f22a.uasset & uexp and AcePlayerPawn_f35c.uasset & uexp in it, while my D:\Nimbus...\Pawn folder only contains AcePlayerPawn_f35c.uasset & uexp.
-
I tried to deleted Pawn_0_P.pak, acmi-pack.exe, D:\Nimbus folder, reboot, etc. The AcePlayerPawn_f22a.uasset & uexp was still packed in Pawn_0_P.pak again and again, while my new D:\Nimbus...\Pawn folder don't have it any more.
-
I deleted D:\Nimbus...\Pawn\AcePlayerPawn_f35c.uasset & uexp, changed other planes, packed it. Yes, both AcePlayerPawn_f22a.uasset & uexp and AcePlayerPawn_f35c.uasset & uexp were still in the new-built Pawn_0_P.pak, while my new D:\Nimbus...\Pawn folder didn't have both of them any more.
-
So I guess ACMI-pack.exe maybe have a data folder to save old history files? Where can we delete it? Name pak as a new name could be a temporary way to make pak clean, but old name problem was still waited to solve.
Thanks.