Setting offscreenInitSurfaces to any value greater than 0 causes an immediate native crash (access violation) on the first rendered frame when using Vulkan. Setting it to 0 resolves the issue entirely. D3D12 is unaffected. Noticed this when a colleague was testing our project on linux, and I was able to reproduce it with -force-vulkan in the unity hub CLI area.

It took me a while to narrow this down, I had a minimal repro project and could not recreate the crash and started just comparing the settings one at a time. I noticed it first with 3.2.12 and then updated to 4.0.0-rc0 to see if it would be fixed. So it's likely in several versions.

Unity: 6000.3.22f1 (URP 17.3.0)
NoesisGUI: 3.2.12 & 4.0.0-rc0
API: Vulkan

To reproduce, create a unity 6000.3.22f1 project (URP 17.3.0) with Vulkan set as the graphics API (can just run -force-vulkan as well). Import Noesis GUI 4.0.0-rc0. Attach a NoesisView with basic XAML to content to a camera, and then set offscreenInitSurfaces to 2 in the noesis settings. Enter play mode, should crash.

Please let me know if these repro steps aren't working, I think there's wiggle room with the versions etc so you could likely test this in any project you have already. It's a hard crash but we can work around it by working on windows, and with on-demand surface initialization (which may still crash but I haven't observed it). To be honest I am not sure why I had this set to 2, I don't fully understand the setting. I guess it's just warming up offscreen surfaces that may be required, I'd be curious to learn a bit more about that!

Thanks!
David