<div dir="ltr">of course, sorry for not noticing the sync issue:<div><br></div><div><div>pi@raspberrypi:/dev $ vblank_mode=0 glxgears</div><div>ATTENTION: default value of option vblank_mode overridden by environment.</div><div>2613 frames in 5.0 seconds = 522.544 FPS</div><div>2731 frames in 5.0 seconds = 546.007 FPS</div><div>2583 frames in 5.0 seconds = 516.513 FPS</div><div>2648 frames in 5.0 seconds = 529.468 FPS</div><div>2518 frames in 5.0 seconds = 503.535 FPS</div><div>3206 frames in 5.0 seconds = 640.964 FPS</div><div>2533 frames in 5.0 seconds = 506.589 FPS</div><div>2530 frames in 5.0 seconds = 505.956 FPS</div><div>2700 frames in 5.0 seconds = 539.864 FPS</div></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 20, 2016 at 8:50 AM, Jose Paulo Moitinho de Almeida <span dir="ltr"><<a href="mailto:moitinho@civil.ist.utl.pt" target="_blank">moitinho@civil.ist.utl.pt</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Can you please post the "FPS" that you obtain without limiting the framerate?<br>
<br>
Using bash the command is<br>
"vblank_mode=0 glxgears"<br>
<br>
Thanks<br>
<br>
ZP<br>
<div class="HOEnZb"><div class="h5"><br>
On Tuesday 19 April 2016 23:01:43 Elvis Chen wrote:<br>
> hi all,<br>
><br>
> This is a status update on vtk on Raspberry pi, with hardware accelerated<br>
> OpenGL.<br>
><br>
> After a few days of trial and error, I managed to get VTK working on<br>
> Raspberry Pi 3. I hope my experience can save others some time, as<br>
> information on the web can be misleading.<br>
><br>
> First of, I am using Raspberry Pi 3. The DOs and DONTs<br>
><br>
> DO:<br>
> - make sure you use the official PSU (rated at 2.5A), as there are reports<br>
> that an under-powered PI causes OpenGL driver to fail,<br>
><br>
> DONTs:<br>
> - don't use the official 7" touch screen. The OpenGL driver apparently is<br>
> very picky on the output format. It won't work with the 7" touch screen<br>
> - don't follow the instruction on<br>
> <a href="https://www.raspberrypi.org/blog/another-new-raspbian-release/" rel="noreferrer" target="_blank">https://www.raspberrypi.org/blog/another-new-raspbian-release/</a>, in<br>
> particular DO NOT UPGRADE Raspbian.<br>
><br>
> Here is what I had to do to get hardware accelerated OpenGL to work:<br>
><br>
> - create a new raspbian/Jessie bootdisk using 2016-03-18 image<br>
> - upon first boot, which boots into X by default, expand the file system<br>
> using Menu->Preference->Raspberry Pi Configuration. Reboot<br>
> - upon 2nd boot, change keyboard/time-zone as desired. Using the same<br>
> configuration utility as the previous step, change the boot option to "To<br>
> CLI" instead of "To Desktop". Reboot.<br>
> - now raspbian will boot into commandline instead of X. Issue the following<br>
> command:<br>
> sudo raspi-config<br>
> - under Advanced Options, Enable OpenGL driver, reboot<br>
> - once rebooted, issue "startx"<br>
> - open a terminal, issue the following command<br>
> sudo apt-get update<br>
> sudo apt-get install libvtk5-qt4-dev cmake cmake-curses-gui mesa-utils<br>
><br>
> I choose vtk5 but vtk6 is also available as a pre-compiled package.<br>
><br>
> - with mesa-utils installed, you can run glxgears to test opengl. I am<br>
> getting 59FPS on RPi3<br>
><br>
> pi@raspberrypi:~/research/bin/vtkViewPolyDataMesh $ glxgears<br>
> Running synchronized to the vertical refresh. The framerate should be<br>
> approximately the same as the monitor refresh rate.<br>
> 293 frames in 5.0 seconds = 58.548 FPS<br>
> 301 frames in 5.0 seconds = 59.994 FPS<br>
> 299 frames in 5.0 seconds = 59.613 FPS<br>
> 290 frames in 5.0 seconds = 57.999 FPS<br>
> 300 frames in 5.0 seconds = 59.807 FPS<br>
> 300 frames in 5.0 seconds = 59.995 FPS<br>
><br>
><br>
> - I have compiled my own VTK program that displays a vtkpolydata and it<br>
> runs well. I'll be making a video and post it online in a few days.<br>
><br>
> Again, please not that while I "updated" the apt packages, I NEVER<br>
> "upgraded" any. I needed to "update" in order to install additional<br>
> programs, but an "upgrade" will brake the OpenGL driver.<br>
><br>
> Hope this helps<br>
><br>
> --<br>
> Elvis C.S. Chen, PhD<br>
><br>
> Imaging, Robarts Research Institute<br>
> Department of Electrical & Computer Engineering<br>
> Biomedical Engineering<br>
> Medical Biophysics, Western University<br>
> London, Ontario, Canada<br>
><br>
> On Sat, Apr 16, 2016 at 8:36 PM, David Gobbi <<a href="mailto:david.gobbi@gmail.com">david.gobbi@gmail.com</a>> wrote:<br>
> > Hi Elvis,<br>
> ><br>
> > One way of checking the OpenGL driver is the "glxinfo" command.<br>
> > The "OpenGL renderer" is usually Mesa if it is a software renderer,<br>
> > but if it gives the name of a specific card or chip, then you probably<br>
> > have hardware rendering, e.g. here's what my laptop reports:<br>
> ><br>
> > OpenGL vendor string: NVIDIA Corporation<br>
> > OpenGL renderer string: NVIDIA GeForce 9400M OpenGL Engine<br>
> > OpenGL version string: 2.1 NVIDIA-8.24.17 310.90.9.05f01<br>
> > OpenGL shading language version string: 1.20<br>
> ><br>
> > I don't know much about the Raspberry Pi, but google found this<br>
> > page that describes how to enable hardware OpenGL:<br>
> > <a href="https://www.raspberrypi.org/blog/another-new-raspbian-release/" rel="noreferrer" target="_blank">https://www.raspberrypi.org/blog/another-new-raspbian-release/</a><br>
> ><br>
> > - David<br>
> ><br>
> > On Sat, Apr 16, 2016 at 6:06 PM, Elvis Chen <<a href="mailto:elvis.chen@gmail.com">elvis.chen@gmail.com</a>> wrote:<br>
> >> Greetings,<br>
> >><br>
> >> I've recently acquired a Raspberry Pi 3. To my surprise, the latest<br>
> >> raspbian (Jessie) comes with a complete development environment,<br>
> >> including<br>
> >> gcc (4.9), cmake, and vtk (both vtk5 and vtk6).<br>
> >><br>
> >> I wrote a small program that reads a polydata and display it as a test<br>
> >> bed. The pipeline is:<br>
> >><br>
> >> vtkpolydatareader->vtkpolydatamapper->vtkactor<br>
> >><br>
> >> nothing fancy.<br>
> >><br>
> >> However, the rendering is surprisingly SLOW. It looks if the graphics is<br>
> >> not hardware accelerated.<br>
> >><br>
> >> My questions are:<br>
> >><br>
> >> 1) How do I check if the video (which I assume to be OpenGL) is hardware<br>
> >> accelerated?<br>
> >> 2) any suggestion on how to optimize the performance?<br>
> >><br>
> >> My next step is to comple vtk myself to see if it makes any difference.<br>
> >><br>
> >> any help is very much appreciated,<br>
<br>
</div></div><div class="HOEnZb"><div class="h5">_______________________________________________<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>
Please keep messages on-topic and check the VTK FAQ at: <a href="http://www.vtk.org/Wiki/VTK_FAQ" rel="noreferrer" target="_blank">http://www.vtk.org/Wiki/VTK_FAQ</a><br>
<br>
Search the list archives at: <a href="http://markmail.org/search/?q=vtkusers" rel="noreferrer" target="_blank">http://markmail.org/search/?q=vtkusers</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://public.kitware.com/mailman/listinfo/vtkusers" rel="noreferrer" target="_blank">http://public.kitware.com/mailman/listinfo/vtkusers</a><br>
</div></div></blockquote></div><br></div>