CIBtheGhost

Hello great citizens of Nexusmods forums, I've been having some issues with Fallout 4 crashing out right around the Win10 4GB limit that is usually saved for those special hours and hours of trying to get 32 bit applications working with 64 bit resources. I was using both ENBoost for memory management and ReShade for color correction and found it curious I was even hitting this limit. I was able to verify both dlls used by the overlay and memory manager were both 64 bit and the only other dll would be F4SE which couldn't possibly be 32 bit. But these are easy things to remove from the loop so I removed the ENBoost, ReShade, AND F4SE (while disabling the mods dependent), and still hit the 4048 MB VRAM wall. So I was stumped. Technically, I still am. I suspect it's a MOD someone made using 32 bit tools but I have no way to test this. Anyway, I started to scour the internet and then I ran into an article surrounding CUDA and VRAM limits in Windows 10 that just seems like pure amateur hour by Microsoft, but I digress. According to a post on some MS Tech Social site, CUDA programs automatically give up 1/8th of the system VRAM as unusable. That's 12.5% of your GPU and RAM. That seems like a ridiculous amount of VRAM to call unusable, especially if you're like me and have 2x11GB GTX 1080 TIs and 32 GB of RAM. I'm giving up ~6GB of non-swap VRAM to CUDA programs. Granted I don't even know if Fallout 4 is a CUDA program, but if it is, is there anyone who can validate this information? Also, given that I have several metric tons of VRAM, anyone have any ideas what could possibly be causing me to hit the old 32 bit VRAM wall? Hardware and software specs My load order sorted with LOOT Thanks for reading!

Yeah. It's lookin' like a purge is next steps. Not windows. But Steam and FO4 and NMM and all the mod packages. Not just an uninstall, but delete all with a flamethrower. Drivers are up to date. I think Steam is holding onto something it shouldn't and then dumping it into my game or I'm using a mod that somehow got changed when I looked up conflicts in F4Edit. Thanks for the suggestions though. Silver linings: I'm getting really comfortable with ALL the mod tools lol.

That's F4SE. The script extender. Entirely different mod to worry about lol. But.... you can fix it with some instructions from this guy who seems like he's pretty legit. And he fixed this same prob today. https://forums.nexusmods.com/index.php?/topic/6851497-another-script-extender-update/&do=findComment&comment=62180472

Lol yeah. Well, any more than a mouthful and you're risking a sprained tongue. It was said so it the OG of mod tales; the movie Weird Science from the year of our lord of mods 1985. It's like my building a better fantasy girlfriend bible. And I was literally a high school freshman in 1985, so it has some very intimately personal connections to me heh. Also, extra instructions on finding versions for future issues: https://steamcommunity.com/sharedfiles/filedetails/?id=1086279994

Sadly, it did not work. Ironically, NMM cleaned out all of Bethesda's crappy high def textures DLC lol. But got everything lined up in my ini files, game folders are clean, everything got re-installed. I even just used a "minimum to make my character" mod load and the hands textures were black and white when messing with Shaun after character creation. But the two tips were excellent and have been added to the arsenal I'm building to deal with all the funny business modding Fallout 4 requires. It's really making me miss the days of problem: "mY PiPboyz is teh borked!!! Plz Halpz!!!" solution: go to data\textures and delete pipboy3000 folder heh. God bless FNV. Soooooo. If there are any other fun tricks to try, let me have em!

Behold, the power to fix your problems! https://forums.nexusmods.com/index.php?/topic/6851497-another-script-extender-update/&do=findComment&comment=62180472

you can always unroll your version in the steam console. A bit of a hassle, but once you've set up the shortcut, you're ready for next time Bethesda tries to take your toys away. find your steam executable (usually in Program Files (x86)\Steam) Create a shortcut Open the shortcut properties and add -console to the end of the target Target will now look like "C:\Program Files (x86)\Steam\Steam.exe" -console Close out steam ALL the way Open with the shortcut and you should see the console tab in Steam Copy/Paste the following into the console and wait for it to finish downloadingdownload_depot 377160 377162 2144426079840954483 for the lastest version Inside whatever directory the console stated (mine was C:\Program Files (x86)\Steam\steamapps\content\app_377160\depot_377162) you should find a shiny new 1.10.98.0 version Fallout 4 exe p.s. is it just me, or is Fallout 4 the mod equivalent of self flagilation? I can't ever remember having to jump through so many effing ridiculous and often somewhat painful hoops just to get my character to wear pretty pretty earrings and tight shorts. Sheesh!

Danke. I'm definitely missing the strings value in my ini. I was using bethini, but it seems to only do some of the work its supposed to. I should probably just download some ini presets for a high end gaming rig. The purge unmanaged files should also be very helpful for next time I break something (which will likely be this afternoon). I was doing them one mod at a time lol. Appreciate the response. 2 more pieces to the mod puzzle pile!

Howdy good folks of Nexus forums. I have got an odd problem. One that I'm sure is mod related, but shows up with or without mods enabled. Colors. All of them. On my hands. On my Guns. On my Pipboy. Well, to be exact, no colors. Black and white as 1950s television. I've been through all the archive invalidation steps, verified files, re-installed mods, messed with settings, deactivate and reactivated, repeated all the previous in a blind attempt to fix it again, and I cannot get this bug fixed. As I said, its even present with no mods active. Part of me wants to blame NMM. It seems to be fickle. And buggy. But, I've gone through everything and installed loose with the same outcome. Alas, I am also fickle. And buggy. I have a feeling its a mesh/texture issue and animation relationship. Like maybe z-fighting from two competing textures, but I can't figure out how to go about troubleshooting it. I've been through the actor textures files and they seem ok. But the problem only exists in first person, and only exists when the game isn't paused by the in game menu. As soon as I pause in game, the colors come back. Wild Wasteland weirdness. Anyways, pics below along with system specs (no slouch here), and the load order which doesn't seem to matter since I can disable them all and get the same result. For those who want to latch onto the "omgz such mods so load order", most of the weapons, pipboy, and bodymods were tossed on in an attempt to overwrite whatever problem exists (of course with no success since I'm here). Thanks for reading :smile: Screenshots System Specs Mod Load Order