Summary: | [r128] Clipping problems in RTCW | ||
---|---|---|---|
Product: | Mesa | Reporter: | Adam Jackson <ajax> |
Component: | Drivers/DRI/r128 | Assignee: | Default DRI bug account <dri-devel> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | paulepanter |
Version: | unspecified | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
URL: | http://sourceforge.net/tracker/download.php?group_id=387&atid=100387&file_id=49201&aid=730471 | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Adam Jackson
2004-06-01 07:47:03 UTC
mass reassign to dri-devel@, i'm no longer the default component owner. sorry for the spam. this is old but probably still valid. Bug 755 might be a testcase... closing due to inactivity and recent bugfixes in the area. please reopen if they're still valid. reopening, still valid apparently. Sounds like this could be related to bad glPolygonOffset implementation. I coded a little test program to figure out how r300s z-bias works: http://nu.rasterburn.org/~aet/offset.tar.bz2 (never mind about the coding style!) Im suggesting something similar to be included in mesas test programs as i didnt find any decent programs that would clearly show if glPolygonOffset is operating correctly. Unless anyone isnt interested in creating a new test im willing to port this to glut and add tests for points and lines. The test looked the same both on ALWAYS_INDIRECT and with hardware on my Rage 128. Given that the decals in question tend to be at large differences in Z, I'm not that surprised that it didn't help. Another possibility is that it's broken software fallbacks that are at fault. Checking if R128_DEBUG=fall <game> shows fallbacks happening could indicate that that's the problem, since fallbacks are rather broken currently. I think it's safe to close this after 7 years of silence, and the driver in question has since been removed from mesa. I don't know if it was fixed in the meantime, but let's assume it was. (In reply to comment #7) > I think it's safe to close this after 7 years of silence, and the driver in > question has since been removed from mesa. I don't know if it was fixed in the > meantime, but let's assume it was. Hmm. In such cases I think CLOSED is better than RESOLVED. Unfortunately there does not seem to be a reason TOO_OLD or similar. I guess WONTFIX is good in this case. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.