Getorex

Out of nowhere Vortex has started throwing out error messages to me telling me it cannot deploy mods. I check the messages and go with "fix" but Vortex is telling me the fix is to break the system: it is suggesting I move the staging folder to my drive K but my fallout 4 game is on drive L. My original staging folder was also always on drive L but now it wants me to move it to K, at the same time it says it must be on the same drive as the game! WTF? I have tried moving the staging folder to the suggested location on K and then moving it back to L but then the errors come back. If I try the game with the staging folder on K, naturally the mods fail because they are on the wrong drive. How do I fix this?

Does anyone have any information on whether or not current mods will be usable, or modifiable to work, with the upcoming Legendary Edition of Mass Effect? In particular, the Mass Effect 3 mods SHOULD be usable or easily adapted to be usable with the new release if they don't change the file formats and encoding methods. As I understand it, BIoware supposedly contacted some modders about incorporating their mods into the new release, so there is some possible communication between some modders and the company. So any information or knowledge about changes to the game setup and current mods?

I SEEM to have "fixed" the issue. I uninstalled Vortex, downloaded it again, then reinstalled it. Then Fallout 3 crashed shortly after I started it so another issue to deal with.

I can't find it in the dashboard. I had to stumble on having vortex install it, then I did it and installed it and...same thing. It's looking at G: when everything is on E: and I cannot find any way to fix this ONE issue, so I cannot start Fallout 3 via Vortex with all the mods because it refuses to see/user fose_loader in the actual game folder!

I have just reinstalled Fallout 3 GOTY via steam. I've downloaded and installed the mods I wanted (and used when I originally played it a couple years ago). When i try to start the game in Vortex, it tells me it needs to deploy some mods (fose loader) so I say OK and it fails. I have 5 harddrives in my computer. The game is on Drive E and Vortex downloads and installs the mods here but whenever I try to do the fose deploy to start the game, Vortex errors out telling me it cannot find the fose loader on drive G:(?!!) Why is it looking at the G: drive when everything is on the E: drive and it APPEARS it otherwise knows this? Where can I make a change to make it look at the correct game folder for fose_loader?

I'm in the middle of it, big time - cannot use terminals, work benches, cannot sit, cannot get out of power armor but can only get in. The only "fix" I've found online is to go back to a previous save from before the bug appeared. If you are at the start of the game then you are screwed, of course. I dread this fix as it will mean I have to go WAY back to near the start again because I'm about 1/3 of the way through the game as it is. No one seems to know for sure whether this bug is tied to any particular mod or mods but the general consensus is that disabling mods won't work. IF you have a mod that caused it, it requires REMOVAL, not just disabling. I have a lot of mods going (about 150) but none of them should affect things like terminals, getting in or out of power armor, or using work benches. IF your only problem is terminals not working, you can get around that with the Remote Terminal Hack mod. Instead of directly entering the terminal you stand in front of it and select remote hack instead and it will bring the terminal screen up on your Pipboy. Works for me with being unable to directly access terminals but it doesn't fix the other problems. I do wonder if the remote terminal hack could be modified to be a remote workbench hack so that you could bring up the work bench screen up on your Pipboy instead of the normal way... UPDATE: I just put it to the test. I went back to a different save from a different character. Same mods installed. In THIS game I can use terminals, workbenches, but won't test power armor because it's a real pain to use get out of the armor when this bug happens (some console commands that I will need to look up again).

Is there a tutorial or demo on how to extract character meshes from Andromeda with the Frosty Editor? In anticipation of SOMEDAY MAYBE being able to import meshes into the game, I'd like to extract Cora, a bunch of Asari, and the female krogans so I can fix them up (make Cora attractive and replace her man hair with something female), swap the Asari heads with those from ME1, 2, and 3, and feminize the female krogan to be like Eve in ME3 (instead of just male krogan with feminized voices). I've tried several times to extract Cora, body or head, for starters from the game but end up with nothing but empty fbx files. I'm not clear which of the many entries actually contains the skeletal meshes for characters. Hell, at this point I'd welcome a hex edit that swaps Cora for Suvi.