This topic is mainly related to this other post:
I’ve been experiencing the exact same thing (which saddens me a lot since I’ve been excited to try out Luduvo for multiple months now). However, with version 44 being released not that long ago, I decided to give it another go.
The client would still hang on a black screen before forcibly closing itself seconds later. However, I noticed that in my case, my crash logs would actually return this 0xc0000005 error:
crash: exception 0xc0000005 at C:\windows\System32\DriverStore\FileRepository\u0197843.inf_amd64_82ec9e2b79afe28f\B025592\amdvlk64.dll+0x1ccb80c read 0x58
The crash logs do not return anything else.
Hardware used during testing:
AMD Ryzen 5 5625U (Zen 3)
16GB RAM (8GBx2)
Built in AMD Radeon Graphics (512MB dedicated, 7.7GB shared)
Windows 11 (Version 23H2, Build 22631.6199)
Additional notes:
- Despite the fact that my hardware is about 3.5 years old, I’m almost certain it’s got nothing to do with it since this issue happens exclusively with the Luduvo client (as others have also pointed out).
- You can also trigger this bug in Luduvo Studio by attempting to create or open a place file, which returns the same error message in it’s own crash logs.
I do have a video copy of me reproducing the bug if it peaks anyone’s interest. I’d prefer to send it over privately though.