uhm.. something between OpenGL 2.0 support and worse 3d accel?
Originally Posted by Erektium
However, I'm asking myself how fglrx and radeon compare at OGL 1.x performance... perhaps the difference there is not /that/ big?
the leaked driver seems to be ok. I am using kwin 4.1.85+effects and watch tv with tvtime - and so far no problems. Resizing windows is as slow as always and at one point the kmenu was stuck until I closed tvtime. Apart from that there doesn't seem to be any problems. I will try 3d later.
To clarify some things, I regularly use an r300 card and as far as i am concerned it behaves remarkably well with the fglrx driver.
I used to have another also, but in the last month upgraded, and IMO the driver works much better on the r300 cards than r700 ones.
I don't understand why some of you are having these issues, as the driver works fine on my older cards. This is with catalyst 8.10, 8.11, and 8.12.
With my new card, I have updated to the 9.1b (removed pesky watermark), and it is about as stable as all the previous releases - ie - random crashes persist
A notable regression from 8.12 has been fixed.
What bothers me most with the drivers is the lack of support for shaders in wine, which makes many games unplayable or not desirable for play.
For example with command and conquer 3, shaders and shadows must be turned to lowest to be playable, but certain things still trigger the 'stretched triangle' corruption, and also the game slows down immensely when there too many effects.
how did you remove the watermark?
Are you sure this isn't more a limitation of Wine or the hardware itself?
Originally Posted by poofyyoda
AFAIK, Wine needs many OpenGL extensions for e.g. DX Shader 2.0 support and those may not be supported by r300 chips.
Removing the watermark is simple. Just copy /etc/ati/signature over from another driver.
Nah, the only people with problems on the appdb, are those with ati cards. The issue exists exactly the same on my new HD 4650 as my older cards also.
Originally Posted by NeoBrain
Composite isn't working on its own as it should, really, so instead of Composite+Video, how about we get Composite first? Then you can think about +Video.
Tags for this Thread