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
Dr W - Fences Support
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
Hi Tom sorry for the lack of clarity there. Sounds good and looking forward to seeing the log!
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
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!
😂😂😂 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
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
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
😫 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
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.
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"?
@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
Thank you!
Yes you have a much different issue goingon @comtronic-gmbh. Please ensure "Advanced Logging" is enabled, which would better log the issue, and upload a new log per instructions in the earlier reply https://forums.stardock.com/533077/get;3957017 Thanks and hope to get this figured out promptly.
@Fencesitting glad to hear it! w00t! Yes I'm thinking issue solved. Hopefully no more problems from here. @comtronic-gmbh sounds good, yes looking forward to receiving that log. Cheers
Ah, thanks for uploading the report. So, would it be possible to head to the Layouts tab, expand the "Backups" area and (1) Save a backup when things seem to be acting fine (2) Save a backup when things are broken? And the please resubmit. I seem to see a handful of backups where it's working properly but not seeing the broken scenario where things are scrunched up (please point out if I'm missing it), so that would be very helpful to have that. Ideally, upload
Hi danielhurtubise this is strange! Could you do a few things to help? 1) Please elaborate more on what it should look like vs broken? What do you need to do to manually fix each time? Screenshots of it broken/fixed? 2) Can you take a couple of snapshots/backups... one with it "good" and another "broken"? 3) Last, can you upload the report to us? You can access via "Troubleshooting" and "Create error report" in About. <img src="https://cdn.stardock.us/foru
Hi sanmarcha, this was an issue with one earlier version. Please update to the latest version for the fix. You might also be able to resolve the issue with your current copy by unchecking & re-checking the option "Move titlebar to the bottom" in the "More options" link in Personalization.
What we're seeing on our end is your system, for some reason, rapidly alternating between showing one monitor and two monitors. And it's getting stuck in a loop going back and forth and back and forth. Just a matter of getting to the bottom of it. With that "Advanced Logging" checkbox enabled in the Troubleshooting tab, give this patch an install. <a href="https://www.dropbox.com/scl/fi/1fmml3bs6isizbmccepad/UpdatePatcher_Debug_2025_01_13__0_46_54_pm.exe?rlkey=15pdjwibn5qs7p4cknw
Definitely seeing an anomaly here; confident we'll be able to get it resolved.
Hi comtronic-gmbh thank you for the logs. Ok, thanks for enabling the "Advanced Logging". Please send in another report when you can with that. Please note that you'll need to log off & on (or reboot) for the "Advanced Logging" to begin to take effect. Once you do, we'll start to get additional information. ===== Regarding the system being so messed up you have to Ctrl+Alt+Del to get back into system – it's unlikely Fences i
Well- that's not great. So, helpful would be the following: (1) Start using the Backup feature to save debug backups, so that when you send in your report, we have them. Take them of (A) Working states, and (B) Non-working states, immediately upon getting into them. You can do this from the Layouts tab <img src="https://cdn.stardock
Got it, thanks comtronic-gmbh. If you do end up with problems, please follow the same instructions above to take Backup snapshots "correct" and "incorrect", + enable Advanced Logging, reproduce the issue at least once and upload an error report. But hopefully the patch takes care of the problem. Is your issue likewise that all of your Fence groups and icons were on your secondary monitor? Thanks for any addl info.
Hi Fencesitting, thanks for the second report. That gave the info we needed 🙌 Complex issue, but I think we may have gotten to the bottom of it. Could you download/run the following patch? https://www.dropbox.com/scl/fi/jppbo74wvw0irhx3slxmg/UpdatePatcher_Debug_2025_01_09__10_29_25_pm.exe?rlkey=tgyzuuf18mn8d8pz
Understood. Could you please send in a new debug report Please enable advanced logging from the troubleshooting link menu in About. Reboot, then Use backups in the layouts pane to make a backup of the current layout. Continue using the program until the problem occurs. When the problem occurs, use the troubleshooting menu to create an error report, and it will guide you on how to upload it to us. Thank you.