Jump to content

Photo

Mod can be updated (but it hasn't changed and can't be updated) 1.2.20/19


Best Answer Tannin42 , 28 July 2020 - 10:19 AM

Update: you can fix this without reinstalling mods:

- Wait at least one hour after you did your last "check for updates"

- Click the little arrow down to the right of "Check for Updates" and in the menu that opens click "Check for Updates (Full)"

 

This check will take longer than the usual update check but it should clear out the incorrect cached data.

If you accidentally clicked the big update button or "Check for Updates (Optimized)" you have to wait for another hour. This wait is because Vortex won't check any mod more than once per hour to avoid using up the limited number of api requests you can make.

Go to the full post »


  • Please log in to reply
15 replies to this topic

#1
Ratziel

Ratziel

    Newbie

  • Premium Member
  • 16 posts

Issue occurred in 1.2.19, persists in 1.2.20

 

I'm using Vortex to manage mods for Fallout 4 with 70 active mods. Windows 10 Pro x64 32GB RAM

All mods have been installed directly via Vortex besides bodyslide.

Three mods have had nif files tweaked for bugfixing, those changes were previously detected by vortex and confirmed. Two are affected by this issue, one isn't.

 

I started Vortex after not using it for a week, and the first thing I did was hit 'check for updates' The search returned available updates for many (although not all) of my mods. Before the search was complete I also got a notification that v 1.2.20 was available.

 

When attempting to update a mod, i get two red errors "Download Failed" and "Unknown Download"

The mod(s) still exist(s) on Vortex, and on closer inspection are all on the same version I currently have installed.

 

