- Navigation
- Contents
- Preface
- Download Issues
- Installation Issues
- Game Crashes
- Other Post-Install Issues
- Gameplay Issues
Please help me to help yourself here. Search this page and the FAQ if you are having issues. Please also use the Discord search function in the WoD channels as your issue may already be solved. Do not just post a question in the support channel without doing your own research first.
It's one of the files on the commonly failing downloads list. Wabbajack even gives you report now, please read that to know exactly what files you missed. All commonly failing downloads can be found on the Wiki page here.
Your Nexus login expired. In the Wabbajack settings, log out of Nexus and then re-login.
The Nexus server you are downloading from is having issues, try switching your preferred Nexus download server to something close to your location in the account settings. You can access this area by clicking on your account in the top right, and selecting site preferences.
Your game files are wrong - this will give a clear error in the Wabbajack log, like so:
To fix this, you need to ensure your game is set to English in Steam and then verify your game files with Steam.
You'll need to wait for a modlist update.
-
Hashes don't match for texture files (files that end in
.DDS) - Your Wabbajack version is outdated, make sure you are using v3.7.0.0 or later. -
File is corrupt (usually
.ba2files) - Wabbajack will tell you what file the error is with in its log as well as to delete it and retry the install. Follow the steps given to you by Wabbajack. -
Your storage drives are full - both the installation drive and the drive you have Wabbajack on need a free space for the installation to be possible.
-
You didn't setup antivirus exclusions.
Heavily modded Bethesda games are prone to crashing at times. Generally speaking, the following is true:
1 crash is a fluke, 2 crashes is weird but not impossible, 3 is a repeatable crash worth reporting and/or investigating.
Before you report a crash, consider these rules and also read below to see if your issue is already known about.
Software such as Medal, EVGA Precision and MSI Afterburner are the most common causes of this - anything that hooks the display to show or record stuff on screen. Close the software and test again.
This shows up in crash logs with the following things in the stack: hclClothInstance, hclClothData and hair parts named, like so:
The crashes are random and seem to appear more often in areas where lower end PC's performance suffers, which will be different between different PC's. You can turn the active portion of Rusty Face Fix Redux off by opening the INI found in Rusty Face Fix - WoD INI and setting the streaming_mode to 0. If there is a version of these settings named Rusty Face Fix - iAm’s Settings enabled, disable it. Note: with the active portion switched off, you may see more rust face NPCs as you play.
This shows up in crash logs with the following things in the stack: JobListManager::ServingThread and PipBoyMapData, like so:
This is a very rare crash that WoD has custom mitigations against. To fix, type the following commands into the console:
player.unequipall
Followed by:
player.equipitem 21b3b
This crash occurs when you enter workshop mode. Do not touch the Disable Volumetric Lightning in NAC X Settings menu/MCM. It will make the game crash every time you enter workshop mode and it can't be reverted - you will have to load an earlier save to fix it.
Make sure your WoD folder is added to your antivirus exclusions. If it is, download Microsoft Redist (June 2010) from here.
The low resolution textures you are seeing after playing for a time is caused by Long Loading Times Fix.
This mod aims to reduce loading times, especially when fast travelling or travelling through loading screens but can sometimes remove the loading screen a touch too early, before textures have fully loaded in.
If this behaviour bothers you, it should be safe to switch off mid-save.
In MO2, under the Essentials separator, find High Physics FPS Fix - WoD INI and double click it. In the window that opens, head to INI Files and click the only option in the left column. Find the line:
Fullscreen=false
and change it to:
Fullscreen=true
This could be caused by a few things:
- You didn't setup a Pagefile as described earlier in this readme or,
- You didn't install on an SSD or,
- Your hardware doesn't meet the minimum recommended specs.
If you genuinely have followed the above steps then ensure the following:
- When setting the pagefile up, you have enough space left on the selected SSD for Windows to allocate the full pagefile size - not having the 20 to 40GB free on the SSD is the same as not having a big enough pagefile in the first place.
- You have added your entire WoD installation folder to your antivirus exceptions/allow list - you want the whole folder, not just the Mod Organizer exe.
- You have your motherboards XMP/DOCP/EXPO setting switch on - without this setting on, your RAM will be running at the default 2400MHz standard, not the speed you paid for. Enabling this will give a good boost in performance across everything you do but especially games. Of course, not all RAM is capable of clocking higher than the standard 2400MHz but most "gaming" prebuilts and "gaming" level RAM should clock higher if allowed.
Note: if you did buy a prebuilt PC, the XMP setting is worth a double check - not all system builders enable this setting before shipping you your PC for some reason.
If you have ensured all of the above is right, try lowering settings in BethINI, following this guide in the modifications channel on the Discord.
We don't use VATS, we use VAFS - consider it like bullet time. If it won't trigger, set the VATS keybind in the Settings menu to something else.
You forgot to investigate Vault 111 first. You have to do this in order to kickstart the main quest.