Can P4G Run 64-bit?

[1A Gaming]

That thing I asked up there ^

[pitch]

it can run on 64 bit systems though I think the app itself is 32 bit, at least judging by the name of the game window

[Vyrtualis]

It'd require Atlus doing a conversion to recompile the .exe to x64. How difficult the process would be varies depending on how the game is structured. It's doubtful that it would be worth the effort.

Something you can do, however, is extend the virtual memory page. You can do this easily with a patcher on ntcore.com (the 4GB patch). It doubles the virtual memory page.

[1A Gaming]

Originally posted by Vyrtual:

It'd require Atlus doing a conversion to recompile the .exe to x64. How difficult the process would be varies depending on how the game is structured. It's doubtful that it would be worth the effort.

Something you can do, however, is extend the virtual memory page. You can do this easily with a patcher on ntcore.com (the 4GB patch). It doubles the virtual memory page.

Does that have a GUI? Or am I gonna have to use strait cmd?

Also will Denuvo have a problem with this?

[Crashed]

Originally posted by Joe Beezy:

Also will Denuvo have a problem with this?

It won't; you aren't tampering with its Anti-Tamper features. That said, it might use up one of your daily activations due to the process's virtual memory map changing.

[1A Gaming]

Originally posted by Crashed:

Originally posted by Joe Beezy:

Also will Denuvo have a problem with this?

It won't; you aren't tampering with its Anti-Tamper features. That said, it might use up one of your daily activations due to the process's virtual memory map changing.

Is there some limit on daily activations? Is there some risk involved here?

[CPT Chthonbeard the Pirate]

Originally posted by Joe Beezy:

That thing I asked up there ^

Any 64-bit CPU can run a 32-bit EXE file just fine. As another person said in the accepted answer, converting a 32-bit EXE file to 64-bit EXE requires recompiling the exe. This requires the source code.

Of course they have the source code to do this with. Now, they also have anti-tamper features which might rely on the 32-bit nature of the file as well, and this could cause other complications making it harder than just a recompilation, but in general, usually recompilation from source code with new parameters is all that is needed.

It's the compiler that handles all of the other stuff, like linking and memory management, which is what he was talking about.

[Crashed]

Originally posted by CPT Chthonbeard the Pirate:

Originally posted by Joe Beezy:

That thing I asked up there ^

Any 64-bit CPU can run a 32-bit EXE file just fine. As another person said in the accepted answer, converting a 32-bit EXE file to 64-bit EXE requires recompiling the exe. This requires the source code.

Of course they have the source code to do this with. Now, they also have anti-tamper features which might rely on the 32-bit nature of the file as well, and this could cause other complications making it harder than just a recompilation, but in general, usually recompilation from source code with new parameters is all that is needed.

It's the compiler that handles all of the other stuff, like linking and memory management, which is what he was talking about.

The anti-tamper software is not specific to 32-bit x86, and the vendor could just as easily wrap a 64-bit executable if provided to them. The anti-tamper is applied after a binary is produced.

As for 32-bit support, all desktop versions of Windows, both x86-64 and ARM64, support IA-32 executables, and as a result actually have a set of 32-bit system DLLs just for running such programs. For x86-64 processors there is native support for 32-bit code, while on ARM64 Windows has an emulator to run IA-32 code.

[CPT Chthonbeard the Pirate]

Originally posted by Crashed:

Originally posted by CPT Chthonbeard the Pirate:

Any 64-bit CPU can run a 32-bit EXE file just fine. As another person said in the accepted answer, converting a 32-bit EXE file to 64-bit EXE requires recompiling the exe. This requires the source code.

Of course they have the source code to do this with. Now, they also have anti-tamper features which might rely on the 32-bit nature of the file as well, and this could cause other complications making it harder than just a recompilation, but in general, usually recompilation from source code with new parameters is all that is needed.

It's the compiler that handles all of the other stuff, like linking and memory management, which is what he was talking about.

The anti-tamper software is not specific to 32-bit x86, and the vendor could just as easily wrap a 64-bit executable if provided to them. The anti-tamper is applied after a binary is produced.

I am not familiar with how Denuvo actually functions, so I'll take your word for it. I just know that there are some tamper mechanisms that could be made such that would not function in a 64-bit executable.

[1GREG7]

Yes

[Arifufu]

By January 2023 update, now P4G only support 64-bit