I restarted vortex and allowed it to update to 1.2.20, the error persisted, I manually reinstalled a handful of mods, which worked, but re-running the update check still erroneously identifies a new version available (which can't be downloaded)

 

Affected mods are in multiple categories, no category seems to exclusively exhibit the bug.

 

The game itself is unaffected, and all mods load correctly. The impact is limited to not being able to easily tell if and when a mod actually is updated.

 

More Complete log available on request, but a handful of log entries related to the update check are as follows:

 

 

Mon, 27 Jul 2020 14:48:51 GMT - info: [update check] Mod update detected modId=0.3 - Patch Job-1934-0-3, lastUpdateTime=0, before.newestVersion=0.3, before.newestFileId=5988, after.newestVersion=0.1, after.newestFileId=unknown
Mon, 27 Jul 2020 14:48:51 GMT - info: [update check] Mod update detected modId=A. Commonwealth Shorts Vanilla-7898-2-0, lastUpdateTime=0, before.newestVersion=2.0, before.newestFileId=39368, after.newestVersion=undefined, after.newestFileId=undefined
Mon, 27 Jul 2020 14:48:51 GMT - info: [update check] Mod update detected modId=Anti Power Armor Gun v1.1-14623-1-1, lastUpdateTime=0, before.newestVersion=1.1, before.newestFileId=58066, after.newestVersion=1.1, after.newestFileId=0
Mon, 27 Jul 2020 14:48:51 GMT - info: [update check] Mod update detected modId=ArchGrassSkirt.rar-28158-1-3, lastUpdateTime=0, before.newestVersion=1.3, before.newestFileId=115619, after.newestVersion=1.3, after.newestFileId=1
Mon, 27 Jul 2020 14:48:52 GMT - info: [update check] Mod update detected modId=Workshop_Planters_Fixed-1490-1-0F, lastUpdateTime=0, before.newestVersion=1.0F, before.newestFileId=4186, after.newestVersion=1.0F, after.newestFileId=0
Mon, 27 Jul 2020 14:48:52 GMT - info: [update check] Mod update detected modId=hangmansalleypatch.esp-12958-1-0, lastUpdateTime=0, before.newestVersion=1.0, before.newestFileId=51168, after.newestVersion=1.0, after.newestFileId=0
Mon, 27 Jul 2020 14:48:52 GMT - info: [update check] Mod update detected modId=Workshop Spotlight Fix with DLC - All in One Installer-11090-v1-0DLC, lastUpdateTime=0, before.newestVersion=v1.0DLC, before.newestFileId=45919, after.newestVersion=v1.0, after.newestFileId=1
Mon, 27 Jul 2020 14:48:52 GMT - info: [update check] Mod update detected modId=Workshop Framework 1.0.8a - Reupload-35004-1-0-8a-1545852914, lastUpdateTime=1594934343829, before.newestVersion=2.0.1a, before.newestFileId=185898, after.newestVersion=1.0.8, after.newestFileId=unknown
Mon, 27 Jul 2020 14:48:52 GMT - info: [update check] Mod update detected modId=Wooden Prefabs Extended-10140-1-21, lastUpdateTime=0, before.newestVersion=1.21, before.newestFileId=51185, after.newestVersion=1.21, after.newestFileId=1
Mon, 27 Jul 2020 14:48:52 GMT - info: [update check] Mod update detected modId=TimerPowerSwitch-10750-1-00, lastUpdateTime=0, before.newestVersion=1.00, before.newestFileId=42413, after.newestVersion=undefined, after.newestFileId=undefined
Mon, 27 Jul 2020 14:48:52 GMT - info: [update check] Mod update detected modId=Starlight Drive In Shutters-20385-1-0, lastUpdateTime=0, before.newestVersion=1.0, before.newestFileId=83432, after.newestVersion=1.0, after.newestFileId=0

Mon, 27 Jul 2020 14:48:52 GMT - info: [update check] Mod update detected modId=Solar Street Lamps-41372-1-4-1-1570237323, lastUpdateTime=0, before.newestVersion=1.9, before.newestFileId=180999, after.newestVersion=1.1, after.newestFileId=unknown

 

I'm no expert, but that "after.newestFileId=" value looks out of place, they're all like that. Looking at older log files they were always 5 digit numbers.

For example:

Fri, 26 Jun 2020 21:50:00 GMT - info: [update check] Mod update detected modId=Solar Street Lamps-41372-1-4-1-1570237323, lastUpdateTime=0, before.newestVersion=, before.newestFileId=168072, after.newestVersion=1.9, after.newestFileId=180999

 

 



#2
maczak

maczak

    Stranger

  • Members
  • Pip
  • 2 posts

I am having a similar problem.

 

Edit: After checking all my mods against Nexus I noticed that quite a few of them showed a red bar on the files tab saying that no files existed. I am wondering if this is a Nexus problem, not Vortex. I don't really use Reddit, but I will try to find the support Reddit for Nexus.

 

Edit #2: My bad I just realized that I'm not on Reddit. Doh!


Edited by maczak, 27 July 2020 - 04:38 PM.


#3
Vindaloojim

Vindaloojim

    Journeyman

  • Members
  • Pip
  • 22 posts

This is also happening to me. Vortex is telling me that there are updates for around 95% of my mods, when they are already at the current/ latest version.



#4
Beyound

Beyound

    Enthusiast

  • Premium Member
  • 221 posts

Yup, just checked for updates, almost every single mod (150+) i have says it has an update, when they don't.



#5
nt5raham

nt5raham

    Fan

  • Premium Member
  • 273 posts

v1.2.20, I didn't notice this in v1.2.19, but my last Optimized Check for Updates might have been v1.2.17 (I missed v1.2.18).  Skyrim SSE, Win10. Numerous false "Update available" flags, 79% of my mods (792/988).  I'm sure a few of them are legit (I've been procrastinating on the DynDOLOD Resources SE update), but I did not anticipate this many.  I have updated several mods this morning using v1.2.20 that were on my "to do" list from a previous Optimized Check, and they updated fine.  I have  not tried to update any since I did the Optimized Check and returned such a high percentage.

 

Here are two clear examples that I just downloaded within the past month.  Neither mod has been updated in over a year, and there is only one file for download:

 

 

Update:  Downloaded the DynDOLOD Resources SE update that had been flagged previously.  No problems updating it after the numerous false positives showed up.

 

Submitted a bug report via Vortex - thanks for the suggestion @rmm200.



#6
rmm200

rmm200

    Faithful poster

  • Members
  • PipPipPipPip
  • 1,990 posts

I hope at least one of you folks open an actual bug report through Vortex (Three dots, upper right).

That way it will both be noticed and get tracked.

Support forum is mostly for helping with user errors - and topics will age off and be forgotten.



#7
Ratziel

Ratziel

    Newbie

  • Premium Member
  • 16 posts

I hope at least one of you folks open an actual bug report through Vortex (Three dots, upper right).

That way it will both be noticed and get tracked.

Support forum is mostly for helping with user errors - and topics will age off and be forgotten.

Well I have, now I know about it.



#8
dreamhive

dreamhive

    Regular

  • Members
  • PipPip
  • 64 posts

Same thing's happening to me with the 1.2.20 update. This pretty much makes the check for updates function useless. I reported it through vortex.



#9
Pickysaurus

Pickysaurus

    Community Manager

  • Admin
  • 13,008 posts

There was a temporary problem with the API last night which caused all file IDs to be blanked out, this means Vortex would "see" an update even if there wasn't one. It has now been corrected, sorry about that!

 

As for a fix, if checking for updates again doesn't correct it, you can always reinstall the mod to clear the update status. 



#10
Vindaloojim

Vindaloojim

    Journeyman

  • Members
  • Pip
  • 22 posts

Checking for updates again didn't correct it for me. RIP.

Guess I gotta reinstall 100s of mods if I want to be alerted for updates again.






Page loaded in: 1.016 seconds