Game requires 64-bit but Steam defaults to 32-bit

[TopazMystique]

I have several Steam games that require a 64-bit processor so I assume that means they have to be installed into 64-bit folder instead of 32-bit folder but my Steam default folder is 32-bit. Is there any way to install a 64-bit game into a 64-bit library while leaving my 32-bit installed games where they are?

[TopazMystique]

|2|Phew™ a écrit :

You could just create a new folder or new drive folder and call it 64bit ?

TopazMystique a écrit :

Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_ldr.161011-0600)

Your other assumption.

I have DOI, Day of Imfamy, inside folder has 2 .exes, one doesnt say 32bit, it just says dayofinfamy.exe, however it also has dayofinfamy_x64.exe

It is infact installed in Program files (86).
When i launch the 64bit version and check ingame, it is indeed 64bit version of game running. the game will inform you of this somewhere, hopefully, mine does.
Does that make sense?

I guess I'm really dense on this stuff. How do you launch 64-bit rather than 32-bit? My game (Langoth) shortcut executes the Steam rungameid but there is a Langoth.exe & Langoth-Win32-Shipping.exe in a Langoth,,,Win32 folder and a Langoth-Win64-Shipping.exe in a Langoth,,,Win64 folder.

[TopazMystique]

It looks like the problem may be the processor. Two of the games that are crashing require "Intel Core i3" and I have "AMD Quad-Core Processor" so just 64-bit alone doesn't cut it.

[Cathulhu]

What are your system specs then?
Core i3 and AMD Quad Core CPUs are not really a new thing. My AMD Quad Core is about nine years old.

[TopazMystique]

Cathulhu a écrit :

What are your system specs then?
Core i3 and AMD Quad Core CPUs are not really a new thing. My AMD Quad Core is about nine years old.

Mine is about 5 years old. Not sure what you want but this is the System Info from DxDiag:
Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_ldr.161011-0600)
Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: GA-78LMT-USB3
BIOS: Award Modular BIOS v6.00PG
Processor: AMD FX(tm)-4100 Quad-Core Processor (4 CPUs), ~3.6GHz
Memory: 20480MB RAM
Available OS Memory: 16382MB RAM
Page File: 2594MB used, 30166MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode

When these two games crash, they display an Unreal Engine crash screen which I have sent multiple times but to no avail.

[Kargor]

|2|Phew™ a écrit :

When i launch the 64bit version and check ingame, it is indeed 64bit version of game running. the game will inform you of this somewhere, hopefully, mine does.

Whether it's running a 32 bit or 64 bit executable is of no concern to users, so most games probably won't tell you.

However, you can always check the task manager; it will tell you whether a given process or application is running as 32 bit or 64 bit.

[TopazMystique]

Kargor a écrit :

|2|Phew™ a écrit :

When i launch the 64bit version and check ingame, it is indeed 64bit version of game running. the game will inform you of this somewhere, hopefully, mine does.

Whether it's running a 32 bit or 64 bit executable is of no concern to users, so most games probably won't tell you.

However, you can always check the task manager; it will tell you whether a given process or application is running as 32 bit or 64 bit.

But that only works if the game actually runs, correct? If it crashes, there's no way to tell?

[Cathulhu]

How did you manage to get 20GB of RAM?
Especially considering that your Windows 7 Edition only allows up to 16GB of RAM to be used.

[TopazMystique]

Cathulhu a écrit :

How did you manage to get 20GB of RAM?
Especially considering that your Windows 7 Edition only allows up to 16GB of RAM to be used.

Added memory.

[Cathulhu]

Which is rather useless as in not used.

[TopazMystique]

Cathulhu a écrit :

Which is rather useless as in not used.

I just left the old memory in there just in case some of it went bad that it would take up the slack.

[Cathulhu]

Or it just slowed down the rest of your RAM and maybe even cause your current issue.

[TopazMystique]

Cathulhu a écrit :

Or it just slowed down the rest of your RAM and maybe even cause your current issue.

I guess that's possible but I've been running with the new and old memory for almost 2.5 years and not noticed any problems like the current ones.