Yes, there is nothing suspicious in this logs.
Maybe in the steam-225540.log file is something more useful.
You have to put PROTON_LOG=1 %command% into the launch options in order to get this log file.
The file will be in then in your $HOME folder.
Hello @Cuddlypuff, 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.
@tfaller yeah I have the log, didnt find any errors other than the usual gameoverlayrenderer.so that cannot preload something (I get it in every game) but I'll add the log file to the issue in case it helps
AFAIK Just Cause 3 can only work with wine-staging (due to Denuvo DRM) + DXVK (due to graphic glitches with wined3d).
tried again in 3.7-6, still doesnt start, all I could find in the log was some sort of failure to load gameoverlayrenderer64.dll, but it comes up as a warning, not an error:
2524.254:0008:0009:warn:module:load_builtin_dll cannot open .so lib for builtin L"gameoverlayrenderer64.dll": /media/3TB/SteamLibrary2/steamapps/common/Proton 3.7/dist/lib/wine/gameoverlayrenderer64.dll.so: cannot open shared object file: No such file or directory
2524.254:0008:0009:warn:module:load_dll Failed to load module L"gameoverlayrenderer64.dll"; status=c0000135
2524.274:0008:0009:trace:module:LdrShutdownProcess ()
wine 3.18 + DXVK 0.90 not running on AMD R380
sunnydrake@main:~/.steam/steamapps/common/Just Cause 3$ PROTON_LOG=1 wine64 JustCause3 0009:fixme:heap:RtlSetHeapInformation 0xa50000 0 0x23e830 4 stub 0009:fixme:debug_buffer:RtlCreateQueryDebugBuffer (0, 0): stub 0009:fixme:debug_buffer:RtlCreateQueryDebugBuffer (168, 0): returning 0x6dc20 0009:fixme:debug_buffer:RtlQueryProcessDebugInformation (9, 14, 0x6dc20): stub 0009:fixme:debug_buffer:RtlDestroyQueryDebugBuffer (0x6dc20): stub 0009:fixme:thread:NtSetInformationThread info class 7 not supported yet 0009:fixme:ver:GetCurrentPackageId (0x22fe40 (nil)): stub 0009:fixme:msvcrt:__clean_type_info_names_internal (0x80c2c0) stub 0009:fixme:msvcrt:__clean_type_info_names_internal (0x704280) stub
It doesn't start with a wine 3.19 + staging + dxvk + Proton patches(*), running steam-for-linux, on nvidia.
But it does run fine without Proton patches (so wine + staging + dxvk, at least on nvidia), so with steam installed manually inside wine. (actually the only Proton patch to disable to get it working with steam-in-wine is the load_library's steamclient-lsteamclient swap)
FWIW, my guess is that Proton's lsteamclient is not enough for Just Cause 3: it might be looking for something else in the Steam install (it's not gameoverlay, you can disable it from steam and it still works with steam-in-wine, and I don't the see the "load module gameoverlay" anymore with Proton).
(I did not test without wine-staging)
(*): "Proton patches" as in Proton's wine fork steam hacks and patches
EDIT: remove log output about "importing dlls for .. failed": was caused by something else. JustCause3.exe dlls load fine now, just quits or crashes at startup.
Was there any headway with this? I'm running Proton 3.16-4
sysinfo+log = https://gist.github.com/benbrockn/cb4e2d40da111262bc9e479b88592b70
It seems to crash on trying to close a handle twice, I'm not sure if this is related to Denuvo. Applying the selected staging patches to Proton doesn't fix the problem (advapi32, all patches related to anti-tamper / anti-cheat engines).
106252.054:0024:0025:trace:module:LdrShutdownProcess ()
106252.054:0024:0025:trace:module:MODULE_InitDLL (0x7f8041a40000 L"lsteamclient.dll",PROCESS_DETACH,0x1) - CALL
106252.054:0024:0025:trace:module:MODULE_InitDLL (0x7f8041a40000,PROCESS_DETACH,0x1) - RETURN 1
106252.054:0024:0025:trace:module:MODULE_InitDLL (0x3b400000 L"steam_api64.dll",PROCESS_DETACH,0x1) - CALL
Setting breakpad minidump AppID = 225540
Steam_SetMinidumpSteamID: Caching Steam ID: 76561198086800809 [API loaded no]
106252.054:0024:0025:trace:module:MODULE_InitDLL (0x3b400000,PROCESS_DETACH,0x1) - RETURN 1
106252.054:0024:0025:trace:module:MODULE_InitDLL (0x7fffff8e0000 L"jc3AudioDSP_MultibandCompressor_SSE_F.dll",PROCESS_DETACH,0x1) - CALL
106252.054:0024:0025:trace:module:MODULE_InitDLL (0x7fffff8e0000,PROCESS_DETACH,0x1) - RETURN 1
106252.054:0024:0025:trace:module:MODULE_InitDLL (0x7fffff890000 L"cudart64_55.dll",PROCESS_DETACH,0x1) - CALL
106252.055:0024:0025:trace:module:MODULE_InitDLL (0x7fffff890000,PROCESS_DETACH,0x1) - RETURN 1
106252.055:0024:0025:trace:module:MODULE_InitDLL (0x7fffff8f0000 L"gfsdk_waveworks.win64.dll",PROCESS_DETACH,0x1) - CALL
106252.055:0024:0025:trace:seh:NtRaiseException code=c0000005 flags=0 addr=0x7fffff89cd73 ip=7fffff89cd73 tid=0025
106252.055:0024:0025:trace:seh:NtRaiseException info[0]=0000000000000000
106252.055:0024:0025:trace:seh:NtRaiseException info[1]=00000000006d0c60
106252.055:0024:0025:trace:seh:NtRaiseException rax=0000000000240038 rbx=00000000006d0c60 rcx=00007fffff8cf220 rdx=00000000006d0c60
106252.055:0024:0025:trace:seh:NtRaiseException rsi=0000000000090f60 rdi=00000000006d0910 rbp=000000007bcf17a7 rsp=0000000000240000
106252.055:0024:0025:trace:seh:NtRaiseException r8=0000000000000000 r9=000000000023fe17 r10=00007fffff94e100 r11=0000000000000000
106252.055:0024:0025:trace:seh:NtRaiseException r12=0000000000090f60 r13=0000000000000000 r14=0000000000000001 r15=0000000000090f90
106252.055:0024:0025:trace:seh:RtlVirtualUnwind type 1 rip 7fffff89cd73 rsp 240000
steam-225540.log from patched version
Attaching gdb show the following backtrace:
Thread 1 received signal SIGTRAP, Trace/breakpoint trap.
0x000000007bc90ff1 in close_handle (handle=handle@entry=0x2502e0) at ../../../../dlls/ntdll/om.c:415
415 RtlRaiseException( &record );
Just Cause 3 crashes at launch for me as well. I have a log file here:
System Information:
Distro: Manjaro
GPU: RX 580 8GB
Driver/LLVM version: Mesa 18.3.3
Kernel version: 4.20.10-1-MANJARO
Proton version: 3.16-4
https://gist.github.com/Simmonz/e2b52bfafda1942b35b86e2847dca620
Even with Proton 4.2 it still doesn't start.
steam-225540.log
Systeminfo: https://gist.github.com/NoXPhasma/b6e8c494cc5f92bbae4aae1f81cb25ee
Still not working on Proton 4.2-5. It says "running" in my Steam library, but never quits. Have to close Steam and choose "Exit Now" to get both Steam and Just Cause 3 to stop.
SysInfo & log = https://gist.github.com/benbrockn/136bd52256014504846aa1d2ac034815
cd ${HOME}/Downloads/DXVK/dxvk-1.2.1/
export WINEPREFIX=/mnt/Data/Steam/steamapps/compatdata/225540/pfx/ && ./setup_dxvk.sh install
Interesting find...
What I think is interesting, is that every log file I upload always states that it cannot find 2 dll files:
Those dll files are clearly in my steam folder (/mnt/Data/Steam/steamapps/common/Just Cause 3/)
Logfile & system info: https://gist.github.com/benbrockn/44da987620d98c922785588e742ebc77
@kisak-valve
Hello, has there been any work on getting Just Cause 3 compatible with Linux? It's been over a year now and I haven't seen any new replies to this thread.
Latest proton log & steam info here: https://gist.github.com/benbrockn/d64d88957729513aa54501f507f23e57
Did anyone manage to get any success with this game? I tried again today, but it's still crashing.
I did try to replicate the steps the Lutris install script runs, but that did not help either.
My log & steam info: https://gist.github.com/dafluf/888a7e1de346ad664bc3305145a1e3cd
It's still weird that it does work by running Steam through wine (using Lutris)...
With Proton 5.0, it starts and runs pretty well, although I'm having issues where after I finish the introduction missions (after the dinner cutscene), I close the game and bring it back up, and it appears nothing was saved, as I have to start all over again.
Log attached:
steam-225540.log
i can confirm the issue with Proton 5.0 that the game doesn't save the progress, so on every start you have to start from the beginning
I can also confirm that it doesn't save with proton 5.0-1
Just Cause 3 does not save game progress
Issue transferred from https://github.com/ValveSoftware/Proton/issues/3515.
@viktorheli posted on 2020-02-11T04:45:40:
The game starts and works fine. But the progress of the game is not saved. How to reproduce:
Apparently the game saves some files in:
$HOME/.steam/steamapps/compatdata/225540/pfx/drive_c/users/steamuser/My Documents /Square Enix/Just Cause 3/Saves/76561198035641064/
File creation dates and access times change after the game starts. But file uploads probably don't happen.
Proton log: https://gist.github.com/viktorheli/ebdd086ad924a0cd30197cf49cf24bd9
Just Cause 3 autosave
Issue transferred from https://github.com/ValveSoftware/Proton/issues/3591.
@CSForever07 posted on 2020-03-01T18:39:17:
I downloaded Just Cause 3 for my Linux gaming PC and while it runs like a beauty it has trouble autosaving where I basically have to start all the way from the beginning.
Creating the appropriate folder structure in protons global pfx does not work either, so saving is impossible as of today. Any idea?
Has anyone tried capturing the file writes/attempted reads using strace? Maybe the same structure is found in other games?
So JC3 works now!! Awesome job guys, I'm so happy you all got it working! @kisak-valve
There's only two issues that I've noticed:
(1) When you quit JC3, it erases your save data. Luckily I had save data from my old Windows box, and putting it in here worked upon starting the game. I was able to play exactly where I left off without any issues. Unfortunately, once you exit the game, it does not save any progress and I'm guessing it overwrites your previous save data with a clean slate. The workaround is to keep copying over the old save data before I start up the game.
/mnt/Data/Steam/steamapps/compatdata/225540/pfx/drive_c/users/steamuser/My Documents/Square Enix/Just Cause 3/Saves/
(2) The second issue is that it does not "see" my Xbox 360 Controller. My controller works flawlessly for countless other games, including No Man's Sky. It looks like JC3 will only detect mouse and keyboard input. I could be wrong and there might be some setting that I need to apply, in which case I'd be grateful if you all could point me in the right direction.
My latest error log can be found here: https://gist.github.com/benbrockn/67dec11cdd83cdcdb382c60ef254e4e6
(Will be updated when Xubuntu 20.04 LTS comes out)
@benbrockn
Luckily I had save data from my old Windows box, and putting it in here worked upon starting the game
It does not save any progress and I'm guessing it overwrites your previous save data with a clean slate.
This shows that saves aren't platform/per game install specific, and the issue appears to lie with file writing only. Maybe a complication with how it writes saves on NTFS or poor API translation?
Can you try installing a program called strace, running it with the launch option strace -o (where you want the file to be, an absolute path eg. /home/dave/strace.txt) %command%, waiting for a quicksave or manually saving, and uploading the file that it produces.
Proton 5.0-4 looks to fix the saving issue. I got past the "tutorial" missions and exited, then when I came back, it saved my progress correctly.
I can confirm that saving works with 5.0-4, but I have a strange bug. When I press on continue, the game just freezes and only goes on after I alt + tab out and back in the game. No idea what is causing this, never had that issue with running the game in Wine. It should just be in the game the moment you press continue.
https://gist.github.com/NoXPhasma/35d7ddf3ae948239a6cc179bca4f234e
steam-225540.log
Just put in an hour on Single Player, Proton 5.0-4, several quit & continues later & the game picks up from where I left off each time.
I go sleep, and the game gets miraculously fixed overnight, nice :)
Anyway, I'll look into the alt-tab issue through those logs. If anyone could leave reviews on protondb, that would make the rating go up since it pretty much works fully. Nice work Valve!
@NoXPhasma try using a different DE, like KDE or openbox and see if it changes.
If it helps narrow things down with the alt+tab bug I'm using Gnome & haven't had that happen so far.
This appears to be an isolated issue then, in the logs @NoXPhasma (sorry for the excessive tagging) provided it states they use Mutter, which is Gnome, I think.
I'm using Cinnamon, not Gnome.
It seems that the issue is with Cinnamon and/or Proton, and not the compositor either.
i can confirm the issue reported by NoXPhasma, same issue here also with cinnamon, but i had not such issue when i played it with steam for windows installed with lutris some months ago.
Not a big issue for me, can anyone confirm that this is only related to mutter?
Rather the opposite @WernerAUT , Gnome uses Mutter and it's fine. It seems to be a Cinnamon specific issue. Though the issue may be able to be fixed through proton.
yeah i overlooked the report which said gnome doesn't have the issue, so it is not mutter related.
Cinnamon uses a fork of Mutter called Muffin, and sure it could be the cause in this case. But the actual issue is not Cinnamon but Proton 5.0-4, as it works fine with Wine Staging. Might be Fshack which is causing this.
With Proton 5.04 all works fine. Big thanks for developers!
JC3 Support is near perfect level now, apart from the alt-tab cinnamon bug. Would it be a bit too early to ask for whitelist?
Did anyone get an Xbox 360 controller working? Not the whole "map the controller to keyboard inputs", but rather have JC3 "see" the controller?
I started playing this since proton 5.0-5 came out, haven' t tried previous versions.
Savegames do not work, same as people described when running versions prior 5.0-4. Could it be a regression?
The savegame I have from playing in 5.0-4 is working with 5.0-5, picks up right where I left off in the game.
I'm sorry. When game starts, it wont save until the first mission is complete. It is like that by design.
There is no regression.
I can't get the game to launch on Proton at all. Whenever I launch the game, it quits out after a second or two after launching. I'm using Proton 5.0-9, and have all of the game files verified. Turns out, I needed to re-install the game. The issue that was listed here happened with other games, even non-Proton ones.
I can't get the game to launch on Proton at all. Whenever I launch the game, it quits out after a second or two after launching. I'm using Proton 5.0-9, and have all of the game files verified.
What are your specs? Run neofetch in the terminal and paste what it says.
I'm using Pop!_OS 20.04 LTS, using kernel 5.4.0-7634-generic. My CPU is
an Intel Xeon E5-1650 0 @ 3.8GHz, with 32 GB of ECC DDR3 installed. My
GPU is an NVIDIA GTX 970.
On Fri, Jun 12, 2020 at 5:42 pm, Ben [email protected] wrote:
I can't get the game to launch on Proton at all. Whenever I launch
the game, it quits out after a second or two after launching. I'm
using Proton 5.0-9, and have all of the game files verified.What are your specs? Run neofetch in the terminal and paste what it
says.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/682#issuecomment-643536397,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACTZTPDCM2TZ3AT32C2ZKVLRWLDQPANCNFSM4FRTKXTQ.
Distro: Ubuntu 20.04 MATE
GPU: Nvidia 2080ti - drive 440.100
Kernel: 5.4.0-37
Proton 5.0.9
Issue - after entering the game the escape key or start key on controller do not bring up the main menu. Only way to quit game is via ALT+F4.
Other than this performance and visual fidelity are good.
I'm trying to run JC3 on SteamOS on a Zotac Nen steam machine, but the game launches to a black screen and stays that way
The following jist contains the proton debug log, as well as some information about the system, though I don't know how to get the steam info from the ssh terminal. Proton version is 5.0-9
https://gist.github.com/urandom/5bebcc5f29e6cc7fd92f0d93f996c643
I have been playing Just Cause 3 on my system and although it is playable, I have ran into quite a few issues:
System Information:
OS: Pop!_OS 20.04
RAM: 8GB
CPU: Intel core i5-8250u
GPU: Nvidia geforce 940mx
Just Cause 3 is broken again as of Proton 5.13-2, works fine on Proton 5.0-10.
Loads to a black screen, then freezes.
@kisak-valve
Had good luck playing Just Cause 3 with proton 6.3-2. Everything seems to work, even the async online features. On the other hand, I'm encountering some random crashes after a while. Sometimes it can take 15 minutes, sometimes I can play for hours without issues. I tried with Proton 6.5-GE-2 to see if it helped but I still see some crashes so I assume there's no difference there.
Updated Sysinfo: https://gist.github.com/Cuddlypuff/6c86804c84489d06e0b4c59b265dbd9a
Steam log that ends with my latest crash after 38mins of playtime: https://gist.github.com/Cuddlypuff/2209148795663f16798b963dd442f21f
(unfortunately this instance was playing with the GE build of proton, I'll switch back to proton default, so if the GE log is an issue I can come back with a vanilla crash log)
leaving a log with the crash running proton 6.3-2 in case it helps - looks like the same exception caused the crash in both versions
gist:https://gist.github.com/Cuddlypuff/307db4a5f71274b0d5b7e07895fba260
455991.069:0114:0118:trace:seh:dispatch_exception code=c0000005 flags=0 addr=0000000143720D51 ip=0000000143720D51 tid=0118
455991.069:0114:0118:trace:seh:dispatch_exception info[0]=0000000000000000
455991.069:0114:0118:trace:seh:dispatch_exception info[1]=0000000055b5c108
455991.069:0114:0118:warn:seh:dispatch_exception EXCEPTION_ACCESS_VIOLATION exception (code=c0000005) raised
Just Cause 3 stuttering with Proton 6.3-8
Issue transferred from https://github.com/ValveSoftware/Proton/issues/5491.
@ayush-sharma posted on 2022-01-10T14:13:04:
Hi,
I'm playing Just Cause 3 on Ubuntu 20.04 with Steam and I'm experiencing a lot of stuttering with Proton 6.3-8 and Proton Experimental.
Using Proton Experimental, game stutters when turning around.
EDIT: I've fixed it by using gamemode, game runs flawlessly.
Just Cause 3 (225540)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/5947.
@5zymon posted on 2022-06-29T07:13:23:
I am not sure if this is actually proton update issue but game run perfectly fine on 7.0-2. I've noticed that proton was recently updated on steam deck to 7.0-3. I also tried other Proton versions. Right now game tries to start, but shuts down seconds after initialization ( you do not see anything from the game actually, just a black screen). I've noticed Iron Harvest(826630) having same issues, and it was also working fine before. I cannot figure out anything from the logs unfortunately. I've removed proton prefix, I've verified local files in steam, but this didn't change anything, same behaviour.
Shows splashscreen when I press "Play" button, then crashes
Just run the game
@kisak-valve could you take a look at the log and see if there's anything obvious that may cause my issue? Thanks in advance!
debian bookworm, game runs, but is unplayable. I cannot figure out how to move the camera, game has no response from any mouse input or xinput controller.
edit: turn out you need to enable steam input, the games seems to not come with any xinput support.
tabbing out of the game causes it to crash.
@mathew2214 Mouse input is working normally on my end, and whether you need steam input will depend on your controller. For example, xbox series controller doesn't require steam input to work with this game, but playstation controllers do.
The game also didn't crash for me, if you're still seeing this issue then share information about your system and run the game with the following launch parameter: PROTON_LOG=1 %command%. This will create a file called steam-225540.log in your home folder, if you get the game to crash then upload the resulting file.
Just Cause 3 (225540): amdgpu page fault using Proton Experimental
Issue transferred from https://github.com/ValveSoftware/Proton/issues/8969.
@hugeblank posted on 2025-08-10T23:20:54:
page fault (see kernel log)
Thank you Kisak for moving the issue, and apologies for not understanding the repo structure.
I've done a bit more testing since posting the issue and I've found that in:
Proton 9.0 - the game freezes/crashes but the GPU does not page fault
Proton 8.0 - the game does not freeze at all and you can play the game normally
proton 8.0x1 2025-08proton 9.0x1 2025-08proton experimentalx4 2025-08proton 6.3-8x1 2022-01proton 6.3-2x2 2021-04proton 6.5x1 2021-04proton 5.0-10x1 2020-11proton 5.13-2x1 2020-11proton 5.0x3 2020-06proton 5.0-9x3 2020-06proton 5.0-5x1 2020-03proton 5.04x1 2020-03proton 5.0-4x3 2020-03proton 5.0-3x1 2020-03proton 5.0-1x1 2020-02PROTON_LOG=1x3 2025-08WINEPREFIX=/mnt/Data/Steam/steamapps/compatdata/225540/pfx/x1 2019-06d3d11.dllx1 2019-06dxgi.dllx1 2019-06cudart64_55.dllx1 2019-02jc3audiodsp_multibandcompressor_sse_f.dllx1 2019-02lsteamclient.dllx1 2019-02steam_api64.dllx1 2019-02win64.dllx1 2019-02gameoverlayrenderer64.dllx1 2018-09
edit: system info: https://gist.github.com/Cuddlypuff/a518019d119623d9a1b7552e284c1f6d
edit2: log: https://gist.github.com/Cuddlypuff/8d0277b8460793c16819388da48147a3#file-steam-225540-log
No error messages that I could find, from the terminal it looks like the game simply shuts down after starting:
Loaded Config for Local Override Path for App ID 225540: /home/cuddlz/.local/share/Steam//controller_base/empty.vdf
GameAction [AppID 225540, ActionID 4] : LaunchApp changed task to ProcessingInstallScript with ""
GameAction [AppID 225540, ActionID 4] : LaunchApp changed task to SynchronizingCloud with ""
saving roaming config store to 'sharedconfig.vdf'
roaming config store 2 saved successfully
GameAction [AppID 225540, ActionID 4] : LaunchApp changed task to SiteLicenseSeatCheckout with ""
GameAction [AppID 225540, ActionID 4] : LaunchApp changed task to CreatingProcess with ""
GameAction [AppID 225540, ActionID 4] : LaunchApp waiting for user response to CreatingProcess ""
GameAction [AppID 225540, ActionID 4] : LaunchApp continues with user response "CreatingProcess"
Opted-in Controller Mask: 72
Game update: AppID 225540 "", ProcID 13318, IP 0.0.0.0:0
Loaded Config for Local Override Path for App ID 225540: /home/cuddlz/.local/share/Steam//controller_base/empty.vdf