Summary: | glxgears in Xorg trunk does not operate smoothly with Solaris's OpenGL 1.3 implementation | ||
---|---|---|---|
Product: | xorg | Reporter: | Roland Mainz <roland.mainz> |
Component: | App/other | Assignee: | Xorg Project Team <xorg-team> |
Status: | RESOLVED NOTABUG | QA Contact: | |
Severity: | critical | ||
Priority: | high | CC: | amir.bukhari, stuart.kreitman |
Version: | git | ||
Hardware: | SPARC | ||
OS: | Solaris | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Roland Mainz
2004-11-07 19:18:30 UTC
(In reply to comment #0) > glxgears 2004-11-08-trunk jumps with Solaris OpenGL 1.3 implementation and is > pretty much unuseable, the gears move forth and back and are far far away from > rotating smoothly... ;-( Is vsync on? Are you using the smooth rotation patch? Depending on the framerate and the vertical retrace rate, it's not unheard of for glxgears to appear to be standing still, or rotating backwards. This is not a bug, the r200 and fglrx drivers show the same behaviour. This is the same effect as watching car wheels spinning on TV. As the car speeds up they look to be rotating forward, then slowing down, then standing still, then rotating backwards. Time domain aliasing. Note that the SPARC graphics group that produces Sun's OpenGL implementation does not provide a hardware-accelerated GL pipeline for the m64, only the software implementation. (For those not familiar with SPARC graphics, m64 was Sun's low end 2-D board in previous generation machines, based on ATI Rage II chipset in early models and Rage XL chipset in later ones.) If you want smooth, usable OpenGL output, use a board with hardware acceleration. so if this is a bug in sun's opengl, then it doesn't belong here. if it's a bug in glxgears, it's still not a bug, since gears is not expected to rotate smoothly but rather to update as fast as possible, which may create aliasing when not synced to vblank. |
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.