Vortex 1.8.5 "Masterlist" issue

[anjenthedog]

For the past several days, I've been receiving a "bad masterlist" notice from Vortex 1.85 upon loading the application (technically, about 15-20 seconds after opening it)

 

game skyrim se

mods: too many to list, but afaik they're all working

steps: explained below

snaposhot(s): same (you apparently don't allow them for this sub forum...although thanks for re-enabling them in the game-specific tech support fora)

 

Note: "bad masterlist" is paraphrasing.

 

This text editor does not allow uploading a snapshot of the error as presented by vortex (tried four times before I gave up), so you'll have to use your imagination.

 

the message reads "This might be a temporary network error. If it persists, please delete 'C:\Users\(user name)\AppData\Roaming\Vortex\)\skyrimse\masterlist' to force Vortex to download a new copy".

 

I tried deleting the file "to force Vortex to download a new copy", but all that resulted in was even more errors popping up the next time I fired up Vortex. (no image, I don't want to repeat the event again)

 

Reinstating the deleted file in its appropriate location resolved the additional errors but again left me with the bad masterlist issue.

 

please assist

[Deleted180062886User]

I had the same problem this week, spoke about it in a couple of the other threads. Idk what happened with the update, but I was able to fix the issue by power cycling my wi-fi router. I hope this works for you, too

Edited June 24, 2023 by Guest

[anjenthedog]

I had the same problem this week, spoke about it in a couple of the other threads. Idk what happened with the update, but I was able to fix the issue by power cycling my wi-fi router. I hope this works for you, too

thanks for the reply.

 

Much as it sounds an easy fix, and much as I might sound pArANoId, for selfishly pragmatic reasons (security) I'll have to forgo that until Nexus officially responds and explains, since no other application or website is reporting any such issues.

 

in any case, a figurative thumbs up, and fwiw, if they come back with the same advise, then you get the "Marked Solved" creds.

[Deleted180062886User]

 

I had the same problem this week, spoke about it in a couple of the other threads. Idk what happened with the update, but I was able to fix the issue by power cycling my wi-fi router. I hope this works for you, too

thanks for the reply.

 

Much as it sounds an easy fix, and much as I might sound pArANoId, for selfishly pragmatic reasons (security) I'll have to forgo that until Nexus officially responds and explains, since no other application or website is reporting any such issues.

 

in any case, a figurative thumbs up, and fwiw, if they come back with the same advise, then you get the "Marked Solved" creds.

 

Thanks lol, I completely understand, hopefully the next update solves this without users having to try as many things as I did

[Pickysaurus]

Sounds like your getting a bad copy of the master list from GitHub. Deleting the file should download a new copy. If it doesn't something in your setup might be interfering with your connection

[anjenthedog]

Sounds like your getting a bad copy of the master list from GitHub. Deleting the file should download a new copy. If it doesn't something in your setup might be interfering with your connection

thanks for the reply.

 

And there's the rub. I have no problems connecting or logging into github to my account from back when I was working as a web dev. And no other applications or websites are affected. Only Vortex.

 

BTW, it's suddenly loading correctly this morning with no further action on my part (ie deleting the indicated file or resetting my router). Odd. Must have been some address malformation at github or similar.

[Pickysaurus]

It could've also have been the LOOT committed an invalid YAML file to their repo or something. Unlikely, but possible.

[anjenthedog]

It could've also have been the LOOT committed an invalid YAML file to their repo or something. Unlikely, but possible.

Could be.

 

I also wonder if working with Vortex in an offline state and then eventually going online might have upset things. I often shut down my internet when not directly engaging with "net" stuff via web browser. fortunately or unfortunately, it "self-repaired", so it's anyone's guess at this point...

[Platinumbers]

I'm still having the same issue, masterlist won't update, deleting the masterlist folder or file just makes more errors pop up and Vortex never force downloads the new masterlist.

[Pickysaurus]

If Vortex isn't downloading it them something in your setup is preventing it. You can (if you feel up to it) go to LOOT's GitHub page and download the latest masterlist then place it in the folder.