Jump to content
  • Advertisement
Sign in to follow this  
mrmurder

OpenGL Program link error with Tessellation Control & Evalution Shaders

This topic is 2348 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hello there,

I'm having a weird problem in my application.

My programs link just fine when using only vertex and fragment shaders, but once i add the Control and Evaluation Shaders in i get a unknown error when Linking.

Im using GLEW and creating a Forward Compatible Context with GL 4.1

This is the info i get from GL

OpenGL Version: 4.1.10428 Core Profile Forward-Compatible Context
GLSL Version : 4.10
GL Renderer : AMD Radeon HD 6750M

Vertex shader was successfully compiled to run on hardware.
Tessellation control shader was successfully compiled to run on hardware.
Tessellation evaluation shader was successfully compiled to run on hardware.
Fragment shader was successfully compiled to run on hardware.

ERROR:
First-chance exception at 0x69d7d918 in GL32Sample.exe: 0xC0000005: Access violation reading location 0x202c5d30.
Link - Vertex shader(s) failed to link, fragment shader(s) failed to link, tessellation control shader(s) failed to link, tessellation evaluation shader(s) failed to link.
unexpected error.
unexpected error.
unexpected error.
unexpected error.


The exception happens when calling this line ( after calling glLinkProgram(id) ):

glGetProgramiv(program_handle, GL_LINK_STATUS, &linkSuccess);



According to gl errors after calling glLinkProgram i get no errors, but once i make that call it gives me a first-chance exception.


Would anyone have any idea on why this is happening?

Thanks in advance

Share this post


Link to post
Share on other sites
Advertisement
Well it seems that even that the tessellation shaders compiled correctly they had problems.

I was using in/out variables to pass data until the Evaluation Shader. Changed it to use gl_in and gl_out and now seems to be fine

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!