same with just dance, i will make a related

No games that use Uplay are working in Proton at the moment.

uplay works now with the new proton version but the game doesn't but it should. It works with the wine tkg 4.4 build https://bugs.winehq.org/show_bug.cgi?id=46880

With Proton 4.2-7 there has been a lot of progress in launching the game.
Yes the game is still crashes, but it happens later after screen of epilepsy warning.

steam-460930.log

$ inxi -bM
System:    Host: localhost.localdomain Kernel: 5.1.0-1.fc31.x86_64 x86_64 bits: 64 Desktop: Gnome 3.33.2 
           Distro: Fedora release 31 (Rawhide) 
Machine:   Type: Desktop Mobo: ASUSTeK model: ROG STRIX X470-I GAMING v: Rev 1.xx serial: <root required> 
           UEFI: American Megatrends v: 2304 date: 05/03/2019 
CPU:       8-Core: AMD Ryzen 7 2700X type: MT MCP speed: 2128 MHz min/max: 2200/3700 MHz 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Vega 20 [Radeon VII] driver: amdgpu v: kernel 
           Display: wayland server: Fedora Project X.org 1.20.5 driver: amdgpu resolution: 3840x2160~60Hz 
           OpenGL: renderer: AMD Radeon VII (VEGA20 DRM 3.30.0 5.1.0-1.fc31.x86_64 LLVM 8.0.0) v: 4.5 Mesa 19.1.0-rc5 
Network:   Device-1: Intel I211 Gigabit Network driver: igb 
           Device-2: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter driver: r8822be 
Drives:    Local Storage: total: 11.57 TiB used: 8.62 TiB (74.5%) 
Info:      Processes: 454 Uptime: 2h 20m Memory: 31.37 GiB used: 11.06 GiB (35.3%) Shell: bash inxi: 3.0.34 

Finally, the game start working with Proton 4.11-1
Impressive work, Valve. I appreciate it.

@NTMan, any tweaks you had in order to get it working?

@NTMan, any tweaks you had in order to get it working?

It a weird but without PROTON_LOG=1 in launch options the game was stuck at the start.

Can approve, that game starts only after adding PROTON_LOG=1 (DXVK_HUD is not neccessary).

Let's talk about graphics glitches in Tom Clancy's Ghost Recon Wildlands.
The most notable glitch is when large bushes appear in front of your protagonist then disappear.


Renderdoc trace is here.

Let's talk about graphics glitches in Tom Clancy's Ghost Recon Wildlands.
The most notable glitch is when large bushes appear in front of your protagonist then disappear.

I am on openSUSE Tumbleweed and had this glitch, too. Installing Mesa-19.2-devel and libllvm9 made it disappear for me.

In my case the game also cannot connect to the Ubisoft-servers. I always get a

ribera-1000b

error. I tried to workaround this with adding

SSL_CERT_DIR=/etc/ssl/certs

to the launch options but it does not help.
Anyone also experiences this and knows a workaround?

Just want to let you know that since proton 4.11.4 wildlands is running perfectly without any workarounds like PROTON_LOG=1 in launch options.

Thanks for all the work to everybody and keep up the good work.

Today I found yet another issue.
When Windows user connect to my game or I connect to Windows user's game then my game stopping with message:

After the latest uplay update the game crashes at startup.

wildlands_crashdump.txt
steam-460930.log

With Proton-6.5-GE-2 the game is playable again.

Unfortunately GRW didn't works anymore with Proton-6.5-GE-2 nor 6.10-GE-1.

Unfortunately GRW didn't works anymore with Proton-6.5-GE-2 nor 6.10-GE-1.

Same issue, not working with any version that i've tested, including GE.

@Mr-McBride also, do you remember approximately what date it was playable with Experimental?

I'm so sorry I missed this. I've changed email providers and completely missed the messages.

To add information. I can completely remove Wildland, then reinstall it and it will work for a bit.

Does not work. It will launch to a black screen, then closes with proton experimental
steam-460930.log

Would like to confirm that the game works on ZorinOS 16.2 pro with Steam installed on Proton: Experimental, 7 and 6. In fact it works great with the exception of multiplayer. Get kicked after about 15 seconds in by EAC (Easy Anti Cheat).

The steam community's fix for crashing at launch is to install Visual C++ Redistributable for Visual Studio 2012 which I did using proton tricks but the issue still persists.

I have also cleared uplay's cache which didn't help.

Anyone have any other ideas or knowledge?

There's this weird issue where Wildlands will just deadlock when there's a piece of intel that triggers the animation when your character picks up the phone, transfer data from that phone to his phone.

Halfway-through the animation, the game deadlocks, 100% everytime.

Hello @gabriele2000, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the deadlock, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

Well, I'm using Plain Wine, but I did spot errors coming from "turf effects", although there is no way they're related, like, at all...

wildlands-log2.zip

https://gist.github.com/gabriele2000/85f19e47d767078d12bc4a7322cc3450

EDIT: Updated log file

New report.

I bought Wildlands a few years ago, and played it for a couple of hours. I tried to spin it up again now, and it only gets as far as the loading screen. I even left the loading screen running overnight, but the next morning it was still loading.

Here's my Steam -> Help -> System Information: https://gist.github.com/opyate/f11eb78a55b1fd5c10bdc620eaa7954c

Attached is the proton log for Proton Experimental.

Other things I tried:

