Genshin Impact not launching

[niclimcy]

Environment (please complete the following information):

• OS: macOS 14.0
• Winery version: 2.9.2.0
• Master Wrapper version: WS11WineCX64Bit
• Engine version: 23.5.0-wip2-D3DMetal
• Hardware: Macbook Pro 14 2021
• Game Name: Genshin Impact

Describe the bug Game does not launch from launcher, launcher reopens after awhile

To Reproduce

1. Install Genshin Impact installer from mihoyo website
2. Set launcher.exe as Windows app
3. Download game files (73GB)
4. Press launch, nothing happens

Expected behavior After pressing launch, separate window of game should launch

Screenshots N.A.

LastRunWine.log https://gist.github.com/niclimcy/997a0b7339de5d9e751dfbe990d61a5c

Additional context On Crossover 23.5, there is an overlay of html content also missing on wineskinserver in the game launcher. Game launches fine there and there are no additional hacks installed as I can see.

[antoninmuller]

same engine with cyberpunk = crash too

[Gcenx]

same engine with cyberpunk = crash too

@antoninmuller please create an issue and attach LastRunWine.log this issue is not related to your crash.

[Gcenx]

@niclimcy

The provided log gave me a hint to the actual issue this was easy to resolve and will be included in the next wip bum.

[Gcenx]

Hum it’s not always displaying the web content might be more a layering issue, but that would also affect CrossOver-23.5.0

[niclimcy]

@niclimcy

The provided log gave me a hint to the actual issue this was easy to resolve and will be included in the next wip bum.

Nice. Are there any instructions on how I can compile the fix for myself first?

Also are there plans on using GPTK 1.0 which was released recently, or do we follow Crossover for such version bumps?

Hum it’s not always displaying the web content might be more a layering issue, but that would also affect CrossOver-23.5.0

Crossover shows it more consistently for some reason

[Gcenx]

Nice. Are there any instructions on how I can compile the fix for myself first?

No as I don’t provide WineskinCX sources but it still requires more work due to the layering issue, I see it appear and vanish.

Also are there plans on using GPTK 1.0 which was released recently, or do we follow Crossover for such version bumps?

I’m already bundling D3DMetal-v1.0 (stable)\ What you call GPTK is actually D3DMetal.

Crossover shows it more consistently for some reason

This might be due to there still using D3DMetal-v1.0.4 beta, where as I’m bundling D3DMetal-v1.0 (stable)

[niclimcy]

Nice. Are there any instructions on how I can compile the fix for myself first?

No as I don’t provide WineskinCX sources but it still requires more work due to the layering issue, I see it appear and vanish.

Also are there plans on using GPTK 1.0 which was released recently, or do we follow Crossover for such version bumps?

I’m already bundling D3DMetal-v1.0 (stable) What you call GPTK is actually D3DMetal.

Crossover shows it more consistently for some reason

This might be due to there still using D3DMetal-v1.0.4 beta, where as I’m bundling D3DMetal-v1.0 (stable)

How can I debug the layering issue?

[Gcenx]

How can I debug the layering issue?

It’s not easy to explain, I’ll try looking into it more when I have the time.

[Gcenx]

@niclimcy while the launcher layering probably won’t have been affected wip3 probably gets the game to launch.

Though if that’s anything like Diablo4 it might require enabling esync/msync.

[niclimcy]

@niclimcy while the launcher layering probably won’t have been affected wip3 probably gets the game to launch.

Though if that’s anything like Diablo4 it might require enabling esync/msync.

Game launches fine now with wip3, do I close this issue and make a new one for the layering issue?

[niclimcy]

Regression with non wip build:

https://gist.github.com/niclimcy/5076a970b709818ea1ff1d4879f5b8d6

[Gcenx]

That’s odd as the only difference from wip3 to none wip was revering a single change that affected Counter-Strike:2

I’ll add it to my list but it seems it’s not finding some game dlls.

[niclimcy]

23.6 fixed it