Avatar: Frontiers of Pandora™ (2840770) #7843
Comments
kisak-valve
added
the
Game compatibility - Unofficial
|
I confirm it, tried proton experimental. |
|
Also crashing on launch for me on every Proton version I've tried.
|
|
Trying with Proton 9 and also a no-go here on desktop: Proton Experimental also a no-go: That's on Kubuntu 24.04, Mesa 24.0.6 Also tried Proton Experimental with Mesa 24.1.1 and no-go as well: |
|
This is odd considering thay the Ubisoft Launcher version worked fine in the past |
|
This looks like something of interest from the logs: I guess Proton's SteamAPI wrapper / lsteamclient needs an update here? |
|
The game should start in the just updated Proton Experimental ([bleeding-edge] branch). I didn't check the actual gameplay beyond starting the game. FWIW, lsteamclient is unrelated here. |
|
Tested proton experimental and it works now. Thank you! Remaining issue: the game does not close properly. Steam sees it running. |
That might be because of Ubisoft Connect, since it's still a process running under Steam. This happens with other games using the launcher |
|
Yes, you can then close the Ubisoft Connect launcher from the systray with right click --> Quit |
|
Sorry being dense, I seem unable to start game at all, actually it seems Ubisoft Connect game launcher is not started (it works OK with other games, I just retested A.C. Odyssey which I still have installed). I manually set "compatibility" to "experimental" but nothing changed (unsurprisingly as "experimental" is my default). I got a very long (>150M) log file (I can post it, if deemed useful). First fixme/warn entries are:Then the backtrace continues to grow till a final:It seems to me there's some nested exception runaway finally consuming all memory (32GB), but I'm far from being sure. |
|
You need to switch Proton Experimental to the bleeding-edge branch as mentioned before. It's under Properties -> Beta Updates I believe |
|
Thanks, |
|
I meant in the Properties of Proton Experimental, not the game. Search for Proton in your Steam Library and in the Properties for Proton Experimental you'll find the option. |
|
Thanks. |
|
It now starts with the latest Proton Experimental but here are a few issues I'm seeing:
|
|
The game freezes after loading into the game from the main menu: |
|
Still freezes with this kernel log which may be an issue in vkd3d or the nvidia drivers itself (umip can probably be ignored): The controller is still not detected, tried with Steam Overlay disabled and enabled. Proton log attached. |
I found that if I disable "dynamic upscaling resolution", the game runs just fine and is stable - no crashes. Looks like NVIDIA doesn't like render resolution switches, no matter if XeSS, DLSS or FSR is used. To get the controller working, one reliable method is to disconnect and reconnect the controller. The game only randomly detects the gamepad during start by itself. Sometimes, it may just suddenly work. But disconnect and reconnect always fixes the "missing" controller. |
|
I wrote a utility that fixes this game not recognizing some Xbox gamepads, particularly wireless ones. It works by creating a second virtual gamepad which is a copy of the first using the uinput API. I discovered this after realizing that attaching multiple physical gamepads simultaneously caused previously non-functional ones to start working. I don't understand the mechanism of action here but it fixes the issue, at least on my machine. It's available on my GitLab here as a compile-it-yourself C program and instructions for use can be found in the readme. |
@amini-allight The problem with Bluetooth controllers may be that bluez lately started to persist device nodes: If you turn the controller off, its device files in This is probably caused by one of these commits: Those were created to fix this issue: bluez/bluez#737 There's a device flag |
Compatibility Report
System Information
I confirm:
steam-2840770.zip
Symptoms
The game crashes immediately after launch.
Reproduction
Always.
The text was updated successfully, but these errors were encountered: