Far Cry 3 (220240)

[rdlf4]

Launching Far Cry 3 via Steam Play makes a Uplay window to pop up and request that the user logs in at least once before we can use offline mode. Because games running via Steam Play do not connect to a network (so far), that Uplay window keeps the game from starting. Typing in username and password and then hitting Log in button won't change anything.

Steam System Info: https://gist.github.com/rdlf4/b77e018feb5104584927851c448f5a63

[tingvarsson]

@kisak-valve You are perhaps already aware but it therefore applies to all Uplay games (Assassin's Creed, Far Cry, For Honor, etc)
And I've seen similar issues for games requiring Origin as well.

[Kzimir]

Wine < 3.15 needs patches from Staging to have the possibility to connect correctly on UPlay.

[rdlf4]

@berillions Could you recommend a PPA that provides an updated Wine version which connects correctly to Uplay? If those patches need to be applied manually, could you give me a URL to point me to the right direction? I need some more clarification on this.

[Kzimir]

You can use the official wine repository for Ubuntu :
https://wiki.winehq.org/Ubuntu

[rdlf4]

Thanks. As much as I'd like to go add this PPA and update my Wine, that'd be way too easy. There's gotta be more to it than just that, right?

[dkoukoul]

I can report the same issue. Tried installing uplay under wine-staging 3.14 (on Ubuntu 18.04) and I can log in normally. From there it installed Steam (Windows version) and I can launch the game this way. But as soon as the game runs past the video intro it crashes with in a few seconds. I hope this helps resolve the issues.

[NanoSector]

Seems to be related to #172 .

[P4NCH1]

Well, we'll have to wait until they add to Proton a possibility to let Uplay connect like @berillions says

[HughPH]

I'd like to play Fractured But Whole, which also requires UPlay. Pretty sure this is about UPlay keeping games from working, so don't mark my comment as off-topic. It's very much on-topic.

[HughPH]

@kisak-valve
Is it worth merging in these?
#172
#1662

[lox-enterprises]

There is some progress on this issue, you can now select 'Proton 3.16 Beta' as 'Compatibility tool' in the Steam Play settings. This solves the issue of not being able to log in (I guess Proton versioning follows the Wine versioning so it's now on par with Wine 3.16, which makes it able to connect).

However... after logging in, it says 'Initializing...' and after a while it comes back telling me 'A Ubisoft services is currently unavailable'. I am able to then switch to offline mode, but it does not show the games from Steam under 'Games', even though I can verify online (on their site) the accounts are linked.

[dreamer]

To work past "Initializing" screen you need to have 32-bit gnutls linked as described in #162.

[lox-enterprises]

@dreamer I've tried the symlinking, doesn't solve it for me. I'm trying Assassin's Creed and it's the exact same situation as described here: #1757 (comments mention symlink doesn't solve it)

[dreamer]

@1202software what symlink exactly have you created and where? Did you link to 32-bit version of gnutls30? What distribution are you using? I have Uplay working correctly for Valiant Hearts by installing corefonts and linking to gnutls (and no other tweaks); linking to 64-bit version or creating link with wrong name won't solve the problem.

[lox-enterprises]

@dreamer I'm on Arch, so I used:

sudo ln -s /usr/lib/libgnutls.so.30.14.11 /usr/lib/libgnutls.so.26

...as per this comment: #162 (comment)

I'm not even sure it's a connection issue, because it does log me in (which requires a working internet connection).

[dreamer]

@1202software You linked 64-bit library. Arch stores 32-bit libs in /usr/lib32. Install lib32-gnutls and fix your link - it should make Uplay work for you :)

[edit] also, avoid placing your link in /usr/ - it's better to create it in ~/.local/share/Steam/ubuntu12_32/steam-runtime/pinned_libs_32/.

[lox-enterprises]

@dreamer Yes, that's it! I did have the lib32-gnutls package installed, but it required the symlink. Also, as you suggested, I put the symlinks in the Steam-directory.

So anyone using Arch, with Proton 3.16 as compatibility tool, should get it working with:

sudo ln -s /usr/lib/libgnutls.so.30.14.11 ~/.local/share/Steam/ubuntu12_32/steam-runtime/pinned_libs_64/libgnutls.so.26
sudo ln -s /usr/lib32/libgnutls.so.30.14.11 ~/.local/share/Steam/ubuntu12_32/steam-runtime/pinned_libs_32/libgnutls.so.26

I will add it to the post about Assassin's Creed as well, because I now verified you can get it running fine with Steam/Proton. Thanks for your help!

[dreamer]

For users of other distributions:

• Fedora and derivatives have 32-bit libs in /usr/lib/, 64-but in /usr/lib64/
• Debian and derivatives have 32-libs in /usr/lib/i386-linux-gnu/, 64-bit in /usr/x86_64-linux-gnu/
• Arch and derivatives have 32-libs in /usr/lib32/, 64-bit in /usr/lib

Creating link just to lib in /usr/lib/ may or may not work, depending on what game needs and what distro puts in there ;)

[SleepProgger]

Can confirm on debian stretch.
Using Proton 3.16-3 Beta and creating the links for gnutls worked.
The steam path is different tho and i linked libgnutls.so.30 which itself is a link to the real version.
This might make sense if there are minor library updates.

ln -s /usr/lib/x86_64-linux-gnu/libgnutls.so.30 ~/.steam/ubuntu12_32/steam-runtime/pinned_libs_64/libgnutls.so.26
ln -s /usr/lib/i386-linux-gnu/libgnutls.so.30 ~/.steam/ubuntu12_32/steam-runtime/pinned_libs_32/libgnutls.so.26

[legluondunet]

now with libgnutls tweak we can connect to Uplay but:

• Uplay WIndow is transparent or just black
• Uplay launch Steam installation instead of launch directly Far Cry 3, it doesn't recognize the Linux Steam client. The install can not continue because the Proton Steam folder is not empty

Someone has better results?

[dreamer]

