Upgrading from 0.13.5 to 0.14 caused dependency issues (same as 0.13.6)

[leifyjai]

This is just a heads up, I posted a while back about having problems upgrading from 0.13.5 to 0.13.6, which introduced a ton of "dependency issues" which didn't exist when running 0.13.5, so I reverted and have been using 0.13.5 until this recent 0.14 release.

 

Well upgrading to 0.14 from 0.13.5 results in the same flood of "dependency issues". I checked and some (a lot, but not all) of my mods had all of their dependency rules wiped ( all conflicts set to "no rule"). So that is causing the dependency issues. Strangely, when I re-install 0.13.5, all of my dependency rules are restored and the problem goes away.

 

I sent feedback from Vortex (while running 0.14), and attached my Application State. Hope this helps. Please let me know if there is a solution to this, as I don't want to either be stuck running 0,13.5, nor manually going through and re-establishing hundreds of dependency rules after letting 0.14 wipe them.

 

Any help appreciated.

 

[leifyjai]

*bump*

 

Seriously, am I the only one experiencing this problem?

 

I just tried 14.1 and got the same problem, yet reinstalling 13.5 always results in my dependency rules going back to normal. Could someone please chime in? Did the rest of you just go back and, one by one, re-define all your dependencies?

 

 

EDIT:

 

Ok, well after some experimenting around, and getting the latest version of Vortex to flat-out crash while trying to activate the "problem" game, I have determined that my Oblivion build is the only thing that is affected by this problem.

 

I also have a heavily modded Skyrim build, which does not have this dependency issue. The crash I got was after switching to Skyrim SE while using Vortex 0.13.5, then quitting and upgrading to Vortex 0.14.1, then running Vortex with Skyrim SE active, and then trying to activate my Oblivion game. Vortex 14.1 completely choked and gave me a pop-up window with a bunch of error information relating to trying to load a database. Unfortunately, though I did report the crash, hitting the report button also closed Vortex before I got a chance to copy and paste any of the error information.

 

So it looks like I have a screwed up Oblivion build, which is only compatible with Vortex 13.5 or earlier.

 

Anyone know how to troubleshoot/repair (or even locate!) the "database" information that Vortex stores for each game?

 

EDIT2:

 

Ok, I found the log file in Appdata/roaming/vortex, and it looks like 14.1 choked on my loadorder.txt file, but I couldn't re-create the crash, and Oblivion still only has (all) its dependency rules when running 0.13.5 or earlier. Here is what I found in the logfile:

 

Mon, 09 Apr 2018 22:04:54 GMT - debug: deserialize format=original, pluginsFile=C:\Users\LeifyJ\AppData\Local\oblivion\plugins.txt, loadOrderFile=C:\Users\LeifyJ\AppData\Local\oblivion\loadorder.txt

Mon, 09 Apr 2018 22:04:54 GMT - error: unrecoverable error message=Database is not open, stack=ReadError: Database is not open

at maybeError (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\modmeta-db\node_modules\levelup\lib\levelup.js:165:23)

at LevelUP.put (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\modmeta-db\node_modules\levelup\lib\levelup.js:225:7)

at LevelUP.promisified [as putAsync] (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promisify.js:223:16)

at ModDB.insert (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\modmeta-db\lib\moddb.js:91:25)

at getAllByKey.tap.result (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\modmeta-db\lib\moddb.js:119:26)

at PassThroughHandlerContext.finallyHandler (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\finally.js:57:23)

at PassThroughHandlerContext.tryCatcher (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\util.js:16:23)

at Promise._settlePromiseFromHandler (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:512:31)

at Promise._settlePromise (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:569:18)

at Promise._settlePromise0 (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:614:10)

at Promise._settlePromises (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:693:18)

at Async._drainQueue (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:133:16)

at Async._drainQueues (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:143:10)

at Async.drainQueues (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:17:14)

at <anonymous>

at process._tickCallback (internal/process/next_tick.js:188:7)

[Pyro2677]

Not alone, when i updated from 13.5 - 13.6 my dependencies came up with red lightning bolts. If i had the rule set on 1 mod then the other mod came up red saying i had to make the rule a second time. Tannin said it should only need to be done once and now when i install a mod it lets me use the load after and I don't need to go to the other mod and create a load before exception.

[leifyjai]

