moirai

Bit of a necro, but... Find 'bSAOEnable' in the CreationKitPrefs.ini file and make sure it's set to '1', as in: bSAOEnable=1 If it's set to '0' you'll get the above effect.

Excellent! That's great news. Glad it's working.... :)

Okay, let's see what we can do.... :) Tell me, step by step, what precisely have you done...?

Yes, it's been updated. There is already a new version available for the latest Fallout4.exe (ver 1.10.162). Bear in mind thought that any mods you have running that require F4SE will most likely not work with the new version of F4SE until the mod authors update their files to use it. So, at present, you're better rolling back and waiting... yeah I know. I already downloaded the new f4se and tried it. game still wouldn't even start. I'm prob gonna uninstall all 400 mods and the game and just not play another Bethesda game again. I'm tired of this s*** breaking constantly restarted my laptop. now i have to redownload the entire game because its not picking up on steam =_= https://gyazo.com/bd25bef584e46be56f2435f5e8f81f07 No need to do anything that drastic at all. Just reinstall the previous version of F4SE and apply the rollbacks as mentioned in this thread. Job done... :smile: F4SE (version 06.17) for Fallout4.exe (ver 1.10.138) is here: https://f4se.silverlock.org/archive/f4se_0_06_17.7z

Yes, it's been updated. There is already a new version available for the latest Fallout4.exe (ver 1.10.162). Bear in mind thought that any mods you have running that require F4SE will most likely not work with the new version of F4SE until the mod authors update their files to use it. So, at present, you're better sticking with the version you have already, rolling back your game files and waiting...

The 'CTD' on loading looks like it's simply being caused by the file version of the Fallout4.esm changing from '0.95' to '1.00'. Wrye Bash bitches about this as well. I fixed that, without rolling back the ESM or BA2s, by hex editing the new ESM's header version number back to '0.95'. So, for reference, that also works... EDIT: Also, again for reference, the files that I see being updated are: Main - Fallout4.exe (Version now 1.10.162 - was 1.10.138) - Fallout4.ccc Data - Fallout4.esm (Header version now 1.00 - was 0.95) - Fallout4 - Interface.ba2 - Fallout4 - Materials.ba2 - Fallout4 - Meshes.ba2 - Fallout4 - Startup.ba2 All these files had the same modified time and date stamp this morning (GMT) For those with the knowledge, software and desire to go the hexedit route of the new Fallout4.esm, do the following: 1) Make a backup the Fallout4.esm file. 2) Open Fallout4.esm in you hexeditor of choice. 3) Make the following edits: - On line 00000010 change the offset values as follows... - - Change offset value 0E from '00' to '33' - - Change offset value 0F from '00' to '33' - On line 00000020 change the offset values as follows... - - Change offset value 00 from '80' to '73' These edits will change the header version (viewable in FO4Edit) from 1.00 to 0.95. 4) Save and quit 5) Start Fallout 4 and check. It should now not CTD on the main menu. Normal disclaimers apply for the above. ;)