cancel
Showing results for 
Search instead for 
Did you mean: 

OpenGL & Vulkan

leoner1
Journeyman III

OpenGL display lists unexpected behavior

Hi,

I'm a CAD software developer and I'm experiencing a strange behavior with some old OpenGL features. 

The strange thing is that the issue appears only when using my Radeon Pro W5500 while everything works fine with Quadro gpus.

I'm new to the forum and I don't know if I should post the actual question here (with all the details and a sample c++ project) or wait until I'm whitelisted and then post this question in the OpenGL/Vulkan section.

Thanks in advance for your time.

 

 

Regards,

Leone Ruggiero

0 Likes
11 Replies
dipak
Big Boss

Hi @leoner1 ,

Thank you for reporting it.  I have whitelisted you and moved the post to the OpenGL forum.

I'm new to the forum and I don't know if I should post the actual question here (with all the details and a sample c++ project) or wait until I'm whitelisted and then post this question in the OpenGL/Vulkan section.

You can provide the information here.

Thanks.

0 Likes

Hi Everyone,

I'm experiencing a strange behavior with display lists.

I've built a sample project (VS Solution) to demonstrate the issue, you can find the files here.

I'll try my best to summarize the description of this issue (please refer to the project for the details):

If I generate some display lists like the following:

 

    // create some display lists
    // -------------------------

    unsigned int line1List = 0;

    //---------------------- LINE 1 COMPILE ---------------------- //
    glDeleteLists(line1List, 1);
    line1List = glGenLists(1);

    glNewList(line1List, GL_COMPILE);
    glBegin(GL_LINES);
    {
        glVertex3f(-0.66, -0.9, 0);
        glVertex3f(-0.66, 0.9, 0);
    }
    glEnd();
    glEndList();

    unsigned int line2List = 0;

    //---------------------- LINE 2 COMPILE ---------------------- //
    // same ...


    //---------------------- LINE 3 COMPILE ---------------------- //
    // same ...

 

 

And use this simple program to do the rendering:

 

const std::string VS_SOURCE =
R"(

void main(void)
{
   
   gl_FrontColor = gl_Color;

   gl_Position = ftransform();
}

)";

const std::string FS_SOURCE =
R"(

void main(void)
{
   vec4 finalColor;    

   finalColor = gl_Color;

   finalColor = clamp (finalColor, 0.0, 1.0);

   gl_FragColor = finalColor;        
}

)";

 

 

I get wrong colors (see the code in the following picture) the first time the display lists are drawn:

Snag_247b3279.png

This problem occurs with the Radeon Pro W5500 while it doesn't occur when using the Quadro P2000.

I know I'm using old OpenGL features and  vertex attribute values not provided per vertex, and I'm going to get rid of all of that one day.

However I'd like to ask if and how I could temporarily solve the issue.

0 Likes

Hi @leoner1 ,

I've reported the issue to the OpenGL team. As I've been informed, they were unable to download the sample project using the link provided in the above post. It looks like the link has expired. Can you please check and share the link again? 

Thanks.

 

0 Likes

Hi @leoner1 ,

As I've come to know, the above issue has been fixed in the latest internal driver build. The fix is expected to be released with an Adrenalin driver around early July.

Thanks.

Thanks @dipak, thanks a lot.

Please let me know when the new release comes out.

0 Likes

Sure, we will notify you once the fix is available with the new driver release.

0 Likes

Hi @dipak ,

Any news about the new driver?

0 Likes

The new driver with the fix is expected to be released next month.

Thanks.

0 Likes

Hi @leoner1 ,

Can you please try the latest Adrenalin driver 22.7.1 to see if the issue is still reproducible or not?

https://www.amd.com/en/support/kb/release-notes/rn-rad-win-22-7-1

https://www.amd.com/en/support/professional-graphics/radeon-pro/radeon-pro-w5000-series/radeon-pro-w...

Thanks.

0 Likes
leoner1
Journeyman III

Hi @dipak,


With the new driver the issue with display lists is not reproducible anymore!

However, it looks like OpenGL shader compilation behaves differently now, some shaders that were compiling fine are now presenting errors. What has been changed in the new driver version?

Thanks in advance for your support.

0 Likes

Thanks for the confirmation.

Regarding the shader compilation issue, I would suggest that you start a new thread and provide a test-case that reproduces the issue. I will check with the OpenGL team.

Please note, the latest Adrenalin driver is available here: Adrenalin-22-8-2

Thanks.

0 Likes