nguenht Posted March 15, 2022 Posted March 15, 2022 So I've decided to pick up Fallout 4 after taking a long break. Too lazy to install all the mods all over again, I decided to copy my whole game directory from the previous PC, including the load order. (Been using NMM at the time). Been modding my Fallout 4 with MO2 and everything seemed more or less fine, though there were some common modding-related issues on my end. One of them was the issue of MO2-bound Bodyslide not rendering textures for the body in preview, even though all the links seemed to be correct. I poked around and tried to launch the Bodyslide x64.exe in the Tools directory, without MO2. Bodyslide x64.exe launched directly showed proper textures, but the archives were old and didn't contain recent presets I installed. Also, the executable was from 2018. The one bound to MO2 is linked SOMEHOW to the same directory (as it turns out not really), shows recent presets BUT doesn't show textures. The executable is from 2022. Trying to figure out what was wrong, I carefully compared all the directory-related settings in both Programs opened at the same time (weirdly enough, task manager showed identical properties) and found out that both of these programs have the same directory BUT. One is situated in "Data\Tools" folder, while another shows "data\tools". Weird thing is that Windows Explorer shows only the capital directory, but if I try to browse the directory from Bodyslide, they show difference in directories, file size and count. What gives?!
nguenht Posted March 15, 2022 Author Posted March 15, 2022 One possible clue to this mind-boggling situation is that on my new PC the drive was initially under a letter Z. On my old PC the game was on drive D. When I initially downloaded the game from Steam, I might have still had my drive as Z, which I might have renamed after I found out the game won't work as it was at the time. So what happened was probably something along these lines: Drive Z: Install fallout Drive Z: dump old game folder onto new machine Drive Z: Game doesn't work, rename the drive to be D, reboot Drive D: Game works now, but there's a side-effect of a hidden directory running at the same time?????
belegost Posted March 17, 2022 Posted March 17, 2022 You know, I think it would've been much less hassle if you just installed everything from scratch using MO2... ...just saying.
nguenht Posted March 23, 2022 Author Posted March 23, 2022 On 3/17/2022 at 2:50 PM, belegost said: You know, I think it would've been much less hassle if you just installed everything from scratch using MO2... ...just saying. I figured out that the difference in directories is caused by MO2's virtual installation functionality (duh?). I'm not sure if this is the expected behaviour, with the game using half of the files from 2018, including cbbe textures, probably some leftover skeleton files, since I can't seem to apply a simple cbp to the game. Yeah, probably just gonna reinstall everything... Some time later though xD
Recommended Posts
Archived
This topic is now archived and is closed to further replies.