<div dir="ltr">Hello Aashish,<br><br>Thanks for the quick answer<br>We are using a vtkImageData, 512x512x591 with short element (you can find the dataset here : <a href="https://www.dropbox.com/s/ptqwi0ebv75kt35/volume.zip" target="_blank">https://www.dropbox.com/s/ptqwi0ebv75kt35/volume.zip</a>). So I think it's all about GPU volume raycast mapper.<br>The new mapper does bring low resolution, but when compared to the old one, it seems less "low resolution" during interaction than the old one<br>Shading is enabled, gradient opacity disabled<br><br>Don't know if you need a minimal example, but I believe the GPURenderDemo used with this dataset is enough to highlight the slow down.<br><br>Thanks<br>Simon<br><br></div><div class="gmail_extra"><br><div class="gmail_quote">2015-10-26 18:57 GMT+01:00 Aashish Chaudhary <span dir="ltr"><<a href="mailto:aashish.chaudhary@kitware.com" target="_blank">aashish.chaudhary@kitware.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Also, <div><br></div><div>Do you have shading enabled? We fixed a bug with shading that was causing the slow performance a while back. I don't remember if that was included in 4.4 or not ( I can check ). </div><span class="HOEnZb"><font color="#888888"><div><br></div><div>- Aashish</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Oct 26, 2015 at 1:53 PM, Aashish Chaudhary <span dir="ltr"><<a href="mailto:aashish.chaudhary@kitware.com" target="_blank">aashish.chaudhary@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Simon, <div><br></div><div>What kind of dataset you are using? Depending on the data type you might be using</div><div>the GPU one or the unstructured renderer. The performance we measured is related to the GPU ray cast mapper</div><div>and will apply only to the vtkImageData inputs. </div><div><br></div><div>Also, helpful would be is if you can tell if the new mapper is bringing low resolution when you interact with the volume (and whether or not it happens with old mapper). </div><div><br></div><div>Thanks,</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Mon, Oct 26, 2015 at 1:47 PM, Simon ESNEAULT <span dir="ltr"><<a href="mailto:simon.esneault@gmail.com" target="_blank">simon.esneault@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr">Hi All,<br><br>We are trying to make the switch to the new OpenGL2 backend for our application, and although the switch was easy (thanks for not breaking the API ;) ), we can see a significant slowdown on the GPU volume rendering part, especially during interaction. Typically we dropped from 15/20 fps to 7/8 fps, on the same machine (Win32, Nvidia Quadro K420), with the same code around.<div><br>This slow down can be seen in ParaView, if you compare the latest 4.4 OpenGL2 build with the classic 4.4 build while volume rendering a big enough volume (512^3)<br></div><div><br>The blog post here<br><a href="http://www.kitware.com/blog/home/post/976" target="_blank">http://www.kitware.com/blog/home/post/976</a><br>claims that the new GPU volume rendering implementation should be faster than the old one, is there some more detailed explanation somewhere ? Are there some important parameters that can make the difference ?<br><br>Thanks, <br><br>Simon</div><div><br></div><div>PS : The polygonal rendering seems a lot faster with the new backend !<span><font color="#888888"><br><div><br></div>-- <br><div><div dir="ltr"><div>------------------------------------------------------------------<br>Simon Esneault<div>Rennes, France<br>------------------------------------------------------------------</div></div></div></div>
</font></span></div></div>
<br></div></div>_______________________________________________<br>
Powered by <a href="http://www.kitware.com" rel="noreferrer" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" rel="noreferrer" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Search the list archives at: <a href="http://markmail.org/search/?q=vtk-developers" rel="noreferrer" target="_blank">http://markmail.org/search/?q=vtk-developers</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://public.kitware.com/mailman/listinfo/vtk-developers" rel="noreferrer" target="_blank">http://public.kitware.com/mailman/listinfo/vtk-developers</a><br>
<br>
<br></blockquote></div><span><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div><div dir="ltr"><font face="trebuchet ms, sans-serif"><i>| Aashish Chaudhary <br>| Technical Leader <br>| Kitware Inc. <br></i></font><div><i><font face="trebuchet ms, sans-serif">| </font><a href="http://www.kitware.com/company/team/chaudhary.html" target="_blank">http://www.kitware.com/company/team/chaudhary.html</a></i></div></div></div>
</font></span></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div><div dir="ltr"><font face="trebuchet ms, sans-serif"><i>| Aashish Chaudhary <br>| Technical Leader <br>| Kitware Inc. <br></i></font><div><i><font face="trebuchet ms, sans-serif">| </font><a href="http://www.kitware.com/company/team/chaudhary.html" target="_blank">http://www.kitware.com/company/team/chaudhary.html</a></i></div></div></div>
</div>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div>------------------------------------------------------------------<br>Simon Esneault<div>Rennes, France<br>------------------------------------------------------------------</div></div></div></div>
</div>