I run Fedora Core 4 on a pentium IV 2.4 Gig with an Nvidia FX5700 LE graphics card.
When running the alpha 1 and alpha 2 release, it starts up in full screen mode as it should, but after splitting the 3D view, when i move the mouse around, I get glitches in the borders that divide screens/windows, as if previous openend screens are still partially visible (one pixel wide or so). Running the test versions from the command line with the option -w doesn't give this glitch. I wasn't sure wether it was interface related or opengl/gfx....
I didn't have this issue in blender 2.37a or before
greets
Description
Description
Event Timeline
Comment Actions
Logged In: YES
user_id=103
Hey Matthijs!
I saw this same behaviour on other nividia cards, for a fix you should check or FAQ on blender.org -> support. It's nividia glitches... most likely the buffer swap method.
Further; you should really test it with blender 2.37a, there's no reason I know why this would change in Blender, apart from you upgrading drivers?
-Ton-
Comment Actions
Logged In: YES
user_id=1841
The solutions in the FAQ made it work ok. I didn't have any trouble with blender 2.37a, same drivers, that's how I noticed (I use the alpha's and 2.37a on the same machine with the same configurations)
Under system tools, Nvidia display settings, OpenGL settings i had to deselect the allow OpenGL flipping
thank you
greets
Comment Actions
Logged In: YES
user_id=1841
ok, an little update.
as stated I never had this glitch with blender 2.37a.
When I download the official builds of blender 2.40 and 2.41, and I run the executable (under linux), blender starts up full screen as it should and there seems to be some residue of the startup splash.(my startup screen has the 3d view devided in two, instead of the whole width) when starting blender with the -w option, this glitch is gone.
when trying the options in the FAQ, this glitch dissapears, but there is also a slowdown. when starting blender fullscreen, the tabs fold in and out much faster. when starting blender with the option -w, the tabs go a bit slower, (probably to do with the extra drawing of the window border)
When aplying the options in the FAQ the speed op the tabs fullscreen gets redused to the speed of the tabs as if I started blender with -w option.
Now, today after the orange merger to HEAD, gabio did a build wich I downloaded (29-01-06). when I click the executable, blender starts up full screen without the glitch!. Somehow, this can't be related to the nvidia drivers but must be related to something inside the source code or during compiling.
anyhow, just thought I drop you a line to let you know...
also, concerning the rotation/scaling pivot; the comma hotkey works, but the period button doesn't.
greets
Comment Actions
Logged In: YES
user_id=1841
please ignore my last post, the glitch is still there, sorry
Comment Actions
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.