jb2k1 Posted January 7, 2020 Share Posted January 7, 2020 Running Vortex 1.1.5 on Windows 7 x64, game is Fallout 4. I manually download mod files, then drag and drop them on the target zone on the downloads tab of Vortex. Then I select them and "query info" and Vortex gets all the metadata and when I install the mod everything is already filled out. However, for the last couple weeks the "query info" function is no longer working for new mod files, it still works for old mod files. It seems that any mod files uploaded to Nexus after some date in the last couple weeks no longer work with the "query info" function. Link to comment Share on other sites More sharing options...
Pickysaurus Posted January 7, 2020 Share Posted January 7, 2020 Interesting. You can still obtain most of the data using "Guess ID" option on mods. I'll feed it back to the team. Link to comment Share on other sites More sharing options...
jb2k1 Posted January 7, 2020 Author Share Posted January 7, 2020 Thanks for forwarding it to the team. Just curious, were you able to reproduce the issue, or is it just me? As for the "Guess ID" option, that's exactly what I've been doing, and it works, it's just a little more work having to manually edit the name as well as the version number, but everything else is automatically filled. Link to comment Share on other sites More sharing options...
Pickysaurus Posted January 7, 2020 Share Posted January 7, 2020 As a result of your report we discovered that the MD5 hashes (a unique key that identifies the file) for new uploads had not been saved in our database correctly. The problem was being fixed today, so I expect it to start working again soon. Link to comment Share on other sites More sharing options...
Guest deleted34304850 Posted January 7, 2020 Share Posted January 7, 2020 just seeing this now, and i had an odd experience earlier this evening. i asked vortex to "guess" the mod id and it came up with a completely random number. of course, this sent me to a mod that was in no way related to the real mod. i manually edited the value in the metadata, pointing to the correct mod.not seen this before so i guess my experience is a result of the nd5 hash being out of whack in the database? Link to comment Share on other sites More sharing options...
jb2k1 Posted January 7, 2020 Author Share Posted January 7, 2020 Glad you were able to find the problem. Do you know if the fix is going to be retroactive or only for files from now on? Link to comment Share on other sites More sharing options...
Pickysaurus Posted January 8, 2020 Share Posted January 8, 2020 Glad you were able to find the problem. Do you know if the fix is going to be retroactive or only for files from now on? Yes, we will make it retroactive. just seeing this now, and i had an odd experience earlier this evening. i asked vortex to "guess" the mod id and it came up with a completely random number. of course, this sent me to a mod that was in no way related to the real mod. i manually edited the value in the metadata, pointing to the correct mod.not seen this before so i guess my experience is a result of the nd5 hash being out of whack in the database? If you can provide specifics I can look into it. Link to comment Share on other sites More sharing options...
Guest deleted34304850 Posted January 8, 2020 Share Posted January 8, 2020 Glad you were able to find the problem. Do you know if the fix is going to be retroactive or only for files from now on? Yes, we will make it retroactive. just seeing this now, and i had an odd experience earlier this evening. i asked vortex to "guess" the mod id and it came up with a completely random number. of course, this sent me to a mod that was in no way related to the real mod. i manually edited the value in the metadata, pointing to the correct mod.not seen this before so i guess my experience is a result of the nd5 hash being out of whack in the database? If you can provide specifics I can look into it. Sure. The mod in question is https://www.nexusmods.com/fallout4/mods/22519 so it's mod id is 22519. yesterday, when i had vortex "guess" the id of the mod the value it assigned was 3, which leads me to this mod; https://www.nexusmods.com/fallout4/mods/3 as i said, i can easily edit the correct mod id value, but this is the first time i've seen this behaviour. i wonder if the two mods somehow share the same md5 hash value, and 3 is being returned as its the first record found? Link to comment Share on other sites More sharing options...
AugustaCalidia Posted January 8, 2020 Share Posted January 8, 2020 Glad you were able to find the problem. Do you know if the fix is going to be retroactive or only for files from now on? Yes, we will make it retroactive. just seeing this now, and i had an odd experience earlier this evening. i asked vortex to "guess" the mod id and it came up with a completely random number. of course, this sent me to a mod that was in no way related to the real mod. i manually edited the value in the metadata, pointing to the correct mod.not seen this before so i guess my experience is a result of the nd5 hash being out of whack in the database? If you can provide specifics I can look into it. Sure. The mod in question is https://www.nexusmods.com/fallout4/mods/22519 so it's mod id is 22519.yesterday, when i had vortex "guess" the id of the mod the value it assigned was 3, which leads me to this mod; https://www.nexusmods.com/fallout4/mods/3 as i said, i can easily edit the correct mod id value, but this is the first time i've seen this behaviour. i wonder if the two mods somehow share the same md5 hash value, and 3 is being returned as its the first record found? The same thing happened to me. My guess is that the problem is either what you suggested or that the mod author didn't follow the proper naming protocols. This wrong guess happens sometimes for older games like Fallout 3 and Fallout NV where there seem to have been no standardized naming conventions. In those cases Vortex sometimes returns no answer to the query, but more often than not it returns a partial mod version number. In the case of the Vault 88 mod, it's interesting that Vortex returns the number "3." Link to comment Share on other sites More sharing options...
Guest deleted34304850 Posted January 20, 2020 Share Posted January 20, 2020 any update on the incorrect value assigned to the mod by vortex? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.