help - vortex deployed mods FO4 VR not present in game

[muskerp]

I had vortex and FO4VR running on the C drive of a PC (win 7) but then I added a new ssd drive with a new operating system Windows 10

 

The steam game files are still on the old drive which is now my E drive - in steam local files it shows as E:\Program Files (x86)\Steam\steamapps\common\Fallout 4 VR

 

Although the game plays fine via steam VR (except for some bugs) none of my mods were present when I played the game from my new Windows 10 boot.

 

I then installed Vortex v1.3.22 on the new windows drive here "C:\Program Files\Black Tree Gaming Ltd\Vortex\Vortex.exe"

 

I added mods in this new vortex instance (initially just a couple) but could not deploy. I changed the mod staging folder - I first tried to set it to the same as the old staging folder on E drive but could not set it to a folder that was not empty so I set it to E:\Users\Paul\AppData\Roaming\Vortex\fallout4vr_new instead.

 

Then I deployed and although the deployment appeared successful the mods are not present in the game. e.g. added jetfuel radio standalone and it does not appear in the list of radio stations.

 

The structure of the new staging folder looks very different to the old one.

 

The old staging directory had a set of folders - icons, masterlist, mods, profiles, snapshots while the new staging directory seems to only have the mods with none of the folder structures

 

I didn't see any errors when I deployed the mods and I don't see anything unexpected in the vortex log but the network.log shows numerous getFileByMD5 failures and getModInfo failures

 

 

Can you suggest what I can do to make the mods have an effect in the game.

 

Cheers

 

 

[HadToRegister]

Vortex info is stored in C:\USERS\YOUR NAME\appdata\roaming\vortex on the C:\drive,
now, according to you it's on your E:\ drive, but vortex expects to find it on the C:\ drive

All you had to do was copy the old folder from E:\ to C:\, that would've been the easy thing to do.

 

However, now there's a possibility that all of the paths are messed up now that you've run it once with the appdata folder on E