I have no problem launching Everest, but when trying to launch normal celeste the game doesn't doesn't open. When launching via Olympus steam detects the game starting, but just reverts to the green start button after ~10sec. Meanwhile steam doesn't even detect the game launching when trying to start it from the ./orig path itself. Switching to normal Celeste inside Everest doesn't do anything either. There is also no log generated (I assume LogHistory is the only log folder?) for launching normal Celeste. Validating the game via steam fixed the issue, but it of course also uninstalls Everest and reinstalling it also causes all issues to return.
#Can't launch from orig/celeste.exe
61 messages · Page 1 of 1 (latest)
idk, just want to say that log.txt is generated by everest, and LogHistory has old logs, latest one is in root folder, next to celeste.exe
two questions:
- what OS are you on?
- what everest version are you using?
thanks, for pointing that out, the log only contains stuff marked 'everest' though
that's because vanilla does not generate any log
I am using windows 10, and everest version 4467-azure-52f83
thanks, will downpatching break anything?
did I acidentally install a beta or smth?
you're on latest beta
which is newer than latest stable so that should be fine
you may want to attempt to run the orig/Celeste.exe via the command line, but im unsure of how easy is that
just uninstalled everest to downpatch
so we can get stdout logs, and see whats up
what if they verify game files, delete the original folder, then reinstall everest
they did that, issues came back
wdym
verifying game files doesn't delete the orig folder
i'm assuming something's wrong there
just do this 
Steam Instructions
Epic Games Store Instructions
If you have Everest installed, you will need to reinstall it after verifying.
once you verify game files delete the orig folder in your celeste files
i love repeating what other people have already said 
then reinstall everest
gimme a sec I'm still trying downpatching
right Downpatching to stable didn't work and executing from command prompt behaves a lot like executing from windows file manager
will try a complete reinstall now
can you please 
fresh install seems to have done it, though none of the mods reinstalled this time so I hope the issues don't happen again as soon as I reinstall stuff. (accidentally reinstalled into a different folder than the my original installation)
thanks for the all the help
that definitely sounds like my suspicions about a broken orig folder are confirmed, which is why i suggested that 
yeah sorry I didn't really know what you meant with deleting the origin folder so I just reinstalled
many thanks everything is now working even with mods
yeah sorry 😓 also it seems that the difference between the two directories seems to be that the old orig dir seems to have something called monomod installed do you have any clue what that might be?
monomod is the framework and toolset everest uses to inject itself into celeste
@spring parrot
why and how was this in orig though?
I mean at least it's pretty clear what the issue was now
im not sure
miniinstaller probably threw everything that was in a legacy install into orig
i don't think it does tbh
(for some reason)
or I did something stupid while trying to install something else
can't remember but that's always the likeliest option
or not, reading Backup in miniinstaller code shows that it does a selective backup
then you may have modded the orig celeste.exe accidentally or something along those lines
yeah probably
oh I'm stupid I didn't use diff recursively so there may have been other stuff that's different
anyways imma stop wasting your time now
nah dont worry, i dont have anything to do either 
yeah I realised that the stuff wasn't what caused the problem weirdly, the version of Everest that was half installed was stable while it was originally running beta