Kilo64 Posted October 15 Share Posted October 15 13 hours ago, Nagev said: Hey Kilo64, The beta.3 update should've indeed fixed the incorrect update notifications as I highlight in the below .gif. I'm pretty certain that the incorrect update notifications on your end may be down to some items hanging in your state. Can you please record a short video or gif which still exhibits the false update notification behaviour to see if I can spot the issue? Please note that some mod update chains are just broken beyond what Vortex can handle, so some mods will always display the external update link icon; but that's down to the lax versioning requirements when uploading/updating a mod on the website. Thank you for the clarification, Nagev. It appears that I am running into the same thing that @dizietemblesssma is encountering in their post. I would record something for this but what I am experiencing is captured in their post exactly. It looks like since my mods were originally erroneously flagged as update available, the state of their update status appears to be permanently stuck as update available. Checking for updates doesn't clear these erroneous update flags and neither does the Clear Update extension. Here is a screenshot of my Vortex searching for mod updates and how it still shows a bunch of mods needing an update when they don't and didn't before 1.13. Only one update in the visible list is correct (B42 Optics NV Patches) and out of the 43 with update available around 10 are real updates. @Petty7 - You might want to double check your mods again because the Clear Update extension only temporarily clears the update flag and it will reset the clear when you restart Vortex. Link to comment Share on other sites More sharing options...
Petty7 Posted October 16 Share Posted October 16 (edited) I'm sorry it doesn't work for you, I already have restarted Vortex a few times, checked mods for updates and the wrong update flag has gone for good. I also have removed the Clear Update extension just to check if the bug reappears but no, it's clean here. Edited October 25 by Petty7 Link to comment Share on other sites More sharing options...
Nagev Posted October 16 Share Posted October 16 Hey guys, looks like I'll need to write-up a state verifier to clean-up leftover update metadata. Will have that in beta.4 which will be released Monday next week at the latest. Sorry you're still affected by this Link to comment Share on other sites More sharing options...
Nagev Posted October 16 Share Posted October 16 Hey again, didn't feel right to leave you guys with this issue over the weekend so I found a workaround. Made an improvement to the Clear Update extension which will help in this instance. 1. Please ensure you've downloaded version 1.0.3 of the Clear Update extension. (The update should become available within the next 15-20 minutes) 2. Choose to ignore the update for the mods you've confirmed are having this issue, and wait for the version column to clear up. 3. Once you confirm that the columns have cleared correctly, run the full update check. 4. You're done. Link to comment Share on other sites More sharing options...
dizietemblesssma Posted October 16 Author Share Posted October 16 Mostly works but still a couple of left overs in Fallout NV https://i.imgur.com/s6cFNMc.png diziet Link to comment Share on other sites More sharing options...
Kilo64 Posted October 17 Share Posted October 17 (edited) 21 hours ago, Nagev said: Hey again, didn't feel right to leave you guys with this issue over the weekend so I found a workaround. Made an improvement to the Clear Update extension which will help in this instance. 1. Please ensure you've downloaded version 1.0.3 of the Clear Update extension. (The update should become available within the next 15-20 minutes) 2. Choose to ignore the update for the mods you've confirmed are having this issue, and wait for the version column to clear up. 3. Once you confirm that the columns have cleared correctly, run the full update check. 4. You're done. Thank you. That did the trick for me this time and worked out. I will check again with beta 4 to ensure it is still working as expected. Edited October 17 by Kilo64 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now