Title

Message

Confirm

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

Triggers and Compatibility not functioning

Avatar from Gravatar.com
BreakIt
3 discussion posts
I'm trying to setup DisplayFusion to move an old game that by default opens on my primary monitor, to my second screen.

I've created a Trigger that uses a Window Created event and Process Filename match condition.
I've also toyed around with using a Process Created event and Windows Text and/or Windows Class match conditions.

The trigger only works sometimes. And never more than once. (ie. If I close the game and reopen it, the trigger wont work again.)

The Frequency is set to Always but I've always toyed with all of those settings with no luck.

I've also setup a Compatibility setting for the game that disables the DF Taskbar while the application is running and Forces DG to treat it as a full screen application.
The game runs in maximised Windowed mode. Without this the taskbar sits on top of the game.

The compatibility settings only function when the trigger randomly works.

How can I get the trigger and the compatibility settings to work correctly every time the game is run?
Oct 28, 2018  • #1
Keith Lammers (BFS)'s profile on WallpaperFusion.com
That's really strange. If you set the Trigger event to "Window Focused," does that make any difference? Also maybe try setting the "delay before checking match conditions" to 250.
Oct 30, 2018  • #2
Avatar from Gravatar.com
BreakIt
3 discussion posts
I've come up with a bit of a work around that seems to be doing the job.

I've changed the trigger to use Window Text and Window Class as these seem to consistently catch the program.
I've also changed the trigger to use Window Focused like you suggested.

I've also created an AHK script that launches a batch file that I've converted to a .exe
I had to go with AHK instead of creating a Custom Function from within Triggers because Window Created and Process Created still doesn't work.

DisplayFusion detects the converted batch file and applies the Compatibility settings that I want applied when the game is opened.

The AHK then kills the converted batch file when the game is closed.

In my testing I noticed that most of the time the game has no Path, Version, Build Time, Description etc. in my task manager (Process Explorer). Which probably has something to do with why DisplayFusion is failing to detect it.

This is the AHK script, just in case anyone needs to use this workaround in the future.
It uses a utility called PsKill which you can find on Microsoft's Windows Sysinternals site.

Code



The batch file is literally just pause. The .bat to .exe converter that I used has an option to allow the batch file window to go invisible and run in the background.
Nov 6, 2018  • #3
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Thanks for posting that workaround! What program do you use for converting the batch files to executables?
Nov 6, 2018  • #4
Avatar from Gravatar.com
BreakIt
3 discussion posts
Quote:
Thanks for posting that workaround! What program do you use for converting the batch files to executables?


I used Advanced BAT to EXE Converter.
I haven't looked to see what else is out there, it was just one of the first results from a Google search.
Nov 7, 2018  • #5
Keith Lammers (BFS)'s profile on WallpaperFusion.com
No worries, thanks!
Nov 8, 2018  • #6
Was this helpful?  Login to Vote  Login to Vote
<< DiscussionsReply