I built a small app over the week-end ... to realize that it does not reproduce the issue. Every Qt openGL code and mine is running, but the app I want.
However, I find a previous version of our app that is working (only with VirtualGL 2.2alpha, seg fault with any other previous versions). I know we did some speed improvement regarding Qt pixmap issues so I will dig into that and let the mailinglist know as soon as I found which one of our "improvements" caused this prob. I will send a small app reproducing the issue as soon as I found which part of the code creates it. Now, the version of our app that works with VirtualGL2.2alpha is very slow. Checking the release notes I saw you are not using the TurboJpeg anymore. Is there a known decrease in performance with this change ? (glxgears is not slow at all ... only our app .... again !) Best regards and thanks for the quick replies. Flo. -----Original Message----- From: DRC [mailto:[email protected]] Sent: Friday, April 09, 2010 1:52 AM To: VirtualGL Users Subject: Re: [VirtualGL-Users] QT + VirtualGL = black viewport flickering - no display I'm not sure it is the same issue. Alex's issue was specific to MITK, and he was able to resolve it by upgrading to a new version. Does your app use VTK or Qt or both? Is it something that could be reproduced with a simple test application that I could build and run here? On 4/8/10 10:24 PM, Flo wrote: > Dear All, > > I have an issue that was previously reported on you mailinglist here and > not answered: > _http://sourceforge.net/mailarchive/message.php?msg_id=cbb4c0f20802191246o28 [email protected]_ > > Specifically, I have a Qt application that uses 2D and 3D rendering in > viewports. Although fine as standalone, when used through VirtualGL, > every viewport (2D or 3D) is black. The only moment when I can see the > proper content is by creating a mouse event (movement, click and else), > where it flickers and for a second I can see the proper content before > it becomes black again. > > I tried many combination of VirtualGL options but it seems not to do any > good. > > The VirtualGL server is a SLED 11, although using few Suse OSS 11.2 > repo, 64-bits and NVidia video card. > > "from what have been said: It sounds like if the > > OpenGL buffer is not flushed properly. > > We are also aware of problems with some OpenGL drivers, beside the > > ones from Nvidia, where setting the VTK rendering mode to "immediate" > > may help." > > But it didn't go any further in the thread. > > Any help would be greatly appreciated. > > Flo. > > > > ---------------------------------------------------------------------------- -- > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > > > > _______________________________________________ > VirtualGL-Users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/virtualgl-users ---------------------------------------------------------------------------- -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ VirtualGL-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/virtualgl-users ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ VirtualGL-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/virtualgl-users