Thanks for the response Pryo2677, nice to know (I mean, sorry you're having problems, but nice to know it's not just some stupid thing I'm doing wrong or something.)

 

I tried activating a blank profile for the problem game, Oblivion, then activating a different game, Skyrim SE, and then updating to 0.14.1, then re-enabling Oblivion and re-enabling my heavily modded profile to see if that helped. It didn't.

 

So I bit the bullet and tried to start re-entering the rules. (I notice that a bunch of the missing rules are relating to the Unofficial Oblivion Patch) Anyway, I went to change the first of many, setting the mod to load "after" the patch, then I started getting an infinite stack of errors showing up in the notification area, all stating: "An error occurred looking up the mod"

 

When I hit "more" to look at the text of the error, I got a system message box stating:

An unrecoverable error occured

 

read ECONNRESET

 

Error: read ECONNRESET

at exports._errnoException (util.js:1024:11)

at TSWrap.onread (net.js:610:25)

 

the text of the "infinite" number of mod-lookup errors was as follows:

Error: Cannot read property 'endorse_status' of undefined (undefined, undefined)

at errorFromNexus (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\extensions\nexus_integration\util\checkModsVersion.js:91:16)

at Promise.resolve.then.catch (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\extensions\nexus_integration\util\checkModsVersion.js:104:85)

at tryCatcher (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\util.js:16:23)

at Promise._settlePromiseFromHandler (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:512:31)

at Promise._settlePromise (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:569:18)

at Promise._settlePromise0 (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:614:10)

at Promise._settlePromises (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:689:18)

at Async._drainQueue (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:133:16)

at Async._drainQueues (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:143:10)

at Async.drainQueues (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:17:14)

at <anonymous>

Fun stuff!!!

[SkunkMonkey]

I've gotten the failed mod lookup error message spam as well. I think what happens is something fails when Vortex starts checking mods for the endorsement status from the Nexus which causes all calls for that feature to fail, so you get a message for *every* plugin. I've usually just exited and restarted Vortex to stop and clear it. I don't think it's anything to worry about on our end, they just need to catch the error and handle it more gracefully.

[sopmac45]

Well, I do not know if my issue is within the scope of this particular thread and I do not know if my issue is related to the previous or last Vortex update but here I go :

 

> Some plugins are showing dependencies from mods/plugins that not longer exist in my load order ... AND ... I have started Skyrim 3 times already from scratch and also, I uninstalled Vortex one time and re-installed it again, so I do not understand why in Oblivion I am showing dependencies ( in my Plugins ) from mods already gone from my load order.

 

I am able to move those plugins to where I want, but why they are showing those dependencies though ?

 

Also, why when I have restarted a new game from scratch, Vortex is still showing under Manage Dependencies ( in the Plugin window ) all my dependencies from the previous game that was already wiped out as I said ( obviously and all mods, plugins and saved games .... ) ?

 

Have someone noticed that or is just happening to me ( which I doubt ) .... ?

 

I perfectly understand that Vortex is in Alpha state but this is not the first time I've mentioned this and still has not been addressed. I also understand that my issue is not just the only one and I could wait as long as it takes for them to be fixed but what I would like to know is if there is anyway that I can do something to eliminate that problem ? Should I delete something in Vortex or reset something so I can have my plugins ... like Madonna says in her song : "like a virgin, touched for the very first time" .... lalalalala ... lol ... please help !

 

:laugh:

[Pyro2677]

Yeah not sure why you're having such a bad time with Vortex. Mine updated from 13.6 to 14.0 and I had no idea it had updated. Nothing had changed and all was working as it should. Updated to 14.1 and same it just worked. Still the updating of mods is a pain in the arse but I'm just dealing with it.

 

I've installed mine in the default location and have my games on a different drive and set Vortex to run as administrator. Every now and then I'll get the error messages like maybe 1 or 2 times in a couple of weeks. I just close and open Vortex and deploy mods or purge then deploy again and everything works ok. Not sure it that helps but that's how mine is set up.

[AugustaCalidia]

Today I upgraded to 0.14.1 from 0.13.5. There were a few hiccups along the way, but I now have everything working properly, and I am pleased with the upgrade.

 

The first hiccup had to do with activating my games. When I started Vortex after the upgrade, I was immediately presented with the dashboard for Fallout 3, which was the game I had been playing when I upgraded. So far, so good. I then tried to activate Skyrim SE, and Vortex balked. After it performed its initial check for Skyrim SE, it then hung when attempting to sort mods. I closed Vortex, reinstalled 0.13.5, re-started Vortex, and activated Skyrim SE. Next I closed Vortex and installed 0.14.1 for a second time. I then re-started Vortex, and it opened with Skyrim SE, which is where I had previously left it. So far, so good. (Does anyone reading this remember those Bruma guards in Oblivion who kept saying, "So far, so good"?) Then I reactivated Fallout 3, and that went smoothly, So far, so good. Finally I tried to activate Fallout 4, but once again Vortex balked. Instead of reinstalling 0.13.5, I simply let Vortex struggle for a few minutes in an attempt to activate Fallout 4. No success. I decided to leave everything alone for a while. After about 45 minutes I returned to Vortex, and it immediately activated Fallout 4. Now I have no activation issues with 0.14.1. Why it behaved this way, I have no idea. I'm just glad it works.

 

The second hiccup had to do with dependency rules. While stumbling around with the first hiccup, I discovered that the 0.14.1 upgrade did not save and/or recognize all of my original dependency rules. However, 0.14.1 did recognize most of them, unlike 0.13.6, which spewed red thunderbolts everywhere. Fallout 3 had the most red thunderbolts (I didn't count them), Skyrim SE had only one, and Fallout 4 (in two profiles) had none. While I was disappointed that the upgrade did not preserve all of my previous rules, I was delighted that the "save" button worked, which was not the case with 0.13.6. It only took me a few minutes to set up the missing rules.

 

When encountering problems such as these, I always view them as a learning opportunity. In this case I learned (duh! and palm to the head) that if I set a before or after rule in one mod, in most cases I don't have to set a corresponding rule in a second mod. And I even discovered that Vortex will show me that!

 

To sum up, I did have some problems with the upgrade, but I view them as minor. I am very happy that I made the change.