wax2k
-
Posts
533 -
Joined
-
Last visited
Everything posted by wax2k
-
@teamster: I can only guess, but the most common cause for a CTD right at startup / main menu is missing master files or wrong load order (master files below the referring files). So most probably you uninstalled at least one .esm/.esp file which is referred to by another still active .esp file.
-
Yeah, materials and other custom assets as well, if existant. If MO2 fails to copy them, it affects all assets apart from the .esp/.esm files. If that still doesn't work, double-check for the ini-changes you mentioned. They have to be in Fallout4Custom.ini, which has to be in \%UserData%\Documents\My Games\Fallout 4\. And in case you have a Fallout4.ini in \%InstallDir%\Fallout 4\data\, you should either delete that or edit in those lines as well. It's most definitely an issue of the game not being able to access custom assets either due to them not being where they should be or the game not being allowed to load them at all.
-
Extract the textures and meshes from your mods manually and place them in the according folders in \%InstallDir%\Fallout 4\data\textures and \%InstallDir%\Fallout 4\data\meshes. MO2 oftentimes fails to do so automatically.
-
Do you use the keyboard or the mouse? Because rotation by keyboard has been reported to not work anymore since one of the patches. Try the left and right mouse button to rotate.
-
Make sure, that the texture files are correctly installed in \%InstallDir%\Fallout 4\data\textures. Copy them manually if necessary. In some scenarios, mod managers like NMM and/or MO2 fail to do so automatically. This mostly happens, when either Fallout is installed in one of Windows' standard "Progam Files" folders and the mod manager is launched without admin rights, or when using virtual mod install on a different harddrive than Fallout itself is on. Also double-check your ini(s): \%UserData%\Documents\My Games\Fallout4\Fallout4Custom.ini must contain the following lines: [Archive] bInvalidateOlderFiles=1 sResourceDataDirsFinal= Make sure, there are no typos. \%InstallDir%\Fallout 4\data\Fallout4.ini should not exist, since that might override \%UserData%\Documents\My Games\Fallout4\Fallout4Custom.ini. If it is needed for a mod you use, make sure, it also contains the lines mentioned above and no conflicting lines (same variable, different values). And make sure to refer to this guide in case of future issues. It covers a lot of the most common issues and provides solutions.
-
That is correct.
-
Please provide a screenshot of you trying to select and place one of the affected objects.
-
@ZoSar: The most common cause for that kind of CTD is an interface mod (which wouldn't be listed in your load order, since it's not an .esm/.esp based mod). Go look for a Workshop.swf or similar in \%InstallDir%\Fallout 4\data\interface and remove it in case or try and rename the whole folder for testing purposes.
-
The "Custom Doors" section is actually from (Safe) SSEx, not from Homemaker. Older versions - like the one you use - cause a known CTD on a certain door in that section. Either update to the latest version, which has been fixed by Ethreon, or get rid of it in the first place, since it doesn't add much that isn't also in Homemaker anyways. Apart from that, it might be that your latest savegame is corrupted by now, so you might have to revert to an older save. And in general, you might also want to check out this guide
-
Since I don't have the DLC myself, it might well be that I didn't list all related files. Mind posting the filenames (I'd guess, it's a DLCRobot.cdx, a DLCRobot - Geometry.csg and a DLCRobot.ba2) and the contents of the DLCList.txt (I'd guess, it's just the DLCRobot.esm), so I can edit them in to make the above post complete for future reference? Edit: nevermind, googled them and edited them in. You might want to double-check, since you only mention 3 DLC files, but according to my information, there should be 6 in total, so that might also be related to your issue. Also it might be worth a try to test it without the DLC once, just to see if it's somehow related to that. Also: are you opted in for the beta and using the latest Survival Mode beta patch? If so, opting out and reverting back to the latest retail patch (by again verifying game cache in Steam after opting out) is worth a try.
-
@ResidentAlien: if you did everything exactly as you described it, there should be no reason for that CTD. But to make sure, double-check for this: The \%InstallDir%\Fallout 4\data folder should look like this: \Strings \Video DLCRobot - Geometry.csg (only if you have the Automatron DLC) DLCRobot - Main.ba2 (only if you have the Automatron DLC) DLCRobot - Textures.ba2 (only if you have the Automatron DLC) DLCRobot - Voices_en.ba2 (only if you have the Automatron DLC) DLCRobot.cdx (only if you have the Automatron DLC) DLCRobot.esm (only if you have the Automatron DLC) Fallout4 - Animations.ba2 Fallout4 - Geometry.csg Fallout4 - Interface.ba2 Fallout4 - Materials.ba2 Fallout4 - Meshes.ba2 Fallout4 - MeshesExtra.ba2 Fallout4 - Misc.ba2 Fallout4 - Nvflex.ba2 Fallout4 - Shaders.ba2 Fallout4 - Sounds.ba2 Fallout4 - Startup.ba2 Fallout4 - Textures1.ba2 Fallout4 - Textures2.ba2 Fallout4 - Textures3.ba2 Fallout4 - Textures4.ba2 Fallout4 - Textures5.ba2 Fallout4 - Textures6.ba2 Fallout4 - Textures7.ba2 Fallout4 - Textures8.ba2 Fallout4 - Textures9.ba2 Fallout4 - Voices.ba2 Fallout4.cdx Fallout4.esm Nothing more, nothing less. Your \%AppData%\Local\Fallout4\plugins.txt should only contain this: Fallout4.esm And your \%AppData%\Local\Fallout4 folder should only contain the plugins.txt and the DLCList.txt (the latter containing the DLCRobot.esm if you have the Automatron DLC or nothing if you don't have it). Your \%UserData%\Documents\My Games\Fallout4\Fallout4Custom.ini should only contain this: [Display] iLocation X=0 iLocation Y=0 And your \%UserData%\Documents\My Games\Fallout4\Fallout4.ini should have the line: sResourceDataDirsFinal=STRINGS\ and not have any of these lines: sResourceDataDirsFinal= bInvalidateOlderFiles=1 in the [Archive] section. This should guarantee a vanilla state of your game. But to be even more on the safe side, you should verify the game cache in Steam once after double-checking the above. Then launch the game from Steam, choose "New Game" and bee-line through the tutorial and to Sanctuary and open the Workshop menu there. Do not load a savegame for this test. Do not launch it from another application (like F4SE or NMM). Do not use any additional programs (like ENB/ReShade, F4SE, CheatEngine or whatever). If it still crashes after this, the cause for your issue is probably outside of the game. Might be a driver issue or even related to failing hardware (harddrive, graphics card, RAM).
-
http://media.tumblr.com/tumblr_luk1irgKnM1qlq05h.gif
-
Haven't used it yet (since I haven't been playing and / or modding Fallout in the past weeks and probably won't anytime soon), but I'd put it in the Weapon Modding section according to the example load order and as far as I can see, that's also where Gambit77 put it in his latest load order posted on Armorsmith Extended. I'll edit it in the original post.
-
Video ripping, Loss of environmental video elements
wax2k replied to Sandcrab2000's topic in Fallout 4's Discussion
This kind of issue happens, when removing certain objects from the game, that are used for LOD rendering by the engine. In Sanctuary this includes the larger hedges and all buildings that are non-scrappable in vanilla. When standing / moving in the place or looking through the area, where that object had been, these visual glitches occur due to the game "thinking", the object still was there and blocking the view. There is no real solution for that, apart from not scrapping / removing these objects from the game. Otherwise you can only try to hide or just ignore the effects. -
If that was the case, I'd wonder how they ever got to know people, when not even talking to people they don't know :wink:
-
I've tried, but never got a reply from the 3 staff people I messaged weeks ago. Which is quite disheartening to be honest, especially when seeing that another guide written by someone, who claims to not even own Fallout 4, gets pinned within less than a day. But then again: it's not the first time I experience two very similar things being handled very differently on this platform. Consistency doesn't seem to be a high priority. :rolleyes:
-
There is no mod that requires Safe SSEx, only compatibility patches from other mods. If you don't use Safe SSEx, you don't need these patches, so just remove them.
-
That is obviously another issue than the one you described before. Look for a Workshop.swf in \Fallout 4\data\interface and delete it in case you have it. And if you use any kind of interface mod which this file might be from, look for an update to make it work again. It has been a commonly reported issue with Fallout 1.4 and several mods using a custom Workshop.swf.
-
Hmkay... let's see if it is related to the savegame and /or one of the .esm / .esp files or maybe one of the custom assets. Please do these following separate tests: 1. Try it on a new game or at least your oldest savegame and see if that makes any difference. 2a. Disable all .esm / .esp files in NMM's Plugins tab and try it on your latest savegame 2b. and afterwards on a new game or at least your oldest savegame. 3a. Rename the following folders in \Fallout 4\data and then enable the .esm / .esp files in NMM again and try it on your latest savegame 3b. and afterwards on a new game or at least your oldest savegame. \interface to \interface_BAK \materials to \materials_BAK \meshes to \meshes_BAK \scripts to \scripts_BAK \sound to \sound_BAK \textures to \textures_BAK Report back afterwards with the outcomes of the 5 different tests. And if you don't want to test that much and don't care for finding out the cause, you could also delete Fallout and your mods, install them again and hope for the best. It could however happen again in case it's related to a certain mod or some sort of savegame bloat / corruption.
-
Hmkay, nothing leaps to the eye. What about different settlements? Does it happen at every one? At which settlements have you tried it? Does it even happen at settlements where you have built nothing yet?
-
Launching the game from Steam or its own launcher will always clear the plugins.txt thus disabling all .esm / .esp mods. Always launch it from NMM and that shouldn't happen. And for double-safety make the plugins.txt read-only.
-
Then it's probably an issue of either graphics drivers or even a graphics hardware issue. Try getting the latest retail drivers for our card and make sure that neither your GPU nor your CPU are overclocked. And you might want to clean your case and fans just to make sure your hardware doesn't overheat due to bad airflow due to dusty fans.
-
Your screens are way too small to recognize anything on them.
-
First of all, don't use this file. It's only for the non-SK versions of SnB and Homemaker: 46 2e Snap'n Build - Patches.esp And i case you use the console menu version of SnB, you will have to disable these files too accordin g to the mod's description: Snap'n Build - Modules.esp Snap'n Build - Capsule Paints.esp You might even want to reinstall SnB in the order according to this post by the mod author: http://forums.nexusmods.com/index.php?/topic/3622795-snapn-build/?p=35271305 Then use this load order and disable everything else for testing purposes: Fallout4.esm ArmorKeywords.esm SettlementKeywords.esm Snap'n Build.esm Homemaker.esm Snap'n Build - Modules.esp Snap'n Build - Capsule Paints.esp Snap'n Build v1.6 SK patch.esp Homemaker - SK Integration Patch.esp Homemaker - Streetlights Use Passive Power.esp and see if it works (which it should) and report back.
-
How do you launch Fallout? From NMM, from Steam or with Fallout's own launcher?