Open thaleslimao opened 6 years ago
Hmm, strange... The controller still works for me even with the overlay disabled. Then again, maybe you're using Steam Input, and that seems to require the Steam overlay enabled for some games (e.g., HZD) for the controller to work. So you could also try disabling Steam Input for this game, most SDL-supported controllers should still work then.
Not sure what Steam Input is but I have an Xbox controller that I use. KDE recognizes it when its connected but the game does not if the overlay is off.
Not sure what Steam Input is but I have an Xbox controller that I use.
That controller should work, I'm using the same (actually, as the xpadneo developer, I'm owning all models, and each one works). Steam Input is the controller mapping tool available from the overlay. To disable Steam Input, either go to the game properties and disable "Xbox controller support" per game, or go to Steam settings to disable it globally. Disabling support for the controller only affects controller support through Steam Input and the overlay, it does not disable the controller for games (usually, there are a few games that actually use Steam Input directly, and need both Steam Input and the overlay enabled, for those games you can still individually enable that support per game if disabled globally). If you see mapping problems with the buttons after disabling Steam Input, try stopping the Steam client, reconnect the controller and start Steam again. Maybe try disabling Steam Input globally in the client and enable per game if needed. An alternative driver may also work around those issues (xpadneo for Bluetooth, xone for the dongle).
PS: I'm not sure why Steam Input seems to be depending on the overlay enabled (at least for some games), and vice-versa, Valve should probably fix that.
Replying to https://github.com/ValveSoftware/Proton/issues/928#issuecomment-1182917472
I think I understand what you are saying. I will try to disable Steam Input for this game.
I was thinking maybe I have problems because I use xbox controller with xow? Its an app that lets me use my dongle with my controller.
I was thinking maybe I have problems because I use xbox controller with xow? Its an app that lets me use my dongle with my controller.
Yes, I know that project well. This is superseded by xone now, xow does not receive further development. You may want to join our Discord server (it's about xpadneo, xow, and xone, joining the developers of each project in one pool), there are people who can help you finding the correct settings.
Anyone else freezing at startup screen with the experimental build? Bleeding edge works fine but I thought the fix was now merged into experimental? Something else must be going on then.
@smintman @vahidshirvani The fix is live in experimental-7.0-20220714b. Hopefully you aren't seeing the hang after the recent game update anymore?
@Tripp024 Could you get 2 logs (just add PROTON_LOG=1 %command% to the command line) -- 1)the freeze on experimental-7.0-20220714b and 2) the game not freezing and proceeding correctly on bleeding-edge
@alasky17 I found out it just happens randomly on the experimental build. It has nothing to do with bleeding edge. It froze once again before I turned on the logging, I tried booting it again a few times afterwards and then it worked fine. Maybe it was some temporary glitch with uplay or something. Logging is on now so when it happens again I'll post the log. Btw, the freeze happened on the warning screen and I'm using a Steam Deck.
This game does not support FreeSync correctly on linux. Not sure if this would be considered a problem with Proton or Linux itself. Have not noticed this issue on any other games. The FreeSync value (hz) will be half that of the FPS. If the fps is 120fps it will be 60hz and if it is 140fps it will be 70hz and so on. Every once in a while it will read correctly which makes for a very inconsistent experience.
The game freezes on launch on a 7900X, 790XTX. Here's the Proton Log:
Hello @QushyQushy, can you temporarily remove or disable mangohud, gamemode, and vkBasalt and see if that has an effect?
Hello @QushyQushy, can you temporarily remove or disable mangohud, gamemode, and vkBasalt and see if that has an effect?
Perfect suggestion and I'm sorry for providing a Proton Log with all these enabled. Power of habbit. XD
vkBasalt seems to be the culprit. I will open an issue on vkBasalt's Github. :)
The game freezes on launch on a 7900X, 790XTX. Here's the Proton Log:
I am having exactly the same issue, on the same graphics card, but I am not using any command line arguments, on Proton Experimental. It perpetually stays in the splash screen warning.
EDIT: Ok, STEAM OVERLAY was the culprit. Turned it off, everything works now.
I had the same problem yesterday but I had already switched the overlay off (many months ago - maybe it tried to switch it back on after a uplay update?). The only way I could fix it was to delete the game and re-install, and then I could switch the overlay off when it started for the first time. I don't know if that's what fixed it, but then the ubisoft connect app started cleanly and the game launched.
Ubisoft Games not working because connection lost always.
Issue transferred from https://github.com/ValveSoftware/Proton/issues/7420. @vuaieo posted on 2024-01-18T12:16:43:
hi if i launch the assasins creed origins game then the ubisoft launcher starts and trying to connect to their service or so but it always fails, and cant run on offline mode because need at least 1 time need to be online in order to use offline mode, so i stuck in the loop and cant play ubisoft games anymore on steam. please help T_T tryed many different proton and GE proton versions but nothing helps , its always the same.
here are the screenshots of the messages:
i remmber last year or so it worked "fine" so something musst have happen...
well if install the ubisoft launcher as a game and start it then the launcher works ok and i think i could play some games but because the assasins creed origin i got on steam its bound to steam acc and so clicking on download opens the launcher and its still same problem... = so cant play : (
just start the assasins creed origin game 🖖
Replying to https://github.com/ValveSoftware/Proton/issues/928#issuecomment-1898715114
I can confirm this on the Steam Deck, as I have seen it happening to someone on social media.
Just to make it clear, the game is working great for me, no issues whatsover, Proton-8.0-4, https://gist.github.com/Patola/5b0f3d30bfdbf276b183d32f997c8500 (Archlinux, Ryzen 7 7800X3D, RX 7900 XTX). So this does not affect everyone. I can try on my nvidia laptop to see if the problem is the GPU.
Just to make it clear, the game is working great for me, no issues whatsover, Proton-8.0-4, https://gist.github.com/Patola/5b0f3d30bfdbf276b183d32f997c8500 (Archlinux, Ryzen 7 7800X3D, RX 7900 XTX). So this does not affect everyone. I can try on my nvidia laptop to see if the problem is the GPU.
No, as this is confirmed to happen on the AMD GPU in the Steam Deck as well.
Ubisoft Games not working because connection lost always.
@vuaieo Try sudo sysctl -w net.ipv4.tcp_mtu_probing=1
before starting the game and report, if that helps.
@kakra ok did this command in terminal but it didnt helped, its still same
@kakra ok did this command in terminal but it didnt helped, its still same
Rename your prefix (it's the folder 582160 in $HOME/.steam/steam/steamapps/compatdata
), e.g. name it 582160.bak
. Apply my sysctl fix, and then start the game. It should reinstall a current version of Ubisoft Connect. Maybe something is broken in your prefix. You will loose your graphics and game settings. If that works, you can try copying over the folder pfx/driver_c/users/steamuser
from the backup prefix to the new prefix, this should bring your game settings back.
If it still doesn't work, restore your prefix backup folder (rename 582160
to 582160.failed
, then rename 582160.bak
to 582160
), and retry with PROTON_NO_FSYNC=1 %command%
as launch options in your game properties. If this helps, you may see #2922. Sometimes, this is only needed to fix updating the launcher, and after that it will work with fsync again. MTU probing may still be needed because without, services of Ubisoft sometimes cannot be reached. Windows defaults to MTU probing on.
I had the same issue @vuaieo was having (and it seems that many on protondb have the same problem) and sadly non of the solutions @kakra was proposing were working for me either.
However, after i used protontricks to install ubisoft connect for the game, it started and i was able to play through the intro with no issues so far I hope this helps others too.
Assassin’s Creed Origins - Black Screen
Issue transferred from https://github.com/ValveSoftware/Proton/issues/7872. @CreeperofDoom posted on 2024-07-04T17:17:11:
2 Days ago i opened Assassin’s Creed Origins on my Steam Deck OLED and it only shows a Black Screen, The Sound of the game still plays and the controller still functions, its just the screen thats pitch black. I tried: Verifying the game files, Reinstalling the game from Steam, Clearing the Proton Compatibility Data (which deletes all game data and the Third Party Launcher requiring it to reinstall) I also tried connecting it to a dock onto a TV, i tried forcing resolutions and it didn’t work. I also tried switching to Proton 9 and 8 and that didn’t work. i tried the Community Made GE-Proton and i get the same issue. I have no idea what causes it
Under the games when clicking on play brings me the UPLAY login screen.
When adding my credentials always returns me error and I can not connect,
If anyone can simulate this scenario to see where exactly the error is, thank you.
Kubuntu 18.04