[ISSUE] CX23 Fullscreen on launch bug - effecting Horizon Zero Dawn

[Rastafabisch]

Environment

• OS: 14.1.1
• Winery version: latest
• Master Wrapper version: latest
• Engine version: CX23.6.0_D3DMetal_1.1
• Hardware: M1 Pro MacBook Pro 16" -Game Name: Horizon Zero Dawn

Describe the bug After installation the game works fine, however its default "Borderless" setting results in a wired white frame. Changing that to fullscreen works as expected. On subsequent launches the game won't start anymore, being stuck on a wired black pseudo fullscreen window.

To Reproduce

1. Install the game
2. Launch the game
3. Change game graphics settings to fullscreen (instead of default borderless)
4. Quit the game
5. Relaunch the game

Expected behavior Launching the game as expected.

Screenshots
"Borderless" white frame	Broken fullscreen

LastRunWine.log

Additional context This issue is present on any CX23 based D3DMetal engine. It is not present on CX22 based engines regardless of D3DMetal version (including v1.1), however.

[Gcenx]

I’ve tried searching but seems your the first person to report this, guess as most of the macgaming community is using other solutions they won’t have seen this.

I’ll try to investigate this as that’s going to be an annoying regression to resolve.

[Rastafabisch]

I could finally retest with the 23.7.1 D3D engine. The issue is still present.

Another quirk I realised though, is, that when the game is launched a second time using the test run button in the wineskin UI, while one broken instance is already running, it‘s working fine for the second instance. I‘m puzzled. Perhaps it has something to do with environment initialisation?

[Gcenx]

@Rastafabisch if you have time, you could try using the WIP wineskin updates.

You can grab the new Winery from https://github.com/The-Wineskin-Project/Winery/releases/download/1.8.4.3/wineskin-winery-v1.8.4.3.tar.xz , you'll want to use the Wrapper/Engines it provides over the current Engines due to changes made for the now bundled GStreamer.framework.

You might want to rename ~/Library/Application Support/Wineskin so only the newer wrapper/engines are used for testing, just keep in mind that new version is WIP so Engines get swapped out with rebuilds without warning.

[Rastafabisch]

Will do!

---

I’m gonna update that post accordingly.

---

Sadly there's no change whatsoever in regards of said issue. I have not conducted any further testing.

[Rastafabisch]

Apparenty it's "fixed" in CrossOver 24 beta. Thought I don't know wether the issue is actually present on CrossOver 23, or wether its Wineskin related.

[Gcenx]

Yeah the fix from @marzent landed in upstream so automatically became part of CX24

Still not clue about the fullscreen bug, currently working on the new Wineskin bump & two other products.

[Rastafabisch]

It seems the issue is also present with CrossOver 24 (beta).

Would it be possible to build for you @Gcenx to release an updated CX22 engine, with the slow motion fix, as it didn’t have this fullscreen bug.

[Gcenx]

@Rastafabisch the 22.1.1 build found using #530 contains the fix. There’s no D3DMetal Engine as you’ll just use the new toggle (see the two linked videos)

[Rastafabisch]

I just finished conducting some tests and I’m happy to report that the WS12 CX22.1.1 engine (with D3DMetal enabled) promotes HZD to be fully working without any workarounds!

@Gcenx: Thank you very much for your continuing development and support of Wineskin and its engines!

---

I‘ll test WS12 CX23 as well but expect it to be broken. I’ll report back. As suspected still broken, and thus apparently a crossover issue.

[Gcenx]

I’ve passed this along to CodeWeavers we’ll see what happens.