kd-11

I'll just disable all extensions for this GPU and let's see if it can boot a core VK1.0 instance.

I realized now that the previous experiment didn't even kick in because your device ID is different from what I expected. It is interesting that there is more than one...

``` ·! 0:00:06.523724 RSX: Dumping requested extensions... ·! 0:00:06.523943 RSX: [Supported] VK_KHR_swapchain ·! 0:00:06.523947 RSX: [Supported] VK_KHR_shader_float16_int8 ``` It keeps insisting on this float16 extension on your setup for some...

There was indeed a bug forcing float16 to enabled on VEGA. Next test build: https://dev.azure.com/nekotekina/nekotekina/_build/results?buildId=11479&view=results

Last one: https://dev.azure.com/nekotekina/nekotekina/_build/results?buildId=11480&view=results If this one crashes, then we know that the driver is reporting float16 but doesn't support it. This is a known issue with Vega, since I can...

Thanks for testing. The fix will be mainlined shortly.

https://github.com/RPCS3/rpcs3/pull/13875 added the checks to catch this type of error. Previously it would have silently sent the incorrect dimensions to the hardware and caused some random device lost errors on...

I'm unable to reproduce any crashing. What are you doing in the menus to trigger the crash?

> One thing I have noticed is that in the logs: " /private/var/folders/76/zy5ktkns50v6gt5g8r0sf6sc0000gn/T/cirrus-ci-build/rpcs3/Emu/RSX/VK/VKTexture.cpp" This file doesn't exist in my file system. It just means it existed on the cloud machine...

https://github.com/RPCS3/rpcs3/pull/16186 appears to be responsible. @Megamouse Likely an upstream issue. Maybe we should just use known-stable versions (current release - 1) for these dependencies.