Hello,
Sorry to hear you are having issues. You would be a good candidate for users that we are looking to collect some data from in Fences 4 in relation to multi-monitor usage. If you have a chance, please review https://forums.stardock.com/516971/fences-multi-monitor-logging 

Thank you,

Basj,
Stardock Community Assistant

Having used Fences for years, I was a version 2 user until just a few months back, and having upgraded to version 4 in hopes it would resolve the issue I had in version 2, I find that 'not having an idea where the icons will be today' is totally unacceptable. I stand amazed that as long as this has been a problem that no solution has been offered to the users to resolve the 'mystery'.

I don't claim to be a wizard in programming, but have spent many years teaching logic and program design.  It seems to me that if the Windows Monitor Identification is not a constant, then quit trying to use it within the software.  If I am not mistaken, the monitor 'name' is always available. So rather than trying to use the display ID, use the Display Name, like in my case, my ID's are 2436, 6 Series 50, and M556-H4.   I would suggest that each Fence be able to be 'configured' or 'assigned' to a display name (as they ARE constants), a user setting within each fence.  A user default set for new fences created. So that when the system reboots or is recovered from sleep, the Fences then places the Fence on the display assigned within each fence.  I can't imagine that this would be that had to design and/or code.

PLEASE correct this flaw in the software.  I believe StarDock has had sufficient time to correct this issue. As this logic error was even prevalent in Version2 as well.

So I first came to this thread regarding this issue as per the topic title on:

Reply #23 November 16, 2022 12:37:23

I was able to resolve the issue at one point, which involved some variation of:

a)  which monitor is plugged into which port

which color profile is assigned to which monitor (though I'm not clear on this at this point in time now as to which/what should be set to which)

I can provide the following info.

1) when I got it to work I had 3x monitors across 2 video cards (different),  2x 27" (I think) and 1x 24",  2 as HDMI, and 1 as DVI

-so it would seem it can handle some diverse connections both monitor specs, connection method, and cards/ports

I have recently removed the 24" (which was far right) and replaced it with a 32" UHD (center)  with the 27"'s on either side.

-ALL hell has broken out, every restart, even the occasional wake from monitor blank/power-save screen causes icons and/or fences to move.

- It is a serious PITA!

I suspect I will have to go through the gambit of the monitor port connection shuffle, and then try to  figure out the color profile stuff again with the new setup.

This thread was opened:   April 30, 2022 12:15:31 PM

To date, it has been on going for 18 months ++

As much as it has been asserted: 

Deciphering corporate speak, this could mean anything.  Investigating is not resolving the issue.

Cold cases sit open (still unresolved, open for investigation) for decades, and sometimes they never have even a single person do anything with them.

I don't really want to come across as a flaming ranting user, but if in 18 months (who knows maybe more) your developers can't seem to figure out how to write code, to access the primary monitor location in tandem with the additional monitor locations (left/right) either through windows environment settings, or Nvidia's Control Panel settings, or both, it really comes across as if either their not very interested in eating up company resources resolving it, or just are not qualified/skilled enough to resolve it.  I'm sure there are a few advanced powershell commands that could retrieve the windows environment variables for multiple monitor placement/configuration.  Once you have that they should be able to encode icon/fence placement relative those.  I couldn't do it myself, but know enough to have an idea where to look.  

What exactly does "Lifecycle" mean in conjunction with your manager title?  Does this mean that   Fences 3/4 are at the end of their lifecycle? I wouldn't expect a company to continue to work and resolve issues with a product that is at the end of it's lifecycle. I would expect them to advise that upfront however, and not just try to maintain market share, customer loyalty, and the hopes that more sales can be garnered from customers with the next iteration of as they might believe the issues will be resolved with it.

Sorry, but understanding frustration and producing results are two different things.

We need results, not understanding.  We need results, not another version we have to pay to upgrade/purchase.

If it's a case that the financial benefits of pumping resources into fixing the issue does not justify the expenditures, just say so.

Personally, I suspect that the base coding is probably fine. As others have discovered over the last year and a half, it has more to do with monitor port, connection order, color profile, and the order in which all of these are done, with/without reboots after each step etc.

Spending company resources to create a defined, concrete step by step guide ie:

-plug 1 monitor into port on primary vid card that is closest to motherboard, set/check color profile. shutdown.

