cpu intel core 2 quad q6600
Open Suse 10.3
Xorg 7.2
NVIDIA nx8800GT
drivers 169.12 or 170.06 , 64 bits
NVIDIA settings antialiasing :'override application settings'
both blender 2.45, and 2.46RC, x86-64
open a new scene, add a cube.
go into 'texture paint' mode
move the mouse to any button, or on the 'view properties' subwindow
viewport goes black. Move the mouse back to viewport, the scene reappears.
In the same scene, go into edit mode, select a vertice, the viewport 'flashes' black for a fraction of second.
Still in edit mode rotate the cube, or scale it. Then viewport flickers black/normal
on a more complex scene with UV mapped textures, objects appear red on a black background.
Setting antialias to 'use application settings' fixes this behaviour
another description here : http://blenderartists.org/forum/showthread.php?p=1083732
I attach the blend file, even if it is straight forward to redo it.
regards,
Lile
Description
Event Timeline
So, to recap: forcing anti aliasing creates visual artefacts?
Sounds a lot like a driver problem.
yas i have same prop on 8600GTS vista
whan i set video card settings to Quality not performance
Can't confirm with svn build, 7300GT, 169.12 driver. Will try with test build releases later.
Sounds like a driver swap buffers issue. What you're seeing is the selection buffer drawn so blender knows which face/vert/edge is under the mouse cursor. This is never supposed to actually be swapper to screen.
Joe
I can confirm problems when enabling this option on an NVidia 8800. Though you can find in the NVidia documentation also that these options will not work with all applications, and that they change standard opengl operation. It seems not implausible to me that such settings would affect buffer swapping, since antialiasing requires different buffer setups. This kind of driver options that override applications settings we really cannot support..
Actually now I think about it I use anti-aliasing on my nvidia quadro pro 3450 and I do get occasional flashes of the selection buffer (though not very often and it's not really been a problem for me).
Joe
ok,thank you for having taken a look at it !
From your feedback, I understand the best might be to send the bug report to nvidia, though, I think it has already be done. I will try to dig into this.
If I have any news from them I will post a comment again here
ty again !
This is a generic request to test your bug report and see if it is still an issue in 2.5alpha2 if so please let me know by making a comment in this report ie 'also in 2.5alpha2' and I will add it to the 2.5 bug list.