Widescreen Gaming Forum

[quote]I too am having the same issues with selecting profiles and not working, I always have to go in a manually create a group or extended desktop. I ended up just keeping the eyefinity group on at all times and using ATI HydraVision Hydragrid. With Hydragrid I'm able to use the monitors basically like an extended desktop.The only problem is you have to right click on your window and attach it to grid when you open a new window this way it doesn't stretch all three monitors. It's not perfect but a nice workaround. This also allows you to use 5760x1200 wallpaper correctly. I would like to see ATI expand on Hydravision altogether in how it works with a 3x1 group.

Where is that located @ can you explain how to set that up. I just had to mess around and cut and edit a wallpaper to get it to work with the center monitor as the main. So far it is working correctly. But when I'm not in Eyefinity I get jumpy displays both displays that are hooked up to DVI. Like the bottom half of screens are tearing lines I think that is what tearing is. This only happens when I open a program. Or move something on the monitor. I wish in Eyefinity there were more option as to what monitor you want to be your main. I will try to locate that Hydragrid thing. I would rather have my monitor on the left in eyefinity and no jumping displays as long as I can open stuff maximized in each display. This is really irritating.

Here is the download for hydravision: http://game.amd.com/us-en/drivers_catalyst.aspx?p=win7/windows-7-64bit (bottom of page)

If you go into CCC it will be just to the right of the graphics tab.

So whats that mean. I am used to Nvidia and they release drivers often it does not seem like ATI cares to due this so a couple of driver releases time that could mean 6 months a year.

AMD is the only company (AFAIK) that schedules driver releases every month (You can tell by the Catalyst release revision - Catalyst 9.11, for instance, equates to the November 2009 release). So when I say a couple of driver releases then I mean early next year.

Why don't they just fix the problem it is obviously a problem right.

We did, thats what I'm saying. Due to release, qualification and WHQL cycles you will see the fix in a couple of months time.

Does ATI not test anything when they update a driver to me it does not seem like it.

Yes, we test lots - as I just said, one of the reasons you will not see the fix for a couple of months is becuase the driver will go through a qualification cycle where lots of things are tested before being packaged for release. Can absolutely every single facet be tested? No, that would be impossible.

This is my first exp with ATI used to always use Nvidia I went ATI for Eyefinity but now it doesn't even seem like they are really working or fully supporting it. Whats the deal. Why should I have to wait for several driver releases to get something working that should work out of the box?

As mentioned, this was a bug that has been fixed and fixed as soon as we were aware of it and couple reproduce it; we care very much about Eyefinty, which is ont of the reasons why this particular issue was addressed as soon as it can be.

[quote]So whats that mean. I am used to Nvidia and they release drivers often it does not seem like ATI cares to due this so a couple of driver releases time that could mean 6 months a year.

AMD is the only company (AFAIK) that schedules driver releases every month (You can tell by the Catalyst release revision - Catalyst 9.11, for instance, equates to the November 2009 release). So when I say a couple of driver releases then I mean early next year.

Why don't they just fix the problem it is obviously a problem right.

We did, thats what I'm saying. Due to release, qualification and WHQL cycles you will see the fix in a couple of months time.

Does ATI not test anything when they update a driver to me it does not seem like it.

Yes, we test lots - as I just said, one of the reasons you will not see the fix for a couple of months is becuase the driver will go through a qualification cycle where lots of things are tested before being packaged for release. Can absolutely every single facet be tested? No, that would be impossible.

This is my first exp with ATI used to always use Nvidia I went ATI for Eyefinity but now it doesn't even seem like they are really working or fully supporting it. Whats the deal. Why should I have to wait for several driver releases to get something working that should work out of the box?

As mentioned, this was a bug that has been fixed and fixed as soon as we were aware of it and couple reproduce it; we care very much about Eyefinty, which is ont of the reasons why this particular issue was addressed as soon as it can be.


Yea I just don't understand how this was not found earlier and included in the driver we are all now using. How long have you guys been working on Eyefinity not to notice this problem. Then all the problems with the Active DP to DVI adapters that many people are having. Is there a beta driver then for the month of December since it is now the 9th of December.

[quote][quote]So whats that mean. I am used to Nvidia and they release drivers often it does not seem like ATI cares to due this so a couple of driver releases time that could mean 6 months a year.

AMD is the only company (AFAIK) that schedules driver releases every month (You can tell by the Catalyst release revision - Catalyst 9.11, for instance, equates to the November 2009 release). So when I say a couple of driver releases then I mean early next year.

Why don't they just fix the problem it is obviously a problem right.

We did, thats what I'm saying. Due to release, qualification and WHQL cycles you will see the fix in a couple of months time.

Does ATI not test anything when they update a driver to me it does not seem like it.

Yes, we test lots - as I just said, one of the reasons you will not see the fix for a couple of months is becuase the driver will go through a qualification cycle where lots of things are tested before being packaged for release. Can absolutely every single facet be tested? No, that would be impossible.

This is my first exp with ATI used to always use Nvidia I went ATI for Eyefinity but now it doesn't even seem like they are really working or fully supporting it. Whats the deal. Why should I have to wait for several driver releases to get something working that should work out of the box?

As mentioned, this was a bug that has been fixed and fixed as soon as we were aware of it and couple reproduce it; we care very much about Eyefinty, which is ont of the reasons why this particular issue was addressed as soon as it can be.


Yea I just don't understand how this was not found earlier and included in the driver we are all now using. How long have you guys been working on Eyefinity not to notice this problem. Then all the problems with the Active DP to DVI adapters that many people are having. Is there a beta driver then for the month of December since it is now the 9th of December.

My guess is that in their testing they have focused exclusively in the Eyefinity mode (grouping), the issue here is switching back and forth between groups and single mode, still it would be nice if it worked right away.

They have fixed a lot through drivers though, i have had this card since it was released and there have been lots of improvements, for instance, i could not use my fourth monitor in conjunction with an Eyefinity group and it was quickly addressed in a subsequent release.

Have faith, they will eventually fix everything, it just takes time, you might not be familiar with the software development life cycle, fixing the problem is not what takes most of the time, there is lots of iteration testing, certifications, etc before they can release.

Triplehead2Go wasnt error free on day of release either, these are new technologies and they still require lots of work, this is just one example.

Cheers

I actually do know about SDLC I will have my Bachelors in Computer Science in 6 months. And yea they must have focused all there testing in Eyefinity grouping mode. So who ever created the Test Plan must not have done a very good job and didn't think outside the box. Or there were no Test Cases to test this feature.

The Hotkey feature is existing capability however Eyfinity is doing something a little different and the two features were not imediately compatible.

In fact the dev's did check this during bringup and did make changes to make it work, however something must have been introduced later in the cycle to create the issue.

The Hotkey feature is existing capability however Eyfinity is doing something a little different and the two features were not imediately compatible.

In fact the dev's did check this during bringup and did make changes to make it work, however something must have been introduced later in the cycle to create the issue.

Ok so they must have added something or tweaked something that made this bug. And they must not have done any regression testing after they resolved any bugs or made any other tweaks then.

So I take it this did not get fixed in 9.12 or did it. My gf is taking a final and I have not had a chance to install 9.12 yet I am on my HTPC right now.