Closed GenghisSwan10 closed 2 years ago
Now I’m getting the same shit where it says installing, pops up a window, then closes
Go to ~/.config/steamtinkerlaunch/mo2/compatdata/pfx/drive_c/Modding/MO2
and see what exists.
I'm not sure why it's having so much trouble installing to be honest :frowning:
All it says after typing that is Invalid Protocol
Don't type it in, go through the folders one at a time :smiley: Not all of those folders might exist. Follow them one at a time, start from ~/.config/steamtinkerlaunch
and click into each one that exists. So if mo2
exists (which it should), click that. If compatdata
exists, click that.
I'm sorry to say that I'm running out of ideas, so I might have to leave it at least for now. Maybe someone else will be able to take over.
For anyone looking into this, the problem is that SteamTinkerLaunch's MO2SETUP
is not being set for some reason. Then, MO2SPATH
is not being set correctly as a result, which is the blank ''
in the last line of the log:
Mon Sep 19 07:51:32 PM CDT 2022 INFO - StatusWindow - for 'Installing 'ModOrganizer''
Mon Sep 19 07:51:32 PM CDT 2022 INFO - getLatestMO2Ver - Search for latest 'Mod.Organizer' Release
Mon Sep 19 07:51:33 PM CDT 2022 SKIP - dlLatestMO2 - No MO2SETUP defined - nothing to download - skipping
Mon Sep 19 07:51:33 PM CDT 2022 SKIP - installMO2 - '' not found - nothing to install - skipping
Those seem to exist. What now?
Also I really do appreciate all your help
What is the contents of the last folder you can get to? A successful MO2 install at ~/.config/steamtinkerlaunch/mo2/compatdata/pfx/drive_c/Modding/MO2
would look like this:
I would guess that either the MO2
folder doesn't exist, or that it is empty.
Also I really do appreciate all your help
No worries, as mentioned STL and MO2 (even on Windows) are tools for advanced users, but hopefully eventually we can get this sorted.
Last one I can get to is drive c
Oh, that's really strange. That doesn't even look like the Wine prefix finished setting up...
Can you run your game with SteamTinkerLaunch again, then click the "MO2" button, wait about a minute, then close your game and attach your /dev/shm/steamtinkerlaunch/steamtinkerlaunch.log
file? For a more up-to-date look at how the logs are and to once again try and document what is going on and why MO2 is failing to install.
This is all that pops up now
That menu you are using is not meant for opening files. It is one of the things it can do but that is not where you primarily should be searching for files or folders.
You can go to this location from Dolphin, the file explorer. Go to /dev/shm/steamtinkerlaunch/
and attach the steamtinkerlaunch.log
file, just like earlier :smile:
Thanks. For some reason, STL is failing to see that MO2 is downloaded. I'm not sure why this is happening. There is definitely a file in ~/.config/steamtinkerlaunch/downloads/mo2
, correct? This should be the MO2 installer that gets downloaded but for some reason STL is falling over for you.
EDIT: Based on what we discussed earlier I thought there was a file there, but looking at the code, it seems like there shouldn't be any downloaded file.
I’m gonna go to bed but if we could continue this tomorrow or something I’d appreciate it! I get off work at 1 PM
No worries, I'm hoping someone else can chime in because I'm kind of out of ideas. For some reason, MO2 isn't downloading. I wonder if maybe one of the variables like the MO2DLURL
isn't set correctly for some reason.
It's something to dive into at a later date, hopefully with someone who knows a little bit more about what's going on than me :)
Btw, typed that all in and it says invalid protocol. Night!
Remember to use your file explorer instead of typing that into Kickoff (the search bar menu coming up from the bottom left of the screen you showed before)!
I am not trying to be rude in any way as I also appreciate your patience, but I will warn you that Mod Organizer 2 is quite a complex tool and modding games in general can be quite involved. This can be quite intimidating for someone who is new to modding let alone someone new to PCs. Please be sure you're willing to spend the time troubleshooting modding issues with games. Things like game updates can break mods entirely and you might have to spend several days trying to fix your mod installs - This is not a Steam Deck thing in fairness, this is just simply how it goes when modding games.
I would take some time to learn how to use the filesystem on your Steam Deck and get used to it, as you'll be spending a lot of time juggling files and looking around different paths. Mod managers generally expect an understanding of how to navigate the filesystem. Also be aware that many modders will expect you to be using Windows and so you'll need to know where to find different files on Linux/Steam Deck.
This tinkering side of the Steam Deck somewhat expects an awareness not just of PCs but specifically of Linux. Valve have done a great job at making the Game Mode experience seamless imo, but when it comes to modding even on Windows you're kind of expected to be doing so at your own risk. Also, I haven't ever encountered this myself, but some mods might not work on Linux. I've used quite a lot of mods for various games (Fallout: New Vegas, Fallout 4, Skyrim Special Edition, Oblivion, Mass Effect Legendary Edition, and more) and I haven't run into any mods that don't work on Linux, but it could happen. There is really no way to know what mods will and won't work until you try them, though. And some mods might require extra steps to get working on Linux, and mod creators may not provide you any support as their mods are likely targeted at Windows users.
I am not at all trying to belittle you or shame you, we all get our start with PCs somewhere, and we all started as beginners! I am also not saying you shouldn't mod your games. I'm just offering a suggestion that you might want to take a little bit of time to familiarise yourself with how SteamOS works on a technical level.
It appears there could be some kind of issue with SteamTinkerLaunch but I believe others have gotten MO2 to work with STL in the past, so someone else will have to take a deeper dive (I don't use MO2 on my Deck). I am not totally sure if it's specific to SteamTinkerLaunch yet, I'll have to wait for someone else to take a look.
I just don't want it to end up that you've gone through so much to get MO2 to work, only to end up having your mod installation end up being a trying process as well. Learning this sort of thing comes with time and just as you've said I've been patient, you have also been patient. So I am just offering some advice, that MO2 is for more advanced users and you might want to take some time to learn the more advanced aspects of tinkering with your Steam Deck before delving too deep into tinkering with mods.
Just once again for anyone looking into this as I am not sure what the problem is or where else to go from here:
STL can't download MO2 on Steam Deck for this user. It shows the following in their logs when they press the "Mod Organizer 2" button from the main menu or when they try to run ./steamtinkerlaunch mo2 install
:
Mon Sep 19 10:18:28 PM CDT 2022 INFO - StatusWindow - for 'Installing 'ModOrganizer''
Mon Sep 19 10:18:28 PM CDT 2022 INFO - getLatestMO2Ver - Search for latest 'Mod.Organizer' Release
Mon Sep 19 10:18:28 PM CDT 2022 SKIP - dlLatestMO2 - No MO2SETUP defined - nothing to download - skipping
Mon Sep 19 10:18:28 PM CDT 2022 SKIP - installMO2 - '' not found - nothing to install - skipping
SteamTinkerLaunch cannot properly set the MO2SETUP
variable in the getLatestMO2Ver
function, which causes dlLatestMO2
to fall over and thus installMO2
doesn't work either.
Wow, just 120 mails for one issue in one night! 😀 Can't thank you enough for your continuous patient and friendly support, @sonic2kk 👍 I haven't read the whole backlog so thank you so much for the summary as well.
Did you already check:
grep MO2DLURL ~/.config/steamtinkerlaunch/url.conf
?
Either way, I'll add some more verbose logs soonish
(steamtinkerlaunch could really use some more modders helping each other...)
Alright, I’ll be at work but if anyone can contact me on what to do next (later ofc) I’d very much appreciate it! Whenever anyone has time
And yes, I totally understand that it’s a learning curve. I’m willing to dedicate anything and everything to be able to mod my games.
Alright, I’ll be at work but if anyone can contact me on what to do next (later ofc) I’d very much appreciate it! Whenever anyone has time
you might want to start with answering
Did you already check:
grep MO2DLURL ~/.config/steamtinkerlaunch/url.conf
?
You might have missed the commit I added above, so a new log from a fresh try (so with a clean ~/.config/steamtinkerlaunch/
and /dev/shm/steamtinkerlaunch/
) using latest git master could be helpful as well.
So just launch the game and then give you the log or? Also what do you mean by latest git master?
1) open a terminal and execute
grep MO2DLURL ~/.config/steamtinkerlaunch/url.conf
If your config is not broken it should return a proper url.
2) git master is the latest revision of the project. As you're running steamtinkerlaunch on the Steam Deck it will automatically pull the latest revision (=git master) automatically. So basically:
remove (or rename if you think you already configured important things in steaminkerlaunch
) both ~/.config/steamtinkerlaunch/
and /dev/shm/steamtinkerlaunch/
, then start your command and then upload the fresh log.
instead of launching mo2 via gui you can as well simply
cd /home/deck/stl/prefix/
and
./steamtinkerlaunch mo2 install
as @sonic2kk already said before
Right, I was thinking when I went to bed last night that we should've tried deleting the /dev/shm/steamtinkerlaunch
folder when reinstalling.
When you have a moment, please answer Frostworx, and after that we can work on updating STL and getting more logging.
if you can delete these folders please, it's easier to do this from your file manager rather than from the menu in the bottom left (called Kickoff):
/dev/shm/steamtinkerlaunch
(just that folder called steamtinkerlaunch
) - This is where STL stores some data files ~/.config/steamtinkerlaunch
- this is where STL stores some config files~/.local/share/Steam/compatibilitytools.d/steamtinkerlaunch
- This is where Steam runs STL from~/stl
- This is the actual SteamTinkerLaunch "installation"After this you can delete the SteamTinkerLaunch folders in your Downloads folder.
Next, you'll want to redownload STL. You might already be familiar with how to do this but here's a rough set of steps: download the latest Git master release of STL. Go to the project home page and click the green "Code" button, and click "Download ZIP". Then you can extract the zip, open the folder from your file explorer, right click inside it and select "Open Terminal here". Then you can run ./steamtinkerlaunch
.
And now you can restart Steam. To do this, right click on the white Steam icon on the bottom of the screen in your panel and select the option to the effect of "Exit". Give it some time to exit, then open Steam again by clicking the Steam icon on the desktop, or opening it from your application menu (the button in the bottom left). You might have to search for it.
You have to restart Steam to make the SteamTinkerLaunch compatibility tool show up.
Side node: When Steam is closed the controls for your Steam Deck will be slightly different. During tinkering if possible I recommend plugging in a keyboard/mouse to your Deck, but it isn't strictly necessary. It should just make life easier.
Once Steam has been restarted you can run your game with SteamTinkerLaunch again. Click on the MO2 menu button, wait a little while, then close your game. Now attach your SteamTinkerLaunch log, located at /dev/shm/steamtinkerlaunch
.
This will update STL and give us a log with the updated STL logging, which should help us debug further.
Oops we responded together, sorry for the info overload both of you!
Thank you for your invaluable detailed and patient support again and again, @sonic2kk! 👍
So follow what Frostworxx said and then do what you said, Sonic? Got it. Will update you guys once I’m home
@GenghisSwan10 It seems like there might be an issue with installing MO2 with SteamTinkerLaunch in general, not relating to Steam Deck specifically. Someone reported having issues on an up-to-date Linux desktop as well.
Almost home. Lemme get settled then I’ll update
It seems like there's a general bug with STL and MO2/Vortex. It can't fetch thee download executable from GitHub anymore because GitHub changed how they lay out the page.
I'm currently experimenting with a potential way to fix it. No ETA yet though :sweat_smile:
@frostworx doing this right?
@sonic2kk understood!
Also when I try to close it this pops up
That indicates that a process is still running, maybe give it a bit.
But so far so good yes?
Also nothing has happened yet just as an FYI ^^
I think you're good so far.
However I don't think it's as important to submit a log. Two others have submitted logs, with one being on the Linux desktop, and I've got to what I believe to be the core of the issue. GitHub changed and so we have to change how we get the MO2 version. Thankfully, this means the issue is entirely unrelated to the previous MO2 installation.
I am currently working on a fix. It should hopefully be ready tonight and merged in sometime in the near future, once Frostworx has time to review it.
Thank you for all of your patience my friend! And thanks for opening the report, thanks to our debugging efforts last night I was able to figure out why MO2 wasn't working.
You can go ahead and follow the rest of the steps if you wish, it wouldn't hurt to have your updated log, but I don't think it'll tell us anything we don't already know.
I am hoping this will be fixed within a couple of weeks, it'll just depend on how long it takes me to implement the fix and how long it takes me to get it up to a standard to be included in the actual project (I'm not the STL dev, just an active user of STL :smile:)
Omg so it’s basically in the bag? That rocks! Will you guys email/update me when it’s ready?
Also a huge thank you to you both. Really.
(Can I exit out of Konsole? It’s still giving me that window saying that it’s running)
You can exit out of console, no worries :smile:
Omg so it’s basically in the bag? That rocks!
In my local testing branch (only on my PC), I have fixed the MO2 download. Didn't test on Steam Deck, but once I get Vortex working it'll go up in a Pull Request. That basically means Frostworx, the creator, can look through the code and make sure it's acceptable to get merged.
This is the process that can take the longest, as the code has to be fairly solid. Feedback will be given and we'll eventually reach a resolution that hopefully resolves in merging in. If the solution I have is, for any reason, not ideal, the PR can be rejected and we'll have to look into getting the problem fixed in another way, but I'm quietly confident in the solution I have :sweat_smile:
Will you guys email/update me when it’s ready?
Most certainly friend, I'll give you an @ on this issue when the bug is fixed. It's going to depend on schedules, but I am hoping that this will be merged sometime in the next couple of weeks. Once it's fixed, you'll just have to run SteamTinkerLaunch again on your Steam Deck, and it should automatically update! You'll know it's updated because it'll have an updated version (v11.1.20220920 is the current version, so if the version is higher than this, you're using the latest version).
If you're using a version that is supposed to have fixed it and you're still having issues, feel free to report back here.
I'm going to leave the issue open and tag this and #591 as the issues that my upcoming PR closes. After that it'll be closed.
Phew, this has been quite the journey. I'm gonna get Vortex fixed then get the PR up ASAP! Hang tight, it should be fixed in the near future.
Hey @GenghisSwan10, the issue has been fixed in the latest STL git! If you run SteamTinkerLaunch again on your Steam Deck and verify that the version ends with 20220922
, you can try to install MO2 again!
A few caveats to note:
Good luck and happy tinkering!
Well spoken, @sonic2kk! 👍
git master is already on v11.1.20220922
though 😀
Oops! Updated my comment, thanks for the correction :smile:
Will update once I am home! Big ups to all of you!
So every time I try to play it, it keeps saying Cyberpunk has flatlined and crashes. Maybe I have too many mods?
It doesn’t look like any of my mods are having a conflict tbh. Downloaded LOOT but I don’t see it.
This probably isn't a SteamTinkerLaunch issue, so we can't give you much help, sorry. However I can give some general pointers.
Make sure you're launching MO2 correctly via STL, that is only trying to configure games when running MO2 by pressing the button on the Main Menu, and only trying to launch the game when you're running MO2 after pressing the STL "Play" button (when you get promoted for "MO2 GUI").
Also, it looks like you're in desktop mode. When you're done configuring your games, you can and should launch your games via Game Mode.
Outside of that, make sure you installed your mods correctly, and MO2 should come with LOOT so you don't need to install that. Also see if anyone has had any issues using the mods you're trying to run on Linux, and if they were able to resolve them.
LOOT should be listed if you click on the executables dropdown on the right hand side. See if you can find and read up on any MO2 tutorials to learn how to get started. SteamTinkerLaunch is not really affiliated with MO2, we just try to bridge the gap to get it installed. After that, users are expected to know how to mod their games.
I'm glad you got MO2 working at least! But we can't really help you any further, you might want to ask around online for some advice.
Happy tinkering!
Well it crashes in Game Mode as well
Hello all. I recently downloaded SteamTinker Launcher on Steam Deck to mod Cyberpunk 2077 via Vortex. When Vortex didn’t work, I resorted to Mod Organizer 2 (which someone recommended). I am able to launch the menu successfully, but when I try to install MO2, it pops up a window then immediately closes it.
I should add I’m very green to modding/PCs in general. Is there a way to fix this. Launching vortex works fine, it’s just that I can’t use it.