[Bf-committers] Bf-committers Digest, Vol 46, Issue 40

[Benoit Bolsee]

> Do you have flipping turned off?

Where do I find the flipping option? Is it a OpenGL driver option? 
I don't have a flipping option in the nVidia control panel, just a quad
buffer enable/disable option. If I disable quad buffer, Blender displays
correctly but I can't run games in stereo at the same time. The idea is
to have quad buffer enabled all the time but still being able to use
Blender normally. 
I don't have a problem with the cross-hair in Windows when quad buffer
is enabled, I just have all the menus and dynamic panels flickering like
crasy. 

/Benoit

-----Original Message-----
Date: Sat, 24 May 2008 20:18:58 -0500
From: Reuben Martin <reuben.m at gmail.com>
Subject: Re: [Bf-committers] Patch 12799 submitted
To: bf-blender developers <bf-committers at blender.org>
Message-ID: <200805242018.58336.reuben.m at gmail.com>
Content-Type: text/plain;  charset="utf-8"

Back on Saturday 24 May 2008, Benoit Bolsee was like:
> I've submitted the patch 12799 that fixes a problem in the ghost code 
> that was preventing the use of quad buffer stereo mode under Windows -

> only useful with the blenderplayer as quad buffer mode is disabled 
> when playing the game in the 3D view. While testing this, I noticed a 
> very annoying problem when the graphic card has quad buffer enabled 
> (nVidia quaro FX 370, Windows XP): the 3D view and other windows 
> display correctly but all the menus flicker horribly when displayed, 
> despite the fact that the chosen pixel format at startup is of 
> non-stereo type (the patch takes care about that). Is it a bug of the 
> nVidia openGL driver or something specific to the way the menus are 
> displayed?
>
> Benoit

Do you have flipping turned off? That's quite a common cause for
problems.

While we're talking about display issues, there is a problem with how
blender 
deals with rendering the cross hairs or circle used in the selection
modes. 
(triggered by the "B" key")

The cross hairs or circle do not display unless the mouse button is
pressed. 
This has something to do with using a 3D rendered desktop (compiz). It 
normally uses a double buffering where all window changes are rendered
to 
offscreen pixmaps. When blender is in full screen mode this is not a
problem 
because compiz allows fullscreen programs to bypass the offscreen
pixmaps and 
render directly. Not sure why these would not be drawn to the offscreen 
pixmap.

-Reuben