Whenever I launch (Vanilla) Celeste through Olympus I get white screened. Everest still works just fine dough, and the only mods that I've installed are SJ and Save states. I tried uninstalling/reinstalling Olympus, to no avail. Any ideas on what I can do to try and fix this, or if more info is needed to pinpoint a possible problem?
#Launching Vanilla Celeste Crashes (White Screen of Death)
hushed swan
hushed swan
update: It seems to only white screen whenever I tab out of the game. Which is still quite impractical. My PC also doesnt seem to be able to "detect" it as a real application. OBS doesn't recognize it as an application, nor does it appear as something I can close externally through task manager. I tried out changing the Olympus version a few times AND launching through both the Celeste button on the Olympus page, and holding right on the Everest title screen.
I dont have a crash log because I quite literally cannot see one/access it because my computer completely dies whenever it white screens, forcing me to restart.
unless there is some way to see a log history or something where I can see its history
thorn shell
update: It seems to only white screen whenever I tab out of the game. Which is s...
to be clear, you're talking about celeste and not olympus, yes?
hushed swan
yes
Olympus works just find, and I can launch Everest and play modded Celeste just fine. But when I go to try and play unmodded is when the issues come up
thorn shell
Olympus works just find, and I can launch Everest and play modded Celeste just f...
and you have everest installed, right
you got celeste from steam?
hushed swan
yes
thorn shell
okay so your vanilla is xna
you clicked yes when installing everest for the first time?
hushed swan
I am not sure, it was a while ago. How can I check?
thorn shell
open the game files and open the orig folder
does a small arrow show up next to the Saves and Content folders inside?
hushed swan
yes, up right diagonal
thorn shell
the arrow direction doesn't really matter, it just matters whether it is there
so you did click yes
okay
i'll need you to do the following:
- verify game files
- delete the orig folder from the game files
- switch to the opengl beta (aka fna)
- reinstall everest
sudden shadowBOT
Steam Instructions
Epic Games Store Instructions
If you have Everest installed, you will need to reinstall it after verifying.
hushed swan
ill try that, just to clarify do I need to uninstall Olympus, or just Everest?
thorn shell
ill try that, just to clarify do I need to uninstall Olympus, or just Everest?
verifying game files uninstalls everest by definition
hushed swan
ok so I can reinstall Everest through Olympus?
oh i seeit
does removing the files cause any problems?
thorn shell
does removing the files cause any problems?
nope
this warning is only applicable for old old everest versions but these don't apply anymore
hushed swan
so I should remove the files then install? or just install just toclarify
thorn shell
you should remove them yes
hushed swan
so then this should be yes then? (sorry if this is obvious, I am overly cautious/double checking)
thorn shell
so then this should be yes then? (sorry if this is obvious, I am overly cautious...
yes
well both yes and no will not affect how everest works
all this does is this
sudden shadowBOT
As of the Everest Core update, Everest tries to create symlinks in order to share these two folders between the vanilla and modded installs of the game:
Saves, to sync save data between vanilla and moddedContent, to avoid making a duplicate of all the game assets and save about 1 GB of storage space
However, creating a symlink requires admin privileges on Windows. Installing Everest will still work if you choose not to give admin privileges, but you won't get the benefits listed above.
Creating the symlink can also fail on external drives that use non-NTFS filesystems (such as some flash drives). Installing Everest 4482 or later will still work on these filesystems, but data will not be shared between vanilla and modded. If this is an issue, moving your Celeste install to the C drive should fix it.