search

Nexus-Mods / Vortex

Vortex Development
GNU General Public License v3.0
927 stars 135 forks source link

Bug Report - Other: Vortex can't find DLC #8555

Closed VortexFeedback closed 3 years ago

VortexFeedback commented 3 years ago

Vortex Version: 1.3.22 Memory: 7.93 GB System: win32 x64 (10.0.17763) Vortex can't find Devil May Cry 5 Vergil DLC, when i try to install, it tells me "Vortex can't find the DLC". I tried searching manually but that doesn't work as well

Reported by: BATATASBONITAS

IDCs commented 3 years ago

Hey BATATASBONITAS, can you please send us your log files so we can investigate this further? You can use the "Attach File" dropdown button to tell Vortex to include its vortex logs automatically

VortexFeedback commented 3 years ago

Vortex Version: 1.3.22 Memory: 7.93 GB System: win32 x64 (10.0.17763) I'll sent the log

External file: tmp-17620XZCVHrzEp63b.7z

Reported by: BATATASBONITAS

VortexFeedback commented 3 years ago

Vortex Version: 1.3.22 Memory: 7.93 GB System: win32 x64 (10.0.17763) I'm sending all the logs

External file: tmp-1116qFTXGqQ9K3Fz.7z

Reported by: BATATASBONITAS

IDCs commented 3 years ago

Hi again BATATASBONITAS, first of all apologies for the late reply - secondly, please click the issue number to open your report in the github page as my response is quite long and you won't be able to see all of it due to a bug in the dialog that prevents you from scrolling inside Vortex. So lets recap; in the first instance of your error (and the first log you sent us) it appears that Vortex was unable to find the mod's file paths inside the DLC's archives. This can only happen due to the following reasons:

  1. You're using an additional modding tool, possibly Fluffy Manager 5000 which has already invalidated the file paths, which would cause Vortex to complain about those files being missing. (I don't think this is the case, but if you are using another mod manager - don't, choose one mod manager and only use that one)

  2. The DLC archive has been updated and the file paths are no longer present in the archive, which would mean that the mod is outdated and simply cannot be installed.

  3. Vortex had previously invalidated those file paths itself, but for some reason was interrupted when it attempted to write the invalidated data into its cache (this is likely to happen if you have Anti-Virus software installed which could interfere with file writing operations, or if you closed Vortex prematurely before it was able to write to file)

  4. You don't own the DLC, and therefore the DLC archive is missing which means you won't be able to install the mod (I'm assuming this is not the case)

In the last logs you sent us, it appears that the cache is indeed corrupted for some reason, which confirms that my 3rd point above is the root problem of the issues you're having. At this stage the only solution for this is to purge your mods inside Vortex (this may fail, if it does just close Vortex) and close Vortex before doing a full re-installation of Devil May Cry 5 (erasing any traces that Vortex may have left behind).

Once that's done, please go to your staging folder which is located inside your "C:\Users\Windows\AppData\Roaming\Vortex\devilmaycry5\mods" folder and delete the "invalcache.json" and "invalcache.file" files in there (if they're present)

You should now be able to start up Vortex and deploy your mods directly, if for any reason you encounter the External changes dialog, always select to revert any changes made and KEEP the files in your staging folder.

Because of certain flaws in the older versions of these extensions in 1.3.22 and below, I would suggest updating to the 1.4.2 beta which should offer improved error handling and hopefully ensure this corruption never happens again. To download and install the beta go to the Settings page -> Vortex tab -> Update dropdown button -> Select Beta image

Unfortunately RE2 and DMC5 are extremely complex to mod which can cause a lot of misery when Vortex is blocked or fails to execute part of the process; especially since when something does go wrong, the only solution is to completely re-install the game which is quite massive disk space wise. I'm going to leave this issue open for a little while longer waiting for your feedback but given that there isn't much we can do given the cache's current state, I may close this soon.

IDCs commented 3 years ago

Hi again BATATASBONITAS - our updates to the RE2 and DMC5 are now live in 1.4.8 and above - hopefully any issues you previously had have now been resolved - going to close this issue as the functionality that does the invalidation is quite different in the new version, so this particular bug report would no longer apply. If you're still seeing issues after updating to 1.4.8 - please re-submit your bug report.