libs shipped with v0.2.18 brake some games

[stonerl]

I patched CrossOver with the latest CXPatcher (v0.2.18) and at least two games that were running before are now crashing on start.

• Metal: Hellsinger (Unity)
• Hellblade: Senua's Sacrifice (UE4)

84 might be related.

[italomandara]

I own one of them Will test now meanwhile will advise not to use V0.2.18 to use a new bottle

[italomandara]

@stonerl One of them works for me:

But I have a fresh bottle with steam installed after I patched with CXP 0.2.18, maybe that's why

[stonerl]

Hmm. I'll try with a fresh bottle and report back.

[stonerl]

Still crashes for me. Even when I create a new bottle. I'm running macOS 13.5 (Ventura). You're on Sonoma, aren't you?

[italomandara]

I am on Sonoma

[stonerl]

That is the error I get on my system when I start Hellblade:

[italomandara]

And this works with the previous patches?

[stonerl]

And this works with the previous patches?

Yes, if I downgrade to 0.2.17 I can run/play the games.

[stonerl]

This is the backtrace for Metal: Hellsinger crashing. Maybe @Gcenx has any use for this.

backtrace.txt

[Gcenx]

This is the backtrace for Metal: Hellsinger crashing. Maybe @Gcenx has any use for this.

backtrace.txt

Unfortunately backtracks are mostly unless it’s need a cxlog

[stonerl]

@Gcenx Here they are:

Hellblade Senua's Sacrifice.cxlog.txt Metal Hellsinger.cxlog.txt

[Gcenx]

@stonerl I'm assuming from these logs your trying to launch the games directly from CrossOver UI with the launcher icons that instead for loading them from Steam?

[stonerl]

Yes, but they also crash when I start dem from within Steam.

Do you need a cxlog für this as well?

[Gcenx]

@stonerl yes please provide a cxlog when launched from within Steam as the currently logs have no mention of loading any d3d dll meaning it doesn’t get very far.

[stonerl]

@Gcenx here are the logs when the apps are started from within Steam.

Hellblade-Steam.cxlog.txt Metall Hellsinger-Steam.cxlog.txt

[Gcenx]

Please try again with V0.2.20

[stonerl]

v0.2.20 fixed the issue.