Proton
Proton copied to clipboard
ValveSoftware
Cookie Clicker (1454400)
Compatibility Report
- Name of the game with compatibility issues: Cookie Clicker
- Steam AppID of the game: 1454400
System Information
- GPU: RX6800
- Driver/LLVM version: mesa 21.1.7
- Kernel version: 5.13
- Proton version: 6.3-6
I confirm:
- [X] that I haven't found an existing compatibility report for this game.
- [X] that I have checked whether there are updates for my system available.
Symptoms
- Game crashes on startup without launch parameters (all default). (Quite a few reports on protondb confirm this behavior, interesting: a handfull of people can run the the game as is, possible DE specific?).
- The game reliably starts up and works when called with
PROTON_LOG=1 %command%.
- The game reliably starts up and works when called with
- The game audio crackles from time to time.
- The framerate is lower than expected for such a simple Electron app.
I can't start the game as well, but for me using PROTON_LOG=1 %command% doesn't fix it.
PFA the generated log with Proton-experimental: steam-1454400.log. System info:
OS: Arch Linux
KERNEL: 5.15.0-rc3-1-mainline
CPU: AMD Ryzen 7 5800H with Radeon Graphics
GPU: NVIDIA GeForce RTX 3070 Laptop GPU
GPU DRIVER: NVIDIA 470.74
RAM: 32 GB
Game works out of the box for me with Proton 6.3-7 with no additional tweaks or launch options. There was some mouse offset when the game maximised but this was fixed by resizing the window. Fullscreen worked as expected. Only played for a few minutes as an initial test however.
System Information
- OS: Arch Linux (KDE Plasma)
- Kernel: 5.14.11-arch1-1
- CPU: AMD Ryzen 3700X
- GPU: AMD RX 5700XT 8GB
- GPU Driver: Mesa 21.2.3
- RAM: 32GB
Doesn't run for me, unless I run steam from the command line.
Proton Experimental.
The game recently started working for me with Proton GE fork. Still doesn't work with native Proton.
Can confirm slightly different behavior than reported: for me the game starts up, with audio, but not rendering anything (blackscreen) when not using launch options
but when using launch options PROTON_LOG=1 %command%, it renders and is playable
i also noticed that when trying to maximize on KDE Plasma (Wayland), the game resizes behind the taskbar, this could be worked around by moving the game window to another display, maximizing it there, and then moving it back with HOME+ARROW KEY(s)
Test were Proton Experimental (see details attached below for exact version) and Proton 6.3-8
Proton: 1640116296 experimental-6.3-20211221
SteamGameId: 1454400
Command: ['/home/hasezoey/mnt/sylvi_games/SteamLibrary/steamapps/common/Cookie Clicker/Cookie Clicker.exe', '--in-process-gpu', '--process-start-args', '-disable-features=HardwareMediaKeyHandling']
Options: {'forcelgadd'}
depot: 0.20211028.32
pressure-vessel: 0.20211027.0
scripts: v0.20210917.0-0-g1cf127d
soldier: 0.20211027.0 soldier 0.20211027.0
Kernel: Linux 5.15.7-1-MANJARO #1 SMP PREEMPT Wed Dec 8 10:09:19 UTC 2021 x86_64
Note: for the Command, i did not add anything other than PROTON_LOG=1 %command%
PS: Proton-6.21-GE-2 did not even start up for me
As a update: i currently cannot get the game (electron) to display anything anymore, only blackscreen From what i know the game did not update since last comment
Tried proton versions:
- Proton 6.3-8
- Proton 1642614452 experimental-6.3-20220119
- Proton 7.0rc6-GE-1
also tried applying PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1, with the same result
Well I have it probably the worst of you all. Game opens for me on experimental, same way as for others with PROTON_LOG=1 %command% otherwise it wont even load for me. However after running the game for some time my whole system crashes. Either just reboots or sometimes gets stuck (ex. if I have video running in the background it repeats last few seconds) until I manually hard reboot it.
I am 99% sure that its caused by Cookie Clicker, with it running my system would crash daily, sometimes even twice. Now few days without it everything seems good.
Proton log: steam-1454400.log
mono_crash.mem ? (not sure its related as I dont know how to open such file) mono_crash.mem.70407.1.zip
Unfortunetly journalctl just ends and then starts new boot so nothing that could help there.
Im running PopOS 21.10, with nvidia 2060 super. Hardware failure is ruled out, I did extensive testing of ram and my disks and still I would thing that it would crash more often if that would be the case.
My girlfriend cant run the game either on Ubuntu 21.10, even with PROTON_LOG enabled it wont even launch.
@pogof do you maybe know what the crash might be related to from the following?
- out of memory (sometimes Cookie Clicker just likes to leak memory)?
- graphical lockup?
- IO stuck (disk access)?
also, what is your environment: X11 or Wayland?
It should be X11 iirc. I do think it might be the memory leakage, but kinda haven't checked it yet. However even if that would be the case I dont think theres something I can do to fix that? Or is there? I genuinely dont know.
However even if that would be the case I dont think theres something I can do to fix that? Or is there? I genuinely dont know.
the simplest option is probably to have a resource monitor open and have a watch with that, and then stop and restart the game if it gets too high
note: i had the memory leak issue too (even made a "bug report" on steam forums, because i couldnt find the bug forum for CC anywhere else), but it does not affect me too much because of my 32GB ram (the game at most after ~10 hours consumed ~12GB sometimes)
Yeah, at 12GB at 10h mark seems like that is it as I have 16GB installed and 4GB if not more is used just idling. I will test it later today and report the results.
I think that there should really be some kind of check mechanism that would kill the process before it can kill the system. And especially now that CC is listed as working on Steam deck. I'm not sure if thats something possible to implement for proton.
After a update in shade cache, this game instantly crashes today, there was no proton, runtime, steam client or system package updates, only shade cache updates
Launch Options: PROTON_LOG=1 %command%
Controller Plugged in: None
System Information
Computer Information:
Manufacturer: MSI
Model: B150M MORTAR (MS-7972)
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: GenuineIntel
CPU Brand: Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
CPU Family: 0x6
CPU Model: 0x9e
CPU Stepping: 0x9
CPU Type: 0x0
Speed: 4500 Mhz
8 logical processors
4 physical processors
HyperThreading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Unsupported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Unsupported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Unsupported
AVX512VNNI: Unsupported
SHA: Unsupported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Operating System Version:
"Manjaro Linux" (64 bit)
Kernel Name: Linux
Kernel Version: 5.16.7-1-MANJARO
X Server Vendor: The X.Org Foundation
X Server Release: 12101004
X Window Manager: KWin
Steam Runtime Version: steam-runtime_0.20220119.0
Video Card:
Driver: AMD AMD Radeon RX Vega (VEGA10, DRM 3.44.0, 5.16.7-1-MANJARO, LLVM 13.0.0)
Driver Version: 4.6 (Compatibility Profile) Mesa 21.3.5
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 59 Hz
VendorID: 0x1002
DeviceID: 0x687f
Revision Not Detected
Number of Monitors: 3
Number of Logical Video Cards: 1
Primary Display Resolution: 2560 x 1440
Desktop Resolution: 6400 x 1440
Primary Display Size: 27.95" x 15.75" (32.05" diag)
71.0cm x 40.0cm (81.4cm diag)
Primary VRAM: 8192 MB
Sound card:
Audio device: Realtek ALC892
Memory:
RAM: 32047 MB
VR Hardware:
VR Headset: None detected
Miscellaneous:
UI Language: English
LANG: en_US.UTF-8
Total Hard Disk Space Available: 143964 MB
Largest Free Hard Disk Block: 93176 MB
Storage:
Number of SSDs: 0
Number of HDDs: 0
Removing the shadercache for this game makes it not crash again
PS: since upgrading to Proton 7.0 (Experimental), i have not seen the memory leak anymore (but this might just be a coincidence)
Hello @hasezoey, the behavior you've described could be a mesa issue fixed by https://cgit.freedesktop.org/mesa/mesa/commit/?h=21.3&id=fe18c96c86b7fcd39836c0915c806acc9a2039b8 in 21.3.6. Please update your video driver.
Please update your video driver.
version is currently 21.3.5-1 (pacman), with currently no update available on Manjaro 21.2.3
after the last 2 Proton Experimental updates i got, the game has become like 1 frame every minute, have also tried cleaning the shader-cache, with no improvement
Proton Experiment Log (via sshfs)
Once moving it to a local storage, it works completely fine again, so it is more of a case of #5563, though i want to note that it worked in Proton 6.x and earlier version of Proton 7.x (Experimental)
Steam System Info: https://gist.github.com/CorruptComputer/f164c2d48606808dbfbc07ee8810efd5
Game did not launch for me at first, had to add PROTON_LOG=1 %command% as my launch options as others here suggested. However once you get in game the input locations are slightly off and shifted upwards. I also confirmed that this doesn't happen when running the game in a Windows 10 VM.
See video for example of what I mean by this: https://www.youtube.com/watch?v=OKuutLVTeWc
Using Proton Experimental in the Steam settings.
Performance for the game is fine seems to stay stable around 60 FPS, I haven't noticed any stuttering or slow downs like others here have seen.
@CorruptComputer i had that too at some point in time (randomly while ingame), so maybe try to re-size the window and try again or de-maximize and re-maximize (or also try a different DE altogether for testing)
Ok, after some further testing with the input issue:
The input being offset only happens when the game is maximized in a window. If you have it in a floating window (even one the same size as the full screen) it works fine. Setting the game to be actually fullscreen instead of a maximized window works fine too. I've not had a chance to test this issue with another DE yet, but I can at least confirm that it happens this way on GNOME 41.
for a while CC ran without requiring PROTON_LOG=1 %command%, but after a system upgrade (and system restart) it requires it again
upgraded from Manjaro 2022-08-16 to Manjaro 2022-09-12
The following log is from when run with PROTON_LOG=1 (where it runs)
steam-1454400.log
Operating System: Manjaro Linux KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.7-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-7700K CPU @ 4.20GHz Memory: 31.2 GiB of RAM Graphics Processor: AMD Radeon RX Vega Manufacturer: MSI Product Name: MS-7972 System Version: 2.0
PS: also already tries restarting steam again, because sometimes that fixes some issues
Proton 8.0-2 and Proton Experimental are not working on Arch Linux. The game window opens up but it doesn't load any further. The last (and currently) working version is version 7.0-6.
Cookie Clicker is working fine for me on Arch Linux KDE Plasma Wayland with Proton 8.0-2d. Running a 5700XT with Mesa 21.1, forget my kernel version but I did a system update a couple of days ago so I should be on the latest Zen kernel.
Cookie Clicker is working fine for me on Arch Linux KDE Plasma Wayland with Proton 8.0-2d. Running a 5700XT with Mesa 21.1, forget my kernel version but I did a system update a couple of days ago so I should be on the latest Zen kernel.
Still no luck after a system update. Running on Xorg though. Here is the log file using Proton 8.0-2.
Hello @IanTrudel, these are the lines of interest in your Proton log:
warn: Skipping Vulkan 1.2 adapter: NVIDIA GeForce GTX 660M
warn: DXVK: No adapters found. Please check your device filter settings and Vulkan setup.
err: D3D11CreateDevice: No default adapter available
Proton 8.0 and newer requires Vulkan 1.3, but NVIDIA discontinued support for your GPU generation after the 470 series video driver, and that does not provide support for Vulkan 1.3. Sorry, but that isn't really a solvable problem without newer hardware.
I am not sure what performance would be like, but would PROTON_USE_WINED3D=1 work? That should force Wine's OpenGL based Direct3D renderer. Performance is generally poorer but for an Electron game like Cookie Clicker it might be acceptable.
Equally, forcing an older version of Proton should work too, such as Proton 7, which should ship an older DXVK. The issue is you'd be using an older Proton version but may have better performance. Using a newer Proton version could mean having to force WineD3D which may mean worse performance, so there is a trade-off.
Hello @IanTrudel, these are the lines of interest in your Proton log:
warn: Skipping Vulkan 1.2 adapter: NVIDIA GeForce GTX 660M warn: DXVK: No adapters found. Please check your device filter settings and Vulkan setup. err: D3D11CreateDevice: No default adapter availableProton 8.0 and newer requires Vulkan 1.3, but NVIDIA discontinued support for your GPU generation after the 470 series video driver, and that does not provide support for Vulkan 1.3. Sorry, but that isn't really a solvable problem without newer hardware.
@kisak-valve That's alright. The day would come sooner or later. Would it be possible to compile Proton 8 against an older version of Vulkan? Or perhaps some build options would be helpful.
@sonic2kk Either using Proton 7 or forcing WineD3D is a working solution.
You may be able to install an older DXVK version by replacing the d3d DLLs in the Proton lib/lib64 folders. But this may get overridden with an update or if Proton tries to validate itself. Proton to my knowledge symlinks a set of bundled DLLs into the Proton prefix based on the supplied bundled DLLs in its lib/lib64 folders, so that's why you'd replace this in Proton rather than the prefix, as the DLLs in the prefix may get overridden.
DXVK is the culprit requiring a higher Vulkan version, not Proton itself, so there should be no need to compile Proton :-)
Alternatively, instad of doing this with Valve Proton, you could do this with a community build of Proton such as GE-Proton. That way the version will remain "fixed" and won't get overridden. Proton-tkg may allow you to specify a DXVK version when compiling as well. Kron4ek Proton builds come without DXVK at all, so that should allow you to install whichever DXVK version you like. Proton versions should have an option to set a name/version in a toolmanifest VDF in their root folder, so you could explicitly name a version to note to yourself that this Proton version uses an older DXVK (though you'd probably need this for every game that uses Proton 8.0+).
You'll have to go through the DXVK release notes to find out when the Vulkan requirement was bumped. I think it was v2.1 but I am not sure.
You'll see when you download DXVK but it is essentially a collection of 32/64bit DLLs which you can replace either in a Prefix for regular Wine, or in a lib/lib64 folder for Proton.
EDIT: Forgot to mention, it should be in the logs too but the DXVK HUD (DXVK_HUD=1) should show you your DXVK version, if you'd like to confirm the version you're using.
I am not sure what compatibility will be like with newer Proton/older DXVK especially as Proton advances, compatibility may not be guaranteed forever. Still, manually installing an older DXVK version may work in the meanwhile. Some tools such as Lutris and Heroic allow you to set a custom DXVK version for games outside of Steam running with Wine at least - These tools support Proton but I am not sure how setting a custom DXVK version works when using Proton in such a case. Just something to keep in mind for general game usage on older hardware :-)
Tried it out on my oled deck and noticed a few things.
1:From my testing and on Protondb, if you launch the game in game mode, the game seems to get stuck on the splash screen. When I booted into desktop mode to try it, it seemed to be getting visually stuck before the language selection screen, if you select a language in desktop mode, that seems to fix it. (Forgot to get a log file for that.
2: The game seems to take longer to load up in game mode compared to desktop mode, desktop mode loads up in around 1-2 seconds after the first cookie clicker logo fades out whereas on game mode, it takes around 3-4 seconds. (I can also see a loading screen visual in desktop mode, whereas in game mode, it just suddenly transitions to gameplay after 3-4 seconds.)
3: When you load a save file, the music is supposed to hold on a note until you click on the cookie, at which point the music begins playing. On desktop mode this works fine, but in game mode, the music sounds oddly crackly and wrong.
steam-1454400.log.txt Tried with proton Experimental
Update: Reading up on this, this may or may not be an issue exclusive to the Oled Deck. Nabbed a screenshot of it from someone else, but I believe issue number 1 seems to happen a bit around pic related.
Was finally able to replicate the behavior of the game getting stuck on a black screen before the language screen and can confirm the new steamos update does not fix it.
Update: Can also confirm issue seems to be Oled deck exclusive, dug out my lcd deck to try it and the language screen shows up fine, though I am noticing with mangohud open, the hud only seems to visually update whenever I hover over a language option.
Apparently someone mentioned getting it working in game mode on the oled with proton GE 7-55, unsure I'd this is a proton, steamos, or gamescope issue.
Update: Apparently someone else has this as a solution, but I haven't been able to confirm.
"Getting stuck on splash, locking and resuming gets you past the issue."
Apparently someone mentioned getting it working in game mode on the oled with proton GE 7-55, unsure I'd this is a proton, steamos, or gamescope issue.
Update: Apparently someone else has this as a solution, but I haven't been able to confirm.
"Getting stuck on splash, locking and resuming gets you past the issue."
Issue has been fixed up as of latest proton Experimental build, it no longer gets visually stuck before the language selection screen on my oled deck in game mode.