-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Whitelist] Sonic Mania (584400) #105
Comments
Work correct on Gentoo uname -a DRI_PRIME=1 glxinfo |grep "OpenGL version string" DRI_PRIME=1 glxinfo |grep "renderer string" |
No issues on NixOS! |
No issues on Ubuntu 18.04 /w GTX 1080. |
failed to run on Ubuntu 18.04 with GTX 1050
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 |
Confirming that I get "server is not reachable" as well. |
Working flawlessly here, Ubuntu 18.04, Ryzen 7 / Vega 10 |
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! |
@kisak-valve Requesting an XAudio2 label for this game... |
Works flawlessly. Finished the game + DLC. Put about 12 hours so far and no issues.
|
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 |
It seems that enabling of "Playstation configuration support" in BigPicture settings solved the Dualshock 4 issue in previous comment. |
Whitelist Request
System Information
I confirm:
Issues
|
No audio issues, but the game flat-out doesn't recognize my PS4 controller, while other games do. |
@serebit From my point of view sonic is working perfect. |
Works fine with my PS4 controller with 4.11-4. |
Manjaro Linux 5.3.1-6.1-tkg-bmq Just got this game with this month's HumbleBundle and I was unable to get it to run until I set The only error in my logs was:
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. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
It used to have audio issues for me but works fine now. System Info: |
Audio cuts out at consistent intervals, producing a "crackly" sound on Arch linux 5.10.7-arch1-1 |
Audio issue appears to be fixed though I have never experienced it on any of the hardware I've used. Tested with Proton 6.3-4 and using Arch Linux 5.12.5, but never experienced any audio issues with any versions of Proton I tried (3.16-X, 4.2-X, 4.11-X, 5.0-X, 5.13-X. 6.3-X). |
Sonic Mania fails to work unless you use Proton 3.16 Issue transferred from #5011. Compatibility Report
System Informationhttps://gist.github.com/coreybruce/dcd2bec911594c9212d351ac2e7a3f98
I confirm:
Log: SymptomsIf you use any version newer than proton 3.16 the game will fail to launch ReproductionLaunch game with latest version of proton, than switch back to proton 3.16 and you will see the game will only work on that version. |
Hello @coreybruce, your Proton log indicates a general failure to initialize Vulkan on your system, the same as #4979. The summary of your hardware doesn't really give any insight into how healthy the Vulkan render paths are, like we see in the extended diagnostics section of Steam's system information. ( Most likely an issue with your system, and not the game / Proton. |
I just installed sonic mania on my setup and it works on proton 6.3-5 I didn't do anything different to click on play button and it works flawlessly. It works for me. PS: the problem that I commented on this issue before about controller not working was a problem that I had on my side. |
Here is my Steam log:
|
This is mesa's faster CPU renderer, it means something's misconfigured and you're not using your nVidia GPU to render (at least for OpenGL). |
Yep confirm it was a issue on my end and has been fixed, the game now runs with the latest proton just fine. Sorry about that. |
Compatibility Report
System Information
I confirm:
SymptomsSonic Mania does not launch ReproductionRun the game on ArchLinux |
Hello @kentosama, these look like the lines of interest from your log:
Glibc used to provide libcrypt.so.1, but no longer does. On Arch, the Can you share a Proton log from trying the game with Proton 5.13 or newer? |
…-plugin-installation Add asdf installation method
Work correct on Linux mint 18.3
Not issues from the moment.
Hardware: i5 7400 + Intel Graphics card
Linux Mint 18.3
The text was updated successfully, but these errors were encountered: