Fallout 4 - Creations Bundle

chudmaxxing bethesda

can not even access the creations menu. I couldn't get a solution either

Complete trash, unable to start the game on windows, but not on linux, inexplicably.

It doesn't work I can download the creations but it refuses to enable so it was essentially a waste of 20 bucks.

Fallout 4 Creations Bundle causing CTD — how I fixed it I had a heavily modded Fallout 4 setup using Vortex. After installing the Fallout 4 Creations Bundle, the game would show the black Fallout window and immediately crash before reaching the main menu. My Nexus modlist itself had been working fine before installing the Bundle. What I did Disabled all Nexus mods in Vortex and launched Fallout 4 completely vanilla. The game launched normally and reached the main menu. This confirmed that the base game itself was fine. Cleaned my plugins with LOOT/FO4Edit as I normally do. I did not delete the Creation Club content at this point. I used the Collective Modding Toolkit to check the installation. With the Creation content installed, the BA2 count was extremely high: General BA2: 309 / 256 Texture BA2: 279 / 255 Total: 588 / 511 So I had exceeded the BA2 archive limits by a significant amount. I tried disabling the Creations through the in-game Creations menu, but the Bundle content would not let me disable everything individually. I therefore disabled the Bundle through Steam first, but that still did not give me the control I wanted over the individual files. As a last resort, I manually removed the unwanted Creation files from Fallout 4's Data folder, specifically the corresponding cc*.esl and cc*.ba2 files. I removed the cosmetic Creations I didn't care about, such as unwanted weapon/Pip-Boy paints and similar content. I did not remove the Creation content I actually wanted to keep. I also avoided verifying the game files afterward, since Steam could simply download the removed Creation files again. After removing the unwanted Creation content, I checked the game again with the Collective Modding Toolkit. The essentially vanilla installation dropped to: General: 20 / 256 Texture: 15 / 255 Total: 35 / 511 I then re-enabled my entire Nexus modlist through Vortex. With my normal Nexus mods active, the Toolkit showed: General: 138 / 256 Texture: 107 / 255 Total: 245 / 511 213 full plugins / 94 light plugins So the Nexus modlist itself was comfortably within the limits. I launched Fallout 4 with my full modlist, and it finally worked. 🎉 Conclusion The problem was not a single broken Nexus mod. The combination of my large Nexus modlist plus the huge number of BA2 archives added by the Creations Bundle pushed Fallout 4 past its BA2 archive limits. The important numbers were: Before cleanup: 309 / 256 General BA2 279 / 255 Texture BA2 After removing unwanted Creations + restoring my Nexus mods: 138 / 256 General BA2 107 / 255 Texture BA2 So if Fallout 4 suddenly starts crashing immediately after installing the Creations Bundle, especially on a heavily modded setup, checking the BA2 counts is definitely worth doing before assuming that your entire modlist is broken. The fix for me was simply removing the Creation content I didn't actually want, rather than rebuilding my entire Nexus load order.

♥♥♥♥. Only purchased because Wabbajack modlists require it.

it was a mistake buying the DLC this game is bugier than 76 ♥♥♥♥ this game to hell. Updated my ass they did ♥♥♥♥ all added ♥♥♥♥ from 76 and made the game bugy again this company is cooked im just gonna keep playing 76 i guess. Dont buy this not worth it. you would have more fun tripping on LSD in a crack den spend the 30$ on LSD 100% better than this ♥♥♥♥

Overpriced and a lot of the content doesn't work or textures are bugged. Yeah Todd, green and purple hands are features. Max level greed from Bethesda.