You are not logged in.
Hi guys, I've already tried to get help on proton's github, but I haven't gotten any answers yet, so I'm trying to see if anyone around here can help me figure out how to solve it.
# Compatibility Report
- Name of the game with compatibility issues: The Division 1, The Division 2
- Steam AppID of the game: 365590, 2221490
## System Information
- GPU: GeForce RTX 2070 SUPER
- Video driver version: nvidia 565.57.01
- Kernel version: Linux 6.11.9-zen1-1-zen
- Link to full system information report as [Gist](https://gist.github.com/FGYada1984/60fd … 1dc114da4b):
- Proton version: Proton Experimental and many other versions
Protonlogs:
https://gist.github.com/FGYada1984/b17c … 6872273bd9
https://gist.github.com/FGYada1984/eb51 … 1d33c491b5
## Symptoms
I can't run these ubisoft games through Steam. What happens is that after installation, when I click on play, it does all the installation processes and even loads the vulkan shaders, but ubisoft connect never opens and the running status returns to play.
Steps I've already tested that didn't work:
- Check the integrity of the files
- Test with different versions of Proton
- Uninstall, clear any residual files and install again
- Install a version from Ubisoft Connect via Bottles / Lutris and replace the version installed via Steam
- Install via Protontricks (in this case Ubisoft Connect from Protontricks opens normally, I can login, but naturally the game doesn't start)
## Reproduction
- Click to Play Game
- Ubisoft Connect don't start
Last edited by FGYada (2024-11-22 02:06:19)
Offline
at least for division 1 it could be an ourdated uplay install - as what comes these days sometimes has trouble to launch and uodate properly (sadly ubisoft doesn't care to update the steam packages but only updates thier games thru uplay itself)
as for d2 everything shoukd be cool - it was released with a fairly up-to-date uplay
if nothing helps use umu-launcher to start uplay directly in its prefix to see if it runs at all or errors out
another option would be to just wipe the prefix in compdata/<id> and have steam rebuild it from scratch
Offline
at least for division 1 it could be an ourdated uplay install - as what comes these days sometimes has trouble to launch and uodate properly (sadly ubisoft doesn't care to update the steam packages but only updates thier games thru uplay itself)
as for d2 everything shoukd be cool - it was released with a fairly up-to-date uplay
if nothing helps use umu-launcher to start uplay directly in its prefix to see if it runs at all or errors out
another option would be to just wipe the prefix in compdata/<id> and have steam rebuild it from scratch
first, thank you for your reply.
currently the package already comes with ubisoft connect and I tried to do this step of cleaning the compdata, and via protonfix (i will try with umu-launcher) managed to get ubisoft connect to start (it even appears that the game is installed), but it doesn't start at all. I really don't know what could be going on.
Last edited by FGYada (2024-11-22 10:42:16)
Offline
well if you got uplay to start same should work from within steam
as for the game: you can try to start steam all the way from terminal and see if you get some log output which maybe hints at some issue
does the issue only affect uplay games or others, too?
Offline
well if you got uplay to start same should work from within steam
as for the game: you can try to start steam all the way from terminal and see if you get some log output which maybe hints at some issue
does the issue only affect uplay games or others, too?
I made a few more attempts and:
- installing the flatpak version of steam works, which led me to understand that the problem is in some component of steam, so again I uninstalled, removed any remaining folder, because my suspicion fell on the runtimes or some version of proton, however when reinstalling everything happens again and directly through steam I can't uninstall the runtimes because they give an error not allowing me to remove them (a message appears that the shared component is missing - unfortunately I didn't get the screenshot of that).
The fact is that it works with steam in flatpak, it's not my favorite format, but until I find a solution, that's what will remain.
Offline