#Everest crashing on startup on Steam Deck
94 messages ยท Page 1 of 1 (latest)
I was wondering if anyone can help me with information on how to install Olympus on steam deck
Please help ๐ฅบ, with the steam deck is my first time using Linux os so i don't even know how to install Olympus on it
Please make a separate help post rather than tagging on to someone else's
Sorry, i didn't know that
I've attached the log here. The error is a "Too many open files" exception. I looked this up on the Everest resources, and the only advice for this is to make sure the mods are in zip files. All of the mods I have were installed through Olympus and are already in zip files; I have a few dozen (most of which are dependencies), but not a number that should be unreasonable (nor, I think, as many as work completely fine on my desktop PC).
Any advice here would be appreciated.
Try the fixes in the comments of this issue
So I'm trying that, and as far as I can tell, it's not working. That said, the only way I can find to directly set MONO_MANAGED_WATCHER is in the terminal using export, which I don't think saves it systemwide. As I understand it, to do that, I would have to put the line in etc/environment, but as far as I can tell that's read only and I have no idea how to give myself the permissions to do that
I'm not the most experienced linux user
I've been trying for the last half hour to set that variable unsuccessfully and I can't find any direct information on the matter that isn't for much more experienced linux users
I am not that experienced with linux either, but if you want to edit a file you don't have permissions for, you use sudo
So I ran "sudo vim environment" in the folder, and it opened, but it still doesn't let me actually type or do anything in the file
Just to check, do you know how to use vim
Oop, it seems the keyboard had just locked up at an inconvenient time, which is annoyingly frequent in desktop mode. It seems to be working now
Awesome, hopefully this helps
Not really lol but for basic text editing I've done it successfully a couple times. I'll try this now!
Alright, was just making sure you weren't stuck in the wrong mode or something
Okay now it's not letting me save. "Could not write to /etc/environment.part"
That sounds like the same permission error, which is weird
Yeah, and this was opened with sudo (I switched to nano because i really dont get vim lol)
I would have done the same tbh
Wait, I just remembered. I think the Steam Deck has a lot of the system folders set to read-only by default. This can be disabled to edit them, but the changes can be reverted anytime there's an update
If that doesn't work out for you, I have another idea
What's your idea? I'd rather do the readonly stuff as a last resort because I don't want to have to do this every time there's an update
Could you try going to your Celeste installation folder, then setting the variable with an export command, then running Celeste from the terminal
you could always run celeste with MONO_MANAGED_WATCHER=whatever path/to/Celeste
Yeah, that basically
I couldn't remember the syntax for doing that in a single line
if the celeste folder itself is read-writable, you could add the export command to the Celeste shell script, which i'm pretty sure is what actually launches the game
just tried "MONO_MANAGED_WATCHER=disabled ./Celeste", no dice ๐ฆ It still crashes right after the EXOK logo
Could you run ulimit -n and see what the result is
are you sure you can't set it higher?
According to that issue linked earlier, you can put a number after the -n to change it
Don't know if it goes up though
Ohhh whoops. I missed that, sorry ๐
Trying now
Okay it looks like the number went up. Lemme try now
yea, there's a soft limit and a hard limit (i.e. a limit for the soft limit)
you can change the hard limit by editing a config file somewhere, but you might not need to
https://stackoverflow.com/questions/34588/how-do-i-change-the-number-of-open-files-limit-in-linux/
Why is there a limit at all? Just to stop a bugged program from causing chaos?
if this works, you can put the ulimit -n <num> at the start of the Celeste file (just after the cd is probably a good place) to have it run for each celeste launch
Okay I set it once and tried it, and it wasn't enough. Now I'm trying and it's saying "bash: ulimit: open files: cannot modify limit: Operation not permitted"
you'll have to change the hard limit then
does the file /etc/security/limits.conf exist? is it writable?
The issue wasn't that the hard limit was too high, it seems. I just restarted the steam deck and tried again, and it works. It looks like I can only change ulimit once per session.
The first one worked and it gives me the error every attempt after that
hmm interesting
does doing this ^ work?
I've tested this on a laptop I have, and it seems I can raise the ulimit once, but lower it as many times as I want
Okay well instead of crashing now the game just freezes up on the loading screen
progress
Freezes completely? Or takes a very long time?
Granted it could take a very long time. But after a full minute of zero animation or audio whatsoever I'm concluding it's just frozen
Okay, yeah, zero animation sounds like it's frozen
can you send log.txt?
Yep. I'm trying this one more time on a much higher ulimit, and if it doesn't work I'll send the log
Nope, it just crashed again lol
Gimme a minute to get the log sent
still System.IO.IOException: Too many open files
maybe try with, say, only one mod enabled?
Okay. Lemme try clearing out the mod list
Okay clearing out like 10 mods worked
I accidentally started celeste in that interim but yeah, it worked lol
ok i guess it was still ulimit or something. on my computer i have it at 1048576; what happens if you try to load eg. spring collab & dependencies with that ulimit?
ah. have you tried setting it equal to the hard limit?
I was still getting crashes at 500000 (that was before i knew my hard limit was around 502000)
ouch. might just be a limitation of the steam deck unless you want to raise the hard limit
idea: try making ulimit really big, and also setting MONO_MANAGED_WATCHER=disabled
Okay. I'll do the thing where I insert those at the start of the celeste script
Do I set that latter one with "export MONO_MANAGED_WATCHER=disabled"?
oki
So editing the Celeste file has turned it into a text file and it no longer executes
How can I change it back?
chmod +x Celeste
That didn't seem to do anything :/
um okay
apparently nano just inserts a line
at the top of the file saying it was modified by nano
And that's messing everything up
I have no idea how to fix that
o wait
that only saved the output of the console that was visible
not the file itself
Alright, it appears to be working!
Setting the ulimit and using export MONO_MANAGED_WATCHER=disabled in the Celeste script file appears to have worked ๐
I have a pretty wide smattering of mods here, including the winter and spring collabs, and the game launched successfully even after installing all the dependencies
Thank you @pine lance and @proven garnet for all the help!! ๐