Shadohz Posted July 10, 2017 Posted July 10, 2017 PCC failed to verify while transplanting: BioD_Nor_001Global.pcc error when using compression option for compatibility files with ThaneMod vA (when Compress compatibility generator output files in Options is ticked).https://pastebin.com/gPsF2SRc
Shadohz Posted July 10, 2017 Posted July 10, 2017 Batch install cancallation button appears to work. However when ticking the Exit (X) in top right corner the original issue persists (cancels a single mod then continues to the next).
Mgamerz Posted July 10, 2017 Author Posted July 10, 2017 Yes I have fixed the compress bug in my current code. The start command is really dumb in Windows. I was thinking starter kit was really fast... I wonder if I broke something in it.
Shadohz Posted July 10, 2017 Posted July 10, 2017 (edited) PCC failed to verify while transplanting: BioD_CEM_203aGalaxyMap.pcc error when using compression option for compatibility files with CEM and JAM2CEM (when Compress compatibility generator output files in Options is ticked).https://pastebin.com/yapfa4in I'm getting more and more of these failed to transplant errors when using the compress output files in Options. Seems to be a top-level problem. I'll wait until you release a new update before reporting anymore. Edited July 10, 2017 by Shadohz
Mgamerz Posted July 10, 2017 Author Posted July 10, 2017 That compress error seems to have to do with my 64bit zlib in what should be a 32bit process. I should just make a 32-bit and 64-bit build and mod manager will download the appropriate version. 32 bit zlib does not work for me, but it should be running in 64bit...
Mgamerz Posted July 10, 2017 Author Posted July 10, 2017 It looks like I broke starter kit when I updated the drag and drop interface. Starter Kit runs the same action as a compile all tlk drag and drop folder action. Good catch :)
Mgamerz Posted July 11, 2017 Author Posted July 11, 2017 Added RC1. Fixes bugs that Shadohz reported. You may want to clear out your data/tools folder if you are upgrading rather than doing it fresh.
Shadohz Posted July 11, 2017 Posted July 11, 2017 "No Game Repair Database" error repeatedly appear if a Batch install is started but no game database was created prior to batch install being started. Recommendation: Break out of batch installation process to allow user to create a game database.Entire dialog: No Game Repair Database. The game repair database has not been created. Mods that affect the basegame or official DLC require the game repair database to install.
Mgamerz Posted July 11, 2017 Author Posted July 11, 2017 Is this on a fresh instance or an upgrade? I changed how some database stuff is done, I am not sure if it changed how it loads. But yes the game DB check should be before all mods are installed, good catch. Will fix tomorrow.
Shadohz Posted July 11, 2017 Posted July 11, 2017 Is this on a fresh instance or an upgrade? I changed how some database stuff is done, I am not sure if it changed how it loads. But yes the game DB check should be before all mods are installed, good catch. Will fix tomorrow.I deleted all custom DLCs and blew away the "data" folder for the beta version of MM. For all intent and purposes the RC would believe this to be a clean install. Was the ME3 folder completely clean? No. However I have just laid down a fresh install because user has been waiting on me to release an update to my mod he's been waiting for.
Recommended Posts