Save up to 50% in our Spring Sale!
Save up to 50% off any of our desktop apps in our Spring Sale, including DisplayFusion,
ClipboardFusion, FileSeek, iTunesFusion, LogFusion, TrayStatus, and VoiceBot!




Want to earn a free DisplayFusion Pro license? We're looking for DisplayFusion translators!
<< DiscussionsReply

[SOLVED] Issues with scripted functions on multiple graphics cards

Avatar from
4 discussion posts
So I've been using a few scripted functions to always move certain windows to certain lokations upon startup. Recently I installed a secondary graphics card and moved some monitors over to that. When I did this I noticed these functions behaved a bit odd. They still work but the window will be moved to monitor 2 before moving back to monitor 1. And this is even if the window already is at its destination location as per the function.

Example function:


Main GPU: AMD Radeon (TM) R9 Fury (Has monitor 1 connected)
Secondary GPU: GeForce GT 640 (Has monitor 2 and 3 connected)
Monitor arrangemend 2,1,3

Worth noting: 2nd GPU also has a TV connected but it is mostly not active.
And, no, this is not a Hybrid PhysX setup.
Mar 14, 2019 (modified Mar 22, 2019)  • #1
Jon Tackabury (BFS)'s profile on
Are the windows minimized or maximized by any chance? If a window needs to be restored to be moved they might get restored to their old location first, then moved. If that's not the case just let me know and we can investigate further. Thanks!
Mar 18, 2019  • #2
Avatar from
4 discussion posts
Just to clarify: This script only runs on the first instance of certain programs, in this case my web browser.
This happens regardless of where the window was closed, and it even happens if I close the window where the script will place it.
Maximized or not, it always jumps to the left monitor (monitor 2, which I assume is the first monitor on the GT 640) before jumping to its correct place.

This did not happen when I hade all monitors in the R9 Fury card.
It all started when I moved some monitors over to the GT 640 that I installed.

EDIT: I mean... In the end it does works, it's just an annoying little glitch.
Mar 19, 2019 (modified Mar 19, 2019)  • #3
Keith Lammers (BFS)'s profile on
Could you attach a debug log for this issue?

  • 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
Mar 20, 2019  • #4
Avatar from
4 discussion posts
Here's the debug info.
I replicated it a few times starting at around 15:53:53 and forward.
I closed Waterfox (Firefox clone) in its location and opened it again, the log will probably show this.
• Attachment [protected]: [42,530 bytes]
Mar 21, 2019  • #5
Keith Lammers (BFS)'s profile on
Thanks! So in this log the issue happened with Waterfox? It looks like the issue is that the Trigger rule has a "Move Window to Monitor 2" action in addition to your scripted function action. Can you try removing the "Move Window to Monitor 2" action from the rule?
Mar 22, 2019 (modified Mar 22, 2019)  • #6
Avatar from
4 discussion posts
Aaaargh! I feel like an idiot! I had completely forgot I had that rule...
I did check Window position profiles but since it was empty I figured this was a glitch of some sort. Turns out I had just forgot about the very first rule that I added before I added the script and didn't think twice about removing sice everyting worked fine at the time.

So I removed that rule and made some tests and now it doesn't jump to monitor 2, go figure! : O

Thanks for a wonderful software and great support!
Mar 22, 2019  • #7
Keith Lammers (BFS)'s profile on
No worries, glad I could help!
Mar 25, 2019  • #8
Was this helpful?  Login to Vote  Login to Vote
<< DiscussionsReply