#FALLOUT 4 SCRIPT EXTENDER CAUSING CTD HOW TO#
#FALLOUT 4 SCRIPT EXTENDER CAUSING CTD MOD#

This seems to work because after I have done this it shows Fallout 4 highlighted and says one (1) process selected and there is a red Stop CPUCores. When the load is finished, find Fallout 4 in the list, highlight it by clicking on the Fallout 4 icon and then press the 'CPUCoresIt' button in the lower right hand corner of the CPUCores panel. On the main CPUCores Panel 'Select a non-Steam application or game' by clicking on the second icon from the left at the top of the CPUCores panel.ĥ. When the game starts and you are prompted to press a button to start the game then Alt-tab to CPUCores.Ĥ.

#FALLOUT 4 SCRIPT EXTENDER CAUSING CTD MOD#

Run the script extender either from a desktop icon or using Nexus Mod Manager.ģ. SOLVED: Actually I was getting the steps required to accomplish this mixed up. Getting the steam game Fallout 4 to start the script extender using a command line (if that is even possible) then this won't be an issue at all.

In the meantime I am going to see if I can come up with another workaround.

Otherwise, it causes crashes when using the workbench. You have the Mercenary Pack, which from my experience, needs to be placed BELOW Armorsmith Extended and ABOVE UCO. I sure appreciate you taking the time to address this issue I'm having. Weapon and armor modification mods should be towards the bottom, placed only above mods that absolutely need to be at the bottom. I think the first time I tried it actually started the game and I alt-tabbed the applications to CPUCores to try to CPUCores It and noticed that the steam game did not show up in the list but any subsequent attempts just retun me to the desktop.

#FALLOUT 4 SCRIPT EXTENDER CAUSING CTD HOW TO#

I was following a previos thread on how to accomplish this and it involved starting the script extender as a non steam game then use CPUCores It to capture the second process, however because the second process is a steam game it does not show up in the CPUCores it list. I can't be the only Fallout or Skyrim player that uses a script extender and have purchased CPUCores. If the script extender normally loads the steam game and your program automatically controls the running of the steam game then I should be able to run the extender normally from either the desktop or Mod Manager. This all may be a moot point if your program automatically starts whenever one of the steam games on the list starts up. It plays the first few sounds of the Fallout 4 startup soundtrack and it briefly shows the startup screen of fallout but then it returns to the desktop right away. Maybe I should say it returns to desktop.

Fallout 4 script extender causing ctd