Cat 5.7 w/High or Optimal Quality breaks LimeWire

  • Thread starter Thread starter Tony DiMarzio
  • Start date Start date
T

Tony DiMarzio

Verified this:

Catalyst 5.7 and "High Quality" or "Optimal Quality" Direct3D settings
results in LimeWire GUI not being able to render.
 
Tony DiMarzio said:
Verified this:

Catalyst 5.7 and "High Quality" or "Optimal Quality" Direct3D settings
results in LimeWire GUI not being able to render.
Click to expand...


What do you think of that? Well, at least you were able to troubleshoot the
problem yourself. Even though I have no clue what LimeWire is, I have heard
of it more than a few times and obviously it must be important to some
users. It might be worth giving ATI a bug report on it.
 
Tony said:
Verified this:

Catalyst 5.7 and "High Quality" or "Optimal Quality" Direct3D settings
results in LimeWire GUI not being able to render.
Click to expand...

Turn off AA.
 
That's like saying the solution to getting game X to run on your ATI is to
turn off 3D acceleration. I'll pass.

'tsa BUG! Not sure who owns the bug though... might actually be LimeWire and
not ATI. Though, this is completely new starting with 5.7.
 
Interestingly, Catalyst 5.7 seems to have fixed the clipping/flashing
polygons in Doom3 with fast writes enabled on my system. Now I don't have to
toggle this BIOS option to view the occasional 1080p video.

If you are using RadLinker, why don't you just set "Balanced" in the ATi
drivers, then make a few game-specific RadLink shortcuts with the desired
AA/aniso settings?
 
That's like saying the solution to getting game X to run on your ATI is to
turn off 3D acceleration. I'll pass.

'tsa BUG! Not sure who owns the bug though... might actually be LimeWire and
not ATI. Though, this is completely new starting with 5.7.
Click to expand...


You need to turn off AA to start Limewire, then you can enable AA
again once Limewire is running and it will work OK (until the next
time you need to start LimeWire that is).

It's not a new bug only to the Catalyst 5.7 drivers, I just got a X800
XL and downloaded the Catalyst 5.6 drivers and have this problem.
 
Andrew Reid said:
You need to turn off AA to start Limewire, then you can enable AA
again once Limewire is running and it will work OK (until the next
time you need to start LimeWire that is).
Click to expand...

Yeah... I found that out through trial n' error earlier.
It's not a new bug only to the Catalyst 5.7 drivers, I just got a X800
XL and downloaded the Catalyst 5.6 drivers and have this problem.
Click to expand...

I do not experience this on my 9800 pro under CAT 5.6

Only CAT 5.7 causes this for me.
 
Andrew Reid said:
You need to turn off AA to start Limewire, then you can enable AA
again once Limewire is running and it will work OK (until the next
time you need to start LimeWire that is).
Click to expand...

Yeah... I found that out through trial n' error earlier.
It's not a new bug only to the Catalyst 5.7 drivers, I just got a X800
XL and downloaded the Catalyst 5.6 drivers and have this problem.
Click to expand...

I do not experience this on my 9800 pro under CAT 5.6

Only CAT 5.7 causes this for me.
I had the same problem with the 5.6 drivers, I was able to correct
the problem by updating JAVA.

Griffin
Click to expand...
 
Griffin McKorn said:
Yeah... I found that out through trial n' error earlier.


I do not experience this on my 9800 pro under CAT 5.6

Only CAT 5.7 causes this for me.

I had the same problem with the 5.6 drivers, I was able to correct
the problem by updating JAVA.

Griffin
Click to expand...

If updating JAVA fixed it, hmmm...... that seems to point to it being a JAVA
bug and not an ATI bug. Could still be an ATI bug though.

I am, in fact, running the LATEST version of JAVA
"jre-1_5_0_04-windows-i586-p.exe" and am still experiencing the problem.
However, it is only with cat 5.7 (like I said above). Cat 5.6 shows no
problem when AA is on and using LimeWire.

Tony
Click to expand...
 
Back
Top