-plug in second monitor into next port closest to motherboard (same vid card if you have more than one) this monitor should be arranged on the left of the primary (middle). boot

-Setup windows/nvidia multiple display

.... etc.

..etc.

Would be a better investment of company resources imho.

I'm not ready to F#$% around with all this now, I just tolerate it at this point. I have stuff that can take 72+ hours of non-stop processing by my PC. trying to find time to mess with this, is just a pita as  I said before.

Just as a test has you trial Fences 5 and see if the issue resolved with it?

Thank you,

Basj,
Stardock Community Assistant

Awesome, appreciate you reporting it here.

Thank you,

Basj,
Stardock Community Assistant

I went to https://www.stardock.com/products/fences/#purchase and clicked the little blue "upgrade" text. For me, it is a $2 savings off the annual renewal. There is also a $29 lifetime offer.

From here: https://forums.stardock.com/524050

Is there an ‘Upgrade’ option for a permanent license?

At this time, ‘Upgrade’ pricing is only available for subscription licenses and not for permanent licenses of Fences 5. However, during the Release Preview, permanent licenses are discounted for all customers.

Thank you,

Basj,
Stardock Community Assistant

We certainly appreciate the patronage and feedback but 'do better' how exactly?  Are you saying that your current and future SD purchasing decisions have been reduced to a single issue with one of the many products we produce?

Furthermore, what is 'so bad' now that was not prior - where have we let you down over time? Or, is it the case that you will 'come back' if we find a way to solve this complex issue that only some have?

Again, thanks for the feedback, Greybird.

Sean Drohan
Stardock Product Lifecycle Manager

We have always been working to improve the reliability of Fences placement on the Desktop.  What has made this challenging over the years are all the variables that are involved:

• Quantity of monitors

• Connection types 

• DPI \ Scale \ Resolution

• Waking from sleep \ hibernate states

• The evolution of Windows itself and how it manages items on the desktop

That said, we have a Fences 5 Alpha build in the early stages that we believe addresses most scenarios and we are looking for users who are willing to test this version of our updated engine.

The build

https://cdn.stardock.us/support/uploads/Fences5_5.5.0.2-j46-Setup.exe

Post-install \ reboot (<-important)

Backups -> Store my layout on a per-monitor-configuration basis

Reporting an issue

Please include the following for anything found:

• Exact Windows version \ build (winver.exe)

• Detailed steps to recreate the issue seen

• Screenshots and videos are very helpful.  Videos can be uploaded to a cloud drive service (GoogleDrive, DropBox, OneDrive, YouTube), with a shared link included in your post.  Images can be copied and pasted directly into a post.

• If there are specific apps that the app does not work (well) with, please note what apps and their exact versions.  If any app is not common, a link to a trial version would be appreciated.

We are very much looking forward to your feedback on this.

Sean Drohan
Stardock Product Lifecycle Manager

This is an Alpha build of Fences 5 that has a new way to handle elements on the desktop in multi-monitor environments.  If all goes well, it will be included in a future general release of Fences 5. 

Excellent. 

That would be a poor client experience if icons became unavailable on the desktop and the client was unaware of why or how to get them back. 

Thank you very much for the feedback, gnorf71.

Sean Drohan
Stardock Product Lifecycle Manager

Yes, its better than them not existing at all and the client believing that they are gone or that Fences deleted them.

Sean Drohan
Stardock Product Lifecycle Manager

I'm using Fences 5.51, and this just happened to me too.  I re-booted and Fences showed up on my secondary display, instead of primary. I have to manually move the fences.  Can this be fixed?  

Please see and participate here

https://forums.stardock.com/527284/fences-55-beta-feedback-thread

When doing so, please detail:

• That you have enabled 'Store my layouts on a per-monitor-configuration basis' in Fences 5
  
• Exact Windows version (winver.exe)
• Exact Fences.exe version
  
• Monitor count
• The exact connection type for each monitor
• If any adaptors are used to bridge monitors (a docking station for example or USB-C to HDMI connector).
• Exact steps to reliably and constantly reproduce the issue.  If it is not reliably and consistently reproducible, we need a percentage of times you use the PC where you would likely see it happen.  For example '
  
  Perhaps 1 out of 100 reboots (1% of them), Fences are messed up post reboot'
  
  
• And the results of a snapshot restore - does it work to restore your Fences \ icons properly when used.

Sean Drohan
Stardock Product Lifecycle Manager