Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GLSL shader issue inside vsgTriangle when using amd ryzen #328

Open
tvatooms opened this issue Nov 12, 2024 · 2 comments
Open

GLSL shader issue inside vsgTriangle when using amd ryzen #328

tvatooms opened this issue Nov 12, 2024 · 2 comments

Comments

@tvatooms
Copy link

tvatooms commented Nov 12, 2024

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 ?

@AnyOldName3
Copy link
Contributor

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).

@robertosfield
Copy link
Collaborator

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants