Rendering Problems with v2.5

ATi Catalyst 5.5 were released yesterday. Try them...

 

Hi. I just installed the 5.5 drivers. The Control Center is ok but the other screen that comes up when you select something is devoid of any green or grey colour.

 

I rebooted the system again and the patches are back and the normal colour is back also. Not beige like I meant to say in above quote. I will knock back the Hardware Acceleration a notch once more. Marcos to ATi come in.

 

A little while back (either 2.5 beta or pre that) I had this issue on one of my PC's. It didn't concern me so I just removed the NOD32 GUI and kept working. Since then (either when installing the 2.5 beta or final - I really didn't take much notice) I've re-enabled the NOD32 GUI and all is fine now. I think (I'm pretty sure) it was on a headless machine that I was having this issue. It is installed with an S3 Trio3D/2X and has no monitor.
Also I've recently begun to notice the brown/orange coloured buttons again when accessing this console with remote desktop.
This is not a complaint or a request for a fix. I'm more than satisfied with NOD32 - Thanks for a great product. If there's anything personally I'm able to contribute to help keep it that way please ESET, do not hesitate to let me know - as I'm able I certainly will.

 

Thank you for the info. However 5.5 do not do any better. even tried a reinstall of NOD 2.5 after the ATI update to no avail. Were up to 104 entries now on this thread. How many more before the developers revisit the issue? Incidently KAV 6.0 Beta is said to be very light on resources.

 

It doesnt seem like a driver bug to me. Did anyone get a response from ATI?

 

Cat 5.5's installed

As I said and will continue to say, NOD32 is the only app with a rendering issue on my system. Since 2.1x looked fine and the issue appeared with the introduction of 2.5.x, I don't need to see code to know where the problem is.

But as I said, it's a minor issue. As long as it catches baddies, that's what's important.

 

OK, if I'm reading the thread above correctly, this only happens with DX8 ATI cards and Matrox cards? I have NOD32 installed on a system right now that has a GeForce 3, but I was thinking of replacing the card with a 9800 Pro that a friend had borrowed and is returning. But that's a DX9 card. Based on the above, I shouldn't see a problem, right?

 

You mean like Marcos or Happy Bytes?

 

Does this rendering bug happen on your GeForce3?

So far there is no reported problems with the ATI Radeon 9800 Pro, therefore it should work fine

 

Marcos, HB, one of us, anyone

 

No, it didn't, but I read stuff about it happening on ATI cards ... granted, what I read indicated DirectX 8 cards only, but ...

 

I was running an ATI 9000 Pro and I also noticed the rendering problem which started with Version 2.5 Beta and continued into the final version. If I changed my settings to 16 bit, the rendering problem disappeared on the main menu but continued on the secondary menus.

Today I decided to update my graphics card to an MSI 6600 GT Nvidia card and immediately noticed that the rendering problem disappeared.

There is no doubt in my mind that there is a programing fault somewhere in the code that conflicts with ATI cards that were designed for DX8. DX9 cards from ATI do not have this problem.

Just my 2 cents.

 

Since this issue seems mostly (not completely) limited to these cards AND having compared some of the different implementations of hardware accelleration across different manufacturers I would think it quite probable that it is an issue with the way ATI have chosen to implement support DirectX. It could just as easiy be a windows GUI+ issue. Either way a code update may solve it.
The fact that no other applications or hardware show this issue does not indicate it to be an issue with a particular applications code(although easy to make that assumption). Look at the previous TCP/IT stack (pending) issue for example.

 

Does this rendering bug only happen on Windows XP? If yes, then it would be related to GDI+ in some way because Win2k and below do not have GDI+ (they have just GDI).

 

I emailed NOD this evening asking that the rendering problems be mentioned in the known issues area on their FAQ page.

 

Installed Catalyst 5.6, yet the bug still there.

 

Maybe Nod developers are waiting for this thread to hit 200 posts before contacting ATi. See you all in a week going fishing in Northern Quebec.

 

Bug still here with Cat 5.6. Time to get on the ball Eset.

 

Installed NOD32 2.50.25, bug still there.
Not that I really expected anything to change.

 

Ditto here. I've filed this under "insignificant but annoying" things. I'm not about to degrade computer performance to mend such a minor issue.

John S.

 

Come on, Eset.....At least investigate the problem. Many people are getting annoyed by this.

 

Should be easy to do Eset makes the program ATi makes the card. Talk to each other.

 

Anyone try the new 5.7 ATI drivers (to fix rendering issue)?

It's not an issue for me, since I have a DX9 card, but I was wondering if the rendering issue still exists with the new 5.7 drivers.

 

Re: Anyone try the new 5.7 ATI drivers (to fix rendering issue)?

Let us know how it goes for you as we still do not know if Eset has even attempted to contact ATi regarding the issue after several requests to do so.