Planet Zoo (703080)

[jtw-cw]

Compatibility Report

• Name of the game with compatibility issues: Planet Zoo
• Steam AppID of the game: 703080

System Information

• GPU: Radeon RX 570
• Driver/LLVM version: Mesa 19.0.8
• Kernel version: 5.0.0-32-generic
• Link to full system information report as Gist: https://gist.github.com/jtw-cw/dd21cb7b59a04b0bca72444f272c6e6b
• Proton version: 4.11-8

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

Symptoms

Game crashes at Startup with a Wine C++ Runtime Error.

Header: "Wine C++ Runtime Library"

Box:
"R
Program: Z
a

Press OK to exit programm, or Cancel to start the Wine debugger"

Reproduction

Just start it again. Reproduction possible with other Proton Versions.

steam proton log

steam-703080.log

[farahanams]

Basically I have about the same output.

[benderni]

I'm encountering the same issue

System Information

• GPU: Nvidia GTX 1050TI
• Driver/LLVM version: Nvidia 435.21
• Kernel version: 5.3.0-20-generic
• Link to full system information report as Gist: https://gist.github.com/benderni/0b1164ceebebbae4381585dd06f2c39c
• Proton version: 4.11-8

steam proton log

steam-703080.log

[miyunari]

i got the same issue on my system :(

System Information

• GPU: Nvidia GTX 970
• Driver/LLVM version: Nvidia 415.27
• Kernel version: 4.15.0-70-generic
• Proton version: 4.11-8

steam proton log

steam-703080.log

[treymerkley]

Can also confirm.

• GPU: NVIDIA GeForce GT 740
• Driver/LLVM version: NVIDIA 430.40
• Kernel version: 4.19.69-1-MANJARO
• Proton version: 4.11-6

[SpntKbrg]

Adding the "ucrtbase.dll" like Planet Coaster #1538 manage to get pass the Wine C++ Runtime Error for me, (I also unplug the USB mouse and keyboard)

but the game still crashes before any black screen appears and shows the game's Crash Reporter and leaves behind the PlanetZoo.exe process that needs killing

System Information

• GPU: NVIDIA GeForce GTX 1060 Mobile 6GB
• Driver/LLVM version: NVIDIA 440.31
• Kernel version: 4.19.86-1-lts
• Proton version: 4.11-9

Steam Proton Log

steam-703080.log

[jtw-cw]

Adding the "ucrtbase.dll" like Planet Coaster #1538 manage to get pass the Wine C++ Runtime Error for me, (I also unplug the USB mouse and keyboard)

but the game still crashes before any black screen appears and shows the game's Crash Reporter and leaves behind the PlanetZoo.exe process that needs killing

I can confirm this behaviour.

[BOFH90]

I can also confirm

[alvarlagerlof]

Does anyone have an update on this?

[nadrolinux]

Game still crashes at startup with Proton 5.0-2.

[nerzhul]

Tested on Proton 5.0-4, still crashes

[steve7233]

I see I am not the only one. Planet Coaster runs fine without any issues but Planet Zoo says C++ runtime error.

[AlexeyProkhin]

After long sessions of debugging, log reading and looking at the disassembly, I think I pinpointed the crash. The game uses nt kernel functions to access files. The functions, however, are case sensitive by default (or, at least, implemented in wine as such). The game tries to read a file by its name in the lower case while the actual file on the disk in the camel case. The games fails to read the file and eventually crashes.
I made a hack to force the relevant functions to be always case insensitive: AlexeyProkhin/wine@c3036bc. With the workaround the game opens a window, shows a logo and, unfortunetely, gets stuck on it. Can someone else test the patch? I would appreciate confirming the game does not crash with it. I am especially interested what would happen for AMD users as the game loads nvapi64.dll for me which may explain its being stuck on the logo.

P.S. I made a build with my workaround: https://drive.google.com/file/d/15i9MSm_sPrAgo2wGaS_4ezCcHC-vvxgW/view?usp=sharing. It is totally untested however, denuvo blocked me for one day.

[sfjuocekr]

You are correct, at first I also got the C++ error and it was looking for a lower case path on z:

This happens with your patch, which is hopeful:)

