Please advise: issues upon reinstallation (and mods reinstall) on a new PC

[Egir]

The main issue is, specifically, 3d models (as well as, possibly, textures) for some mods not loading at all. (And before responding, please read the disclaimers in the end, as it seems a rather specific iteration of an otherwise frequent problem.)

My old PC ('old' as in, I bought a new one three days ago) run Windows 7 with a GeForce GTX 760, and the relevant mod-cons of the time relevant to this set up. A solid build for Fallout 4, and generally had no issues at all running it with the mods I wanted.

My new PC is a more modern beast, running the AMD RX 7900 XTX, with all one would expect to see built around this. Clean install of Fallout 4, everything works top notch mechanically, but my mods are glitching out.

Issue 1

This is 'the odd one out': a shortkey for the building manager has stopped working. (I could activate anywhere in my settlements by pressing and holding 'V'.) For the life of me, I cannot remember whether this shortkey came with a mod, or was vanilla, but it does not work. Not a huge issue, but maybe indicative of the broader problem.

Issue 2

Now, the main issue is 'invisible stuff'. I have seen reference to invisible modded weapons (particularly from replacer mods). I don't use replacer mods, the weapons in question are all 'added'. But the issue touches also on clothing (headgear especially), as well as decorations (like posters and rugs).

Two further points. When in comes to the weapons, both sounds and animations are present, but 3d models & textures do not load. In all the cases (weapons, clothing, decor), everything is 'present' in the game, i.e. the weapon names and clothing show in inventory and crafting lists, the rugs and posters show in their building roasters, but the models do not load.


A couple of important notes, to save time, and anticipate the most basic advice:

(1) Yes, Vortex is up to date;
(2) No, the issue is not corrupted files, I did a clean install of everything, and exactly the same things were installed, same mods, same versions, and all was tripple-checked;
(3) Everything worked without a glitch on my old PC, everything loaded properly, and showed as it should. However, I did do a clean install of everything on the new rig.
(4) Yes, mods are installed on the same drive as the game.

Please help, if you have a solution.

[id795078477]

The most obvious thing is to try a clean unmodded install to see if graphical issue persists. If it does - then the root of the problem is in the rig setup (i.e. drivers, configs and what have you). If it doesn't - then it's the mods, so then you're in for a wonderful journey of removing them one by one to see what causes the issue; once that mod(s) was found - either removing it or trying to make it work (likely by asking the mod author(s) or skimming through logs in the hope to make sense of them)

Either way, I doubt anyone will be able to give you a solution on a silver platter. As with everything modding-related, you'd need to put in some work to make it work. Although maybe you get lucky and someone with precisely the same issue and a similar setup turns up and tells you what they did - and that also works for you.

[sdack]

What about the update? Was the old game updated and if not, did you avoid installing the updated game but rolled it back to the old version?

Also, did you do a clean reinstallation, meaning, did you wipe all the directories manually, or did you copy the files over?

[Egir]

Originally posted by sdack:

What about the update? Was the old game updated and if not, did you avoid installing the updated game but rolled it back to the old version?

Also, did you do a clean reinstallation, meaning, did you wipe all the directories manually, or did you copy the files over?

Ah, yes, the update. Was playing on my old PC post-update. And had specifically avoided mods which people were mentioning as not working well with it.

Clean reinstallation of the mods. Manually..? In a way. When uninstalling on Vortex, you can tell it to delete everything, the mod and its archive. I did that.

[Egir]

Originally posted by id795078477:

The most obvious thing is to try a clean unmodded install to see if graphical issue persists. If it does - then the root of the problem is in the rig setup (i.e. drivers, configs and what have you). If it doesn't - then it's the mods, so then you're in for a wonderful journey of removing them one by one to see what causes the issue; once that mod(s) was found - either removing it or trying to make it work (likely by asking the mod author(s) or skimming through logs in the hope to make sense of them)

Either way, I doubt anyone will be able to give you a solution on a silver platter. As with everything modding-related, you'd need to put in some work to make it work. Although maybe you get lucky and someone with precisely the same issue and a similar setup turns up and tells you what they did - and that also works for you.

I think this is quite sensible. So, you are saying it might be that something with the game itself could be corrupted? Haven't thought of that, since I did do a clean install.

I am less suspicious of the mods at this point, because everything is present and in its expected place, it just doesn't download some of models and textures, while loading others with no problem. (This is a significant point, because all mods are installed in the same place, so it is not a matter of location.)

I'll uninstall everything on Vortex, and reinstall the game itself. I'll be back in a bit.

[id795078477]

Originally posted by Egir:

Originally posted by id795078477:

The most obvious thing is to try a clean unmodded install to see if graphical issue persists. If it does - then the root of the problem is in the rig setup (i.e. drivers, configs and what have you). If it doesn't - then it's the mods, so then you're in for a wonderful journey of removing them one by one to see what causes the issue; once that mod(s) was found - either removing it or trying to make it work (likely by asking the mod author(s) or skimming through logs in the hope to make sense of them)

Either way, I doubt anyone will be able to give you a solution on a silver platter. As with everything modding-related, you'd need to put in some work to make it work. Although maybe you get lucky and someone with precisely the same issue and a similar setup turns up and tells you what they did - and that also works for you.

I think this is quite sensible. So, you are saying it might be that something with the game itself could be corrupted? Haven't thought of that, since I did do a clean install.

I am less suspicious of the mods at this point, because everything is present and in its expected place, it just doesn't download some of models and textures, while loading others with no problem. (This is a significant point, because all mods are installed in the same place, so it is not a matter of location.)

I'll uninstall everything on Vortex, and reinstall the game itself. I'll be back in a bit.

Well it's a Bethesda game. Even unmodded it might refuse to work properly on some rigs, it's a known issue. So vetting your foundation itself would be a good idea. At least you'll be able to answer the question "is it the mods issue or is it the game itself"

[X]

Vortex sometimes don't load all files that are needed for mods.

Have you ever thought about using MO2?

You should be using Windows 11 now did you install Steam out side of windows controlled area?

Did you have your game updated to the next gen on your old computer?

Downloading now the next gen update is included and a lot of mods have not been updated yet.

[sdack]

Originally posted by Egir:

Originally posted by sdack:

What about the update? Was the old game updated and if not, did you avoid installing the updated game but rolled it back to the old version?

Also, did you do a clean reinstallation, meaning, did you wipe all the directories manually, or did you copy the files over?

Ah, yes, the update. Was playing on my old PC post-update. And had specifically avoided mods which people were mentioning as not working well with it.

Clean reinstallation of the mods. Manually..? In a way. When uninstalling on Vortex, you can tell it to delete everything, the mod and its archive. I did that.

You did not answer my question.

Did you copy the game files over or not?

See here under "Reinstallation Checklist":
https://steamcommunity.com/sharedfiles/filedetails/?id=3241230342

[Egir]

Originally posted by sdack:

Originally posted by Egir:

Ah, yes, the update. Was playing on my old PC post-update. And had specifically avoided mods which people were mentioning as not working well with it.

Clean reinstallation of the mods. Manually..? In a way. When uninstalling on Vortex, you can tell it to delete everything, the mod and its archive. I did that.

You did not answer my question.

Did you copy the game files over or not?

See here under "Reinstallation Checklist":
https://steamcommunity.com/sharedfiles/filedetails/?id=3241230342

Well no, I did not follow that guide (yet), because I am only now re-installing the main game. The first install on the new PC was the first install, so there was nothing to delete, manually or otherwise, nor did I copy anything over at the time.

