Jurassic World Evolution 2
@Lizardon09 Could you run a quick test to try to narrow down which component regressed? It looks like that game uses dx12 - it is possible to drop the vkd3d-proton files from one Proton version to another to see if that is the source of the regression.
cp -rf ~/.steam/steam/steamapps/common/Proton\ 7.0/dist/lib/wine/vkd3d-proton/* ~/.steam/steam/steamapps/common/Proton\ 6.3/dist/lib/wine/vkd3d-proton/.
cp -rf ~/.steam/steam/steamapps/common/Proton\ 7.0/dist/lib64/wine/vkd3d-proton/* ~/.steam/steam/steamapps/common/Proton\ 6.3/dist/lib64/wine/vkd3d-proton/.
After you are done testing this, you can return to the original version of vkd3d-proton that ships with 6.3-8 by just deleting the Proton 6.3/dist directory - it will recreate itself the next time you launch that version.
Did some tests. That component does not seem to be causing the issue. 6.3-8 still works even with 7.0 vkd3d-proton files. Included log files bellow.
@Lizardon09 Do you have a save game that you could upload that highlights this issue? I'm not getting anything close to 10fps that you got in your screenshot.
@alasky17 please find attached save game files (extracted from "steamapps/compatdata/1244460/pfx/drive_c/users/steamuser/Saved Games/Frontier Developments/Jurassic World Evolution 2/")
The save game I was using to test that yeiled the results was "Jurassic Park (Chaos Theory)" (should be the last one on the list) found under the Chaos theory tab when loading a saved game
@alasky17 An additional interesting observation i have made.
When using the time speed up mechanic during game play, the fps seems to tank drastically - when the game is running any of the proton versions except 6.3-8 (which gives desired performance)
Whilst the speed up does not tank fps when the game is running on proton 6.3-8. This you can see clearly as well, using the suggested save game scenario in the first comment of this issue.
Using the save game posted in my previous comment will also yield these results and show more effectively
Seems to be yet another game that suffers from the NVIDIA 530 version of the driver. Other games like Elite are suffering from it, too. Game just randomly has artifacts(especially while aiming in the helicopter in the first mission) and not because the GPU is fried(in my case it's a 1 month old 4080 and only shows these issues with the new driver version). Only fix currently seems to be to roll back to an older version of the driver.
Hello @PapaBones, can you be more specific with affected and known good video driver versions?
@kisak-valve
Hello @PapaBones, can you be more specific with affected and known good video driver versions?
There was some discussion on NVidia's forums that seems to confirm that, directly from the horses mouth.
ahuillet [An NVidia Forum Mod]
Jurassic World Evolution 2 (1244460)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/7148.
@MelvinRedondoTanis posted on 2023-10-03T17:04:23:
Compatibility Report
- Name of the game with compatibility issues: Jurassic World Evolution 2
- Steam AppID of the game: 1244460
System Information
- GPU: Intel® Xe Graphics (TGL GT2)
- Video driver version: 23.1.6
- Kernel version: Linux 6.5.5-200.fc38.x86_64
- Proton version: all
I confirm:
- [x ] that I haven't found an existing compatibility report for this game.
- [ x] that I have checked whether there are updates for my system available.
Symptoms
Logs : Proton : 8.0-3
Image :
(translation) : no 3D graphics card available, check that you have a graphics card compatible with directX12 and that the correct drivers are installed.
Reproduction
- launch the game with Proton (not version specific)
Steam Deck on latest Preview Build, tested on Proton Experimental, 8.0.4, 7.0.6.
Most dino models are broken, tried different settings in-game - no change.
Dinosaur models still seem to be broken as of recently on deck.
@waspennator I tested this one last night and found that the Dino models were no longer broken for me after the Stable 3.5.17 update. If you are still seeing broken models on Proton 9.0-beta, could you send a screenshot and describe which models/where I should be looking?
@waspennator I tested this one last night and found that the Dino models were no longer broken for me after the Stable 3.5.17 update. If you are still seeing broken models on Proton 9.0-beta, could you send a screenshot and describe which models/where I should be looking?
I don't exactly have the game on hand to check, I've mainly been seeing more people bring up the bugged dinosaur models around.
Update: Checking the community hub talking about the issue, seems like someone confirmed it was fixed on their end.
Compatibility Report
- Name of the game with compatibility issues: Jurassic World Evolution 2
- Steam AppID of the game: 1244460
System Information
- GPU: AMD RX7600S dGPU, 780M iGPU
- Video driver version: Mesa 24.2.7
- Kernel version: 6.11.10-304.bazzite.fc41.x86_64
- Link to full system information report: https://gist.github.com/lpomfret/efc7ca5dbdacb3e5037b46a697f19961
- Proton version: Proton Experimental (2024-12-09)
I confirm:
- [X] that I haven't found an existing compatibility report for this game.
- [X] that I have checked whether there are updates for my system available.
Symptoms
Screen locks up when attempting to enter any level, making the game unplayable.
Logs: steam-1244460.tar.gz
Reproduction
- Launch the game with the latest Proton Experimental (2024-12-09)
- Select any story or challenge mission
- Let any opening cinematic play
- Loading screen will appear to show progress at first, however will eventually lock up. The game has however continued to load in the background, as evidenced by dialogue and audio cues for pausing with space and bringing up the menu with ESC.
@lpomfret it appears both your dgpu and igpu are getting loaded, could you try adding the following to the game's launch parameters and let me know if it works? DXVK_CONFIG="dxvk.hideIntegratedGraphics = True" %command%
@simifor Doesn't appear to have made any difference. Had the same hang in the same place as before.
To confirm, what's the full complete line I should be adding to launch options to try that and get the proton log? I tried
PROTON_LOG=1 %command% DXVK_CONFIG="dxvk.hideIntegratedGraphics = True" %command% and PROTON_LOG=1 DXVK_CONFIG="dxvk.hideIntegratedGraphics = True" %command% and neither gave a log. Ended up running just DXVK_CONFIG="dxvk.hideIntegratedGraphics = True" %command% on its own just to make sure I wasn't somehow screwing up the launch options somehow by trying to include both.
@lpomfret %command% refers to the game that will be executed, so you only place it once, when you see the format string=string you can assume these are environment variable to be read by something that executes (in this case proton) so they have to be placed before what you're trying to run, either DXVK_CONFIG="dxvk.hideIntegratedGraphics = True" PROTON_LOG=1 %command% or PROTON_LOG=1 DXVK_CONFIG="dxvk.hideIntegratedGraphics = True" %command% would work here. If the issue still happens then upload a new log
@simifor The issue persists, unfortunately. New log attached. I allowed the opening cinematic for the scenario to play in full (rather than skipping it to go straight to the loading screen), and waited until the initial audio dialogue for the scenario to complete before closing, just to make sure the log would be as complete as possible. Hope this helps identify the issue.
steam-1244460.tar.gz
@lpomfret well that takes the igpu out of the picture, the only suspicious thing I see in your logs is a xrandr issue xrandr:xrandr14_get_adapters Failed to get adapters so I'm kinda curious if the game grabs your monitor's resolutions properly (settings > display). The last time I saw a user with a similar issue, it was due to the game trying to load both radv and amdvlk at the same time, but this doesn't seem to be your case. I tried mesa git, 24.3.1 and 24.2.7, but I couldn't reproduce the issue in either case.
@simifor Now that's interesting. The game was not grabbing my resolution correctly. It was outputting 1440x900, rather than 1920x1200.
After setting that to the correct value, I tried switching the game to windowed (I think it was borderless before), and then found I was able to start the level just fine. No idea whatsoever why windowed would work when borderless doesn't though.
Did you try starting it borderless after correcting the resolution?
On Sat, Dec 14, 2024, 7:32 PM lpomfret @.***> wrote:
@simifor https://github.com/simifor Now that's interesting. The game
was not grabbing my resolution correctly. It was outputting 1440x900,
rather than 1920x1200.
After setting that to the correct value, I tried switching the game to
windowed (I think it was borderless before), and then found I was able to
start the level just fine. No idea whatsoever why windowed would work when
borderless doesn't though.—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/6070#issuecomment-2543375684,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQZQ4EASRFXVFBPYEGTULET2FS5ZPAVCNFSM6AAAAABTQQCYY6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBTGM3TKNRYGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>
@simifor I've tried both Fullscreen and Borderless after correcting the resolution. Fullscreen had the same issue as before. Borderless got past that loading screen, but then crashed on the in-engine cutscene before the actual start of the level.
Jurassic World Evolution 2 (1244460)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/9227.
@gituser823 posted on 2025-11-16T13:15:29:
Compatibility Report
- Name of the game with compatibility issues: Jurassic World Evolution 2
- Steam AppID of the game: 1244460
System Information
- GPU: AMD Radeon RX 9070 XT
- Video driver version: 4.6 (Compatibility Profile) Mesa 25.1.9
- Kernel version: Linux 6.17.7-200.fc42.x86_64
- Link to full system information report as Gist: -
- Proton version: Experimental
I confirm:
- [x] that I haven't found an existing compatibility report for this game.
- [x] that I have checked whether there are updates for my system available.
Is this necessary?
Symptoms
Heavy artifacting of UI Elements, game unplayable with them, although it launches fine.
Reproduction
Just start the game and wait some minutes until the artifacts appear.
heres a screenshot of the issue:
Proton versions
proton experimentalx3 2024-12proton 9.0x2 2024-03proton 6.3-8x3 2022-09proton 6.3x1 2022-08proton 7.0x1 2022-08
Launch options
DXVK_CONFIG="dxvk.hideIntegratedGraphics = True"x3 2024-12PROTON_LOG=1x2 2024-12
Launch lines
PROTON_LOG=1 DXVK_CONFIG="dxvk.hideIntegratedGraphics = True" %command%x2 2024-12DXVK_CONFIG="dxvk.hideIntegratedGraphics = True" PROTON_LOG=1 %command%x1 2024-12DXVK_CONFIG="dxvk.hideIntegratedGraphics = True" %command%x2 2024-12
Upstream links
- ValveSoftware/Proton/issues/9227x1 2025-11
- ValveSoftware/Proton/issues/7148x1 2023-10
Compatibility Report
System Information
I confirm:
Proton Logs:
Symptoms
Playing the game on any proton version (using a save-game where there is a lot of stuff on the map and a lot of dinosaurs will yield more effective results, as when you launch the game and play the map, the GPU and CPU utilization will start at high percentages).
As you zoom in close to the ground - the GPU and CPU utilization drops from a certain point and even goes bellow 50% causing the game to run at very low performance even on low settings, the closer you are to the ground. When you zoom out, the utilization goes back up to what it should be when your close to the ground.
This happens with every proton version, EXCEPT Proton 6.3-8 (which is getting the desired rectified performance results for the symptom situations)
Cant use 6.3-8 to play the game because the pause menu does not work on that version, so would really really want this fixed :(
Following picture is using other Proton versions, that shows the problem:
Following picture is using proton 6.3-8, that shows the desired and proper performance situation that it should be:
Reproduction
(using a save-game where there is a lot of stuff on the map and a lot of dinosaurs. Will yield more effective results, as when you launch the game and play the map, the GPU and CPU utilization will start at high).