Hi Steven,

Strange, I tested it out on my end and it seemed to work fine. Could you send me a copy of your troubleshooting info? Here are the steps:

• Open the Settings > Troubleshooting tab
• Click the "Export Info to File" button
• Reply with the file attached

Thanks!

Aug 23, 2021  • #2

Hi there,
Thanks for the reply. I have attached the troubleshooting info below, I also attached a video of me running the script with a hotkey. Thanks.

• Attachment [protected]: DisplayFusionDebugInfo.zip [90,219 bytes]

• Attachment [protected]: record.mp4 [617,279 bytes]

Aug 23, 2021  • #3

Hi Steven,

Thanks for sending that over. If you create a new script that just has the maximize function in it, is there still a delay?

Thanks!

Aug 24, 2021  • #4

Nope, using the built in "move window to current monitor and maximise" function works fine.

Aug 24, 2021  • #5

Hi Steven,

Could you send me over a debug log? Here are the steps:

• On the DisplayFusion Settings > Troubleshooting tab, change the Logging drop-down to "L1: Log Minimal" and click Apply
• Reproduce the issue and note the time so we'll know where to check in the log file
• Click the "Export Info to File" button on the Settings > Troubleshooting tab
• Reply with the file attached
• Disable debug logging after sending the log

Thanks!

Aug 24, 2021  • #6

Hi, here's the log file, the time would be 2021/08/25 03:41, although looking at the log file myself, there seem to be many instances of

FAIL:L1##_##displayfusionservice.exe:18416##_##BFProcessHelpers.Static:GetProcessMainFileNameOldMethodNOCACHE:69

, with the pid pointing to either memory compression or registry. Not sure how they're related to my issue but hope the info would help.
Thanks!

• Attachment [protected]: DisplayFusionDebugInfo.zip [177,504 bytes]

• Attachment [protected]: Screenshot_1.png [10,948 bytes]

Aug 24, 2021 (modified Aug 24, 2021)  • #7

Hi Steven,

It doesn't look like the file were looking for got attached, it should be called "DisplayFusion.log". Could you try running through those steps again?

Thanks!

Aug 25, 2021  • #8

Hmm this is weird, when I click export info to file, the log file doesn't get exported, this is pulled from AppData\Local\DisplayFusion. The time would be 2021/08/25 22:17:25. Thanks.

• Attachment [protected]: DisplayFusion.log [107,325 bytes]

Aug 25, 2021  • #9

Hi Steven,

Sorry for the delay. Does the issue also happen with any other applications outside of your browser?

Thanks!

11 days ago  • #10

Hi, I have tried opening other browsers (Brave, Edge, IE) using the same command and the same behaviour was exhibited.

11 days ago  • #11

Hi Steven,

Interesting, and it doesn't matter which monitor it opens on, as long as it's opening within a monitor split, the issue will happen?

Thanks!

10 days ago  • #12

Hi Owen,
That is correct, on my main monitor without a split, there is minimal delay and the time it takes to complete the script is consistent. But on my other two monitors with splits, there will be a delay and the time for the window to be maximised varies. I'm using monitors with different resolutions, could that be what's causing the problem?
Thanks.

10 days ago  • #13

Hi Steven,

If you remove the splits on one of your side monitors and then try it, does the issue persist? I don't think it's an issue with mixed resolutions, but this should point us in the right direction

Thanks!

9 days ago  • #14

Hi Owen,
I seem to have found the potential issue. Removing the splits didn't seem to reduce the latency, so I tried changing the resolution of the monitors. For context I'm using 3 monitors with 1080p, 1440p and 4k respectively, with the 1440p and 4k running at their native resolution and the 1080p monitor upscaled to 2880x1620. The 4k and upscaled monitor just so happened to be the ones with splits, hence I assumed that the splits might be causing the problem.
I removed the upscaling and changed the resolution of the 4k monitor down to 1080p, and the delay when executing the script is gone. I have also tried with upscaling disabled and the 4k monitor running native resolution, there is minimal delay on the 1080p monitor and the usual longer delay on the 4k monitor. It seems that there will be a longer delay with increased resolution, the delay of running the script is slightly shorter on the 1080p monitor compared to the 1440p monitor. I have tried this with splits enabled and disabled (splits might be causing a very slight delay but I can't really tell), and with the different browsers mentioned in the earlier message.

9 days ago  • #15