sEKx
12 discussion posts
Since DisplayFusion 12, I’ve been having the problem that triggers no longer work correctly.
Normally, Discord should start at a specific position that I defined using a trigger. Discord is therefore set to launch on startup. However, this no longer happens, and I have to close Discord and restart it once DisplayFusion has finally started.
Since version 12, DisplayFusion also takes noticeably longer to start.
Can you confirm rolling back to v11 moves the Discord window on Windows boot?
sEKx
12 discussion posts
Won’t I lose all my settings if I uninstall version 12 and install version 11?
If you run the installer directly overtop of your current install, it will keep your settings.
sEKx
12 discussion posts
I have now installed version 11.1.1, and the problems are gone. So for me, the issue seems to be with the latest version. I guess that means waiting for now.
Can you send me a screenshot of the trigger you created?
sEKx
12 discussion posts
Sure, no problem. =)
• Attachment [protected]: DisplayFusion Trigger.png [69,744 bytes]
Thanks for sending that over. Discord opens a splash window first which might be causing some issues as we've adjusted the way triggers are processed in v12. Two things to try here:
1. Set the "Delay before checking match condition" in your move trigger to something like 5000ms. If that fixes it, you can lower the value until it breaks, and then set it slightly higher
2. Try using the "Window Text" match condition, so it looks for the specific window you're trying to move, rather than the exe. If you use the "Window Text" condition, you'll need the "Delay before checking match condition" value set as well.
sEKx
12 discussion posts
I’ve now tested it with version 12.0.1 and 12.0.2 Beta 7, and it doesn’t work. Then I went back to version 11.1.1, and it works immediately.
• Attachment [protected]: DisplayFusion Test.png [78,360 bytes]
sEKx
12 discussion posts
With version 11.1.1, Discord started faster than DisplayFusion. With this version, however, there are no issues, so the program’s startup shouldn’t be a problem then, right?
If Discord starts before DisplayFusion does, it's impossible for the DisplayFusion Trigger to detect the Discord window being created so the trigger wouldn't fire. Is Discord.exe starting before DisplayFusion.exe with 12.0.2 Beta 7?
sEKx
12 discussion posts
I tested the behavior with DisplayFusion versions 11.1.1 and 12.0.2 Beta 7.
In both versions, Discord appears first in the Windows Task Manager under Details as an .exe process, followed by DisplayFusion.
Expected Behavior:
The trigger should position the Discord window according to the configured rules, as it does in version 11.1.1.
Actual Behavior:
With 12.0.2 Beta 7, the trigger does not behave correctly.
The Discord window is initially placed at the correct position. However, as soon as the secondary taskbar is initialized, the Discord window is moved to a different position that does not match the trigger configuration.
Regression:
This issue does not occur in 11.1.1, where the trigger works reliably and as expected.
sEKx
12 discussion posts
Sure, no problem. =)
• Attachment [protected]: DisplayFusionDebugInfo.zip [337,928 bytes]
Could you send me a backup of your DisplayFusion Settings? (Settings > General > Export)
sEKx
12 discussion posts
Sure =)
• Attachment [protected]: DisplayFusion Backup (2026-01-23 @ 23-17, 11.1.1.0, ANDY, SettingsWindow).reg [197,336 bytes]
Thanks for sending that over! It seems to work ok for me in testing here, I didn't realize you had a Trigger setup for launching Discord from within DisplayFusion. Can you confirm that the "Open Discord on Startup" option in Discord Settings > Windows Settings is set to disabled? That's the only thing that I can think of here, is that Discord is starting itself up before DisplayFusion launches, instead of being launched by the DisplayFusion Trigger.
sEKx
12 discussion posts
Discord launches automatically on Windows startup, just as I intended and configured within the Discord settings. These issues don't occur with DisplayFusion 11.1.1, they only started appearing with the more recent versions.
sEKx
12 discussion posts
Okay, I stand corrected. Discord itself is set so it doesn't start automatically with Windows. It's actually being launched via DisplayFusion.
sEKx
12 discussion posts
Okay, I’m confused. I don’t know why, but suddenly it’s working with version 12.0.1. I didn’t change anything,I didn't adjust the delay or check the "Windows text" box. Discord wasn't set to autostart in Windows or within the app itself. I can't explain it, maybe it was just a Discord or Windows bug. I appreciate all the time and effort you put into helping me. =)
