StupendousMan
Published
The game's servers have been turned off, so the official game is no longer playable.
Project Celeste is a continuation of the game, and can install on top of the Steam installation and be made to work.
The display settings can get weird after changing them (1080p can just center in the middle of a 1440p screen, even on fullscreen), but everything is fine (and the settings are accepted) after restarting the game.
Controller must be on before the game is launched, and if it gets disconnected, game must be relaunched before controller can be reconnected.
If the Uplay overlay is opened, it works, but upon closing the overlay, the overlay graphics just sit on top of the game making it unplayable. Best to just disable it.
Uplay may require being relaunched after logging in the first time.
The game can't be launched from the Uplay client that gets installed, the play button in Steam must be used.
Uplay also doesn't quit on its own, it has to be quit manually (or via the Steam "Stop" button) in order for Steam to register the game as not running.
Lack of cutscenes are disappointing, but there aren't many, and the game is plenty fun without them.
I have audio crackling in many proton games, probably an issue with my system
Cutscenes don't play, occasional graphical stuttering
I had occasionally soft freezes, where the game refused to advance. Seems to be a Windows bug as well. I believe saving before getting to the issue and rebooting fixed it.
The window hung when clicking exit, had to kill process using task manager
I had to create the full engine.ini file from a comment on the issue on github https://github.com/ValveSoftware/Proton/issues/641#issuecomment-627059621 (use the full details section). No commands needed.
Had to use downgrade nvidia driver to 435. Doesn't seem to work on 440.
Overworld is very laggy sometimes
The files download, but the install window hangs on "creating local game files...", and clicking cancel uninstalls the game.
Works perfectly with GE. Menus wouldn't respond to clicks on first launch on Proton Experimental.
Proton-6.9-GE-2 GloriousEggroll
Proton-6.9-GE-2
Make sure not to launch with a different proton version first. If you do accidentally (like I did) you have to wipe your prefix in compatdata before you can get the game to work, you can't just switch to the right GE.
6.9-GE-2 GloriousEggroll
Crashes started out occasional, but then became more frequent, possibly related to my upgrading from Kubuntu 20.04 to 21.04
The crashes I'm currently experiencing are incredibly annoying, especially since you can only save in specific places.
6.10-GE-1 GloriousEggroll
6.9-GE-2 ran, but with quite a few crashes. Haven't had a single crash since switching to 6.10.
Don't use regular fullscreen, and the game will work great.
Fullscreen crashes with Alt-Tab, Borderless Fullscreen works fine.
taskset -c 0-6 %command%
Native version needs "taskset -c 0-6 %command%" in the launch options to stop frequent crashes. It runs perfectly if the command is added.
A couple of the main menu graphics don't clear properly (while in the main menu), but the main menu is still perfectly usable, and everything else seems to work perfectly.
Graphics are messed up in fullscreen, press alt-enter to go into windowed mode, where the game works fine.
If using fullscreen mode, leaving the window and coming back makes mouse clicks not register. Everything runs fine windowed.
Pretty quiet and ignorable, but occasionally mildly annoying.
--skip-intro must be set in launch options, otherwise the game crashes with an unhandled exception on launch
Once I got the font installed, the game worked great. There was lots of water coming out of my eyes, but I think that's a feature.
I installed VL Gothic on my computer to get a compatible font
On first launch, there was a grey rectangle in the middle of the screen. Upon closing and reopening, it went away.
Without installing the new font, text was missing.
Right-clicking caused input to be ignored until I alt-tabbed out and back in.