• earlier versions of Proton
• Glorious Eggroll versions of Proton
• disabling Steam overlay

Note that this is a new install of Ubuntu 23.10 and I use this one solely for gaming, and all my other games work nicely (Elden Ring, Hogfarts Legacy, Deus Ex: Mankind Divided, Prey 2016, etc etc)

steam-460930.zip

Edit: What worked in the end was downgrading the NVidia driver from 535 to 525.
Hopefully this advice helps someone else.

It's working for me with Proton 9.0-4 on Debain 13.

@MatPhysComp the game is launching fine every time on my amd desktop and nvidia laptop, the nvidia laptop is on a newer driver version with 580.82.9 so that's something worth trying to see if it makes a difference on your end. That aside, it's also worth trying proton experimental bleeding edge, there were changes helping with another ubisoft game that'd also not progress past the initial splash screen in certain configurations https://github.com/ValveSoftware/Proton/wiki/Proton-Versions#proton-bleeding-edge .

Hello @simifor,

Thanks for the quick response and for confirming the game works on your hardware.

I have followed both suggestions but am still stuck at the initial splash screen:

NVIDIA Driver Update: I successfully updated my driver to 580.95.05 (which is newer than the 580.82.09 version you mentioned).

Proton Version: I also switched to the Proton Experimental bleeding-edge build via the Steam client.

Unfortunately, the game behavior remains the same (stuck/freezing on the initial splash screen).

Are there any known issues regarding the Ubisoft Connect launcher specifically, or any specific launch options (PROTON_USE_WINE=1, etc.) I should try?

Thank you for the help.

Hello, im on the latest stable SteamOS on my steam deck OLED.
I bought the game last month, but was only able to try it today.
When I try to start it, the error "Easy Anti-Cheat not found" comes up. When I click OK, the game closes. I can't do anything. (I don't even want to play online).
I use the default Proton Experimental for this game. I also tried -eac_launcher as launch option. But no dice.

Edit: I think something with Proton Experimental is giving this error.
I used Proton 10.0-4 now and removed all launch options and it works.

I have been able to run it with Proton Hotfix, haven't saw any crashes/freezes so far.

@kisak-valve After trying too run with the updated proton experimental the issue remains the same. The game still freezes after a while. However the game runs fine with Proton Hotfix for me.

@darkhatcher17 Could you please get a log of the failure on Proton - Experimental as well as a log of the game running successfully on hotfix with the PROTON_LOG=1 %command%launch option? You'll need to rename the log between runs so it doesn't overwrite itself - default logs are stored in ~/steam-[appid].log.

@darkhatcher17 Could you please get a log of the failure on Proton - Experimental as well as a log of the game running successfully on hotfix with the PROTON_LOG=1 %command%launch option? You'll need to rename the log between runs so it doesn't overwrite itself - default logs are stored in ~/steam-[appid].log.

I am extremely sorry for the delay. Got caught up in some work and health issues.

steam-460930_experimental.log

proton_hotfix.log

The hotfix version is old, and it the only one that is working for me. Hope it helps!

@darkhatcher17 Thanks! Unfortunately nothing obvious in the logs, and the game is working here with a similar setup... you could try:
a) delete the game prefix (by default located in ~/.steam/steam/steamapps/compatdata/460930) after saving a backup in case there are save files or something in there.
b) Deleting your Proton - Experimental install folder (by default located in ~/.steam/steam/steamapps/common/Proton - Experimental) and using "verify integrity of tool file" to redownload - it is possible something is weird there.
c) Getting rid of any extra config files, launch options, etc.

@darkhatcher17 Thanks! Unfortunately nothing obvious in the logs, and the game is working here with a similar setup... you could try: a) delete the game prefix (by default located in ~/.steam/steam/steamapps/compatdata/460930) after saving a backup in case there are save files or something in there. b) Deleting your Proton - Experimental install folder (by default located in ~/.steam/steam/steamapps/common/Proton - Experimental) and using "verify integrity of tool file" to redownload - it is possible something is weird there. c) Getting rid of any extra config files, launch options, etc.

Did all that, still happening! the fps drops by a little and then gets stuck. Thanks anyways

I solved my problem and able to run the game. even with proton 11.
if after using my launcher options you still see a black screen, be patient it takes about 20 seconds on first launch.
The only problem that remains for me is after you quit the game, gamescope stays running with a gray background. you will need to quit it manually (not a big deal to me).

LD_PRELOAD="" gamescope -f -W 3440 -H 1440 -r 60 --force-grab-cursor -- %command% --launcher-skip

-If you don't use --force-grab-cursor then the cursor will escape if your desktop setup has multiple monitors.
-If you don't use --launcher-skip while using --force-grab-cursor the game crashes on startup. when i added this flag "--launcher-skip" it seems that the launcher that comes with the game doesn't like the force grab cursor flag.

Hardware:
3 Monitors (Samung S34E790C, Samsung S32D850T, ASUS VE278) all connected through displayport
CPU: AMD Ryzen 7 3700x
MB: ASUS X570-l
Storage: 2x 2TB M.2 SSDs Sk hynix Platinum P41 SSD PCI-e 4.0.
RAM: 64GB DDR4 @ 3000Mhz
GPU: Nvidia RTX 3060 (Driver Version: 580.173.02 CUDA Version: 13.0)
Mouse: wireless LogiTech M170
OS: Pop! 24.04
Kernel: 7.0.11-76070011-generic

Screenshots from the game: