Hello Marcus,
Marcus Lindblom wrote:
> Carsten Neumann wrote:
>> Marcus Lindblom wrote:
>>> I noticed a change from 1.x to 2.0, namely that PassiveWindow inherits
>>> NativeWindow (which is Win32Window on my platform), which means that
>>> swap calls (that call doSwap()) are made twice in our apps, since Qt
>>> swaps, and I have a PassiveWindow in a QGLWidget.
>> I fixed a bug in r1880 that got rid of double swaps for me.
>
> Ok. We're currently on 1874.
ok, Gerrit fixed some typos in r1875 that fixed the conditions in
Window::render so it should not call doSwap() but swap().
>>> Shouldn't swap be disabled by PassiveWindow? It currently does not
>>> implement doSwap(), but only the regular swap().
>> where does the call to doSwap() come from? Normally the call should come
>> from swap, but since that is overridden for the PassiveWindow nothing
>> should happen, unless there is a direct call to doSwap() from somewhere?
>
> Here's the call stack (for r1874):
>
> SwapBuffers - GDI32.dll
> OSG::WIN32Window::doSwap - osgwin32window.cpp, line 195
> OSG::Window::render - osgwindow.cpp, line 1824
> OSG::SimpleSceneManager::redraw - osgsimplescenemanager.cpp, line 883
> SSMWidget::paintGL - qtssmwidget.cpp, line 67
> QGLWidget::glDraw - qgl.cpp, line 3458
thanks, this is the case that is fixed in r1880.
>> we could implement the do*() functions for PassiveWindow, but I'm more
>> interested where the call to doSwap() comes from, as that seems a
>> potential bug.
>
> Hope it helps.
yes, thanks, I wanted to rule out that there is some code path nobody
thought of, but the one you have is not unusual at all ;)
> We also use a SimpleStage to draw to an FBO, if that matters.
>
> Related-ish: Mipmaps are _not_ updated even if the texture has a
> min_filter with mipmaps in it. This had us scratching our heads for a
> while, before we figured out what it was. Can auto-mipmap-generation be
> enabled somehow? (IIRC it's a simple GL call to call once the rendering
> is complete.)
did you set postProcessOnDeactivate on the FBO? That will enable the
mipmap generation for atteched TextureBuffers.
Cheers,
Carsten
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
