mzaeemnasir
commented
8 months ago Same Here
Open GoldenLynel opened 8 months ago
mzaeemnasir
commented
8 months ago Same Here
GoldenLynel
commented
8 months ago Also switching to crossover wine does not do it for me because the performance is way worse and its bugged out(green car windows and invisible guns)
Emulord
commented
8 months ago Yup, same issue over here on an M3 Max.
AXZER10
commented
8 months ago Works with dxvk but still no fix for gptk
azsoftware
commented
8 months ago The same issue after update:
Launching "Grand Theft Auto V" (legendary)
Native? No
Installed in: /Users/alex/Games/Heroic/GTAV
System Info:
CPU: 10x Apple M1 Pro
Memory: 17.18 GB (used: 9.03 GB)
GPUs:
OS: 14.1.1 (darwin)
The current system is not a Steam Deck
We are not running inside a Flatpak container
Software Versions:
Heroic: 2.12.1 Vegapunk
Legendary: 0.20.34 Direct Intervention
gogdl: 0.7.3
Nile: 1.0.0 Jonathan Joestar
Game Settings: {
"autoInstallDxvk": true,
"autoInstallVkd3d": true,
"preferSystemLibs": false,
"enableEsync": true,
"enableFsync": true,
"launcherArgs": "",
"nvidiaPrime": false,
"offlineMode": false,
"enviromentOptions": [
{
"key": "WINEDEBUG",
"value": "fixme-keyboard"
},
{
"key": "MTL_HUD_ENABLED",
"value": "0"
}
],
"wrapperOptions": [],
"showFps": false,
"useGameMode": false,
"language": "",
"wineVersion": {
"bin": "/Users/alex/Library/Application Support/com.isaacmarovitz.Whisky/Libraries/Wine/bin/wine64",
"name": "Whisky - 2.2.1",
"type": "toolkit",
"lib": "/Users/alex/Library/Application Support/com.isaacmarovitz.Whisky/Libraries/Wine/bin/../lib",
"lib32": "/Users/alex/Library/Application Support/com.isaacmarovitz.Whisky/Libraries/Wine/bin/../lib",
"wineserver": "/Users/alex/Library/Application Support/com.isaacmarovitz.Whisky/Libraries/Wine/bin/wineserver"
},
"wineCrossoverBottle": "Heroic",
"winePrefix": "/Users/alex/Library/Containers/com.isaacmarovitz.Whisky/Bottles/4ADC8143-E436-4D5C-8C0C-7DE8526234F2",
"ignoreGameUpdates": true,
"enableDXVKFpsLimit": false,
"DXVKFpsCap": "50"
}
Game launched at: Sun Feb 04 2024 12:01:48 GMT+0200 (Eastern European Standard Time)
Launch Command: HEROIC_APP_NAME=9d2d0eb64d5c44529cece33fe2a46482 HEROIC_APP_RUNNER=legendary HEROIC_APP_SOURCE=epic WINEDEBUG=fixme-keyboard MTL_HUD_ENABLED=0 LD_PRELOAD= DOTNET_BUNDLE_EXTRACT_BASE_DIR= DOTNET_ROOT= WINEPREFIX=/Users/alex/Library/Containers/com.isaacmarovitz.Whisky/Bottles/4ADC8143-E436-4D5C-8C0C-7DE8526234F2 WINE_FULLSCREEN_FSR=0 WINEESYNC=1 WINEFSYNC=1 /Applications/Heroic.app/Contents/Resources/app.asar.unpacked/build/bin/darwin/legendary launch 9d2d0eb64d5c44529cece33fe2a46482 --wine "/Users/alex/Library/Application Support/com.isaacmarovitz.Whisky/Libraries/Wine/bin/wine64" --language ru
Game Log:
[cli] INFO: Logging in...
[Core] INFO: Trying to re-use existing login session...
[cli] INFO: Checking for updates...
[Core] INFO: Getting authentication token...
[cli] INFO: Launching 9d2d0eb64d5c44529cece33fe2a46482...
esync: up and running.
0024:fixme:thread:get_thread_times not implemented on this platform
00b4:fixme:module:dlopen_32on64_opengl32 loaded "/Users/alex/Library/Application Support/com.isaacmarovitz.Whisky/Libraries/Wine/lib/wine/x86_32on64-unix/opengl32.dll.so" early @ 0x6d9bb000
00b4: thread_get_state failed on Apple Silicon - faking zero debug registers
00f4: thread_get_state failed on Apple Silicon - faking zero debug registers
00bc:fixme:imm:ImeSetActiveContext (0x37a9e0, 0): stub
00bc:fixme:imm:ImmReleaseContext (0000000000010020, 000000000037A9E0): stub
00f4:fixme:imm:ImeSetActiveContext (0x8e80c0, 1): stub
00f4:fixme:imm:ImmReleaseContext (0009004E, 008E80C0): stub
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:thread:get_thread_times not implemented on this platform
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:seh:WerSetFlags (1) stub
00fc:fixme:file:NtLockFile I/O completion on lock not implemented yet
0104:fixme:file:NtLockFile I/O completion on lock not implemented yet
0104:fixme:process:SetProcessShutdownParameters (00000100, 00000001): partial stub.
00fc:fixme:shcore:SetCurrentProcessExplicitAppUserModelID L"RockstarGames.SocialClub.UI.Final": stub
00fc:fixme:bcrypt:BCryptGenRandom ignoring selected algorithm
00fc:fixme:bcrypt:BCryptGenRandom ignoring selected algorithm
00fc:fixme:bcrypt:BCryptGenRandom ignoring selected algorithm
00fc:fixme:bcrypt:BCryptGenRandom ignoring selected algorithm
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:module:LdrLockLoaderLock flags 1 not supported
00fc:fixme:thread:GetThreadUILanguage : stub, returning default language.
00fc:fixme:thread:GetThreadUILanguage : stub, returning default language.
00fc:fixme:imm:ImeSetActiveContext (0x2d6520, 1): stub
00fc:fixme:imm:ImmReleaseContext (000000000002007E, 00000000002D6520): stub
0114:fixme:thread:get_thread_times not implemented on this platform
00fc: thread_get_state failed on Apple Silicon - faking zero debug registers
0124: thread_get_state failed on Apple Silicon - faking zero debug registers
0130: thread_get_state failed on Apple Silicon - faking zero debug registers
0134: thread_get_state failed on Apple Silicon - faking zero debug registers
0138: thread_get_state failed on Apple Silicon - faking zero debug registers
013c: thread_get_state failed on Apple Silicon - faking zero debug registers
0140: thread_get_state failed on Apple Silicon - faking zero debug registers
0144: thread_get_state failed on Apple Silicon - faking zero debug registers
0148: thread_get_state failed on Apple Silicon - faking zero debug registers
014c: thread_get_state failed on Apple Silicon - faking zero debug registers
0150: thread_get_state failed on Apple Silicon - faking zero debug registers
0154: thread_get_state failed on Apple Silicon - faking zero debug registers
0158: thread_get_state failed on Apple Silicon - faking zero debug registers
015c: thread_get_state failed on Apple Silicon - faking zero debug registers
0160: thread_get_state failed on Apple Silicon - faking zero debug registers
0164: thread_get_state failed on Apple Silicon - faking zero debug registers
0168: thread_get_state failed on Apple Silicon - faking zero debug registers
016c: thread_get_state failed on Apple Silicon - faking zero debug registers
0170: thread_get_state failed on Apple Silicon - faking zero debug registers
0174: thread_get_state failed on Apple Silicon - faking zero debug registers
0178: thread_get_state failed on Apple Silicon - faking zero debug registers
0024:fixme:imm:ImeSetActiveContext (0x276490, 1): stub
0024:fixme:imm:ImmReleaseContext (0000000000040082, 0000000000276490): stub
010c:err:kerberos:kerberos_LsaApInitializePackage no Kerberos support, expect problems
010c:err:winediag:ntlm_check_version ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
010c:err:ntlm:ntlm_LsaApInitializePackage no NTLM support, expect problems
0104:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA, 000000000011FD70
012c:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA, 000000000011FD40
============= End of game logs =============When run manually Rockstar Games Launcher (Launcher.exe) and PlayGTAV.exe it runs but it's infinitely waiting for Epic Games Launcher authorization. So, I think, the problem is with launch command or config that Heroic uses.
Also in logs I see errors related to ntlm_auth dependency:
010c:err:kerberos:kerberos_LsaApInitializePackage no Kerberos support, expect problems
010c:err:winediag:ntlm_check_version ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
010c:err:ntlm:ntlm_LsaApInitializePackage no NTLM support, expect problemsNot sure if it's the root cause, but maybe something was changed in authentication.
And also I have a question. Why option "Ignore game updates" is not working and GTAV is updated anyway? (sometimes it requires few GB of data)
jeetmehta13
commented
8 months ago Yes even I am facing the same error on my M1 Max
rebelpercy
commented
8 months ago I have had the same for my M2 Pro since 31st Jan 2024. Updating GPTK to 1.1 didn't fix it. I think that Heoric needs to have an update on its gptk wine bottle.
Is there any fix so far?
Gcenx
commented
7 months ago This ain’t a Heroic Games Launcher problem but a D3DMetal problem.
jeetmehta13
commented
7 months ago @Gcenx is there any workaround?
Gcenx
commented
7 months ago @jeetmehta13 the workaround is to use DXVK
ShakshamTaneja
commented
7 months ago @jeetmehta13 the workaround is to use DXVK
so do you have any solution to fix it
Gcenx
commented
7 months ago @jeetmehta13 the workaround is to use DXVK
so do you have any solution to fix it
This ain’t a Heroic Games Launcher problem but a D3DMetal problem.
the workaround is to use DXVK
jeetmehta13
commented
7 months ago @Gcenx I am new to this, is it possible to use DXVK with game porting toolkit?
Gcenx
commented
7 months ago @jeetmehta13 no as game-porting-toolkit isn’t built to support Vulkan (required for DXVK)
rebelpercy
commented
7 months ago @jeetmehta13 the workaround is to use DXVK
I tried crossover 23.7.1 and wine 9.2 and winsky 2.2.3, with DXVK clicked in Heroic Launcher. All crashed in a minute after get in GTA OL. Is there something extra I need to do to make one of them work?
Gcenx
commented
7 months ago @rebelpercy
I tried crossover 23.7.1 and wine 9.2 and winsky 2.2.3, with DXVK clicked in Heroic Launcher. All crashed in a minute after get in GTA OL. Is there something extra I need to do to make one of them work?
As you’ve managed to get passed the issue with Rockstar Games Launcher, that’s now a separate issue.
biggie95
commented
7 months ago Hey guys same here on M3 Max. It used to work perfectly via RockstarLauncher on a friends M2 Pro back in October. Still using gpt version 1.0 or 0.x not sure. So maybe version 1.1 buggered it up? Any ideas? Is it possible to roll back to v 0.x?
MicheleSottocasa
commented
7 months ago Same issue here on M3 Any solutions?
Gcenx
commented
7 months ago Rockstar Games Launcher won't work with D3DMetal
biggie95
commented
7 months ago Well i had it working back in november on an m2 pro. So whats different now?
Gcenx
commented
7 months ago Well i had it working back in november on an m2 pro.
Yes it worked then but not now.
So whats different now?
A Rockstar Games Launcher update, the same one that now makes it require Window 10.
biggie95
commented
7 months ago Ooh okay i see. I didnt know there was a major update. Thanks for clarifying! :)
GoldenLynel
commented
7 months ago There is a possible fix on discord, many people have the issue to. I didn't read through all of it but some say it fixes the issue on heroic and mac. I can't try it right now because in on vecation. Here's the Link: https://discord.com/channels/812703221789097985/1210747284086849578
jeetmehta13
commented
7 months ago The possible fix works for Crossover but does not work for gptk I think, it is not working for me
Gcenx
commented
7 months ago Rockstar Games Launcher won’t work with CrossOver-22.1.1(and lower)/Game Porting Toolkit/Whisky. It also won’t work with CrossOver-23.7.1 when D3DMetal is enabled.
CrossOver-24.0.0 is required to run Rockstar Games Launcher using D3DMetal.
shad0w-jo4n
commented
6 months ago @Gcenx what about versions between 22.1.1 and 23.7.1?
Gcenx
commented
6 months ago @Gcenx what about versions between 22.1.1 and 23.7.1?
Only CrossOver-24.0.0 works with D3DMetal enabled, DXVK probably works with CrossOver-23.0.0 > 23.7.0. I mainly test the latest major release not each prior patch version of a releases.
So I’d only test against CrossOver-22.1.1/CrossOver-23.7.1 & CrossOver-24.0.0 anything in-between isn’t worth the time.
F4rozen
commented
6 months ago Describe the bug: After Rockstar games removes windows 7/8.1 support since the update GTA V on GTPK (Heroic Launcher) doesn't launch the game anymore giving the error " Rockstar games failed to initialise , Unable to launch the game please trying reinstalling"
Tuesday 30th January with a new update they've released.
Screenshots:
e8">
Logs: 2024-03-18T07_02_49-heroic.log 2024-03-18T07_02_49-legendary.log 9d2d0eb64d5c44529cece33fe2a46482-lastPlay.log
Heroic Version: Latest Stable 2.14.0
System Information: Mac OS Sonoma
Possible Error: I think i figured out why this is happening..
Rockstar Games Launcher won’t work with CrossOver-22.1.1(and lower)/Game Porting Toolkit/Whisky. It also won’t work with CrossOver-23.7.1 when D3DMetal is enabled.
CrossOver-24.0.0 is required to run Rockstar Games Launcher using D3DMetal.
Only CrossOver-24.0.0 works with D3DMetal enabled, DXVK probably works with CrossOver-23.0.0 > 23.7.0.
Summary:
Crossover 23.7.1 both DXVK and D3D METAL doesn't work ....
As we know that D3D Metal is a translation layer for D3D11 and D3d12 Part of the game porting tool kit When we launch the game using crossover 23/7.1 (CX PATCHED-D3D METAL) the game shows the same error as the problem with heroic launcher saying "Rockstar games failed to initialise"****
**This issue is because Direct x .. the setup doesn't install it properly into the wine/wineprefix
If we delete the wineprefix folder.. nd hit play button on heroic launcher, it normally installs the social club/rockstar games launcher.. but when its finishes the installation next step direct x is to be installed, thats where it fails nd gives the error.**
I tried installing the dirext x into the wineprefix using RUN EXE ON PREFIX OPTION to run and it gives another error.. Below are the images
I also tried replace the Dirext X Setup in the "Redistributes Folder" from the official micorsoft website, gives the same error as above image!
Gcenx
commented
6 months ago @F4rozen
As we know that D3D Metal is a translation layer for D3D11 and D3d12 Part of the game porting tool kit When we launch the game using crossover 23/7.1 (CX PATCHED-D3D METAL) the game shows the same error as the problem with heroic launcher saying "Rockstar games failed to initialise"
Where did I say Rockstar Games Launcher would work with CrossOver-23.7.1 + CXPatcher?
Working just fine with CrossOver-23.7.1
I've already explained Rockstar Games Launcher won't work with game-porting-toolkit, it's not an issue with DirectX runtime installation.
It's simply not worth looking into getting Rockstar Games Launcher working with game-porting-toolkit nor CrossOver-22.1.1.
Abrahampresidentovich
commented
4 months ago @F4rozen
As we know that D3D Metal is a translation layer for D3D11 and D3d12 Part of the game porting tool kit When we launch the game using crossover 23/7.1 (CX PATCHED-D3D METAL) the game shows the same error as the problem with heroic launcher saying "Rockstar games failed to initialise"
Where did I say Rockstar Games Launcher would work with CrossOver-23.7.1 + CXPatcher?
Working just fine with CrossOver-23.7.1
I've already explained Rockstar Games Launcher won't work with game-porting-toolkit, it's not an issue with DirectX runtime installation.
It's simply not worth looking into getting Rockstar Games Launcher working with game-porting-toolkit nor CrossOver-22.1.1.
Please tell me how did you manage to run it with 23.7.1
Describe the bug
After an update of GTA in heroic, GTA 5 does not launch anymore.
Add logs
Steps to reproduce
Expected behavior
The Game launches like before the update.
Screenshots
Heroic Version
Latest Stable
System Information
Mac OS Sonoma 14-2-1
Additional information
I think it has to do with the launcher not supporting windows 7 anymore even though my wine is set to 10.