-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Query Info picks the wrong mod for some large files (MD5 result overflow) #770
Comments
I just had the exact same thing happen with https://www.nexusmods.com/skyrimspecialedition/mods/6096 - including it using the exact same MD5 in the log. |
Aha. However, the problem happens with the two files from https://www.nexusmods.com/skyrimspecialedition/mods/18115 as I originally reported even with the files fully downloaded. So, the original problem was not due to copying empty files, and MO2 does appear to be doing something wrong. However, the fact that MO2 is trying the hash for an empty file when it's querying the Nexus may give a clue as to what's wrong. |
So I believe its the size of the files that are the issue, I tried a couple of files and one that was around 2gb worked, but larger files failed and gave the blank md5. I suspect its an overflow bug since it looks like its caused by using an int which has a max value of 2,147,483,647 which is approx 2gb |
Fixed by PR #844 in version 2.2.2 |
The problem:
When Query Info is used on two of the three main files from https://www.nexusmods.com/skyrimspecialedition/mods/18115, MO decides that they're from https://www.nexusmods.com/skyrim/mods/92886 (which has been deleted) instead of the correct mod.
To Reproduce:
Steps to reproduce the behavior:
Download the main files from https://www.nexusmods.com/skyrimspecialedition/mods/18115?tab=files For 1.0, that's
Copy them into the Downloads tab in MO2.
Right-click and select "Query Info" for each of the three files.
Music - HQ-18115-0-1.7z
will be correctly selected as being from "Unofficial High Definition Audio Project" (https://www.nexusmods.com/skyrimspecialedition/mods/18115), whereas the other two will be selected as being from the deleted mod https://www.nexusmods.com/skyrim/mods/92886.Environment:
Details:
The steps to reproduce should be pretty self-explanatory for showing the problem.
As for why, it's failing, based on the log, it looks like the current Nexus API searches based on the MD5 of the file, and for some reason MO2 is searching for the wrong MD5. These are the MD5s of the files.
The line
from the log therefore looks correct for "Music - HQ-18115-0-1.7z," and it correctly identifies the mod that the file comes from. However, for both of the others, MO2 seems to be searching for the same, wrong MD5.
So, it at least seems like the problem is that somehow, MO2 is searching for the wrong MD5 for both of those files. But I haven't looked at the code at all, just what the log says and what the result in the .meta file is.
I did try changing the corresponding .meta files to the correct mod, but for better or worse, "Query Info" seems to just throw away what's in the .meta file, though I doubt that whoever worked on that bit of code was expecting someone to manually change the .meta file to try to get "Query Info" to look at the correct mod, and I couldn't fully fix the .meta file, because I have no clue what the fileIDs are. If I did, then MO probably wouldn't think that "Query Info" needed to be run again and wouldn't display the red exclamation sign.
Link to Mod Organizer logs:
The relevant part of mo_interface.log seems to be
This is from copying the three files into MO2 together, and then using "Query Info" on them in the order of
Curiously, before using "Query Info," when the UI lists the file names instead of the mod names, it seems to list two spaces in a row as one space, showing the file name for "Part 2" with one space instead of two after the EN, which is presumably why the UI then lists Part 1 before Part 2, whereas otherwise, lexical ordering would put Part 2 before Part 1 (which is how File Explorer shows them). So, the Downloads tab UI doesn't actually show the exact file names for some reason, but I suppose that that isn't relevant to this bug, just odd.
The text was updated successfully, but these errors were encountered: