Dr W - Fences Support

Dr W - Fences Support

Joined Last seen Member # 650776
2 Posts 745 Replies 794 Reputation

The details are good, keep em coming! This is the second time I've heard of this problem, so this is something we have to deal with even if it's not Fences' fault. Learning more about the problem is useful. This other user likewise solved by switching from their integrated to nvidia graphics card. https://forums.stardock.com/533077/get;3957644

19 Replies 13,655 Views

Question- when this is happening, do you see the AOC monitor turning on and off etc on repeat while the other monitors stay on, or kinda what's going on with that monitor? Sounds like the system itself is unresponsive, but yeah, what's happening with that monitor? Does it just stay on and keep the same imagery or does it still have an image even when your Resolution Monitor App was saying "monitor is gone". (Or does it never turn on at all.) Such a strange situation.

19 Replies 13,655 Views

Oh wow! Ha. Ok. One drive update at a time! Ha. Noted – so you too are seeing (independent from Fences) that that AOC monitor is coming and going. So, that confirms that. What is surprising is this is the second report I've gotten of this this week, but have otherwise never heard of this before. This makes me wonder if a Windows update made this occur. Because that type of disconnect/reconnect would absolutely trash the operating system, so, should be handled at the OS l

19 Replies 13,655 Views

Nope nothing else needed. If it reoccurs, apply patch and then wait for the next occurrence after that and that’ll give us extended info. Hopefully though nothing more ☑️ Curious btw — did this begin after any specific event? Windows update, Fences update, system config change, etc? Also – which specific Windows build number are you running? (using WinVer.exe)

33 Replies 20,848 Views

SO- it seems like this is the the one coming in and out. [4480|8|1920|1080|100|\\.\DISPLAY4|\\.\DISPLAY4\Monitor0|\\?\DISPLAY#AOC2752#4&36bf8516&0&UID4147#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|\Registry\Machine\System\CurrentControlSet\Control\Class\{4d36e96e-e325-11ce-bfc1-08002be10318}\0003]; It's 1920x1080 @ 100% DPI, to the right of the primary. Its ID is "AOC2752". so I'd say it's that AOC monitor. &

19 Replies 13,655 Views

@comtronic-gmbh, Added more debug data to try to dig into this further. This patch which will upgrade you to "5.88 (Revision 2)". (You may need to shift+rightclick desktop or open Settings to start Fences back up) https://www.dropbox.com/scl/fi/nrnroy36fmp33nvwsihga/UpdatePatcher_Debug_2025_01_19__10_06_54_pm.exe?rlkey=fil

33 Replies 20,848 Views

Hey Tom. Interesting things I am seeing in your report – thank you for sharing. Specifically: I'm seeing a WM_DISPLAYCHANGE message be sent repetitively (as in sometimes multiple times per second), and reporting back different results each time. It seems like one of the displays is coming in and out in and out, which would present a big problem for the system. I made a patch to help take a next st

19 Replies 13,655 Views

Hi sanmarcha, you'll want to use this option in the Layout panel. It will maintain different layouts when the monitors are plugged vs unplugged. I see you note "where the other portals don't exist" – so you cannot have a layout where individual groups don't exist in a different monitor config, but you can shrink them or dock them to the edge. When you restore to 3 monitors, that layout will be restored, and likewise when you return to 1 monitor, that layout will be restored

3 Replies 3,745 Views

lol great! Yes it sometimes needs a kick after the patch. Well cool yes submit a new report after the next occurrence, and then get after the experiments listed in post @ https://forums.stardock.com/533742/get;3957685 Beta was published today so if you see a beta update available don't download it, as as noted you're technically one revision ahead. #cuttingedge

23 Replies 15,058 Views

Hello each CleverFox, jeygez, A few diagnostics steps please if we could 1. Enable Advanced Debug Logging. You can find this option under the Troubleshooting link menu on the About tab. Reboot. (Or just log off and on) 2. Reproduce issue. 3. Right after reproducing issue, head back to Troubleshooting link and choose “Create Error Package”. It’ll walk you through uploading it to us. Thank you!

19 Replies 13,655 Views

😂😂😂 Patch is a revision ahead of what they’re prepping for beta — added a potential fix — so feel free to give it a shot. We’ve got a bunch of fixes we’re working to get to release so would love to have this be a part! Might fix the issue, or might just give richer detail in the Advanced Debugging log. If not fixed, with the advanced debug logging turned on just submit a new report when the issue occurs next + also try some of the

23 Replies 15,058 Views

Actually– since I'm not sure the beta will be coming out this week, here's a patcher to get you there. You may get some messages complaining about "mismatching version" when you open settings until your next full update, but feel free to ignore https://www.dropbox.com/scl/fi/et2evui75himq77b547r4/UpdatePatche

23 Replies 15,058 Views

To see this effect in live action PS! Try setting your icon size on desktop to "small". Then resize a fence down to smallest it can be. Then change icon size to "large". You'll see they all get larger. But, so long as you don't move/resize, if you change back to "small", it'll shrink again. That includes through reboots and screen resolution changes. So yeah my GUESS is that's what's going on here, and there's just some delay going on regarding Explorer properly updating the m

23 Replies 15,058 Views

😫 Ok. So– inconsistent. We have a new build coming out shortly that will nab a little more debug info in the Advanced Logging. ==== Here's sorta what I'm thinking: This seems to be happening to your single-width fence groups only. (Correct? Not correct?) Fences get sized based on two things. (1) the size you set them to, and (2) minimum size, based on the size of a single icon. This size can get messed with heavily based on DPI...es

23 Replies 15,058 Views

Yes something very strange is going on with your system, and yes it would absolutely lock up under those conditions. I have no idea what could possibly cause such a rapid and continuous "monitor detached / attached" cycle. Hopefully the nvidia upgrade helps. Less concerned about how Fences reacts as again I don't think it's at all involved, and invite you to disable (via bottom of the Welcome tab in UI) or uninstall to confirm for yourself.

33 Replies 20,848 Views

Hmmmm. So getting some hints from the debug data but not finding it yet. Question: your OP said that it goes BAD upon reboot, but other times, it seems to be fixed upon reboot? The way I'm seeing this I feel like I could most likely see this going bad if one of the monitors isn't powered on during boot... or if one of them goes to sleep then comes back etc. I'm most curious about: "if it's in a broken state, does just rebooting it often fix it"?

23 Replies 15,058 Views

@comtronic-gmbh, I'm going to continue looking, but this unfortunately seems to be a problem with your system and not with Fences. I'm noticing that we're receiving just a *flurry* of WM_DISPLAYCHANGE messages, which indicate a change in monitors attached to the system. They start and do not let up. And each time, it cycles between the monitor config signatures [0|0|3440|1440

33 Replies 20,848 Views