-
Notifications
You must be signed in to change notification settings - Fork 85
Please add Starfield as an option #528
Comments
Please... |
@sbalani the file you’re looking for is step/download_external_resources.sh |
Please note that only beta4 of MO2 2.5 will run with wine/proton. Betas 5 and 6 will crash. Currently the stance of the MO2 devs (on their Discord channel) seems to be that because they are not targeting linux directly, it's not their problem and should be solved in wine... |
(This has been edited to incorporate suggestions/progress.) Here's the steps I did to get MO2 installed for Starfield.
|
@closms This is what i used in my steam to launch the Starfield Script Extender, I hope this offers some insight. |
This worked perfectly for me! I'm running it on Steamdeck and it turns out @closms is right and the original exe needs to remain untouched to actually load a game. After renaming _Starfield.exe back to Starfield.exe, the mo2 launcher from Starfield.exe to mo2.exe, and using |
Just a few things on this, I did not have to do step 3, 4, or 8. The plugin could actually be why your mod wasn't working, and you can edit the .ini directly from within MO2. |
Hi. MO2 dev here. There are three distinct differences between Beta 4 and the other builds. We are using Qt 6.5, Python 3.11, and OpenSSL 3. No other changes exist that would break Wine compatibility, but we don't maintain any of those projects nor do we have an easy way to debug a collision within Wine. As core components of our application are built specifically for Windows and it would be a metric ton of work to create an alternative build path with a functioning VFS on Linux, we simply aren't going to go out of our way to solve these kinds of issues. But if somebody can pinpoint an issue that we actually can patch in our own code which would resolve the compatibility problem, we would do so. We aren't going to be moving backward on the dependencies at this point. |
If anyone else is looking for help, I forked this repo and have a beta release which automates the bulk of the process mentioned here.
This works well for me on Steamdeck with Proton Experimental as well as one of the newer GE Proton releases. |
After working with one of the folks in our main Wine support GitHub issue, they believe they've identified the problem and created a pull request with Wine to patch it. https://gitlab.winehq.org/wine/wine/-/merge_requests/3931 I guess you can keep your eye on that for an eventual Wine build that will work with the final 2.5.0 version. |
Thank you! I tried your repo and it really did work just fine. |
I've tried your repo and while the script worked, Mod Organizer won't launch. I've taken a look at the proton logs and only this part sticks out to me compared to default game launch (without the launch command):
I haven't really tinkered that much with proton in the past but it seems to suddenly be unable to find the Z drive? Any clue what could be causing this? |
So my issue was a variation of #285. Turns out the not so helpful error "ERROR: cannot execute 'Z' - No such file or directory" doesn't actually mean that the Z: drive cannot be accessed, rather that a file on the Z: drive cannot be accessed. I originally installed Mod Organizer in the default suggested location /home/user/Games/mod-organizer-2-starfield, but from within the prefix i could only get as far as /home/user/ where the only visible folder was Downloads. I had to re-do the entire process but this time install Mod Organizer in an accessible location, afterwards everything worked. |
How am I supposed to install the Starfield MO2 plugin? As far as I know the MO2 folder doesn't exist until MO2 is installed, and when I try installing the MO2 under starfield, MO2 says that Starfield is an unrecognized game when I try to choose the Starfield directory. |
@Gary8thomas I don't believe the plugin is necessary. If you check my fork of the repo I think it makes installation a lot easier, and someone above confirmed it worked for them |
Nevermind... i'm an idiot. I thought the MO2 was in the drive_c folder then like AppData then local, I just learned that the actual MO2 folder is in the .config folder. But also, I did try creating a starfield instance in MO2 without the plugin beforehand and it just didn't let me, it said the game was unrecognized. However, installing the plugin seemed to make MO2 work with Starfield Edit: I am also doing this on a steam deck, I'm not sure if that changes things. |
Steamdeck runs(Or used to) a modified version of Debian for as far as i am concerned its almost the same as any other debian or debian based distro |
Sep 25, 2023 02:45:44 JeroenMathon ***@***.***>:
Nevermind... i'm an idiot. I thought the MO2 was in the drive_c folder then like AppData then local, I just learned that the actual MO2 folder is in the .config folder. But also, I did try creating a starfield instance in MO2 without the plugin beforehand and it just didn't let me, it said the game was unrecognized. However, installing the plugin seemed to make MO2 work with Starfield
Edit: I am also doing this on a steam deck, I'm not sure if that changes things.
Steamdeck runs a modified version of Debian for as far as i am concerned its almost the same as any other debian or debian based distro
—
Reply to this email directly, view it on GitHub[#528 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AB4OXMEFZ4TJBJV34DB4YKTX4ESBLANCNFSM6AAAAAA4TPWM4A].
You are receiving this because you are subscribed to this thread.
[Tracking image][https://github.com/notifications/beacon/AB4OXMHHTXAALLMB7BNENA3X4ESBLA5CNFSM6AAAAAA4TPWM4CWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTHJPAJ2.gif]
Message ID: ***@***.***>
That's incorrect. The prior SteamOS versions intended for the now defunct Steam Machines project were based on Debian 8, however, as stated in Valve's APT repository readme for those versions: https://repo.steampowered.com/steamos/README.txt
The Steam Deck's version of Steam OS is Arch-based.
|
You seem to confuse the Steam Deck with the Steam Machines from 2015. The Deck runs SteamOS 3, which is based on Arch. |
Thanks, I am aware of this but lets stay on track :) |
Does anyone here is having a issue on this latest update + SFSE 1.7.36? When I launch SFSE the console shows up (sfse_loader) loading all scripts (afaik it didn't happen before) but at the end it show this error: |
I'm attempting to replicate your fork locally with updated sfse and mo2 betas from the discord, have you tried it with the newer ones like beta 13? Also why did you specify sfse files instead of using "*"? |
The Wine patch has been merged. Hopefully there will be Wine builds soon with the fix included. If you are able to test and verify the fix, please let us know here: ModOrganizer2/modorganizer#372 |
I don't know why it's happening now but I'm getting the error: I'm on Arch, is it a dependency I might be missing? Baffled. Funnily enough, and I mean funny as in odd as it's not fun not having Starfield available for modding, 4.4.0 works just fine. |
AHA! I may have found the issue of it not launching - because there is no MO2 that installs! The URL to get MO2 2.5 Beta 4 (as linked to on the MO2 discord to a google drive) leads to a 404, they took down Beta 4. Important info for getting this to work since manually setting things up works awfully for me, all due respect to the attempt here by @closms ( #528 (comment) ). Does anyone have a copy of 2.5 Beta 4 they'd like to host so we can point the installer made by @cab4444 to it instead of the broken google drive link? |
Currently blocked by #543 |
Contributors should start submitting patches in anticipation of #582. I'd like to get an experimental release out that we can move to stable as soon as Proton 9.0 is out of beta. |
I was able to get starfield working by using @cab4444 s fork, with these additional steps: I edited gamesinfo/starfield.sh and edited the new sfse url to make it look like the following: game_steam_subdirectory="Starfield"
game_nexusid="starfield"
game_appid=1716740
game_executable="Starfield.exe"
game_protontricks=()
game_scriptextender_url="https://sfse.silverlock.org/download/sfse_0_2_6.7z"
game_scriptextender_files=( \
"sfse_0_1_2/sfse_1_7_29.dll" \
"sfse_0_1_2/sfse_loader.exe" \
) I then edited step/download_external_resources.sh and added the link to the most recent stable Mod Organizer 2 download: mo2_url='https://github.com/ModOrganizer2/modorganizer/releases/download/v2.5.0/Mod.Organizer-2.5.0.7z' After this I ran install.sh and installed as normal I then launched Starfield in steam with GE-Proton9-2
Mo2 was unable to find the Starfield install, so when it prompts for the path, I gave it the following:
make sure to replace with your actual home directory name |
Understandably the mod manager version for Starfield is the beta one. I´m trying to figure out how to do this myself, but I can't seem to find where you put the download location for mod manager in your script. I know how to add it as an option, but I cannot figure out the installer option
The text was updated successfully, but these errors were encountered: