I know this is a super old mod, but this actually works in Nov 2024 with MO2 & SFSE. Even tested with Steam RemotePlay, starts like normal and doesn't bug out on the SFSE startup window.
Launches without SFSE for me, both with and without quotation marks :/ Putting 2 hyphen makes the game to launch without SFSE Not putting them like on your screenshot makes it so SFSE loader couldn't read arguments
such a useless mod, just add the SFSE to your steam library as a non steam game. hover over "games" "add a non steam game" "browse" find SFSE and add it, DONE
I already mentioned this on the mod page. But by adding it as a non-Steam game, achievements etc. are not shown on the SFSE page. This way, you keep everything as is and it launches SFSE.
Add 'sfse_loader.exe' to the list of executables in MO2. See the example. Note that I added the force loading of 'GameOverlayRenderer64.dll' to enable the Steam overlay to work.
Then, add the following Steam launch options: "<full path to ModOrganizer directory>\ModOrganizer.exe" "moshortcut://Starfield:SFSE" %command%
In my example, the SFSE executable entry in MO2 is named 'SFSE' and the Starfield mod instance in MO2 is named 'Starfield' which is why I wrote 'moshortcut://Starfield:SFSE.' If you are using different names, make sure to adjust it accordingly (<instance_name>:<executable_entry_name>).
doing it with quatation marks gave me an error in steam, tried it without and I could launch it with sfse but it gave me an error with the cmd. "failed to find AddINISetting_fMipBias_hook!"
I didn't get that error. Did you install sfse manually or using Vortex? try launching sfse using sfse_loader.exe and type "getsfseversion" in the console. (without the quotation marks)
Edit: After some googling, I found that some user's or other mods are having the same error. Are you using MO2 by any chance?
it seems like it can still launch it, it tells me every launch that I shouldnt try to run it but running it seem to work. Writing getsfseversion shows the current version
It's weird that it gives you an error when trying to launch. If it bugs you that much you can try adding the script extender as a non-Steam game, but you'll need to edit the name and modify the icon if you want it to look like Starfield. It's what I was doing before, if you look at the pictures I uploaded you'll see "Starfield Mod" in my library.
32 comments
bash -c 'exec "${@/Starfield.exe/sfse_loader.exe}"' -- %command%
sfse_loader does work when ran as a non-steam game with Proton Experimental so I know it is working.
Manjaro Gnome 45.0
Thanks
Putting 2 hyphen makes the game to launch without SFSE
Not putting them like on your screenshot makes it so SFSE loader couldn't read arguments
Simple also means no unforetold issues or bugs from entering needless commands in Steam's Launch options.
- Add 'sfse_loader.exe' to the list of executables in MO2. See the example. Note that I added the force loading of 'GameOverlayRenderer64.dll' to enable the Steam overlay to work.
- Then, add the following Steam launch options:
In my example, the SFSE executable entry in MO2 is named 'SFSE' and the Starfield mod instance in MO2 is named 'Starfield' which is why I wrote 'moshortcut://Starfield:SFSE.' If you are using different names, make sure to adjust it accordingly (<instance_name>:<executable_entry_name>)."<full path to ModOrganizer directory>\ModOrganizer.exe" "moshortcut://Starfield:SFSE" %command%
Anyone know what it could mean?
Edit: After some googling, I found that some user's or other mods are having the same error. Are you using MO2 by any chance?
"C:\Program Files (x86)\Steam\steamapps\common\Starfield\sfse_loader.exe" -- "%COMMAND%"
Also it looks like you haven't updated the mod page yet.