Zelda64Recomp
[Bug] Black screen on game boot
Describe the bug Pressing the "Start game" button causes a black screen. This black screen will stay indefinitely, and sometimes crash, terminating the program without any error shown.
To Reproduce
- Fresh install 1.1.0 or any other version
- Select 1.0 USA ROM - MD5 2a0a8acb61538235bc1094d297fb6556
- Click "Start game"
Expected behavior The game boots and continues to work correctly.
Screenshots
Desktop (please complete the following information):
- OS: Windows 11 Pro
- Version: OS build 26120.670
- CPU: AMD Ryzen 5 2600
- GPU: NVIDIA GeForce GTX 1070
- GPU driver: Nvidia driver 555.85
Additional context I have tried running the debug version from the deployments but the issue prevails, and no output is shown in the terminal. Is there something I can do to get logs of the crash?
This is all I could get from Event Viewer:
- Faulting application name: Zelda64Recompiled.exe, version: 0.0.0.0, time stamp: 0x66537785
- Faulting module name: VCRUNTIME140.dll, version: 14.40.33810.0, time stamp: 0x119a1ae6
- Exception code: 0xc0000005
- Fault offset: 0x000000000001137d
Update: Changing the graphics API to Vulkan in graphics.json seems to solve this issue.
Seems like this is an issue with the latest insider build of Windows 11, we'll look into what can be done about it.
I have this issue on Ubuntu 24.04 LTS too (WSL). Not sure if it is worth being mentioned, since i just play on Windows instead.
Is there a way to choose a different API on Linux's AppImage file? I found the config file, but I don't know the options for different ones since I only know of Auto and Vulkan. I know this is a strange question, but Nvidia's Full Compositor on fullscreen options in Mint Cinnamon causes the app to lock up, and maybe something like a WineD3D or borderless fullscreen can bypass that.
Is there a way to choose a different API on Linux's AppImage file? I found the config file, but I don't know the options for different ones since I only know of Auto and Vulkan. I know this is a strange question, but Nvidia's Full Compositor on fullscreen options in Mint Cinnamon causes the app to lock up, and maybe something like a WineD3D or borderless fullscreen can bypass that.
Can you try a recent build such as this one? (select Artifacts near the top and choose your platform). We recently fixed some causes for crashes on boot on Linux, especially under Wayland or when using gamescope.
And no, the native Linux version does not have DX12 support. If for whatever reason you want to use DX12 on Linux via DXVK you can use the Windows build and force the graphics.json to the DX12 API. But that will be a bad experience.
Can you try a recent build such as this one? (select Artifacts near the top and choose your platform). We recently fixed some causes for crashes on boot on Linux, especially under Wayland or when using gamescope.
And no, the native Linux version does not have DX12 support. If for whatever reason you want to use DX12 on Linux via DXVK you can use the Windows build and force the graphics.json to the DX12 API. But that will be a bad experience.
Edit: Seems like there's been a driver update to 555 recently. It appears to make most of the screen tearing issues go away so far from 535's issues without the full pipeline compositor set so far.
Yeah, from what I read, the minute long fullscreen freeze (before needing to alt+F4 out of it) has to do with x11 and the way Nvidia's proprietary drivers handle the full pipeline composition. It locks up in that build of the app as well as many other games that I believe use DXVK and Proton 8.0 and up. This is why I was curious about the different potential windows API to see if I could achieve a sort of workaround as I know there's no hard solution to this. It'll work windowed, but only windowed. If I want it fullscreen, I need to run the windows app through proton 7.0.
Given we haven't had reports of this in a while, I'm going to assume that whatever was causing it was fixed. Feel free to re-open if you're still experiencing this.