Jump to content

Ratziel

Premium Member
  • Posts

    2
  • Joined

  • Last visited

Nexus Mods Profile

About Ratziel

Profile Fields

  • Country
    United Kingdom

Ratziel's Achievements

Newbie

Newbie (1/14)

  • First Post
  • Conversation Starter
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

0

Reputation

  1. 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: 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:
×
×
  • Create New...