-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Just Cause 2 (8190) #670
Comments
Juste Cause 2 is a DirectX 10 game and I think Proton does not integrate yet the DirectX 10 feature from DXVK (look at the changelog). Anyway, Just Cause 2 is too unstable to be playable with last Wine version and DXVK doitsujin/dxvk#567. |
Using Proton 3.16-1 Beta Just Cause 2 can be launched after several attempts. Overwhelmingly unstable, despite great performance (constant 60 fps).
|
I am using Proton 3.16-2 Beta. still unable to launch it System info:
|
The Game doesn't launch for me as well. In the log file is a trace. steam-8190.log None of the parameters posted by @pchome helped. Sysinfo: https://gist.github.com/NoXPhasma/0342aabb8fe583a36509c772718c179d |
@NoXPhasma |
I'm not going to smash the launch button just to be lucky at some point. If you look into my log file, you will see that there is a trace, so something wents really wrong and needs to be fixed or considered to be garbage. |
Backtraces for this game are considered useless, even when I launch this in environment full of debug symbols -- I can see different points every time.
and so on.
Aaa..nd you shouldn't. |
Here's a log from Proton 3.16-4 Beta still no joy. |
Fun fact: the game now works for I successfully launched it three times in a row, just for curiosity.
|
@pchome does not work for me. Then Winetricks can not install d3dcompiler_47, how did you install it? |
I copied it from another prefix into game's directory. |
The game is stable for me with DXVK built from current git master. FPS =~50-60 with everything maxed (except AF/AA). Also, see above referenced issue, if you trying to launch the game on odd days 🤕 . |
Just Cause 2 crashes at startup for me as well. I added PROTON_LOG=1 %command% to the game's launch options and received the following log: My system: https://gist.github.com/Simmonz/43bcff5808cdb180aa995542353a6bb6 |
Good news... sorta. Proton 4.2 loads it to a black screen (doesn't crash beforehand at least). Had to Alt F4 and wait for the window manager to offer to kill the process. |
Proton 3.16-8 beta has always lead to a black screen on Just Cause 2 for me. Takes 2-3 minutes for the screen to load up though. The game is fully functional on wine 3.21 and above (oldest version I tested) so this is definitely a proton issue. There's some talk on here about the game being unstable with certain options selected. I don't use vsync, but the game runs butter smooth with everything as high as they can go on Nvidia's latest drivers in regular wine. |
I tested JC2 with Wine 4.2 staging (Lutris version) + Steam for windows. The game launched and I can go to the aim menu and launch a demo. |
@tsalwierz Ahh thanks. I thought I had tried on 3.16 and was getting the instant crash. Good to know. |
Proton 4.2-3 still no joy getting it to run. |
It works with a cracked .exe and then install with protontricks: d3dcompiler_43, d3dcompiler_47 and d3dx10. The DRM is, with no surprise, CEG. See #753 |
This game seems to work with recent Wine-Saging 5.5 version (and so soon in a future Proton version?). After a lot of tests, I can finally launch this game (steam version). |
Just Cause 2 (8190) Issue transferred from #4644. Compatibility Report
https://gist.github.com/ioannis120/c664f015742641d8441b0f4fdddf985b It does not start |
Just cause 2: crash on startup Issue transferred from #4692. Compatibility Report
System Information
I confirm:
SymptomsGame crash on startup ReproductionJust launch the game |
After some debugging myself, I can confirm the game crashes in Proton due to the Steam DRM working improperly. Code that should get mapped to a certain address doesn't, and the game crashes on an invalid instruction due to this. Even once that's fixed, it tries to compile shaders that are unsupported with Wine's current built-in d3dcompiler and ends up hanging at a black screen. Hopefully this adds some context for anyone trying to work on this in the future. |
I'm curious if this game will end up working on the Steam Deck. Valve did say they couldn't find a game that didn't just work. |
Works for me on latest beta client and experimental proton. Just had to run some proton fixes to fix direct x issue. |
@smintman What DirectX issues are you talking about? I made the game work with DXVK back in 2019, are there any issues with it now? |
Can’t remember the exact error but was something about Direct x 10 fatal error Looked in proton db and some where suggesting using protontricks 8190 dlls d3dx10 d3dcompiler_43 d3dcompiler_47 Which did the trick and ran amazingly. If I could run it without using the above proton ticks that would be even better? |
Seeing a black screen, then a crash when using, after running the protontricks. |
I have gotten the game to work properly including a workaround for the game staying permanently minimized. The game seems to detect the xbox 1 controller ok as an option menu shows up for x360 controller. The benchmark tool runs. I didn't actually play the game yet though. Currently you need to switch Proton Experimental to the "bleeding-edge" beta. Then set the following launch options for the game. Note that at least for me the game will be permanently stuck minimized if you don't use the borderless command line switch option. This may work differently depending on DE or number of monitors connected. The game doesn't have a borderless switch in the game, just fullscreen on/off so you have to set it on command line. The game has a binary settings file so even if you could set borderless in the settings file it would be difficult. Edit: also I had ran "protontricks 8190 d3dx10 d3dcompiler_43 d3dcompiler_47" on the prefix. |
Actually, i had to I did not have to "PROTON_NO_FSYNC=1 PROTON_NO_ESYNC=1 %command% /borderless=1" yet. |
I did some test on the campain, it's did go well untill the Casino. Unfortually, i do freeze a lot, had to restart the pc many times. I did try "PROTON_NO_FSYNC=1 PROTON_NO_ESYNC=1 %command% /borderless=1" Not but changes. I will wait for @BillFleming to get pass the Casino to see if he also have issues. |
Apparently, my problem wasn't Wine-Proton based but windows players also have it. There is the solution : https://steamcommunity.com/app/8190/discussions/0/154644598510833416/?ctp=23 I did disabled Decals & Bokeh Filter. Probably that the Casino scene had more gunfights and action than the precedent scenes. |
After running this command (this is a prerequisite for DXVK's DX10 support, IIRC) the game is playable. |
Proton Experimental with the protonricks from above it gets to splash screen for 1 second and then crashes out https://gist.github.com/parkerlreed/42118febd90183f763b087bdf25d763c |
Seems to bail at ERROR: Could Not Get Primary Adapter Handle right after wine's built-in avrt.dll audio? EDIT: Finally got a popup saying fatal DirectX error (Same log entries) after switching back to Experiemental. |
Trying WWINED3D ends in the same errors but spits out some more info about typeless format errors. |
I don't know what it is or what it was, completely uninstalling the game and prefix, reinstalling, and using the protontricks from above has finally made this game work. |
If it's not one thing it's another... Was able to play a little bit into the tutorial with no issues. Very shortly after getting the first gun and then hopping on the turret to take out helicopter, a weird mouse issue appears. Anytime the mouse is moving (which is a lot in an FPS...) the frame rate drops to 0. Stop moving the mouse, back to 60 I've seen this in one or two other games but thought they were one offs and don't recall which ones. https://gist.github.com/parkerlreed/42118febd90183f763b087bdf25d763c New log if it's at all helpful Video 20220619_015712.mp4 |
Appears to be a re manifestation of https://bugs.winehq.org/show_bug.cgi?id=46976 Setting the USB HID polling rate to 125Hz (off the default 1000) and re plugging my G400s allows the game to work properly. |
Unfortunately I cannot reproduce any noticeable video dropouts with a high polling rate mouse (G502 Hero), so I can't speak for it being anything but a specific hardware quirk. One thing I've noticed about JC2 is that it has some NV specific effects when nvapi is enabled - unfortunately, current Experimental seems to lack the ability to enable this for other games, but using the GE fork of Proton I can use Given the recent efforts to enable NVAPI in Experimental, will there be plans to allow this game to be enabled for nvapi support in upstream Proton? And if so, could the nvapi-related crashes in this title be addressed? If not, would this be considered a DXVK-NVAPI issue (considering it's only affected by having the NVAPI enabled), or an upstream DXVK one (because of it causing crashes, presumably unimplemented functions in that side)? |
@SeongGino You mean running with nvcuda is a dll included with valves wine fork from what i can see. But it doesn't actually contain any code. |
I'm pretty sure the Wine Staging version doesn't support D3D interop, especially not with DXVK. I think it's possible to implement (a lot of the CUDA interop work is already done for DLSS) but I don't think anyone is going to do it. |
Indeed. This is all just history from my experimentation with Batman: Arkham Asylum's PhysX and what I found (typically) allowed real HW accelerated CUDA operations. I guess I'm not all that surprised that support for these functions in JC2 may not come; I was simply being thorough with reports when going through my PhysX/CUDA-utilizing games library--it's the only game I've found which doesn't work with Nvidia extras. Would be nice if it ever came tho - even if it's just for some minor graphical nicety. |
So far didn't have any problem playing using the Protontrick method tested under Ubuntu 22.04.2 LTS x86_64 with Proton Experimental, full controller support and gyro. |
The game does not launch, whatever the tips I tested on Protondb. https://gist.github.com/legluondunet/8c353105c386d1a121041a3ad1b4a2b4 |
I uninstalled the game and reinstalled it today, it launched fine, without any tricks, no need to install anything with protontricks either, you changed something that could explain this good news ? |
Game still gets stuck on a black screen on launch on my oled deck. |
I got it working, here are my steps:
However, I was running into one issue. The game would launch but immediately crash with this error:
The solution was the install the following packages:
DXVK was throwing these errors:
Thus the missing 32-bit libraries were needed, as the game is indeed 32-bit and not 64-bit.
|
@waspennator @jessienab
I never need to install anything with Protontricks, I think it is no more necessary, Steam already install all this dependencies at first game launch. Result could depend your config too, this is mine: Manjaro 23.1.4 Vulcan |
One more thing: |
Using Proton 3.7-4 Beta Just Cause 2 crashes on startup with
Unhandled exception: privileged instruction in 32-bit code (0x00449000).
Logs: https://gist.github.com/stratus-ss/6aa9f13c36972cfd0868834d6bce7c50
System info gist: https://gist.github.com/stratus-ss/73e90ae7dcc42caf324190ea36e979cc
I am posting this one because I have seen this error in a few other games I have tried this past weekend. It seems to me there may be a common fix, but this is the game I have put the most time into overall
The text was updated successfully, but these errors were encountered: