<div dir="ltr">OK so the specific failure point appears to be OSMesa with llvmpipe. For some reason we are getting a 3.0 context instead of 3.2. I am not sure how to request a 3.2 context from OS mesa. We are just doing a OSMesaCreateContext(GL_RGBA,0) Is there an argument or build option to get 3.2?<div> </div><div><h2>OSMesa+llvmpipe</h2><table style="font-size:12.8px"><thead><tr><th>Name</th><th>Value</th></tr></thead><tbody><tr><td>glGetString(GL_VENDOR)</td><td>VMware, Inc.</td></tr><tr><td>glGetString(GL_VERSION)</td><td>3.0 Mesa 11.0.4</td></tr><tr><td>glGetString(GL_RENDERER)</td><td>Gallium 0.4 on llvmpipe (LLVM 3.6, 256 bits) </td></tr></tbody></table></div></div><div class="gmail_extra"> <div class="gmail_quote">On Wed, Dec 9, 2015 at 6:30 AM, Olivier Galibert <<a href="mailto:galibert@pobox.com" target="_blank">galibert@pobox.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">llvmpipe/softpipe support all of 3.3 with one exception which it fakes: MSAA. You may be detecting that? OG. On Wed, Dec 9, 2015 at 2:11 AM, Brian Paul <<a href="mailto:brianp@vmware.com">brianp@vmware.com</a>> wrote: > On 12/04/2015 07:10 AM, Ken Martin wrote: >> >> Thanks! Seems the system in question was using llvmpipe which passes >> ~95% of our tests when we tell it be a 3.2 context using the environment >> variables. For some reason I was thinking llvmpipe was full 3.2 Core. > > > llvmpipe does support OpenGL 3.2 core profile (3.3 actually). > > For your users who are having trouble, seeing the output of glxinfo might > yield a clue. > > -Brian > >> I >> tried playing with softpipe to see if that had better results but it had >> significantly more failures. I think the Intel SWR is at the 99% or so >> mark now on our tests so that may be a good bet for our pure software >> rendering. >> >> Thanks Again! >> Ken >> >> >> On Thu, Nov 26, 2015 at 6:41 AM, Albert Freeman >> <<a href="mailto:albertwdfreeman@gmail.com">albertwdfreeman@gmail.com</a> <mailto:<a href="mailto:albertwdfreeman@gmail.com">albertwdfreeman@gmail.com</a>>> wrote: >> >> On 26 November 2015 at 11:37, Albert Freeman >> <<a href="mailto:albertwdfreeman@gmail.com">albertwdfreeman@gmail.com</a> <mailto:<a href="mailto:albertwdfreeman@gmail.com">albertwdfreeman@gmail.com</a>>> wrote: >> > On 25 November 2015 at 22:45, Ken Martin <<a href="mailto:ken.martin@kitware.com">ken.martin@kitware.com</a> >> <mailto:<a href="mailto:ken.martin@kitware.com">ken.martin@kitware.com</a>>> wrote: >> >> >> >> Noob question incoming... I have an application that requests a >> 3.2 core >> >> context from Mesa. I tell folks to make sure they have mesa >> version 10.6.5 >> >> or later which I thought supported OpenGL 3.2. Usually this >> works but now >> >> and then I get users who's Mesa (including version 11) fails to >> provide a >> >> 3.2 Core context. I tell them to set >> >> >> >> MESA_GL_VERSION_OVERRIDE=3.2 >> >> >> >> and >> >> >> >> MESA_GLSL_VERSION_OVERRIDE=150 (or something like that) >> >> >> >> and it generally works. But I'm not sure why the original >> request for 3.2 >> >> Core is failing on some systems (drivers?). Looking at >> >> >> >> <a href="http://mesamatrix.net/" rel="noreferrer" target="_blank">http://mesamatrix.net/</a> >> >> <<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__mesamatrix.net_&d=BQMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=T0t4QG7chq2ZwJo6wilkFznRSFy-8uDKartPGbomVj8&m=DgUiZLZLE5l5BuSC2NBUMBQS2DGA9QhpHNlB-VsdiFA&s=265u7-eKXnTubRJ-iofPSBX-H-LKHhoyVG6X43hKuqs&e=" rel="noreferrer" target="_blank">https://urldefense.proofpoint.com/v2/url?u=http-3A__mesamatrix.net_&d=BQMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=T0t4QG7chq2ZwJo6wilkFznRSFy-8uDKartPGbomVj8&m=DgUiZLZLE5l5BuSC2NBUMBQS2DGA9QhpHNlB-VsdiFA&s=265u7-eKXnTubRJ-iofPSBX-H-LKHhoyVG6X43hKuqs&e=</a>> >> >> >> >> leads me to think that all drivers with a recent mesa should be >> fine with >> >> 3.2 Core but obviously I am missing something. Do I need to be >> telling them >> >> to use a specific driver? Is there a list of drivers that do not >> support 3.2 >> >> I should tell them to avoid? Anything else come to mind? >> >> >> >> I just want to try to provide a bit more help to folks to get >> them up and >> >> running with Mesa and even better get our code to handle it >> automatically if >> >> we could. >> >> >> >> Any pointers appreciated. The application is vtk. >> >> >> >> Thanks >> >> Ken >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> Ken Martin PhD >> >> Chairman & CFO >> >> Kitware Inc. >> >> 28 Corporate Drive >> >> Clifton Park NY 12065 >> >> <a href="tel:518%20371%203971" value="+15183713971">518 371 3971</a> <tel:518%20371%203971> >> >> >> >> This communication, including all attachments, contains >> confidential and >> >> legally privileged information, and it is intended only for the >> use of the >> >> addressee. Access to this email by anyone else is unauthorized. >> If you are >> >> not the intended recipient, any disclosure, copying, >> distribution or any >> >> action taken in reliance on it is prohibited and may be >> unlawful. If you >> >> received this communication in error please notify us >> immediately and >> >> destroy the original message. Thank you. >> >> >> >> _______________________________________________ >> >> mesa-users mailing list >> >> <a href="mailto:mesa-users@lists.freedesktop.org">mesa-users@lists.freedesktop.org</a> >> <mailto:<a href="mailto:mesa-users@lists.freedesktop.org">mesa-users@lists.freedesktop.org</a>> >> >> <a href="http://lists.freedesktop.org/mailman/listinfo/mesa-users" rel="noreferrer" target="_blank">http://lists.freedesktop.org/mailman/listinfo/mesa-users</a> >> >> <<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.freedesktop.org_mailman_listinfo_mesa-2Dusers&d=BQMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=T0t4QG7chq2ZwJo6wilkFznRSFy-8uDKartPGbomVj8&m=DgUiZLZLE5l5BuSC2NBUMBQS2DGA9QhpHNlB-VsdiFA&s=GUHRuxZw-TCs8qGxwpn4d6zy7Et2yH5D2dq7lVdtxR8&e=" rel="noreferrer" target="_blank">https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.freedesktop.org_mailman_listinfo_mesa-2Dusers&d=BQMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=T0t4QG7chq2ZwJo6wilkFznRSFy-8uDKartPGbomVj8&m=DgUiZLZLE5l5BuSC2NBUMBQS2DGA9QhpHNlB-VsdiFA&s=GUHRuxZw-TCs8qGxwpn4d6zy7Et2yH5D2dq7lVdtxR8&e=</a>> >> >> >> > Not all mesa drivers support gl 3.2, e.g. the r300 gallium driver >> in >> > the git mesa supports only glsl 1.20: >> > case PIPE_CAP_GLSL_FEATURE_LEVEL: >> > return 120; >> > >> > That website is based on gl3.txt. It does not list all drivers mesa >> > supports (as gl3.txt dosen't). They are both only meant to be a >> rough >> > guide. The svga driver apparently supports gl 3.3 and it isn't even >> > mentioned in gl3.txt. So I think some of the vtk users have >> really old >> > gpus that don't support gl 3.2. Some gl versions already have >> software >> > emulated components for gl features not supported by the hardware >> on >> > older gpus and some older gpus simply don't have support. >> As those environment variables you use simply fake the gl version to >> the application. If the application then uses say a gl 3.2 feature >> that isn't supported by that driver, the behavior is undefined (e.g. >> application can crash). >> >> >> >> >> -- >> Ken Martin PhD >> Chairman & CFO >> Kitware Inc. >> 28 Corporate Drive >> Clifton Park NY 12065 >> 518 371 3971 >> >> This communication, including all attachments, contains confidential and >> legally privileged information, and it is intended only for the use of >> the addressee. Access to this email by anyone else is unauthorized. If >> you are not the intended recipient, any disclosure, copying, >> distribution or any action taken in reliance on it is prohibited and may >> be unlawful. If you received this communication in error please notify >> us immediately and destroy the original message. Thank you. >> >> >> _______________________________________________ >> mesa-users mailing list >> <a href="mailto:mesa-users@lists.freedesktop.org">mesa-users@lists.freedesktop.org</a> >> >> <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.freedesktop.org_mailman_listinfo_mesa-2Dusers&d=BQIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=T0t4QG7chq2ZwJo6wilkFznRSFy-8uDKartPGbomVj8&m=DgUiZLZLE5l5BuSC2NBUMBQS2DGA9QhpHNlB-VsdiFA&s=GUHRuxZw-TCs8qGxwpn4d6zy7Et2yH5D2dq7lVdtxR8&e=" rel="noreferrer" target="_blank">https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.freedesktop.org_mailman_listinfo_mesa-2Dusers&d=BQIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=T0t4QG7chq2ZwJo6wilkFznRSFy-8uDKartPGbomVj8&m=DgUiZLZLE5l5BuSC2NBUMBQS2DGA9QhpHNlB-VsdiFA&s=GUHRuxZw-TCs8qGxwpn4d6zy7Et2yH5D2dq7lVdtxR8&e=</a> >> > > _______________________________________________ > mesa-users mailing list > <a href="mailto:mesa-users@lists.freedesktop.org">mesa-users@lists.freedesktop.org</a> > <a href="http://lists.freedesktop.org/mailman/listinfo/mesa-users" rel="noreferrer" target="_blank">http://lists.freedesktop.org/mailman/listinfo/mesa-users</a> </blockquote></div> <div> </div>-- <div class="gmail_signature">Ken Martin PhD<div>Chairman & CFO Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 518 371 3971<div> </div><div>This communication, including all attachments, contains confidential and legally privileged information, and it is intended only for the use of the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken in reliance on it is prohibited and may be unlawful. If you received this communication in error please notify us immediately and destroy the original message. Thank you.</div></div></div> </div>