You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi All,
Using AMD ryzen which hosts AMD radeon renoir IGPU , some examples (vsgTriangles) don't run because of shaders issues :
when GL_ARB_separate_shader_objects extension enabled , layout values are not taken into account (specific to AMD .
see AMD note inside : https://www.khronos.org/opengl/wiki/Layout_Qualifier_(GLSL) .
I'm not vulkan expert . However when removing the extension call, the issue still appears.
Fixed when giving the same variable name on the outColor from vertex shader and the input from fragment (which is very limitating).
Any idea ?
The text was updated successfully, but these errors were encountered:
The AMD-specific note in that wiki page isn't relevant to the VSG as shaders are compiled and linked by glslang and fed to Vulkan as SPIR-V, not fed to AMD's OpenGL driver as GLSL to be compiled and linked, so any historic limitations of AMD's OpenGL driver (which probably aren't relevant anymore even for OpenGL as it had a total rewrite a couple of years ago).
glslang-15 is reporting that it has issues with the different naming of vertex and fragment shader varying colour value, so I've renamed it to avoid this issue. c27a5a8
@tvatooms Could you test VSG/vsgExamples master on your system?
Hi All,
Using AMD ryzen which hosts AMD radeon renoir IGPU , some examples (vsgTriangles) don't run because of shaders issues :
when GL_ARB_separate_shader_objects extension enabled , layout values are not taken into account (specific to AMD .
see AMD note inside : https://www.khronos.org/opengl/wiki/Layout_Qualifier_(GLSL) .
I'm not vulkan expert . However when removing the extension call, the issue still appears.
Fixed when giving the same variable name on the outColor from vertex shader and the input from fragment (which is very limitating).
Any idea ?
The text was updated successfully, but these errors were encountered: