Open racofer opened 11 months ago
Having the same issue here!
And this is using F4SE version 0.6.23? Updates to the game exe almost always require updates to F4SE itself.
It would seem a workaround is required for this. Add -forcesteamloader
to the launch arguments for F4SE for the time being.
It would seem a workaround is required for this. Add
-forcesteamloader
to the launch arguments for F4SE for the time being.
You're a lifesaver
It would seem a workaround is required for this. Add
-forcesteamloader
to the launch arguments for F4SE for the time being.
Bless your heart, you a true savior!
It would seem a workaround is required for this. Add
-forcesteamloader
to the launch arguments for F4SE for the time being.
How do I do this?
It would seem a workaround is required for this. Add
-forcesteamloader
to the launch arguments for F4SE for the time being.How do I do this?
Depends on mod organizer you use.
How to do this for Vortex?
Could somebody please explain how i am supposed to add this line if i'm running Fallout 4 GOG through MO2?
Creating a FOSE shortcut and adding -forcesteamloader starts the game without MO2 and disables all my mods so i'm obviously doing it wrong.
Could somebody please explain how i am supposed to add this line if i'm running Fallout 4 GOG through MO2?
Creating a FOSE shortcut and adding -forcesteamloader starts the game without MO2 and disables all my mods so i'm obviously doing it wrong.
You need to modify the executable definition in MO2, see https://github.com/ModOrganizer2/modorganizer/wiki/Executables-window
Could somebody please explain how i am supposed to add this line if i'm running Fallout 4 GOG through MO2? Creating a FOSE shortcut and adding -forcesteamloader starts the game without MO2 and disables all my mods so i'm obviously doing it wrong.
You need to modify the executable definition in MO2, see https://github.com/ModOrganizer2/modorganizer/wiki/Executables-window
Hey, thanks for helping me out! I added -forcesteamloader in the Arguments box for the FOSE executable located in the Modify Executable window and i no longer have the presets options greyed out.
Did i do it right? And for future reference, is this something i need to do with other dll-based mods?
Could somebody please explain how i am supposed to add this line if i'm running Fallout 4 GOG through MO2? Creating a FOSE shortcut and adding -forcesteamloader starts the game without MO2 and disables all my mods so i'm obviously doing it wrong.
You need to modify the executable definition in MO2, see https://github.com/ModOrganizer2/modorganizer/wiki/Executables-window
Hey, thanks for helping me out! I added -forcesteamloader in the Arguments box for the FOSE executable located in the Modify Executable window and i no longer have the presets options greyed out.
Did i do it right? And for future reference, is this something i need to do with other dll-based mods?
You usually do not need to add it, that depends on the script extender and game variant (you do not need that flag for the Steam variant of Fallout 4).
The problem:
Mods that rely on F4SE are failing to load with the new GOG edition of Fallout 4. As reported on the Discord channel by multiple users, MO2 is not working properly with this new FO4 release since it's not injecting F4SE dlls and .pex files.
When manually copying the same mod files directly into FO4 install directory, everything works.
Environment: