I am trying to install celeste arm64. I patched it with celeste-arm64 :https://github.com/pixelomer/Celeste-ARM64, and it works when i run the commands in wsl. However, when i move the files to my switch and try to run the commands, i get the error command not found
#Celeste ARM64
172 messages · Page 1 of 1 (latest)
yeah
i think
im new to linux
only have it to run this
it works in wsl
everything installs fine
that's not wsl, that's just plain bash
..why are you running celeste via wsl?
you really shouldn't be doing that
i will not in the future
anyways
does ./Celeste have the execute permission
do ls -l ./Celeste inside the celeste folder
still get command not found
don't sudo it
can you ls -l ./Celeste again
still the same thing
im not getting a response from chmod cmd
do you want me to redo the patch
you're not supposed to, it's supposed to just run
when i run 'ls -l ./Celeste' I still get -rw - r - - r - -
this is what you're supposed to get
is your storage read-writeable
what does df -PTh say
oh wait
hold on
i did it after moving it from mmy sd card to my desktop
now i get
the sd card might not be formatted as ext4
yes
yes
i think its working
its installing stuff now
thank you so much dude
i dont really know what im doing i just want to play celeste on vacation bro lmao
fyi this is how you read unix file permissions; let's take rwxr-xr-- permissions
- the first
rwxtriple means that the owning user (brite) has read, write and execute permissions - the second
r-xtriple means that the owning group (brite) has read and execute permissions - the third triple
r--means that others (so everyone else that's not the userbriteor not inside of the groupbrite) only have read permissions
In Unix and Unix-like operating systems, chmod is the command and system call used to change the access permissions and the special mode flags (the setuid, setgid, and sticky flags) of file system objects (files and directories). Collectively these were originally called its modes, and the name chmod was chosen as an abbreviation of change mode.
its just overwhelming for me as i am not super familiar
chmod stands for change mode (aka permissions)
the wiki page does a good job explaining unix permissions
i assume that permissions are like step 1 of troubleshooting or something?
files by default don't have the x permission
you have to explicitly give the execute permission via something like chmod +x file
oh i guess that makes sense
i followed the guide on their github
it wasn't super descriptive so ive been trying to do things by looking it up and whattnot
i got to the point of installing wsl on my own but got stuck once I was on my switch
i believe this might be a case of "this is too old"
everest has been recently updated in a big way the arm64 patch does not expect
i have no clue how the arm64 patch works
gotcha
i think i can find when it was uploaded to github and grab an everest release from then
right?
have everest
i got time on my paws- i mean hands

you should look at the page
it says that this needs to be done before moving it
if you think i should do it on my switch though i will
im down to try anything atp
wait what
can you possibly move it to somewhere else
onedrive tends to be super fucky and make things not work properly
i have no clue, sorry
all good
i think i can dm the creator of it on reddit should i encounter any more problems
the guide is just so bad dude its clearly made for people who have an idea about what theyre doing
that is kinda the nature
im lamenting my own incompetence
lol
not actually complaining
getting close
it started to boot and then gave me an error
said it was missing fmod
seems to be a consistent error
(that is likely because it skipped the fmod makefile)
crap
im completely out of my domain now
no idea whats being said in the issues or how to resolve it
maybe you could send a screenshot?
of the issue?
sure
do you want a screenshot of my error message from my switch?
yeah
this is what the issue says in response to my problem, however I do not know what is going on tbh
you are missing some libraries, either because those are not there, or because those have the incorrect name
so revise that
okay
@keen depot I got it working!
actually you did
the write permission wasn't on which made one of the steps not work
then I ran into another problem where a library was named wrong
ended up contacting the creator of the patch and he told me to run
ln -s libfmodstudio.so.13 libfmodstudio.so
to rename it
I guess

