Closed GrimDawn-max closed 4 weeks ago
Could you add the following to the Unix command field
export DYLD_PRINT_LIBRARIES=YES
Then provide an updated LastRunWine.log
Added WS12WineCX64Bit23.7.1-3_D3DMetal-v1.1
that Engine is a rebuilt version of WS12WineCX64Bit23.7.1-3_rc2
but using the prior method of using D3DMetal.
Due to D3DMetal files being directly bundled inside this Engine the option is grayed put since it can't be disabled.
Attached is the LastRunWine.log wit the added Unix command LastRunWine.log
Added
WS12WineCX64Bit23.7.1-3_D3DMetal-v1.1
that Engine is a rebuilt version ofWS12WineCX64Bit23.7.1-3_rc2
but using the prior method of using D3DMetal.Due to D3DMetal files being directly bundled inside this Engine the option is grayed put since it can't be disabled.
The new engine works ! Path of Exile started up as usual. Thanks. You can go ahead and close the report as fixed.
I won’t be closing this as I don’t consider this an actual solution more a workaround like the other solution l included inside the engine you tested.
I’ve been working on a more stable solution that’ll require all supported Engines to be rebuilt but has other advantages.
@Gcenx @GrimDawn-max sorry to mother you grys, im trying to run POE through wine on my MacBook. I can't seem to get the engine running properly. World you be able to help me?
@Gcenx @GrimDawn-max sorry to mother you grys, im trying to run POE through wine on my MacBook. I can't seem to get the engine running properly. World you be able to help me?
Join this discord channel - https://discord.gg/XbdFZT6G
The mac-os channel has a pinned message with a link to a wiki page on the official poewiki site. It outlines how to install POE using Wineskinserver.
We’ve been working hard on a large backend change that also resolves the issues related to currently needing the -d3dmetal
Engines again.
@Gcenx @GrimDawn-max sorry to mother you grys, im trying to run POE through wine on my MacBook. I can't seem to get the engine running properly. World you be able to help me?
Join this discord channel - https://discord.gg/XbdFZT6G
The mac-os channel has a pinned message with a link to a wiki page on the official poewiki site. It outlines how to install POE using Wineskinserver.
Hey sorry would you be able to resend the link? I was away from home so didn’t even get to see the message. Thank you for the response.
We’ve been working hard on a large backend change that also resolves the issues related to currently needing the
-d3dmetal
Engines again.
Have you managed to successfully make it work? If so I’d love to try. Also I have encountered a problem when I closed wine skin and reopened it, it won’t relaunch the game anymore. States there is some sort of error that the tmp or exe is still running in the background.
Have you managed to successfully make it work? If so I’d love to try.
There still some bugs to iron out but once we’re happy we’ll push an update for all Wineskin users.
During testing the newly revised Engines (due to backend changes) are working nicely this includes fully functional CX24 and CXP based Engines.
Also I have encountered a problem when I closed wine skin and reopened it, it won’t relaunch the game anymore. States there is some sort of error that the tmp or exe is still running in the background.
It would be best to open an issue for this and provide as much formation as possible.
The game works in Kegworks with WineCX23.7.1 once renders/d3dmetal/2.0
is removed, once I provide WineCX24 engine it’ll work with D3DMetal-v2.0.
Environment (please complete the following information):
Describe the bug
When using ANY WS12WineCX64Bit engines Path of Exile will start but then crash to the desktop before getting to login page.
Path of Exile runs correctly when using WS11WineCX64Bit23.7.1.-D3DMetal-v1.1
To Reproduce
Describe the steps to reproduce the behavior:
Expected behaviour
Path of Exile should start up and present a login screen to login and play the game.
Screenshots
If applicable, add screenshots to help explain your problem.
LastRunWine.log
If the log is larger drag/drop into the issue window. LastRunWine.log
Additional context
None