version and catagory missing

[imprezza86]

I had to move back to windows 10 in order to play fallout 4. I backed up the mods and then reinstalled them. The game runs correctly but many of the mods have missing version and category information. I tried reinstalling mods, refreshed content. sometimes the category information shows up but not always. Any newly installed mods have no issues. Obviously without the version information, vortex is unable to find updates.

 

 

 

Any suggestions? I really don't wont to download every mod all over again but that might be the only choice.

[Pickysaurus]

Right-click and there may be an option update missing metadata.

[imprezza86]

I tried the function of missing ids but it doesn't work. so I'm stuck with the situation unless i want to download everything all over again.

 

 

not a great solution but I'll deal with it.

[Guest deleted34304850]

you dont need to download every mod, if you double click a mod missing its meta data, you can set the source to nexusmods and assign it the relevant nexusmods id and that should enable vortex to fill in the missing info.

[imprezza86]

you dont need to download every mod, if you double click a mod missing its meta data, you can set the source to nexusmods and assign it the relevant nexusmods id and that should enable vortex to fill in the missing info.

I did try that but it made no difference. However, I will give it one more chance. thank you.

[imprezza86]

 

you dont need to download every mod, if you double click a mod missing its meta data, you can set the source to nexusmods and assign it the relevant nexusmods id and that should enable vortex to fill in the missing info.

I did try that but it made no difference. However, I will give it one more chance. thank you.

 

 

 

I tried again to set the source to nexusmods and the category to its correct nexusmod category. What happens is that most of time but not all, it finds the mod id but not the file id or the version. If I tell it to query the server for the file id, it reports that it can't find it. Example Mod: Everyone's Best Friend (https://www.nexusmods.com/fallout4/mods/13459). I did experience a 404 server error a couple times but general vortex says it can't find the file id. If you look at the file name as it posts the error message, it is the correct the file name.

 

I've tried this multiple times with multiple mods and the same thing occurs every time.

 

I set the source and the category, restarted vortex, and then ran the "fix missing ids" tool. no joy.

[imprezza86]

So here is what I have learned from my experience so far.

 

 

1. I had to backup my mods from vortex when I backrev my computer from win11 to win10 due to issues with win11 not playing nice with fallout4 and other older games. I copied all the mods from folder:

 

C:\Users\XXXX\AppData\Roaming\Vortex\fallout4\mods

 

to my house server.

 

 

2. I then copied all the files back to one of my PC's data drives.

 

3. I reinstalled win10, steam, fallout4, vortex, etc.

 

4. I then installed all the mods back into vortex from my data drive.

 

5. the mods work however, version, category, source, file id are missing most of the time.

 

6. since the data is missing, I have to manually look for any updates to my mods.

 

 

Current Resolution:

 

So far the only way to resolve this issue to download each mod again. For whatever reason, the archived file is important to how vortex works with mods. I understand why the programmers don't save the archived file because it saves additional space.

 

vortex uncompresses the mod into a folder using the file name for each mod then delete the file. It makes sense but somehow its causing issues when you want to backup your mods from vortex and reinstall them. I never had this issue using the Nexus mod manger because it kept all the archived mods. With Vortex, the uncompressed mod is causing the problem because of how it reads it. You don't have any issues when using the actual mod file.

I did try to compress a mod folder back into a .zip and attempt to reinstall it but Vortex didn't like that at all. I was using 7-zip to compress the file. I might try using a different compression algorithm to see if that makes any difference.

 

My guess without seeing the code, the mod folder name should also be set as the file name during the install routine. then create a flag that lets the routine know that the file has already been uncompressed so it can bypass that routine. It can continue to process the mod as though it had just been uncompressed from the file and begin the install process.