ElainCorrine

It's been that way since it was installed 2 years ago. Vortex had no issues seeing games on C or A, and ran just fine. I recently re-installed Starfield because of that, went looking for the mods I had used before only to discover Vortex no longer see's Starfield at all, and Starfield is installed on the C drive, along with Vortex. BG3 is on A, HZD and HFW are on C as well. Even after a full removal and clean install, Vortex just isn't seeing any games on C, but it has no problem seeing BG3 on A, though when I originally installed BG3 it was on C. I removed it (BG3) and reinstalled it after a mod I tried to make for it fubared the game so bad it had to be redownloaded.... yeah.. it didn't end well lol. Just seems to me that Vortex is simply NOT scanning my computer like it is implied to do, to find games installed on it, and w/o the ability to do a manual scan, I can't seem to find any way to get Vortex to find or recognize my games. It's frustrating to say the least. I mean, I can manually install the mods for Starfield, but I'd prefer to one click and go. I'll manually mod it if I have to though. Just hoping someone else may have experienced this and could whisper their voodoo in my ear.

LOL no, I renamed it to A from D or whatever it was when I did it.

Ok so I have 2 SSD's I have games installed on. Steam is installed on the A drive, some steam games are installed on the C drive, Starfield being one of them. However, NONE of my games (except BG3) are being detected by Vortex (and they used to be detected). I've done a full removal of Vortex, including deleting all Blacktree Gaming and Vortex folders, deleting the %appdata% stuff etc, then rebooted my computer and did a fresh clean install of Vortex. Problem is Vortex says it only supports 83 games and none of my games are in that list except BG3, which is installed on the A drive. Starfield, on the C drive, as well as 2 other games that vortex (Horizon Zero Dawn and HFW) supports, are simply NOT being shown as available to manage by Vortex. It's literally like vortex simply didn't scan my drives for games (which is why removing the scan tool is fubar). Any advice/help here? I'd love to mod starfield using vortex, but if I have too, I'll do it manually, I'd just prefer not to have to do that much work for the stuff I want to install into Starfield.

Yep, that seems to have fixed it. Thank you for taking the time to respond. I tried everything on my end to figure it out and was just left scratching my head. I know you folks are busy, got lives of your own etc, so patience is always my first go to when asking for tech support. Ya'll rock with all you do, and I def ain't looking a gift horse in the mouth and not being appreciative of your hard work. Stay Frosty! :-) ECM

Vortex 1.9.5 Baldurs Gate 3 via Steam Mods: Mod Fixer, Tutorial Chest Summoning w/script extender, BG3 script extender (latest), LSLib/Divine Tool Since the last BG3 update I have been getting that message in the title, and when I click More: it tells me Cannot read properties of undefined (reading 'id') The show details shows this: TypeError: Cannot read properties of undefined (reading 'id') at C:\Users\Me\AppData\Roaming\Vortex\plugins\Vortex Extension Update - Baldur's Gate 3 v1.3.7\loadOrder.js:122:36 at Array.forEach (<anonymous>) at C:\Users\Me\AppData\Roaming\Vortex\plugins\Vortex Extension Update - Baldur's Gate 3 v1.3.7\loadOrder.js:119:23 at Generator.next (<anonymous>) at fulfilled (C:\Users\Me\AppData\Roaming\Vortex\plugins\Vortex Extension Update - Baldur's Gate 3 v1.3.7\loadOrder.js:28:58) 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:547:31) at Promise._settlePromise (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:604:18) at Promise._settlePromise0 (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:649:10) at Promise._settlePromises (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:729:18) at _drainQueueStep (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:93:12) at _drainQueue (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:86:9) at Async._drainQueues (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:102:5) at Async.drainQueues (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:15:14) I've been pulling my hair out trying to figure out why this is happening. I've even gone so far as to reduce my mods to Mod Fixer, LSLib/Divine Tool. BG3 script extender, and Tutorial Chest Summoning. But even with just that running I still get the error message, and no mod seems to actually run.