<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">It would be hard to change to one render window at this point, but, we’re "pretty sure” each render window has its own actors/mappers, because we ran into trouble with that in 6.3.0 - <div class=""><br class=""></div><div class="">I can write some test code to verify….I’ve added some more vtkOpenGLCheckErrorMacro and I am rebuilding 7.0.0 now...<div class=""><br class=""></div><div class="">Thanks</div><div class=""><br class=""></div><div class="">Rick</div><div class=""><br class=""></div><div class=""><br class=""><div class=""><div><blockquote type="cite" class=""><div class="">On Feb 24, 2016, at 12:16 PM, Ken Martin <<a href="mailto:ken.martin@kitware.com" class="">ken.martin@kitware.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Thanks that helps. I am starting to wonder if the issue is related to multiple render windows. With multiple windows it is important to not share actors or mappers in the new OpenGL backend. Each window needs its own mappers and actors. They can share the same data source/readers but not the opengl pieces like actors/mappers. Does the problem still exist if you only have one renderWindow?<div class=""><br class=""></div><div class="">Thanks</div><div class="">Ken</div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Wed, Feb 24, 2016 at 12:04 PM, Richard Frank <span dir="ltr" class=""><<a href="mailto:rickfrank@me.com" target="_blank" class="">rickfrank@me.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=""><div class="">I traced through the VTK code and then added a vtkOpenGLCheckErrorMacro :</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">vtkOpenGLPolyDataMapper::UpdateShaders(<br class=""> vtkOpenGLHelper &cellBO, vtkRenderer* ren, vtkActor *actor)<br class="">{<br class=""> vtkOpenGLRenderWindow *renWin = vtkOpenGLRenderWindow::SafeDownCast(ren->GetRenderWindow());<br class=""><br class=""> cellBO.VAO->Bind();<br class=""> vtkOpenGLCheckErrorMacro("failed after cellBO.VAO->Bind()");</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">ERROR: In vtk770\Rendering\OpenGL2\vtkOpenGLPolyDataMapper.cxx, line 1390<br class="">vtkOpenGLPolyDataMapper (0000025BBD546CB0): failed after cellBO.VAO->Bind() 1 OpenGL errors detected<br class=""> 0 : (1282) Invalid operation<br class=""></div><div class=""><br class=""></div><div class="">and the gl log has</div><div class=""><br class=""></div><div class="">GL ERROR - Function glBindVertexArray generated error GL_INVALID_OPERATION<br class="">GL ERROR - Function glDrawRangeElements generated error GL_OUT_OF_MEMORY</div><div class=""><br class=""></div><div class="">I'm guessing the glBindVertexArray is generating the error? Any ideas what might cause that?</div><div class=""><br class=""></div><div class="">The 6.3.0 code seemed to not use any shaders when rendering my model - when I launched the Shader Editor using 6.3.0 it was blank. When I launched the 7.0.0 code there were a bunch of shaders being used.....</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Thanks</div><div class=""><br class=""></div><div class="">Rick</div><div class=""><br class=""></div><div class=""><br class="">On Feb 23, 2016, at 11:58 AM, Ken Martin <<a href="mailto:ken.martin@kitware.com" target="_blank" class="">ken.martin@kitware.com</a>> wrote:<br class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class="">Hmm something is really odd there. 16600 points/normals is trivially small. Even if you had 100 actors each with 16600 points that would be small. There are a couple ways to debug something like this. One is to go old school and sprinkle<div class=""><br class=""></div><div class=""><div class=""> vtkOpenGLCheckErrorMacro("failed after something");</div></div><div class=""><br class=""></div><div class="">throughout the code to see where the issue is. Another option on windows is to use </div><div class=""><br class=""></div><div class=""><a href="https://github.com/dtrebilco/glintercept" target="_blank" class="">https://github.com/dtrebilco/glintercept</a><br class=""></div><div class=""><br class=""></div><div class="">which produces a log showing the specific call that caused the problem and when run in the debugger it will break on opengl errors. There are other tools with similar capabilities available as well. </div><div class=""><br class=""></div><div class="">If you can boil it down to something smaller I could try it out, my dev systems are all Qt4 though...</div><div class=""><br class=""></div><div class="">Ken</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Tue, Feb 23, 2016 at 11:37 AM, Richard Frank <span dir="ltr" class=""><<a href="mailto:rickfrank@me.com" target="_blank" class="">rickfrank@me.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 0.8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=""><div class="">There are 16600 points and 16600 normals in each model, I'm using Qt 5.5 and there are four of these models - 1 in each renderview - (Sagital, Axial, Coronal, etc). Each model is composed of surfaces created with triangle strips.</div><div class=""><br class=""></div><div class="">Each model contains a number of actors for each surface, (variable, depends on anatomy) put together into an assembly.</div><div class=""><br class=""></div><div class="">It's a medical application. Works fine in VTK 6.3.0 </div><div class=""><br class=""></div><div class="">NVidia quadro K5200<br class="">Graphics Card should be beefy enough.</div><div class=""><br class=""></div><div class="">Rick</div><div class=""><br class=""></div><div class=""><br class="">On Feb 22, 2016, at 09:44 PM, Ken Martin <<a href="mailto:ken.martin@kitware.com" target="_blank" class="">ken.martin@kitware.com</a>> wrote:<br class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class="">Out of memory is an unusual one. Maybe the mesh is too big to load all at once in the new backend. How big is the mesh you are trying to render (number of points, number of triangles) and does it use cell colors or cell normals? That would help me get a feel if it is really just exceeding what the card can handle.<div class=""><br class=""></div><div class="">Thanks</div><div class="">Ken</div><div class=""><br class=""></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Mon, Feb 22, 2016 at 6:50 PM, Richard Frank <span dir="ltr" class=""><<a href="mailto:rickfrank@me.com" target="_blank" class="">rickfrank@me.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 0.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br class=""> <br class=""> I get the following errors ( and my fairly complex polygon mesh fails to render ) when using VTK 7.0.<br class=""> ERROR: In<br class=""> <br class=""> \vtk770\Rendering\OpenGL2\vtkOpenGLPolyDataMapper.cxx, line 1440<br class=""> vtkOpenGLPolyDataMapper (0000016618EFD490): failed after UpdateShader 1 OpenGL errors detected<br class=""> 0 : (1282) Invalid operation<br class=""> <br class=""> <br class=""> <br class=""> ERROR: In \vtk770\Rendering\OpenGL2\vtkOpenGLActor.cxx, line 91<br class=""> vtkOpenGLActor (0000016619E228B0): failed after Render 1 OpenGL errors detected<br class=""> 0 : (1285) Out of memory<br class=""> <br class=""> <br class=""> This is code is " works " fine in 6.3.0.<br class=""> <br class=""> I'm using an NVidia quadro K5200 with 8G.<br class=""> <br class=""> Any tips on how to debug this?<br class=""> Thanks<br class=""> <br class=""> Rick<br class=""> <br class=""> <br class=""> Sent from my iPad<br class=""> _______________________________________________<br class=""> Powered by <a href="http://www.kitware.com/" rel="noreferrer" target="_blank" class="">www.kitware.com</a><br class=""> <br class=""> Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" rel="noreferrer" target="_blank" class="">http://www.kitware.com/opensource/opensource.html</a><br class=""> <br class=""> Please keep messages on-topic and check the VTK FAQ at: <a href="http://www.vtk.org/Wiki/VTK_FAQ" rel="noreferrer" target="_blank" class="">http://www.vtk.org/Wiki/VTK_FAQ</a><br class=""> <br class=""> Search the list archives at: <a href="http://markmail.org/search/?q=vtkusers" rel="noreferrer" target="_blank" class="">http://markmail.org/search/?q=vtkusers</a><br class=""> <br class=""> Follow this link to subscribe/unsubscribe:<br class=""> <a href="http://public.kitware.com/mailman/listinfo/vtkusers" rel="noreferrer" target="_blank" class="">http://public.kitware.com/mailman/listinfo/vtkusers</a><br class=""></blockquote></div><br class=""><br clear="all" class=""><span class="HOEnZb"><font color="#888888" class=""><span class=""><span style="color:#888888" class=""><div class=""><br class=""></div>-- <br class=""><div class="">Ken Martin PhD<div class="">Chairman & CFO<br class="">Kitware Inc.<br class="">28 Corporate Drive<br class="">Clifton Park NY 12065<br class=""><a class="">518 371 3971</a><div class=""><br class=""></div><div class=""><span style="font-size:10pt;font-family:'tahoma',sans-serif" class="">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.</span></div></div></div></span></span></font></span></div></div></blockquote></div></div></blockquote></div><span class="HOEnZb"><font color="#888888" class=""><br class=""><br clear="all" class=""><div class=""><br class=""></div>-- <br class=""><div class="">Ken Martin PhD<div class="">Chairman & CFO<br class="">Kitware Inc.<br class="">28 Corporate Drive<br class="">Clifton Park NY 12065<br class=""><a href="tel:518%20371%203971" value="+15183713971" target="_blank" class="">518 371 3971</a><div class=""><br class=""></div><div class=""><span style="font-size:10pt;font-family:'tahoma',sans-serif" class="">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.</span></div></div></div></font></span></div></div></blockquote></div></div></blockquote></div><br class=""><br clear="all" class=""><div class=""><br class=""></div>-- <br class=""><div class="gmail_signature">Ken Martin PhD<div class="">Chairman & CFO<br class="">Kitware Inc.<br class="">28 Corporate Drive<br class="">Clifton Park NY 12065<br class="">518 371 3971<div class=""><br class=""></div><div class=""><span style="font-size:10pt;font-family:Tahoma,sans-serif" class="">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.</span></div></div></div>
</div>
</div></blockquote></div><br class=""></div></div></div></body></html>