Open JobeSound opened 1 year ago
Adding PROTON_USE_WINED3D=1 fixed it for now, only thing that remains is determining wether it's really a fix or a workaround.
EDIT: Not fixed: It launches, but reduces my fps to under 20 (instead of great, but not measured framerate playing through Lutris before the Steam release) and displays a lot of textures as black.
I'm unable to reproduce this on my end, the game starts fine on both my AMD and Nvidia setups.
@JobeSound Could you try to turn off shader pre-caching in the steam options and see if that changes anything?
@JobeSound Could you try to turn off shader pre-caching in the steam options and see if that changes anything?
It makes the entire map show as black. Only UI elements are still visible.
working fine here as well
It makes the entire map show as black. Only UI elements are still visible.
Thats with dxvk and not wined3d?
With wined3d. Without the wined3d launch option, the error from the main post occurs no matter if I have shader pre-caching on or off. I haven't been able to get the game back to horrible fps but visible map either since i tried disabling shader pre-caching
@JobeSound try clearing the Proton prefix (will erase local state such as settings, replays, maps) and use Proton 7.0-6 to set up a new one.
Using wined3d is not a fix. It's a workaround at best.
I have finally had the time to try all these things (I manually removed all the Proton-related files from my steam library including compatdata) and have had no success. Bypassing steam completely and installing the game through Ubisoft Connect in Lutris works, however. Could this be because flatpak installs its own version of the Nvidia Driver when installing Lutris?
I have abnormally high memory usage that grows over time in game while playing with the ubisoft overlay enabled. Using htop I can see that winedevice.exe memory usage starts growing (2GBs in like 1hour, when normally it's under 100MB). I can reproduce both on my desktop PC and on my Steam Deck. It doesn't happen while idle in the menu, only when playing any map
Log: steam-2225070.tar.gz
Replying to https://github.com/ValveSoftware/Proton/issues/6507#issuecomment-1493299894
can you install this game through a custom wine patched with https://gitlab.winehq.org/wine/wine/-/merge_requests/2439 ?
Replying to https://github.com/ValveSoftware/Proton/issues/6507#issuecomment-1493402967
I will try doing that tomorrow, should I just patch proton wine and then build proton? (I also forgot to mention that I'm using proton experimental as of today, 7.0-6 straight up crashes with the overlay enabled)
Replying to https://github.com/ValveSoftware/Proton/issues/6507#issuecomment-1493409541
yeah that should work, if there's some conflicts/issues, I would just copy the logic over
Replying to https://github.com/ValveSoftware/Proton/issues/6507#issuecomment-1493522495
I just built a custom proton version using proton experimental as a base with that patch applied, seems to completely fix the issue (thanks!)
Possible regression? Game doesn't start, just see an shadow outline of the ubisoft connect/uplay window and nothing else happens. Seems to affect others recently too. Arch i7 9700 RX580 Gnome Wayland Proton Experimental and Proton GE 8.3. steam-2225070.log
Possible regression? Game doesn't start, just see an shadow outline of the ubisoft connect/uplay window and nothing else happens. Seems to affect others recently too. Arch i7 9700 RX580 Gnome Wayland Proton Experimental and Proton GE 8.3. steam-2225070.log
it's working fine for me try bleeding edge beta of proton experimental
edit: game crashes with RADV GPL on mesa-git, RADV_DEBUG=nogpl disables GPL and avoids the crash while we wait for mesa devs to fix it edit2: works on mesa stable (no workarounds needed)
it's working fine for me try bleeding edge beta of proton experimental
Good to know... I'm on mesa stable btw. Tried the RADV gpl command anyway but no difference.
bleeding edge beta didn't solve it unfortunately.
it's working fine for me try bleeding edge beta of proton experimental
Good to know... I'm on mesa stable btw. Tried the RADV gpl command anyway but no difference.
bleeding edge beta didn't solve it unfortunately.
Try Deleting the compatdata folder for the game
(Note that this deletes settings, player profiles and custom tracks. Make backups first.)
Thanks, already did that by uninstalling the game and checking the compatdata folder to make sure 2225070 wasn't in there anymore, before switching to the bleeding edge beta. Should have mentioned that before, sorry.
Possible regression? Game doesn't start, just see an shadow outline of the ubisoft connect/uplay window and nothing else happens. Seems to affect others recently too. Arch i7 9700 RX580 Gnome Wayland Proton Experimental and Proton GE 8.3. steam-2225070.log
I suddenly got this today on Fedora on mesa stable. RADV_DEBUG=nogpl seems to be the only fix
Possible regression? Game doesn't start, just see an shadow outline of the ubisoft connect/uplay window and nothing else happens. Seems to affect others recently too. Arch i7 9700 RX580 Gnome Wayland Proton Experimental and Proton GE 8.3. steam-2225070.log
I suddenly got this today on Fedora on mesa stable. RADV_DEBUG=nogpl seems to be the only fix
That's because by the time you applied your env variable the devs had uploaded a new proton experimental build with the issue fixed :)
Just remove that variable, it's actively hurting performance
It stopped working for me again about a week ago; launching Trackmania from the Steam Library opens the Ubisoft Connect library instead of the game. Launching the Trackmania (Steam) entry from Ubisoft Connect then switches back to Steam, which then "launches Trackmania" by switching back to Ubisoft Connect. Tried with Bleeding Edge, Experimental, 8-03 and a few GE versions. Log file is from Bleeding Edge: steam-2225070.zip
It also takes very long to open Ubisoft Connect at all, I'm pretty sure it used to launch the actual game faster. I actually thought at first I had the same issue as described by bradgy because Ubisoft took so long to launch.
@JobeSound it just launched fine for me using Proton Experimental.
Proton-GE prefixes can often be incompatible with regular Proton. Try renaming compdata (rename not delete since it contains settings, replays and more things you probably want to keep).
Issue persists, I've tried reinstalling the game completely as well, no change
On Proton 8, launching the game now nets the launcher crap thingy to not load properly; all I see is a black outline. In the log I can see that it's launching a slew of processes every 2s but it does that seemingly forever.
Getting a bunch of these in the log:
9577.402:0178:01c4:warn:debugstr:OutputDebugStringA "D:\\JenkinsWorkspace\\workspace\\client_build_installer\\client\\shared\\libs\\ceffacade\\mg\\ceffacade\\CefClientHandler.cpp(1051) : CEF render process crashed\n"
Proton Experimental and hotfix work but I get like 15fps at 100% GPU usage on a 6800XT and it's even at 100% in the menus which just isn't right. This wasn't the case a few weeks ago as evidenced by the comment above.
Replying to https://github.com/ValveSoftware/Proton/issues/6507#issuecomment-1730775127
It works perfectly here on proton experimental... (RX 6800) I will retest today, but this was the case 2 weeks ago i think
Trackmania 2020. Ubisoft connect is not currently installed
Issue transferred from https://github.com/ValveSoftware/Proton/issues/7235. @DocCringol posted on 2023-11-04T23:44:05:
Launching trackmania 2020, on linux machine. Used proton experimantal and 8.0-4. It shows Ubisoft connect is not currently installed
It should install it on a game installing process or on first launch, but it doesn't. So maybe there is the way to install it manually
Can confirm I am experiencing the same problem on a computer that hasn't had Trackmania installed before. It still runs fine on a computer where I installed it several months ago; the problem seems to be in the install routine.
I tried to launch game after several months, it stopped working for me, after successfully loading ubisoft connect and going into game it shows black fullscreen for a second and then crash. I tested both steam-native and steam-runtime (on Arch Linux, both discrete Nvidia card and integrated Intel), different versions of Proton (8.0-4, Experimental, GE). After crash I have to press "Stop" button in Steam. Entire output:
wine: Using setpriority to control niceness in the [-10,10] range
/bin/sh\0-c\0prime-run /home/flowneee/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=2225070 -- /home/flowneee/.local/share/Steam/ubuntu12_32/steam-launch-wrapper -- '/home/flowneee/.local/share/Steam/steamapps/common/SteamLinuxRuntime_sniper'/_v2-entry-point --verb=waitforexitandrun -- '/home/flowneee/.local/share/Steam/steamapps/common/Proton - Experimental'/proton waitforexitandrun '/home/flowneee/.local/share/Steam/steamapps/common/Trackmania/Trackmania.exe' -upc_steam_free_package_id 62710 -uplay_steam_mode\0
chdir "/home/flowneee/.local/share/Steam/steamapps/common/Trackmania"
ERROR: ld.so: object '/home/flowneee/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/flowneee/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/flowneee/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/flowneee/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/flowneee/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/flowneee/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
fsync: up and running.
wine: Using setpriority to control niceness in the [-10,10] range
Setting breakpad minidump AppID = 2225070
Steam_SetMinidumpSteamID: Caching Steam ID: 76561198004862369 [API loaded no]
@Flowneee Set PROTON_LOG=1
and paste the log from your home dir into a gist.
https://gist.github.com/Flowneee/40dbded912cb71cae14d68e9570841bf on native runtime and Proton Experimental
i can´t find my log but just updating as im currently facing the same issue.
With Proton 8, neither the game nor Ubisoft Connect terminate when I exit the game. I always have to forcefully stop the game from the Steam interface, and run pkill -f Ubisoft
to terminate Ubisoft Connect. If I forget to do this, nothing happens when I try to boot up the game the next time. Very annoying.
Currently, the game is unplayable because Ubisoft Connect fails to start and claims that it isn't installed. This is after a fresh install, verifying the game files doesn't do anything. Other games run fine etc. etc… Tried Proton 9, 8, GE 9-5, Experimental.
Replying to https://github.com/ValveSoftware/Proton/issues/6507#issuecomment-2118370685
you just have to manually install ubisoft connect, it works after that
Or remove the compatdata folder for the game usually works for me, instead of having to manually install Ubisoft Connect. Any time you switch to another major version of Proton, Ubisoft Connect breaks and you'll have to repeat the process.
On Sat, 18 May 2024, at 00:06, Etaash Mathamsetty wrote:
Currently, the game is unplayable because Ubisoft Connect fails to start and claims that it isn't installed. This is after a fresh install, verifying the game files doesn't do anything. Other games run fine etc. etc… Tried Proton 9, 8, GE 9-5, Experimental. Error Screenshot https://private-user-images.githubusercontent.com/91573410/331728049-a7a1fc88-46b7-407f-9e49-db6472f7da9a.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTU5ODc0NTIsIm5iZiI6MTcxNTk4NzE1MiwicGF0aCI6Ii85MTU3MzQxMC8zMzE3MjgwNDktYTdhMWZjODgtNDZiNy00MDdmLTllNDktZGI2NDcyZjdkYTlhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA1MTclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNTE3VDIzMDU1MlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTlhOTU5ZGUwOWM2ZDEyMmYwOTBiZTVkOGVjNjFmYjMxYTg3Mzk5YjRhM2E5OTE2YWZlZDEzZmQ0MThmMGUyMzkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.RkE41DaDbrvcWav0gOBx4gy3HyJKUCbrm8jfUhq5UrA
you just have to manually install ubisoft connect, it works after that
— Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/6507#issuecomment-2118474148, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFIPSDTKATG25TNGS5SOULZC2EP5AVCNFSM6AAAAAAUUMKPTWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJYGQ3TIMJUHA. You are receiving this because you commented.Message ID: @.***>
I can confirm that the latest Proton Experimental fixes the Ubisoft Connect not starting issue and the game now works, although it didn't when I initially updated the day the changelog came out.
Compatibility Report
System Information
I confirm:
Symptoms
After logging into Ubisoft, the game opens a small black window and immediatley shows an error message saying: "Corrupted Installation. Please verify files integrity or reinstall the game."
I have done both several times with several Proton and Proton-GE versions, without change.
Reproduction
Launch fresh install of the game on same or comparable system.
Log: steam-2225070.log