Graphics card: ATI Radeon HD 58xx with latest drivers from AMD for Windows 7, 64-bit

The card has 3 HDMI outputs, but I only have monitors connected to 2 of them

When hitting the "next monitor" titlebar button for a window on monitor 2, the window to moves to "monitor 3" and becomes invisible/difficult to access.

I've tried "Settings - Advanced Settings - General: Monitor Order = "1, 2", but that did not have any effect

Thanks in advance!

Forgot to mention: using DisplayFusion Pro v3.3.1

Hi Keith!

When I bring up the Windows Display settings, it shows 2 displays (2 blue boxes, numbered "1" and "2").

If I click the "Detect" button, an additional gray box appears with the text "Another display not detected" inside.

If I select the grayed out display, the "Mutiple Displays" drop-down list defaults to "No display detected" with "Try to connect anyway on: VGA" twice below it. Don't see an option to "Disconnect the Display".

I've attached a screen shot (after pressing the "Detect" button), which will hopefully make things clearer.

Happens to me too. A radeon 6970. But that is not a Displayfusion issue. That's a displaydriver issue. I have a tv and 2 monitors. When the tv is switched off the card still detects the hdmi signal. If i switch the tv on it's the luck of the draw which screen becomes primary. Switching it off and sometimes i have to hunt for my opened windows. The button shows on real windows taskbar but clicking it makes the window open on the tv, which is switched off.

Usually opening the display Catalyst control applet resets everything. So i wrote a tiny app that does a video reset. Works most of the time.

Well done! And a bit of a mystery. I do have Air Display installed, but it's not running. I'll try uninstalling it for now since I haven't been using it.

Many thanks!

Confirming: removing the Air Display Support driver fixed the phantom third monitor problem with DisplayFusion AND some weird behavior I was having with AMD Vision Control Center (which used to be the Catalyst stuff IIRC).

Thanks again!

It's the same issue as with me then. The displaydriver detects the virtual screen. Attached or not. I use EnumDisplayDevices to get the current state of the display but admittedly that isn't very accurate.

Nope, it's either just greyed out or it doesn't show at all but still is floating in the system. Only when i pull the plug on the tv (Toshiba Regza, good standard one) does it completely disappear (no more on/off buttons, pisses off my wife no end ).

When the tv is in standby it's a 50/50 chance that the displaydriver will recognize it's altered state. Sometimes it just doesn't do anything, the tv was already there in it's opinion and i have to force a redetect, or it'll recognize it and changes state.

I've tried myself for my own home automation system to get it to work right but the only way i could get it to work using standard API calls was with a monitor resolution reset with null values.

That's not an option for DF since all monitors recalibrate.

Maybe just live with it is the best option.

Good call. I never need the taskbar on my TV, i use an IR remote.

ops: