I have M3 installed on three machines and was alerted to batch installs with the recent "Show Us Your Mass Effect Mod Group" event. Though I had been simply creating a TXT file with the names of the mods in their install order, I had created 7z files for the event and realised I could use them to keep the three machines synched.
But when I tried to copy the 7z files to a second machine, drag'n'dropping them on M3 resulted in no files being shown in the Batch Mod Installer's Install Groups window. I tried to Import them (also in the Mod Mgt menu,) but was alerted to the fact that this would replace extant files with the same names. I imported them anyway, but there are still no files in the Install Groups window.
I have tried restarting M3 and the machine, to no avail.
I'm not even sure how to troubleshoot this; an error log seems irrelevant.
I have already installed mods manually (using my text list) for LE1 and LE2, and they work just wonderfully; I'm addicted and grateful. But this is my first playthrough since discovering M3, and after modding the crap out of LE (I have about 50GB of mods installed,) I have only completed LE1&2 so far; I thought I might be able to save myself some time manually installing (which usually takes an entire evening after work.)
Is there something subtle to the Batch Mod Installer that evades me ATM?
#Batch installer doesn't load or show 7z install groups
brazen hull
fickle belfry
!m3log
buoyant parrotBOT
brazen hull
Since this glitch is happening in the Batch Mod Installer, which game should I select in the Logs and Diagnostics dialogue box? (I have both dragged and Imported the 7z files to the Batch Mod Installer for all three games, and none of them appear in the Install Groups window.)
But for giggles, here's one with that set to no game: 0583e040ac0f79d7bce1ded42244cb4c
brazen hull
That's the most recent log. I'm running another with it set to ME3, which I haven't run on this machine (the second of the three, and will post it as soon as it completes. The Full Texture Check is taking a long time.
fickle belfry
thats not a link.
brazen hull
put https://me3tweaks.com/modmanager/logservice/logviewer?logid= in front of it.
https://me3tweaks.com/modmanager/logservice/logviewer?logid=0583e040ac0f79d7bce1ded42244cb4c
fickle belfry
you have : in your queue name
this likely will not work cause : cannot be a character in the filesystem. M3 technically should have sanitized it, but I probably didn't code that in.
brazen hull
It coughed a hairball about that when I tried to save it...I thought I'd replaced it with an underscore.
fickle belfry
2023-10-24 22:33:53.570 -04:00 [INF] [M3] Writing batch installer group to C:\Users\User1\Documents\ME3TweaksModManager\mods\BatchModQueues\ME1:AitD.biq2
this isn't in a try catch, it likely failed and then went unhandled
which is why log doesn't show it
brazen hull
Looks like I'll have to go back to the machine I generated the 7z file on to rename it, then?
Well, thanks for helping me figure out what the problem was.
brazen hull
Wow...thanks for the extra help. I figured it was my problem at this point.
fickle belfry
yea its using the queuename "queuename": "ME2:AitD",
brazen hull
Is there a way to edit that? I won't be back to that lab until after Thanksgiving.
fickle belfry
you can just manually extract this .biq2 file into C:\Users\User1\Documents\ME3TweaksModManager\mods\BatchModQueues
brazen hull
Yeeow, that was fast.
fickle belfry
it looks like the code sanitizes it on serialization into the archive but it uses the name for deserialization which can differ, which is where this error is. I'll adjust it to use the filename directly
brazen hull
The other log just finished, but it seems superfluous at this point.