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:
That is just not the case. It is being actively investigated.
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.
We understand that it is a frustrating issue for the clients that do see it and, again, we are working on it.
Stardock Product Lifecycle Manager
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
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.