Proton
Proton copied to clipboard
ValveSoftware
[Whitelist] Sonic Mania (584400)
Work correct on Linux mint 18.3
Not issues from the moment.
Hardware: i5 7400 + Intel Graphics card Linux Mint 18.3
Work correct on Gentoo
uname -a Linux localhost.localdomain 4.14.63-gentoo-r1 1 SMP PREEMPT Sun Aug 19 04:55:38 CEST 2018 x86_64 Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz GenuineIntel GNU/Linux
DRI_PRIME=1 glxinfo |grep "OpenGL version string" OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.0-rc3
DRI_PRIME=1 glxinfo |grep "renderer string" OpenGL renderer string: AMD Radeon HD 8800M Series (CAPE VERDE, DRM 3.19.0, 4.14.63-gentoo-r1, LLVM 6.0.1)
failed to run on Ubuntu 18.04 with GTX 1050
$ uname -a
Linux firelord 4.15.0-32-generic #35-Ubuntu SMP Fri Aug 10 17:58:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
$ glxinfo |grep "OpenGL version string"
OpenGL version string: 4.6.0 NVIDIA 396.51
$ glxinfo |grep "renderer string"
OpenGL renderer string: GeForce GTX 1050/PCIe/SSE2
EDIT: today I got a new version of nvidia-driver and now it is working!
$ glxinfo | grep "OpenGL version string"
OpenGL version string: 4.6.0 NVIDIA 396.54
I have the same issue with the server is not reachable error message. Arch Linux with GTX 980 Ti
Working here on Arch with AMDGPU. Was actually surpised since by default Mania needs xact to fix choppy audio. Is this already included as a lib/one of the patches?
@parkerlreed I had a look at the prefix, and the xaudio2_[0-7] files appear to be the native ones, since their filesizes are around 500kb each, whereas the built in dlls are just text files with a few lines of code. So yes, it looks like xact is already included.
Confirming that I get "server is not reachable" as well. RX 480 Ryzen 5 1600 Mesa 18.1 LLVM 6.0
Working without any flaws here, heck it even installs the Plus DLC fine right from the game, in Proton.
I'm getting the choppy audio issue here. I tried installing xact (using winetricks, setting WINEPREFIX to the game's compatdata folder) but that didn't fix it.
EDIT: Saw someone suggested changing the emulated Windows version to XP, and that did it for me. Thanks!
Works flawlessly. Finished the game + DLC. Put about 12 hours so far and no issues.
- Fedora 29
- Kernel 4.18.16
- NVIDIA 410.66
The game do not detect Dualshock 4 on the first launch after Steam start. If I close the game using keyboard and launch it again Dualshock works properly until next Steam restart.
Proton version 3.16-4 beta OS Fedora 29
It seems that enabling of "Playstation configuration support" in BigPicture settings solved the Dualshock 4 issue in previous comment.
Whitelist Request
- Name of the game to be whitelisted: Sonic Mania
- Steam AppID of the game: 584400
System Information
- GPU: GTX 970
- Driver/LLVM version: NVIDIA 415.25
- Distro version: Ubuntu 16.04.5 LTS
- Link to full system information report as Gist
- Proton version: 3.16-6 Beta
I confirm:
- [x] that pressing the
Playbutton in the Steam client is sufficient. - [ ] that runtime config options are necessary to run the game.
- [ ] that no workarounds other than PROTON_* env variables are necessary.
Issues
- [ ] I haven't experienced any issues.
- [ ] There are no issues left open for this game.
- [x] Although I consider the gaming experience equal to Windows there are remaining issues:
- Application appears to work as expected but detects an incorrect display resolution during launch process (not fullscreen).
No audio issues, but the game flat-out doesn't recognize my PS4 controller, while other games do.
@serebit Not sure why, but I can use it if I disable steam controller option and use it as a normal controller. my ps4 controller never works on any proton title if I opted in for ps4 steam controller feature.
From my point of view sonic is working perfect.
Manjaro Linux 5.3.1-6.1-tkg-bmq MSI RX 580 Mesa 19.3.0_devel.115749.336b021d36f-1 Tested Proton 4.11-6; proton-tkg with dxvk master; wine-staging 4.17 LLVM 10.0.0_r327586.23aac95a32c-1 amdvlk 2019.Q3.6-2 Tested with FSYNC on and off
Just got this game with this month's HumbleBundle and I was unable to get it to run until I set VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd32.json %command% or VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.i686.json %command% under the launch options.
The only error in my logs was:
terminate called after throwing an instance of 'dxvk::DxvkError'
pid 37033 != 37032, skipping destruction (fork without exec?)
Using exiftool on the binary showed it to be a 32bit executable which gave me the idea to try to use a 32bit vulkan implementation which works great and makes it perfectly playable for me.
Works fine with my PS4 controller (Bluetooth).
EDIT:
Realized after posting this that I set a 64bit vulkan implementation globally upon boot. While I have to leave the house right now, I'll test this game when I get home in another hour or two without radeon_icd.x86_64 set globally on boot and see if that fixes my issue and turns this from a Proton/Wine issue to my setup being the issue.
UPDATE:
It was because of my globally set 64bit Vulkan ICD. Removed it and all my launch options and it works just fine.
Doesn't even launch on Linux Mint 19.1 on Thinkpad T430 (Intel iGPU) with Proton 4.11-12
Hello @Johnystar, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box. Also, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.
I have tried switching to Proton 5.0-2 in the meantime with no luck.
info: Required Vulkan extension VK_KHR_surface not supported -> terminate called after throwing an instance of 'dxvk::DxvkError' is the line of interest from your log. Please check if any vulkan application like vulkaninfo from vulkan-utils works.
Mesa also has an incomplete vulkan implementation for your Ivybridge generation hardware. You could try updating to a newer mesa version using a PPA like oibaf or kisak-mesa.
Alternatively, you could try adding PROTON_USE_WINED3D=1 %command% to the game's launch options to try wine's DirectX to OpenGL render path, but this is unsupported and is expected to come with a performance penalty.
After installing vulkan-utils onto my system, I got the following output from vulkaninfo:
===========
VULKAN INFO
===========
Vulkan Instance Version: 1.1.70
Cannot create Vulkan instance.
/build/vulkan-UL09PJ/vulkan-1.1.70+dfsg1/demos/vulkaninfo.c:768: failed with VK_ERROR_INCOMPATIBLE_DRIVER
Incompatible driver? Sounds like the Mesa incompatibility you mentioned... I added the oibaf repository and ran apt update & upgrade to get the latest versions of all packages on my system. That didn't really do much and I'm still getting the same vulkaninfo output as before.
Enabling Wine 3D or PROTON_USE_WINED3D=1 worked alright, but the game did indeed use more system resources than I'd usually expect and when I try switching to fullscreen it crashes, which is a significant problem considering the game without it covers a quarter of the laptop's screen at best.
You can also double check that you have the mesa-vulkan-drivers and mesa-vulkan-drivers:i386 packages installed with something like apt policy mesa-vulkan-drivers mesa-vulkan-drivers:i386.
Yep, Installed: (none). I guess that explains a lot. After installing the necessary drivers, the game now runs as expected including fullscreen and everything.
Thanks for your help and time :D
It used to have audio issues for me but works fine now.
System Info: https://gist.github.com/Ruedii/a1dacec22e0649421574050423a5529c
Audio cuts out at consistent intervals, producing a "crackly" sound on Arch linux 5.10.7-arch1-1
