Translucent Fences show incorrect background on multi-monitor systems

if monitors are arranged [2][1] positions

from Stardock Forums

If monitors are physically arranged [2][1] instead of [1][2], a faded-out translucent fence, when moused over, will show the alpha blended portion of the other monitor's wallpaper behind the icons.  This bug has been verified on Windows 7 and 10. The only workarounds are moving the monitors into a [1][2] orientation, or having identical wallpapers and resolutions on each monitor. 

fences
7,525 views 6 replies
Reply #1 from Stardock Forums Top

Hello,

Sorry to hear you are having issues. Not happening on my setup. I have [2][1] monitor setup, with different wallpaper on each monitor. I have no such issue as you can see from my S/short below.

Would like to know more on your system.

1) Windows version. Please use Winver.exe for full window version numbers.

2) Fences version.

3) Monitor resolution on both. And scaling applied to each monitor.

Thanks

 

 

Basj,

Stardock Community Assistant.

Reply #2 from Stardock Forums Top

The issue only occurs on mouse-over, when bringing the fence into focus. Note how the in-focus fence shows the bluff with the gazebo on it.  The faded out image is also incorrect, but too transparent to notice. But the effect is obvious when moused over.  This particular instance is on Windows 7, using DisplayFusion to span a large background image - but I have seen the same effect at home on Windows 10 Pro using multiple wallpapers without DisplayFusion.

Start11 - Customize the Start Menu and Taskbar in Windows 10/11.
Reply #4 from Stardock Forums Top

Hello can you try turn off the Translucent Fence background and see if it help.

Thank you,

 

Basj,

Stardock Community Assistant

Reply #5 from Stardock Forums Top

That appears to eliminate the issue.  I attempted to re-verify the issue on my Windows 10 pcs, and could not recreate it, so it may be some incompatibility with DisplayFusion.  The translucent fence feature is clearly labeled as Win 10 only, so I guess now we know why... It was most likely enabled by default though, as I have no recollection of ever changing that setting. 

Reply #6 from Stardock Forums Top

Great, glad you solved it.

Thank you,

 

Basj,

Stardock Community Assistant