Hello! For anyone interested, you may join our new server. It is for all current and future mods that are included in the R suite VRAMr, ParallaxR, BENDr, MisMatchR etc
https://discord.gg/cNUFFh3aVq
Whether you're interested in potential announcements for future projects or would just simply like to chat with us, you are welcome!
If MisMatchR has helped you find mismatched texture sets and saved you time - Please Endorse!
If you would like support from myself or PogIsDog then please provide us your Logfiles - see Description page for details
Version 3 uses a different approach to identify mismatches. At the moment we have Green (no mismatch) and Orange (possible mismatch) And Version 4 will expand by introducing Red (confirmed mismatch) by using image analysis++
Is there a way to define exclusions, i.e. mods that don't get treated as conflicting when textures are supplied by (only) those mods? Use case: i have big texture packs for materials textures installed (for example Skyland CM for Skyland AIO), and since every single _m texture naturally comes from a different mod (Skyland CM) than the base textures (Skyland AIO), all of the Skyland textures show up in the list of conflicts, and they are all false positives... in fact, thousands of false positives (for materials textures), which makes the tool almost unusable D:
That's a good point, I'll look into it although 'unusable' is a bit extreme, simply export and filter them output. V4 will bring image analysis mismatching so this tool is about to get a huge uplift over the next month or so.
I'm certain that I am doing something silly or have overlooked something obvious, but I followed the installation instructions and the tool doesn't seem to be finding my mods properly.
When I point it to my profile, exactly as described in the image, MisMatchR doesn't seem to be able to detect which mods are supplying textures.
I know that it sees my profile, because the "Base Name" column contains paths to assets for the mods that I am using and I can even click on them to show thumbnails. However, under the texture columns they all either say "Not Found" or "N/A".
So this happens even when you have selected the name of your profile? Hmm... permissions issue maybe? Do you think you could try to run Mod Organizer 2 as admin?
My support for this mod is limited since I don't have any experience with it yet, but this almost sounds like some access is being denied.
Thanks for the help! It wasn't a permission issue but it got me looking in the right place. I think I may have found the issue since I tripped over the .log files in the overwrite folder.
It appears that it is searching for mods by default in %BASE_DIR%/mods instead of reading my Mods folder location from MO2. However, my actual Mods folder is NOT in the same place as my profiles folder, nor is it called "mods", so it is finding my mod list but not the mods themselves. Is there a place where I can tell the application where my Mods folder is, or am I going to have to move my base directory / profile folder so that it will find it?
I have a similar setup where I share mods across VR and SE so they aren't in the Profiles folder. It would be nice if it read the Mods variable from MO2 as Gawdzila mentioned, but setting it manually would work too.
Hmmm... well, the installation instructions say to install MisMatchR like any mod, right? Is there a way to get it to use its own folder path since it should be in the mods folder?
So i understand your meaning, your asking me to code an option to stipulate exactly where your MO2 \mods folder is, because yours is in a non-standard location?
No no, I was just suggesting a programmatic method of obtaining the mods folder location without getting it from MO2 (i.e. from the location of the .bat/.exe itself, assuming it could obtain its own location) since it is apparently hidden. But I just discovered the new version and found that you put in a prompt for the mods folder, which was a pleasant surprise since I didn't see that change in the changelog. Manual selection is 100% fine! Thank you for the update, the tool is working well! Endorsed! :)
Yes, many AV's can see compiled Python code as a threat. The fact that it passed through Nexus's own VirusTotal scan should give you confidence that this is a false positive....which i assure you it is. I'm not batty enough to distribute viruses Skinjack.
66 comments
VRAMr, ParallaxR, BENDr, MisMatchR etc
https://discord.gg/cNUFFh3aVq
Whether you're interested in potential announcements for future projects or would just simply like to chat with us, you are welcome!
If MisMatchR has helped you find mismatched texture sets and saved you time - Please Endorse!
If you would like support from myself or PogIsDog then please provide us your Logfiles - see Description page for details
At the moment we have Green (no mismatch) and Orange (possible mismatch)
And Version 4 will expand by introducing Red (confirmed mismatch) by using image analysis++
.......and if all goes to plan - Vortex support!
Use case: i have big texture packs for materials textures installed (for example Skyland CM for Skyland AIO), and since every single _m texture naturally comes from a different mod (Skyland CM) than the base textures (Skyland AIO), all of the Skyland textures show up in the list of conflicts, and they are all false positives... in fact, thousands of false positives (for materials textures), which makes the tool almost unusable D:
When I point it to my profile, exactly as described in the image, MisMatchR doesn't seem to be able to detect which mods are supplying textures.
I know that it sees my profile, because the "Base Name" column contains paths to assets for the mods that I am using and I can even click on them to show thumbnails. However, under the texture columns they all either say "Not Found" or "N/A".
Anyone know what I'm doing wrong?
My support for this mod is limited since I don't have any experience with it yet, but this almost sounds like some access is being denied.
I think I may have found the issue since I tripped over the .log files in the overwrite folder.
It appears that it is searching for mods by default in %BASE_DIR%/mods instead of reading my Mods folder location from MO2. However, my actual Mods folder is NOT in the same place as my profiles folder, nor is it called "mods", so it is finding my mod list but not the mods themselves. Is there a place where I can tell the application where my Mods folder is, or am I going to have to move my base directory / profile folder so that it will find it?
Is there a way to get it to use its own folder path since it should be in the mods folder?
Wondering though why its doing this... i guess newest version just asks for permissions Norton doesn't like?