Hi, I'm using DisplayFusion on a 5120x1440 display to divide the physical monitor up into 3 virtual monitors.

Whenever I start the Game Forza Horizon 5, no matter what compatibility options I set for this game, DisplayFusion always forces it over onto the right most virtual monitor, instead of letting it run full screen. I can only get the game to run full screen if I quit DisplayFusion entirely.

I've tried adding the game by dragging the target over the window and also adding it from the list but it still seems to interfere with it.

I'm on Windows 11 21H2 DisplayFusion 10.0 Beta 6

File attached as requested.

Hi again,

Believe I have solved this. DisplayFusion was not detecting the path correctly for the game when I dragged the little target over to the window.

I had to enter it in the compatibility settings as C:\WINDOWS\system32\Volume{538a6a1f-4dc8-6248-5b5f-13c49b28a56a}\ForzaHorizon5.exe

If anyone has this problem, enable logging, start the game, then exit it and search for "ForzaHorizon5.exe" in the log file, you should see the path to the game on your system. You can then set compatibility options to disable DisplayFusion with the game.

Course if you buy the game on Steam it's easy to find just in your Steam library folder. Good old Windows App store making things needlessly complicated.

Seems I spoke too soon, the bug has returned and DisplayFusion is forcing the game over onto the third virtual monitor again. I tried adding *ForzaHorizon5.exe as the app name but it didn't work.

I also have this issue, and I have independently tried all of the suggestions listed here before finding this thread.

If required, I can provide any debugging logs required.

I also noticed the discrepancy on the name of the application via the "drag the target method". It has a really weird path when you do that:



When you scroll down the application list to "Windows Universal Applications", you get this:


Note the version number there -- that will change with every patch of the game.

I can also confirm that Wildcards do not work at all:
does nothing to help this issue.



I believe your momentary success here was because you may not have waited long enough for DisplayFusion to "reinitialize" after the configuration changes before launching the game, and it just "snuck through" while DF was setting itself up again.

Sorry it took so long to get back to this.
I found a workaround that prevents this behavior (maybe it's actually a different bug that prevents hooks from working, but that's for you to determine), I'll detail the steps later in this post.
As a result, I am attaching two debug logs.

The first illustrates the issue as originally noted, and contains the following events:

• Start FH5 by clicking the desktop icon.
• FH5 starts by showing a medium-sized loading screen in the center of the main monitor (2.2)
• Loading screen finishes, then a very small splash graphic appears in the center split of the main monitor (2.2)
• At 12:26:07 the full-screen game comes up, restricted to the leftmost split of the main monitor (2.1) (this is the bug)
• I switch back to DF Settings and export the log (without quitting the game)

The second debug log details what happens in the workaround, and contains the following events:

• Start FH5 by clicking the desktop icon.
• FH5 starts by showing a medium-sized loading screen in the center of the main monitor (2.2)
• I click the Time & Date in the Windows Taskbar (on 2.2) and the Time & Calendar popup appears. I leave it in the foreground. This is what constitutes "the workaround".
• Loading screen finishes, then a very small splash graphic appears in the center split of the main monitor (2.2); Time & Calendar continues to be the focused window
• At 12:27:44(ish) the full-screen game comes up, properly spanning all three montiors of the main display (2.1, 2.2, 2.3)
• I focus the game (closing the Time & Calendar popup)
• I quit the game
• I switch back to DF Settings and export the log

Sounds like just quitting displayfusion is a better workaround!

This makes no difference.

It makes no difference, respectfully the issue isn't that the compatibility options don't work, it's that DisplayFusion is unable to detect when this game is running.

I can confirm that the latest beta does, indeed, fix this issue.

Thank you so much!