I am aware of the workaround by adding " /x64" to the launch arguments. This, however, does not work if your OS doesn’t have Multilib installed or has ia32_emulation=0 Kernel argument set (Linux). It does currently work on Windows, however.
If possible, please fix this issue and allow running the game on 64bit natively without any 32bit dependencies.
Thanks for the suggestion, but the issue isn’t with Wine or Proton. In fact, the game runs flawlessly with 32bit enabled.
The issue is that you can’t launch the 64-bit-version of the game directly (this will result in a crash), you need to launch the 32-bit-binary and then have it redirect to the 64-bit-version with the " /x64" launch argument. This, however, will also fail if you don’t have Multiarch (32bit dependencies) enabled.
The ideal solution would be to have the game start directly as a native 64-bit program. MangoHud reports the game as running on 64-bit though, so I assume it’s possible.
if you’re using the GoG version you need to use the gog’s “launch grim dawn” shortcut (found inside Gog’s GD install folder), it will launch x64 version by default
you cannot launch the x64 exe from folder direct/never could, it was always handled via the redirect or shortcut above 64-Bit Executable Crashes Immediately - #10 by Zantai
Hi there, thanking you for your insight. Sadly, there’s no such shortcut in my game folder nor in the Prefix Heroic created. And even if there was, I don’t think it differs from launching the 32-bit-exe with the aforementioned “/x64” argument.
As I’ve stated in my initial post, I am aware of this workaround. But as I’ve said it relies on 32bit architecture being enabled, which is what I want to dismiss.
My hope is that with the upcoming expansion and the technical overhaul that comes along with it, this dependance can be removed and we’ll be able to launch the 64bit version directly!
I’m having the same issue. I can no longer play in 64-bit, neither on the beta nor on the live version of the game. This problem started when I began testing the 1.3 beta.
I’ve already reinstalled the game, updated my video drivers, repaired files via Steam, and reset the game settings, etc. Nothing works.
OPs issue is about launching the x64 exe direct (which is currently unintended),
game not working 64bit when launching the game the normal way (ie redirect/steam) would be something else
Hey there,
posting again since there’s a two-month-timer running on this thread.
Has anyone involved in the development of GD looked into this? I don’t mind being told it’s not possible/not planned, I’d rather have that confirmation than seeing this thread quietly close.
In the windows version, there should be a file (redirect / shortcut) “Launch Grim Dawn” in the game folder, this files starts the 64 bit version of the game (the “Grim Dawn.exe” in the x64 folder), but runs the file in the game folder (not the x64 folder).
Before you try it, copying the 64bit exe to the main folder will not work.
The thing is that the working directory has to be the main game folder and if you just start the exe in the /x64 folder that becomes the working directory.
At least that’s my professional guess
So it should work if you launch it from the command line/terminal starting in the main directory and go ./x64/Grim Dawn.exe
There’s no way of launching the 64-bit version directly. Doing so will result in a black screen, both on Linux and Windows as well (see this Reddit thread for example)
As suggested, it is possible to launch the 64-bit version indirectly. This is also possible on Linux, however the reason I made this post is to inquiry on the possibility of a future patch resolving that dependency and allowing for launching the 64-bit version directly.
