64-bit mode with Source SDK: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
{{lang|64-bit mode with Source SDK}} | {{lang|64-bit mode with Source SDK}} | ||
{{ModernNote|The info below are most likely outdated as Valve no longer providing a 64-bit build of Source SDK and Half-Life 2. This page will remain for archival purposes only.}} | {{ModernNote|The info below are most likely outdated as Valve no longer providing a 64-bit build of Source SDK and Half-Life 2. This page will remain for archival purposes only.<br> Third-party Source games however, may have 64-bit support, or Source 2 which fully support 64-bit, but it is unknown if this command-line also applies to them.}} | ||
The current Source SDK release has issues starting up on systems running the Source engine in 64-bit mode with the 64-bit version of Windows XP. | The current Source SDK release has issues starting up on systems running the Source engine in 64-bit mode with the 64-bit version of Windows XP. | ||
Revision as of 08:42, 15 June 2023
The current Source SDK release has issues starting up on systems running the Source engine in 64-bit mode with the 64-bit version of Windows XP.
To correct the problem:
- In the Steam Games window, right-click on Half-Life 2 (or any installed Valve game you want to run) and select the Properties option.
- Then select Set launch options... and add the line
-32bitto the edit box. - Close the dialog and launch the game you just edited (ie. Half-Life 2). When it has successfully started up, close the game.
You should now be able to run the SDK on your 64-bit OS. Note, however, that if you run any of your Valve games without the -32bit option, your SDK will go back to being incompatible and you'll need to repeat this process.
This means that if you run a game through Hammer, you'll also need to launch that game with the -32bit command line parameter as well. The same is true running a game from a batch file, command line, etc.