Summary: | blender running with nvidia opengl and AA blurs interface | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Graeme Humphries <unit3> |
Component: | Current packages | Assignee: | Gentoo X packagers <x11> |
Status: | VERIFIED TEST-REQUEST | ||
Severity: | minor | CC: | hanno, lordvan, malverian, tux |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
URL: | http://demoni.ca/pics/blender_aa.png | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Graeme Humphries
2003-06-09 14:12:19 UTC
Whoops, I just thought of an additional thing to test, and my guess was correct. Blender displays correctly for all __GL_FSAA_MODE values *except* 2. 2 is for NVidia's QUINQUNX (or whatever that silly name is) AA on my Geforce 3 card, so it's definately a problem with that kind of antialiasing. I'd suggest pointing out the deficiency to NVidia, and closing the bug, since all other AA modes seem to be working fine. I don't have a nvidia (it's a Centrino) and I have the same problem, so maybe it's only AA related Is this still a problem with the new drivers? This bug is 10 months old now so im just wondering if nVidia have fixed the issue, or do we need to mark it upstream and point it to them still? I have no idea what you meant in comment #2 Andre, could you please clarify. Since my problem isn't on a NVIDIA, I was wondering if the real issue was with Anti-Aliasing, as was commented on the Description. So are you saying that the fix mentioned works for you aswell? setting the env AA to 0 doesn't work for me, but I've read somewhere, don't remember where, that the problem was with the _animated cursors in X_, so I've moved .icons to icons just to test it out, and now with the default xorg cursor, blender works as expected. Strange, because I *always* had the animated cursors enabled, but was able to make the problem disappear by changing the AA settings with an NVidia card. Mind you, now I don't have access to the machine that I initially reported the problem from, so I can't do any further NVidia testing. Perhaps it's a combined trigger, where you have to have (at least in some cases) antialiasing and animated curors enabled? Please test this with 6111 which just went into cvs. Report back on success or failures. Thanks. Can we close this ... no activity recently at all Yeah, I no longer have any machines with NV cards to test this with, and since changing the AA settings seems to fix it, I wouldn't worry overly much. Closing, i see no reason to leave on test. |