Mr_Hosed
Published
Title says it all. Game kept crashing with a g_mLocalToClip error when I tried to run it in Debian Steam.
I'm pretty sure it just required overwriting/installing VC Redist 2010 SP1 into the instance, but I tried it in Flatpak steam first and it just worked. No tinkering at all.
Replace Uplay with UConnect, login once without command line, login again with, everything works like native
uplay://launch/4
The Game package hasn't been updated to Uconnect and still tries to run/install UPlay. This means you need to update the wine instance with the files from a successful uconnect install.
1.) Install and run without any changes at all (no command line, etc). Will fail at Uplay trying to connect.
2.) Delete UPlay Files and Copy UConnect files in it's place. I did this by installing uconnect in Lutris, navigating to program files (x86)/Ubisoft/ etc, copying the Launcher folder directly into your Steam install of Creed at the same location.
3.) Launch Creed again (still no cmd line) and link the game to UConnect after logging in. I found that Creed would still crash/stall at this point and forced it to stop.
4.) Add in the command line option above and relaunch. Creed should now run perfectly.
I'm currently doing this for all my UConnect game installs to make them work.
Note: There is a strange issue where, because you're launching UConnect through the proton profile in steam, UConnect stays running and the game doesn't "Stop" running until you force it to through the steam client using the stop button.
Installs and runs with zero issues. I did disable the Steam Overlays (always do this) and forced the Compatibility mode to use Proton Experimental.
The game has a Legacy mode, but I haven't tried it.
Runs perfectly in 16:9 mode.
The reviews actually show this doesn't run worth crap on modern Windows so Linux seems to be the preferred way to play these days.
Works the same as on Windows... which requires bypassing the dumbest DRM ever made
Game requires editing the Setting.lua file by replacing -- with just spaces and disconnecting from the internet to play. This isn't unique to Linux, but what's required on Windows as well.
Game isn't really recommended in general (didn't have a lot of fun with it), but if you have and want to play it, well, it works.
Proton 3.16 fixed all the issues the native client has.
The Native Client is buggy as hell. Weird halting start-up and you cannot exit the game. Alt-F4 or hitting "Stop" in steam was the only way to exit.
Proton 5.13 crashes on start (like it always seems to), but I saw another user reporting success with 3.16 and that worked for me as well. No idea why, but I've ran into this on most games. 3.16 works well, but newer versions don't...
Through Proton none of the bugs appeared, the game ran smoother, started correctly,, and the exit button actually worked.
Make sure to start with the "-windowed" Launch option to configure the game for my resolution in full screen mode.
Game is a modified version of Source.
Basically works out of the box with the .deb based Steam install using Proton 8 once you figure out how get past the start-screen crash.
gamemoderun %command% -offline -offline_mode
If I don't alt-tab out during start-up, the game crashes when moving past the starting screen. If I alt-tab out and back in, no problems at all.
I haven't tested if I the -offline -offline_mode flags are needed or do anything, but I've played the game 4+ hours straight and never had a crash while using them so...
Works Well out of box as long as you can handle 30 FPS
This is not a Linux/Proton issue, the game is just unstable unless you frame-lock it. I set it to 30 FPS using the game's own options menu and had no problems at all, but you would get "hiccups" in during cut-scenes that would have crashed the game at higher FPSes for me.
Seems to be very hardware dependant, but Naughty Dog is notorious for buggy crap like this in their games so...
Like before, the game was designed for specific hardware at specific frame rates for stability in the graphics engine and the port to PC didn't really account for both lower end and higher end hardware. This causes stability issues at higher framerates as it borks the caching/streaming of assets, especially in cut-scenes, unless you set it to 30 FPS.
At 30 FPS I never had an issue both in performance and in stability, just that I really do prefer 60 FPS for my games (being a First Person Shooter gamer and all). Since it's a third-person view though I didn't get the head-ache I usually get at 30 FPS in most games.
It's a very low-resource pixel-art game so once you get the right Proton version selected everything seems to work as in native windows.
Game doesn't switch to it's Window on start-up and sometimes requiring switching back and forth with other windows before it properly displays.
Alt-Tabbing also doesn't seem to properly focus the window.