But it hangs at this screen now, I have a GTX970.

Added this to launch options:

WINEDLLOVERRIDES="nvapi=d;nvapi64=d" %command%

Didn't work either.

How do I get meaningful logging out of Proton / game? It's just waiting for something right now, if you close the game with alt + F4 the window closes but the game never does.

Too bad you get the 24 hour timeout pretty fast :(

[Gertjan-Timmerman]

Same issue with an 5700XT

[JWolvers]

@AlexeyProkhin I build proton GE with your patch and now it is working!

Just unpack this build here: ~/.steam/root/compatibilitytools.d/
Then restart steam and select proton-planet-zoo under The "Force the use of a specific Steam Play compatibility tool" option.

[ruunix2]

I tried @AlexeyProkhin 's build per the notes in @JWolvers post, and was not able to get it running. After clicking play, Steam switches to say the game is running, and a few seconds later it goes back to saying Play. Nothing appears to pop up indicating the game is actually running though. Sounds like an early crash but nothing is in the logs.

Checked through the main Steam logs and was only able to find a line indicating that the app started, and then a line immediately after saying the app exited.

Proton log attached.
steam-703080.log

Not sure if I'm missing something from the above.

[Qwertie-]

@R-u-u Run steam via the terminal and it will give you better logs

[SpntKbrg]

Tried the Proton-GE build in @JWolvers post as well.
The game does start and reach the main menu.

But after a minute it froze and need to kill the process.
The full proton log is way too big to be uploaded here because of a repeated error
err:nls:get_codepage_table too many codepages and a lot of trace.
Here's the log without codepage and trace:
planetzoo_proton_filtered.log

I'll try again with a clean install later. (EDIT: still froze randomly on the menu screen)

[nerzhul]

It sounds promising. Can we expect new NT functions patch to be implement both in proton and wine ? That may help wine upstream on some other games outside of steam

[Gertjan-Timmerman]

Also tried the Proton-GE build. It seems to start, and I do see the menu and can start a game, but the main screen stays black.

Edit: Seems to be working when putting all graphics settings to low/off

[AlexeyProkhin]

@JWolvers Thank you for confirming. I was actually planning to do the same thing today. Because yesterday I was able to get into the game for the first time. I added the game into lutris and used the wine steam runner and lutris-5.5-2 wine build. But to bypass the case sensitivity issue I remounted my ntfs drive with games as case insensitive:

sudo umount /media/wingames/
sudo mount -t lowntfs-3g -o ignore_case /media/wingames/

It sounds promising. Can we expect new NT functions patch to be implement both in proton and wine ? That may help wine upstream on some other games outside of steam

As of right now, no. First there must be some tests to confirm if it's wine's issue or if the game makes wrong assumptions. The hack may probably go into GloriousEggroll's fork, but even before that it must be modified to be enabled only for the game.

[EchoUrandom404]

After long sessions of debugging, log reading and looking at the disassembly, I think I pinpointed the crash. The game uses nt kernel functions to access files. The functions, however, are case sensitive by default (or, at least, implemented in wine as such). The game tries to read a file by its name in the lower case while the actual file on the disk in the camel case. The games fails to read the file and eventually crashes.
I made a hack to force the relevant functions to be always case insensitive: AlexeyProkhin/wine@c3036bc. With the workaround the game opens a window, shows a logo and, unfortunetely, gets stuck on it. Can someone else test the patch? I would appreciate confirming the game does not crash with it. I am especially interested what would happen for AMD users as the game loads nvapi64.dll for me which may explain its being stuck on the logo.

P.S. I made a build with my workaround: https://drive.google.com/file/d/15i9MSm_sPrAgo2wGaS_4ezCcHC-vvxgW/view?usp=sharing. It is totally untested however, denuvo blocked me for one day.

This game works flawlessly after applying this patch! However, I have noticed the clouds are a bit buggy. Though I doubt this is going to stop players from playing the game given how it never even booted before hand. :)

I am using Fedora 31 with AMD RX 580 GPU using the open source drivers. I am not sure if this is reproduce-able but I will provide logs if necessary to fix it.

[vpfeiffer]

Just unpack this build here: ~/.steam/root/compatibilitytools.d/
Then restart steam and select proton-planet-zoo under The "Force the use of a specific Steam Play compatibility tool" option.

This patch works out of the box for me although in game there is some lag. I haven't tried tweaking the graphics settings yet. I was able to get in game and interact with a zoo. I'm using NixOS channel 20.03 and have a Nvidia GTX 760 graphics card.

Update: I am unable to reliably load saved games. Changes to the master volume setting are reverted to the previous sate.

[AlexeyProkhin]

As of right now, no. First there must be some tests to confirm if it's wine's issue or if the game makes wrong assumptions.

I looked into it one more time. Like I said before the game uses NtCreateFile() but does not set OBJ_CASE_INSENSITIVE attribute. It tries to open "gamemain" directory while the real name on the disk is "GameMain". It works because windows mounts ntfs drives as case insensitive.

It is clearly a bug in the game, it makes an incorrect assumption that drives are always case insensitive. A hack similar to the above one is probably the only way to fix the issue. I can't be sure about it, but I'll open a merge request and let the proton devs decide. Edit: I just remembered the hack does not work with proton master for most people. So it is way too soon opening a merge request.

[Qwertie-]

@AlexeyProkhin Do you think this could be worked around by renaming the file to gamemain? I gave it a shot and it still crashed but I don't know too much about what is going on. I can confirm the patched proton got it working for me on Fedora 31 with an RX 5700xt.

Edit: I gave this a longer play and it crashed after about 20 minutes

[TvanZ]

The game initially works, but freezes or crashes during the tutorial after some time. At that point it shows to be using over 100% of the CPU.
Edit: even in the menu screen, the process is reported to use over 100% of CPU, however the CPU reports only a load of around 35%. The CPU is an Intel® Core™ i7-8750H. When exiting the game through the 'quit game' button in the main menu, the process remains running in the background while the reported CPU usage ticks down over time.

I have an RTX2060 and am using proprietary nvidia drivers. The game also gives a warning when starting saying that the drivers are out of date, which I know for a fact is not true. After a clean install this warning does no longer show.

I will look into how to provide a better log by running steam/planet zoo through the terminal, but I have never done that yet, so it might be some time.

[Guite]

Just unpack this build here: ~/.steam/root/compatibilitytools.d/
Then restart steam and select proton-planet-zoo under The "Force the use of a specific Steam Play compatibility tool" option.

This looks very promising! Game starts without problems. No further tests done yet though. Using a GeForce GTX 1060 with proprietary drivers.

[EchoUrandom404]

After long sessions of debugging, log reading and looking at the disassembly, I think I pinpointed the crash. The game uses nt kernel functions to access files. The functions, however, are case sensitive by default (or, at least, implemented in wine as such). The game tries to read a file by its name in the lower case while the actual file on the disk in the camel case. The games fails to read the file and eventually crashes.
I made a hack to force the relevant functions to be always case insensitive: AlexeyProkhin/wine@c3036bc. With the workaround the game opens a window, shows a logo and, unfortunetely, gets stuck on it. Can someone else test the patch? I would appreciate confirming the game does not crash with it. I am especially interested what would happen for AMD users as the game loads nvapi64.dll for me which may explain its being stuck on the logo.
P.S. I made a build with my workaround: drive.google.com/file/d/15i9MSm_sPrAgo2wGaS_4ezCcHC-vvxgW/view?usp=sharing. It is totally untested however, denuvo blocked me for one day.

This game works flawlessly after applying this patch! However, I have noticed the clouds are a bit buggy. Though I doubt this is going to stop players from playing the game given how it never even booted before hand. :)

I am using Fedora 31 with AMD RX 580 GPU using the open source drivers. I am not sure if this is reproduce-able but I will provide logs if necessary to fix it.

I've been out of the loop with the progress here since I reported it working well after the patch was added. I upgraded to an RX 5700 XT and started using Fedora 32. I noticed it crashes now. Not sure why. I can confirm that enabling ACO fixes this somehow. Also the clouds do not bug out anymore.

[Fantu]

I cleaned up my patches for the hanging issue at exit and made a build with them. The patches are in my repo. I would appreciate the testing.

@AlexeyProkhin thanks for your work, I played it and works very well
tested on ubuntu 18.04 with NVIDIA 440.82 drivers

[SpntKbrg]

I cleaned up my patches for the hanging issue at exit and made a build with them. The patches are in my repo. I would appreciate the testing.

This build wasn't working for me with the game stuck in a black screen while the music plays after the Frontier Logo. Even the MangoHUD overlay froze.

But with Proton 5.0-8 RC, the game seems to be working perfectly. Played for about an hour without any problem. There isn't any graphical issue that I noticed and the process exits without hanging.

Arch Linux
Intel i7-7700HQ
GTX1060 with nvidia-vulkan 440.66

Cheers!

[PenguLePenguin]

I cleaned up my patches for the hanging issue at exit and made a build with them. The patches are in my repo. I would appreciate the testing.

How do you get it to work with the patch? I just got Planet Zoo, didnt work out of the box with this crash message

I have the patch downloaded but what do I do from here to make it work?

Im on Ubuntu 18.04.4

[AlexeyProkhin]

@PenguLePenguin You need to opt in into proton beta. Here's a nice gif that shows how to do it.

This build wasn't working for me with the game stuck in a black screen while the music plays after the Frontier Logo. Even the MangoHUD overlay froze.

@SpntKbrg Nice to hear. But strange it didn't work with my build as the patches are the same.

[Newbytee]

@PenguLePenguin That patch is no longer needs to be applied manually. Use Proton 5.0-8 RC 1 as AlexeyProkhin suggested.

[dpanter]

Proton 5.0-8 released today, can someone test and verify the game runs properly?

Fix crashes in Detroit: Become Human, Planet Zoo, Jurassic World: Evolution, Unity of Command II, and Splinter Cell Blacklist.

[Newbytee]

Proton 5.0-8 released today, can someone test and verify the game runs properly?

Tested just now. I haven't played for a longer period, but the game starts up and I'm able to load into a zoo. Also exits cleanly.

[Qwertie-]

I just had a 20 minute test on 5.0.8 and did not notice any issues. Looks like we are done here.

[EchoUrandom404]

Proton 5.0-8 released today, can someone test and verify the game runs properly?

Fix crashes in Detroit: Become Human, Planet Zoo, Jurassic World: Evolution, Unity of Command II, and Splinter Cell Blacklist.

Running the game without gamemoderun RADV_PERFTEST=aco %command% causes the clouds to glitch still. Using the launch options fixes that. The game quits normally without getting stuck and doesn't appear to crash either.

[Newbytee]

Running the game without gamemoderun RADV_PERFTEST=aco %command% causes the clouds to glitch still. Using the launch options fixes that.

So it's most likely an LLVM bug. not a Proton bug. Apart from this, is there anything blocking this from becoming a whitelist request?

[Mushoz]

Very rarely it does still crash upon exiting the game for, al though it mostly exits just fine. It doesn't influence the playability of the game though.

[Mushoz]

Took 4 tries to reproduce. Steps to reproduce:

1. Open Planet Zoo
2. No need to do anything ingame. In the main menu just exit the game via the button in the top-right corner.
3. Repeat steps 1 & 2 until it crashes.

Result: https://imgur.com/a/3pHKApV

[DBerke]

Proton 5.0-8 released today, can someone test and verify the game runs properly?

I just spent about an hour in-game. One thing I've noticed is that the game always starts up in windowed mode, regardless of which setting I closed it in, and if I load into a zoo without first switching it to borderless or fullscreen, the game gets very slow and laggy. Changing mode on the main menu before loading a zoo works fine, however. Overall playability is fine, though!

[fabi20750]

Proton 5.0-8 released today, can someone test and verify the game runs properly?

Fix crashes in Detroit: Become Human, Planet Zoo, Jurassic World: Evolution, Unity of Command II, and Splinter Cell Blacklist.

Also tested it and I can confirm that it works

[nerzhul]

Same for me, both Detroit demo (not the full version i have on epic games store...) & Planet Zoo works

[sfjuocekr]

Yup, new Proton working great!

[hakzsam]

For RADV users: the black screen issue is LLVM specific and now that ACO is enabled default, it should just work.

[rasmus91]

So, here the game crashes on selecting plants to set. Not everytime. I have followed the instructions to set proton version to 5.0-8, but it does not seem to exist, and 5.0-9 just starts a black screen.

The logging option does not produce any log file, so I am kind of at a loss here.

[rinaldus]

The game 100% crashes when I click on my avatar on Earth in in-game menu or when I press F12 to make screenshot. As I understood, the game try to access to Steam overlay during this and crashes (however, Steam overlay works properly if press Shift+Tab).

OS: Manjaro Linux
CPU: AMD Ryzen 7 2700X
RAM: 32 GB
GPU: NVIDIA GeForce RTX 2060 SUPER
Drivers version: 455.45.01

[Galcian79]

It seems that, since the last update, Planet Zoo returned to the old behavior of crashing at start with C++ Runtime Library error.

Note: i had to zip the log file because it was very huge (1.4GB)
https://drive.google.com/file/d/1wcMBoBeJzBe7TZX_F07ykdxg8kdsNxOx/view?usp=sharing

[Galcian79]

So the issue is related to fullscreen mode with nvidia cards. VK_ERROR_DEVICE_LOST.
Temporary workaround: set the game to borderless window (both in game or by editing the XML config file inside the game prefix). Then run protontricks----->winecfg, select graphic tab, enable virtual desktop and set a resolution matching your screen. If you don't set a virtual desktop the low bottom bar of your desktop will stay on screen.

[TheTimeKeepers]

So the issue is related to fullscreen mode with nvidia cards. VK_ERROR_DEVICE_LOST.
Temporary workaround: set the game to borderless window (both in game or by editing the XML config file inside the game prefix). Then run protontricks----->winecfg, select graphic tab, enable virtual desktop and set a resolution matching your screen. If you don't set a virtual desktop the low bottom bar of your desktop will stay on screen.

My game also crashes immediately on startup seemingly regardless of which version of Proton I use (including the most recent release of Proton-GE). I can't seem to find the XML file in the prefix folder to try out this workaround though.

[nerzhul]

works fine for me with proton 5.0-10

[Qwertie-]

@TheTimeKeepers I was having exactly the same issue. For me it was because proton does not work in flatpak. I had to install this https://github.com/flathub/com.valvesoftware.Steam.CompatibilityTool.Proton-GE

More info here: flathub/com.valvesoftware.Steam#642

[besentv]

The game seems a little unstable under current Proton Experimental, getting regular crashes:

16903.498:012c:0160:trace:unwind:dispatch_exception  info[1]=0000000000000008
16903.498:012c:0160:warn:seh:dispatch_exception EXCEPTION_ACCESS_VIOLATION exception (code=c0000005) raised
16903.498:012c:0160:trace:seh:dispatch_exception  rax=000000004b11fc78 rbx=0000000000000000 rcx=0000000000000000 rdx=000000004b11fc78
16903.498:012c:0160:trace:seh:dispatch_exception  rsi=0000000000000000 rdi=00000000082fc2a8 rbp=000000004b11fc90 rsp=000000004b11fb90
16903.498:012c:0160:trace:seh:dispatch_exception   r8=000000004b11fcf8  r9=0000000087eada30 r10=0000000000000002 r11=0000000000000010
16903.498:012c:0160:trace:seh:dispatch_exception  r12=00000000082fc030 r13=000000000df42dc0 r14=0000000087eadca0 r15=0000000087eadca8
16903.498:012c:0160:trace:seh:call_vectored_handlers calling handler at 00000003591544D0 code=c0000005 flags=0
16903.498:012c:0160:trace:seh:call_vectored_handlers handler at 00000003591544D0 returned 0
16903.498:012c:0160:trace:seh:call_vectored_handlers calling handler at 00000002EDF9B860 code=c0000005 flags=0
16903.498:012c:0160:trace:seh:call_vectored_handlers handler at 00000002EDF9B860 returned 0

Could be related to alt+tabbing, as they usually happen when I do that or during game startup or loading.

EDIT: Seems like I had a corrupt autosave file...