New beta shows spurious updates

[dizietemblesssma]

The recent 1.13 beta shows new updates for all my games - Bethesda games plus witcher3.  They are all marked with the symbol for needing to go to the nexus page to choose the update.  They are not updates, often but not always the mods are years old.

When I updated to the beta it told me it was a downgrade from 1.12.6, which doesn't make sense since I've always been on the beta channel all through the 1.12 series and earlier and 1.13 is later than 1.12

 

diziet

[Pickysaurus]

Sounds like you might've checked for updates during a network error and Vortex got confused. You can reset the mod rows with this extension https://www.nexusmods.com/site/mods/171

[Petty7]

Using Vortex 1.13.0-BETA.2 here and I have the exact same issue as dizietemblesssma described. I checked for updates on my over 1000 mods Skyrim SE game and surprisingly over 200 mods were erroneously marked as "Mod can be updated" when they are up to date.

I tested the Clear Update extension on an affected mod and indeed it removed the mark but when I manually right click on it and select Check for Update the mark is back again, so that's not a solution.

My internet is working good but today I noticed that the download speed from nexus is unusually slow.

I hope this can be fixed because it's a big problem when updating the mods.

Edited October 9 by Petty7

[ChemBoy1]

Can confirm this is happening for me as well on 1.13.0-Beta.2. 

[Kilo64]

I can also confirm that using Beta.1 and Beta.2, random mods for my FNV and FO4 showed as needing updates.  These were mods showed as 'pick the file yourself' for an update in Vortex when no actual update exists.

[Nagev]

Hey there,

We made a few improvements to the update code to better handle version comparisons for mods that do not use semantic versioning (i.e. Major.Minor.Patch pattern), while also improved update chain inference if/when a mod author archives their main mod file and fails to highlight the _new_ main file as an update to the older one (which practically creates a schism in the update chain)

Can you guys send us a few urls for the affected mods so we can debug this behaviour. Also specify which mod version you are on, and whether you sourced that specific mod through a collection or just manually.

[Kilo64]

36 minutes ago, Nagev said:

Hey there,

We made a few improvements to the update code to better handle version comparisons for mods that do not use semantic versioning (i.e. Major.Minor.Patch pattern), while also improved update chain inference if/when a mod author archives their main mod file and fails to highlight the _new_ main file as an update to the older one (which practically creates a schism in the update chain)

Can you guys send us a few urls for the affected mods so we can debug this behaviour. Also specify which mod version you are on, and whether you sourced that specific mod through a collection or just manually.

Here are some of the mods that say they need an update for FO4/FNV for me along with the version I have installed and what Vortex thinks needs to be updated (these are always the same).  These are sourced manually.

New Vegas

https://www.nexusmods.com/newvegas/mods/89032 - 1.01

https://www.nexusmods.com/newvegas/mods/77205 - 1.0

https://www.nexusmods.com/newvegas/mods/86605 - 1.3

Fallout 4

https://www.nexusmods.com/fallout4/mods/29735 - 1.1

https://www.nexusmods.com/fallout4/mods/62518 - 1.1

https://www.nexusmods.com/fallout4/mods/16304 - 1.03

Edited October 10 by Kilo64

[Nagev]

Thanks for that, looks like it's the non-semantic version comparison improvement - will have a look and let you guys know once we fix it.

[Petty7]

Here are a few more:

https://www.nexusmods.com/skyrimspecialedition/mods/122660 -> 2
https://www.nexusmods.com/skyrimspecialedition/mods/103215 -> 1.10
https://www.nexusmods.com/skyrimspecialedition/mods/78159 -> v0.13.0.1
https://www.nexusmods.com/skyrimspecialedition/mods/110508 -> 1.0.2
https://www.nexusmods.com/skyrimspecialedition/mods/66915 -> 1.0.1
https://www.nexusmods.com/skyrimspecialedition/mods/14103 -> 1.1.0
https://www.nexusmods.com/skyrimspecialedition/mods/71516 -> 1.01
https://www.nexusmods.com/skyrimspecialedition/mods/44642 -> 1.0.0
https://www.nexusmods.com/skyrimspecialedition/mods/44914 -> 1.1.0
https://www.nexusmods.com/skyrimspecialedition/mods/128585 -> 1.01
https://www.nexusmods.com/skyrimspecialedition/mods/73437 -> 1.0.1
https://www.nexusmods.com/skyrimspecialedition/mods/92529 -> 1.0.0
https://www.nexusmods.com/skyrimspecialedition/mods/70992 -> 2.1.2
https://www.nexusmods.com/skyrimspecialedition/mods/129992 -> 1.1
https://www.nexusmods.com/skyrimspecialedition/mods/124787 -> 2.0
https://www.nexusmods.com/skyrimspecialedition/mods/70595 -> 2.0.1
https://www.nexusmods.com/skyrimspecialedition/mods/95269 -> 1.0
https://www.nexusmods.com/skyrimspecialedition/mods/61648 -> 1.1
https://www.nexusmods.com/skyrimspecialedition/mods/80271 -> 1.1

Edited October 10 by Petty7

[Nagev]

Hey all, thanks again for reporting this issue. Good news is - the bug has been fixed; bad news is we can't release anything on Thursdays as we can't provide support over the weekend. Beta.3 will be released early on Monday to fix this, in the meantime please just ignore any update notifications that point you to the website asking you to choose the update yourselves.