rocky-demo.exe doesn't want to start

[kahlenberg]

Hi,
I succesfully built the rocky-demo.exe and set the environment variables VSG_FILE_PATH, ROCKY_FILE_PATH
and PROJ_DATA, however I receive following error message:

All necessary dll files are in the build directory.

[Harsh-patel00]

The shaders are present in rocky's_install_directory/shaders folder, make sure you have that folder present. If not, try re-installing rocky.

[gwaldron]

This code in rdemo.cpp checks for a layer error:

        if (layer->status().failed())
            return layerError(layer);

[gwaldron]

Since abort() was called, you probably ran into a ROCKY_HARD_ASSERT failure. Run from the debugger and it should breakpoint where the assertion occurs. or click "Retry" to see the call stack.

[kahlenberg]

This code in rdemo.cpp checks for a layer error:

        if (layer->status().failed())
            return layerError(layer);

It loads layers correctly, it doesn't return at that point.

[kahlenberg]

Since abort() was called, you probably ran into a ROCKY_HARD_ASSERT failure. Run from the debugger and it should breakpoint where the assertion occurs. or click "Retry" to see the call stack.

Debugger points the line for (auto queueInfo : queueCreateInfos) in DisplayManager.cpp as I posted image above.

Callstack:

[gwaldron]

Strange. Not able to reproduce here with the main branch. I wonder if building in RelWithDebInfo config would make a difference. I have never personally tried to build VSG or Rocky in Debug config.

[AnyOldName3]

If the problem's what I think it is, then it's fixed by the vendor-neutral barycentric coordinate commit that's made it into the VSG 1.1.2 PR. Rocky's set up to use an Nvidia-specific GLSL extension, and requests it when the Vulkan context is created, so the VSG errors out if there's no Nvidia GPU present. There's an identical vendor-neutral extension that also works on many GPUs from other vendors, and all the same Nvidia GPUs provided they're using a driver from 2022 or later.

[AnyOldName3]

I also didn't find any information about barycentric coordinates support for this CPU. However, I'm lack of information and knowledge in Vulkan and VSG, so I can't realise it by myself even without checking whether extension presented or not.

These days I use this site to see which things support which extensions. Here's a link specifically for Iris Xe on Windows with the 101.5534 driver: https://vulkan.gpuinfo.org/displayreport.php?id=30782#extensions

[gwaldron]

Which was causing the crash? The use of GL_NV_fragment_shader_barycentric in the shader without an ifdef, or the code in DisplayManager.cpp?

[AnyOldName3]

If you've not got the extension, then as DisplayManager.cpp tells the VSG that it's a hard requirement, a Vulkan context won't be created, and when DisplayManager tries using the context, it won't work. It doesn't get far enough to try using the shaders.

[gwaldron]

Thanks. I pushed a couple changes that will hopefully (a) check whether the extension is supported before requesting it, and (b) check in all shaders whether it's been enabled.

[kahlenberg]

Thank you all,
It now works on my machine :)
I can build and run the applications.