Re: [Flightgear-devel] Grey panel with Radeon 7500 and dri driversstill there.
David Luff a écrit: FWIW, the grey panel with the Radeon 7500 and the DRI drivers still persists despite the patch to fix this behaviour with the ATI binary drivers. I jump onto this post to say that I've just see that I've got the same problem with my new Dell Latitude C610, which have a Radeon Mobility LY. It's possible I've not done a perfect XF86-config-4 for now, but it seens that the problem is known. I can see the instruments only when I press 'S' (mini panel), but I don't see the (...don't remember the english word...) the moving cursors like on a clock. ;-O Note also that with a normal screen plugged, when playing video with overlay, the Dell LCD screen is black, but I can see the video on the normal screen. Bye, Fabien ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Grey panel with Radeon 7500 and dri driversstill there.
Fabien ILLIDE wrote: David Luff wrote: FWIW, the grey panel with the Radeon 7500 and the DRI drivers still persists despite the patch to fix this behaviour with the ATI binary drivers. I jump onto this post to say that I've just see that I've got the same problem with my new Dell Latitude C610, which have a Radeon Mobility LY. I hereby call not it and point you guys to the DRI list. This just looks like a driver bug to me, sorry. I don't have a Radeon 7500 to test against. https://lists.sourceforge.net/lists/listinfo/dri-devel It's worth pointing out that the DRI driver the current distributions are shipping is rather old. I've seen lots of work checked in and discussed (I'm a lurker on the list) over the past few months. You might very well see better results with current code, although sadly building an entire X server isn't terribly easy. If someone can come up with a good test case and screenshot and is willing to test fixes for them, I'll happily chime in with remarks about how the code works. Andy -- Andrew J. RossNextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com Men go crazy in conflagrations. They only get better one by one. - Sting (misquoted) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Grey panel with Radeon 7500 and dri driversstill there.
Jim Wilson wrote: FWIW I'm also seeing a significant degree of what appears to be z-buffer fighting with geforce2 at 24bpp. The c310-3d panel goes grey at certain angles and the c172-3d and a4-yasim panels display a lot of instability in the rendering (problems between layers in the instruments), although they do not go grey. The fighting is more pronounced with instruments at an increased angle from the camera vector. I see this too. I think (maybe) that it's due to the cockpit jitter issue, though. The loss of precision issue will result in different depth slopes for polygons that should mathematically be on the same plane. Thus the problem is worse for the near cockpit geometry (A-4), and with off-angle viewing. I need to work on the jitter bug, but keep getting distracted by more interesting things. The problem, if anyone forgets, is that the matrix the cockpit draws into has a translation component that looks like: eyepoint-to-origin + origin-to-aircraft-body Since the origin can be kilometers away, and the math is done in 32 bit floats, you end up with millimeter scale (several pixels or so) imprecision in the resulting positions. What needs to happen is for the model code to calculate a eyepoint-to-aircraft transformation on its own (in double precision) and not simply push a translation onto the matrix. Andy -- Andrew J. RossNextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com Men go crazy in conflagrations. They only get better one by one. - Sting (misquoted) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Grey panel with Radeon 7500 and dri driversstill there.
Jim Wilson wrote: Right, the polygon offsets that I thought I rememebered Andy had been adjusting for this issue seem to have introduced some other problems though. The way it worked was that the original code I submitted used a very high offset number (because I'm using NVidia hardware too, and needed it to prevent fighting between layers -- I didn't understand the jitter issue yet at the time). But this caused the infamous panel visible through the aircraft bug with 16 bit Z buffers. David experimented and found a much smaller number that worked well for him at 16 bit, in the process re-introducing the Z fighting bug on NVidia hardware with a 24 bit depth buffer. But again, the Z fighting issue is (I'm pretty sure) related to the matrix precision issues. It's not a PolygonOffset issue per se. Andy -- Andrew J. RossNextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com Men go crazy in conflagrations. They only get better one by one. - Sting (misquoted) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
