Cat 6.10 out !!!!!!!!!!!!!!!!!!!!

  • Thread starter Thread starter SL
  • Start date Start date
SL said:
Cat 6.10 are finally out ( at the lastest, lastest october time)

Best regards

Sid
Click to expand...

"Chuck" HDR/AA support finally included. Quote from 6.10 release notes:

"HDR + Anti-Aliasing support for The Elder Scrolls Oblivion
Users no longer need to download and install the Chuck patch - the Direct3D
driver now includes native support for High Dynamic Range and Anti-Aliasing
with The Elder Scrolls Oblivion."

I presume that we'll still need to rename executables from games other than
Oblivion to "oblivion.exe" to gain HDR/AA in titles that are not officially
supported for HDR/AA.

Tony
 
SL said:
Cat 6.10 are finally out ( at the lastest, lastest october time)

Best regards

Sid
Click to expand...

I upgrade from 6.9 (after uninstall 6.9) to 6.10.

The (XP) system event viewer reports now an error:
Source: ati2mag
Description: I2c return failed
 
Wouter said:
I upgrade from 6.9 (after uninstall 6.9) to 6.10.

The (XP) system event viewer reports now an error:
Source: ati2mag
Description: I2c return failed
Click to expand...

Same here (Catalyst 6.10 witch X1600Pro AGP, 2x 19" TFT). Additionally
to the l2c error it gives an "edid checksum error" each time the control
center is scanning for new display devices.

Error messages at system start:

- I2c return failed
- Rom does not support this device
- Edid checksum error

I mean ATI has released an buggy driver which isn't able to handle any
form from edid information(s) from the display(s). Rock you baby, the QM
has to be fired ...

Also on the "urgently to do list" is the deinterlacing prob in VMR9
rendering modes while avivo is acitvated. In overlay and VMR7 all is
well done, VMR9 seems to be unusuable for all kind of interlaced video
stuff which is played with direct show decoders with activated hardware
acceleration (sdtv, hdtv).

Oh, not that i forget that: The tearing in dark scenes from movies isn't
fixed yet (avivo devices), they only promised in august to do that.


Fell back aslept over the keyboard until ATI wakes me and say they
release an usuable driver made for non-gamers.

Regards,
Thomas
 
Wouter Smaal said:
I upgrade from 6.9 (after uninstall 6.9) to 6.10.

The (XP) system event viewer reports now an error:
Source: ati2mag
Description: I2c return failed
Click to expand...

Event Viewer / System shows the following for me:

/*
Event Type: Error
Event Source: ati2mtag
Event Category: GCO
Event ID: 44044
Date: 11/2/2006
Time: 4:39:50 AM
User: N/A
Computer: DJRAID
Description:
I2c return failed

Event Type: Error
Event Source: ati2mtag
Event Category: GCO
Event ID: 44044
Date: 11/2/2006
Time: 4:39:50 AM
User: N/A
Computer: DJRAID
Description:
I2c return failed

Event Type: Warning
Event Source: ati2mtag
Event Category: LCD
Event ID: 48137
Date: 11/2/2006
Time: 4:39:50 AM
User: N/A
Computer: DJRAID
Description:
Rom does not support this device
*/

That said, I am not experiencing any visual/noticeable impact to performance
or stability as a result of the above.

Tony
 
Thomas said:
Same here (Catalyst 6.10 witch X1600Pro AGP, 2x 19" TFT). Additionally
to the l2c error it gives an "edid checksum error" each time the control
center is scanning for new display devices.

Error messages at system start:

- I2c return failed
- Rom does not support this device
- Edid checksum error

I mean ATI has released an buggy driver which isn't able to handle any
form from edid information(s) from the display(s). Rock you baby, the QM
has to be fired ...

Also on the "urgently to do list" is the deinterlacing prob in VMR9
rendering modes while avivo is acitvated. In overlay and VMR7 all is
well done, VMR9 seems to be unusuable for all kind of interlaced video
stuff which is played with direct show decoders with activated hardware
acceleration (sdtv, hdtv).

Oh, not that i forget that: The tearing in dark scenes from movies isn't
fixed yet (avivo devices), they only promised in august to do that.


Fell back aslept over the keyboard until ATI wakes me and say they
release an usuable driver made for non-gamers.

Regards,
Thomas
Click to expand...


Maybe you can consider the ATI Omega drivers http://www.omegadrivers.net/
 
Wouter said:
Maybe you can consider the ATI Omega drivers http://www.omegadrivers.net/
Click to expand...

Highly possible not. Its different to await some registry tweaks and GUI
cosmetics, and at the other side to imagine that in the omega drivers
the avivo engine could be more enhaced than in the ATI originals.

For the last part: I'm not an dreamer. And also for the problem with the
l2c exceptions the latest omega drivers are not an more sophisticated
solution than the original fallback from 6.10 to 6.9. Both are in that
point of view the same.

We keep it in mind: The latest 6.10 drivers are buggy by reading the
edid information from connected displays. 6.9 not (thats also the latest
omegadrivers). But ALL released drivers from 6.7 to 6.10 are buggy
because with AVIVO-enabled GPUs the interlacing is corrupted in VMR9
rendering mode, another problem is the tearing in dark video scenes with
VMR9. Not affected is overlay, and (sometimes) not in VMR7. I see no
reason why an switching to the omegadrivers should help.

Regards,
Thomas
 
I get about 10-12 of these messages every day since Catalyst 5.xxx

Just remember an entry in Event Viewer isn't the same as an error message.
If it doesn't hurt performance or application compatibility, then leave it
alone.
 
Back
Top