To reiterate (unless I'm missing something, sorry it has been a long day): new PC - installed Steam, made a new game installation - new Vortex installation - new mods installation through Vortex - some tweaking of the Graphics panel, and off I went and encountered the issues I mentioned.

Then, was fiddling with the mods, not the main game. Then, I came here with my questions above.

Thank you for the link! While I did do some things intuitively (like forcing the frame rate on AMD Adrenaline) there are other things I wouldn't have thought to do. So, now that I will be reinstalling afresh, I'll be sure to follow this checklist and wipe everything before reinstalling.

[sdack]

Make sure not to only install the old mods, but also to keep their old load order intact.

If you still have access to the old computer then check in AppData\LocalFallout4\loadorder.txt if it matches the new load order.

[Nitemares]

sdack's guide is a great place to start.

The "V" hotkey is a standard feature of fallout 4. So if that hotkey is not working, its either being over-ridden by a mod, or you have a corrupted install (Yes, it can happen even on a fresh install... thank your connection and packet transfers)

Also, I have a feeling you made a classic mistake
I have a feeling you tried to use your modlist from your old rig on the fresh install on the new rig, Am I right?

If you did, I think you forgot about the NG update that came out 2 months back. and that some mods are not updated to the NG library, and can create all sorts of issues.

Any mod that uses a DLL file most likely needs to be updated, this includes weapon and armour mods that use "injectors" to add them to merchants, npcs and whatnot... And can even include craftables in settlements -depending on how the mod creator went about adding the items.

Once you get the base game running and tested that things are working... You are going to have to go through your mod-list slowly to make sure that they are NG compliant, Easy way to do that is read the posts for the mod.. if its not working, there will be posts about it...

Keep in mind too, not all mods need to be updated, and some mods are abandoned, meaning they will never get an update

[Egir]

Originally posted by Nitemares:

sdack's guide is a great place to start.

The "V" hotkey is a standard feature of fallout 4. So if that hotkey is not working, its either being over-ridden by a mod, or you have a corrupted install (Yes, it can happen even on a fresh install... thank your connection and packet transfers)

Also, I have a feeling you made a classic mistake
I have a feeling you tried to use your modlist from your old rig on the fresh install on the new rig, Am I right?

If you did, I think you forgot about the NG update that came out 2 months back. and that some mods are not updated to the NG library, and can create all sorts of issues....

No, not quite.

I do have access to the old PC, it is sitting on a smaller table next to my desk, temporarily, while I finish setting up everything.

So, what I did was kill the internet on that (so that I don't get any changes), and then opened Vortex, and looking at that, downloaded the exact same mods, the exact same versions, from the nexus. As they installed on Vortex, they installed in the exact same way (and, I am assuming, though, as per sduck's suggestion I will double-check, Vortext loaded them in the same order. With Vortex this stuff is automatic, I believe.

I did not copy the files from the old and pasted them in the new. (I made that mistake with XCOM 2, though there it is easier to deal with, you just verify integrity, and then reedit the mods' inis as needed.)

Re. the Update, that hit us about a month ago, if not longer. I was playing with my mods on the old rig withough an issue three days ago.

Now, of course, the update might be having a different effect on Windows 10, so that I can (still) play on my old PC (WIn 7), but not on the new PC (Win 10), even though I have the exact same everything. Which is where the suggestion about compatibility mode might help.

Anyway, I need to take it all in now, and do all the checking.


Is anyone making a workaround that fixes the chaos of the Update, by the way? E.g., a fix that rolls it back, or something? The whole idea of next-gen is mildly ridiculous in a game so extensively modded, because the game does not even handle mode than 60 frames decently.

[Nitemares]

There are several "roll-back" methods out there from the manual way, to mods that make it practically automatic. just search Nexus for "down grader" or the like and they should pop right up.

I did it manually, mostly because I keep a back-up copy of all Bethesda games for this exact reason and I have the storage space to do so.

Did you update your old rigs Fallout 4 to the NG update, or did you have it on "update on launch" and then used F4SE shortcut to launch the game?


The reason I ask, and keep pushing this is because I really feel you have a version mismatch between your fallout 4 and the mods. And using the same mods, but on different fallout 4 versions would explain that.

But I could be wrong.