@legluondunet Uplay window being transparent will be fixed once you install corefonts. Let Uplay install Windows Steam client (just choose some new directory), but DO NOT let installer run Windows Steam (there's no reason to). Once installation will be done, Uplay will work and login normally.

[kakra]

@dreamer This is how far I've come now (with my own wine-3.19-based Proton build). But the game still won't start. It just opens a black window after the splash logo, then closes. The wine processes stay running, closing Uplay from the systray doesn't fix this.

So we have two new problems:

1. The way Uplay titles start and stop is somewhat incompatible with how Proton expects titles to work. Not sure how to fix it but it could be a major inconvenience for many people.
2. Something in wine/Proton is still incompatible with the game itself - at least for me.

[RiderExMachina]

@doitsujin Awesome. Thanks for all your hard work!

[NTMan]

@doitsujin Today proton was updated to v4.2-9. By change log DXVK v1.2.3 should be shipped with this version proton, but the issue still here.

[doitsujin]

@NTMan Proton 4.2-9 still ships DXVK 1.2.1 with an Unreal Engine 4 fix.

[rdlf4]

@doitsujin Would you happen to know what Unity version this Proton release brings? Or does it not bring any Unity version at all?
See, the reason I'm asking is because I still cannot manage to run PCBS on Proton.
However, if I sideload the game and run it on Crossover with Hardware acceleration enabled, I get past the brands screen, have access to the menu and everything works as it should.. I mean, almost everything. There is no text or characters on the game.

I wonder why that is.

[kotek14]

Hey guys!
I decided to play Far Cry 3 today. This discussion was super helpful.

So, I ran into a problem.
I start Far Cry 3 via Steam, it says "Running", but nothing happens.
And I found a solution

sudo killall UplayCrashRepor

It looks like Proton doesn't know how to handle the crash reporter window or something like that.
I killed it and Uplay imediately popped up.

Hope my comment will help someone

[rdlf4]

For those of you who have been following this thread and are unaware, Proton 4.11 has been released. And this is big news because it features D9VK Support.
So if FarCry 3 struggles to run in DX11 on your machine, it might be a good idea to switch to DirectX 9 from the game menu. After that, exit the game, go to its properties and then set PROTON_USE_D9VK=1 as the launch parameter (along with DRI_PRIME=1 if you're running this game on a laptop) and see how it goes.

[leshow]

Does anyone know how to get the uplay launcher to show up? I unfortunately only found out you have to disable the overlay after already running the game. Now, when I launch the game it appears to skip the uplay launcher (it is running in the bg and draws it's overlay though).

[ziabice]

Using Proton 5.0-5 (but the same is with 5.0-4), the game doesn't work.

What happens:

• Uplay works perfectly at first run
• Game is stuck at the loading screen
• Alt-Tab is impossible, I have to switch to a console
• I have to manually kill farcry3_d3d11.exe
• Then Uplay doesn't respond: clicking on the tray icon doesn't bring it up
• Steam remains in a "Running" state
• I have to kill upc.exe

This is the log, launched the executable with PROTON_LARGE_ADDRESS_AWARE=1 flag.

The log:
steam-220240.log

[ziabice]

This is the log using PROTON_USE_WINED3D=1 flag, the results are the same.

The log:
steam-220240.log

Game and Uplay refuses to start at all using PROTON_NO_D3D11 and/or PROTON_NO_D3D10

[PedanXr]

Tried it today. Uplay is launching fine. But as soon as I run the game, I get the FC3 splash screen and another black window, where the game is supposed to run in.
Happens on current official experimental build and 6.3-5

Currently running pop!OS with NVIDIA proprietary drivers

[lucas-deangelis]

I have the same issue as PedanXr. I'm running Pop!_OS 21.04 with NVIDIA proprietary drivers (nvidia-driver-470). This happens on the experimental build and Glorious Eggroll 6.14-GE-1. 6.3-5 has a transparent window where Uconnect should be and stays here.

Here's a log of a run with 6.14-GE-1:
steam-220240.log

[intelligentgaming]

Tried it today. Uplay is launching fine. But as soon as I run the game, I get the FC3 splash screen and another black window, where the game is supposed to run in.
Happens on current official experimental build and 6.3-5

Currently running pop!OS with NVIDIA proprietary drivers

Same here on Kubuntu 21.04.

Tested with Proton Experimental and 6.3-6.

nVidia GTX 1080 - 470.63.01

[kakra]

For those with a black window: FC3 may start in D3D9 mode, and that will hang for ages at least because wine complains about invalid shaders in the compiler. If I remember correctly, you'll have to set it to D3D11 mode manually in that case by editing a config file. Or D3D10? Don't remember...

[intelligentgaming]

For those with a black window: FC3 may start in D3D9 mode, and that will hang for ages at least because wine complains about invalid shaders in the compiler. If I remember correctly, you'll have to set it to D3D11 mode manually in that case by editing a config file. Or D3D10? Don't remember...

That's exactly whats happening, I presume you can change it to DirectX 11 in a config file since I can't in game?

Strangely Far Cry 3 Blood Dragon does not have this issue.

[kakra]

FC3 may fall back to D3D9 more easily if it failed to start before... But ever since I changed it in the config file, it runs. But I don't remember which file it was but I found it on some game settings wiki.

[Patola]

I guess you are referring to the pcgamingwiki [entry about Far Cry 3](entry about Far Cry 3). It mentions GamerProfile.xml, which on proton resides under <steam prefix>/steamapps/compatdata/220240/pfx/drive_c/users/steamuser/My Documents/My Games/Far Cry 3/GamerProfile.xml. There's the following line in there:

        <RenderProfile MSAALevel="2" AlphaToCoverage="2" SSAOLevel="1" SDSM="0" ResolutionX="2560" ResolutionY="1080" Quality="optimal" QualityEditor="editor_ps3" Fullscreen="1" Borderless="0" UseD3D11="0" D3D11MultithreadedRendering="0" WidescreenLetterbox="0" UseWidescreenFOV="1" FOVScaleFactor="1.2" EnableSubResolution="0" SubResolutionX="960" SubResolutionY="540" VSync="0" RefreshRate="0" DisableMip0Loading="0" GPUMaxBufferedFrames="1" ShowFPS="0" Brightness="1" Contrast="1" GammaRamp="1" AllowAsynchShaderLoading="1">

So there's the UseD3D11 directive, which if at "0" should be changed to "1" to reactivate DirectX11.

[intelligentgaming]

Fixed it, you disable the Uplay overlay, and after that, the game launches.

I also added "PULSE_LATENCY_MSEC=90 PROTON_LARGE_ADDRESS_AWARE=1 %command%" to the game's custom launch options as recommended on ProtonDB.

This was with Proton 6.3-6

[Eddy-Pin]

Not sure why, but after having to install Ubuntu on a new SSD, the game doesn't launch. Proton Experimental and Proton 6.3-7 refuses to load dll's.

Here's the three error's in the proton log when I attempt to launch the game:

1. err:steam:initialize_vr_data Could not load libopenvr_api.so.
2. err:module:import_dll Library mfc100.dll (which is needed by L"Z:\home\edgars\.steam\debian-installation\steamapps\common\Far Cry 3\bin\FC3UpdaterSteam.exe") not found
3. err:module:LdrInitializeThunk Importing dlls for L"Z:\home\edgars\.steam\debian-installation\steamapps\common\Far Cry 3\bin\FC3UpdaterSteam.exe" failed, status c00001
   Also dropped the entire log for anyone interested.

steam-220240.log
35

[ghost]

@Eddy-Pin I had the same error, then I went to the terminal, issued: WINEPREFIX=~/.local/share/Steam/steamapps/compatdata/220240/pfx winetricks → selected "Select standard wineprefix" → Install Windows-DLL and searched for mfc100.dll, it's there.

But it wasn't enough: when trying to run Far Cry 3 again I'm met with a Windows dialog (through wine of course) saying "Far Cry 3 didn't find necessary registry, reinstalling it [the game] might solve the issue.". Checked proton logs, nothing useful...

[ghost]

Weird, after installing this other games: TES: Oblivion, Warhammer 40K Dawn Of War, Resident Evil 5, Halo Wars Definitive Edition, I just reinstalled Far Cry 3, without changes and it worked; fired up Steam autoinstaller (for DirectX and Uplay) and everything.

I think the other games installed some missing modules in Wine prefix, but it's just a guess.

[kakra]

I think the other games installed some missing modules in Wine prefix, but it's just a guess.

This won't happen, each game has its own private wine prefix.

I had the same error, then I went to the terminal, issued: WINEPREFIX=~/.local/share/Steam/steamapps/compatdata/220240/pfx winetricks → selected "Select standard wineprefix" → Install Windows-DLL and searched for mfc100.dll, it's there.

Please don't do this, do not use your system wine for a Proton-wine prefix, it can damage the DLL installation of the prefix. Rather, use protontricks instead.

It's more likely that using winetricks on the prefix damaged something, and some time later (after you installed the other games), some Proton update was downloaded and applied to the prefix, essentially "repairing" it.

[ghost]

Please don't do this, do not use your system wine for a Proton-wine prefix, it can damage the DLL installation of the prefix. Rather, use protontricks instead.

Thanks for the heads up.

It's more likely that using winetricks on the prefix damaged something, and some time later (after you installed the other games), some Proton update was downloaded and applied to the prefix, essentially "repairing" it.

Now that you've mentioned it, I remember deleting the game's prefix contents. I think that's exactly what happened.

[kisak-valve]

Proton Experimental 22-07-14 Update - New Issues in Far Cry 3

Issue transferred from #5993.
@K3zter posted on 2022-07-14T13:13:41:

Currently playing through Far Cry 3 on Steam Deck using Proton Experimental, was working okay however in the latest update there are strange colour issues and visual artefacts - when blood decals appear on the screen (e.g. when skinning an animal or being shot at), they are now luminous green, when going underwater there are flashes of various colours often filling the entire screen. Particle effects around glowing objects such as fire are also strangely discoloured.

[hakzsam]

@K3zter Can you explain how to reproduce? Can you upload a screenshot of the issue? Does proton 7 work fine? Is it Proton Experimental Bleeding Edge? thanks!

[alasky17]

@K3zter Also, could you 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?

[K3zter]

Hey, thanks for picking this up! I'll try to address all your queries:

@hakzsam

• To reproduce, you just go out to any body of water and swim around near the surface, or kill an animal and skin them
• Proton 7 does not load for me with this game, it hangs on the first loading screen. The game used to work fine in Proton Experimental until it did an update earlier today.
• I was using "standard" Proton Experimental I guess, not bleeding edge - didn't know bleeding edge existed until now, however I enabled it and the issue seems to have vanished so it may have already been fixed!
  Here is an imgur gallery with some screenshots (and one showing my settings)

@alasky17

• Here is a gist containing my Steam system info. As mentioned before it is a Steam Deck.

[intelligentgaming]

The game works out of the box with Proton Experimental, however you need to disable the Steam overlay otherwise the game will get stuck in an infinite loading loop on the first screen.

And annoying the Ubisoft Client does not close when the game is exited.