Try to update your nvidia drivers, it's newest version is 410.xx atm. That already helped me with several games on proton 👍

I'm on the latest Dev drivers now, no change

It seems like old WINE versions needed a patch to avoid the black screen problem. See :
https://bugs.winehq.org/show_bug.cgi?id=39731

Altho i got it to run with PlayOnLinux without a problem some time ago (except the uplay launcher problems that is)

Proton 4.2 has the same problem for me.

I attempted that but still get a black screen. Far cry 3 had the same black screen problem for me but disabling Uplay overlay worked for that and I'm able to play that game now.

Same issue for Assassin's Creed Freedom Cry (277590) which was a standalone expansion pack based on the same engine.

Using proton 4.2.4 still return a black screen.
Even with Lutris, and using the last script on https://lutris.net/games/assassins-creed-iv-black-flag/
I need to change manually the Wine version to 4.8-ge-faudio-protonfied to fix the black screen, and I could play this game with standard settings. In contrast, 4.6 branches are totally broken!
Selecting Single Play are OK, but multiplayer will close the game.

@kisak-valve you can approved the merge request in wine? for https://github.com/ValveSoftware/wine/pull/55 or i need to wait to something more, with this patch i can play the game in staged wine, please thanks

I attempted that but still get a black screen. Far cry 3 had the same black screen problem for me but disabling Uplay overlay worked for that and I'm able to play that game now.

how disable overlay in game? i press always shift + f2 and never working, and uplay icon no show.

I attempted that but still get a black screen. Far cry 3 had the same black screen problem for me but disabling Uplay overlay worked for that and I'm able to play that game now.

how disable overlay in game? i press always shift + f2 and never working, and uplay icon no show.

Either when uplay launches during initial install or when uplay is visible in system tray after game closes.

if i disable overlay still dont work, the patch no working in 4.11.1

any update, this game works with lutris but dont works with proton, ,any advance

It works with latest Proton 5.6 from @GloriousEggroll and I believe this is due to the media foundation patches that went into it. I think Proton upstream will soon receive similar patches.

But I'm having issues with the controller: I need to keep a trigger pressed, otherwise the camera spins. In fact, I just need to move any axis of the controller to stop the spinning. This issue is also present in AC Unity but it worked properly in Proton 4.2, so there's a regression in Proton 5.0 (and thus also in GE version). Ubisoft forums suggest that this happens when multiple controllers are connected, so maybe Wine presents multiple instances of the same controller to the game? According to winecfg, there's only one.

It works with latest Proton 5.6 from @GloriousEggroll and I believe this is due to the media foundation patches that went into it. I think Proton upstream will soon receive similar patches.

But I'm having issues with the controller: I need to keep a trigger pressed, otherwise the camera spins. In fact, I just need to move any axis of the controller to stop the spinning. This issue is also present in AC Unity but it worked properly in Proton 4.2, so there's a regression in Proton 5.0 (and thus also in GE version). Ubisoft forums suggest that this happens when multiple controllers are connected, so maybe Wine presents multiple instances of the same controller to the game? According to winecfg, there's only one.

thanks for report

i have made for working

wget https://github.com/GloriousEggroll/proton-ge-custom/releases/download/5.6-GE-2/Proton-5.6-GE-2.tar.gz
mkdir ~/.steam/root/compatibilitytools.d
tar -C ~/.steam/root/compatibilitytools.d/ -xvf Proton-5.6-GE-2.tar.gz 

Restart steam and in properties of each game select proton-5.6-GE

and works, the multiplayer no working stale i get fps around 10 to 15 but the single player working well all settings in high and 60 fps

Just an update to confirm that this problem still exists in the last version of mainline Proton.

Compatibility Report

Name of the game with compatibility issues: Assassin's Creed Black Flag
Steam AppID of the game: 242050

System Information

GPU: RX 6700 XT
Driver/LLVM version: Mesa 23.0.3-1
Kernel version: 6.1.31-2-MANJARO
CPU: Ryzen 5700g
Ram: 32gb
Proton version: 8.0.1 and Experimental

Game doesn't launch and will sit there until the button goes back to play
Log: https://gist.github.com/coreybruce/a6dff4cb7ea13efce43eb7ac253926f9

• Install Black Flag.
• Launch game and it will just show it setting up the proton prefix but than sit there saying it's playing until it will close itself

I cannot activate the game to play it. When I put the CD Key in the required field it always fails with this error:

Maybe login to Ubisoft website and try to register the key in your account there?

You can also try this first (before starting the game):

sudo sysctl net.ipv4.tcp_mtu_probing=1

With latest Proton Experimental, 'ACBF' will start from via 'Ubisoft Connect' and playing with HIGH graphics settings (incl. SSAO, VSYNC, etc.) works.

Problems with a choppy/jerky rendering occur after some time playing, though - e. g. near ending the first introductory shipwreck surviving island episode.

I've seen this kind of problem before, e. g. with 'Journey to the savage planet':

The environment and character animations run smoothly, as long as there's no mouse movement changing the POV - when just using X/Y movement keys, there's almost no noticeable graphics 'stuttering', which looks similar to a slow, choppy shutter setting on a digital video camera, where several frames are dropped in a fixed interval.

Once this behavior 'kicks in', rendering stays that way and the only remedy seems to completely stop the running Proton instance and relaunch everything from start.

Therefore, this bug may not be game-specific, but it struck on ACBF now and again, so I'm reporting it in this thread.

I've updated the comments on how I managed to properly set up 'Ubisoft Connect' and the games in the same prefix here:
Ubisoft Connect Thread