SDK workaround: Difference between revisions
No edit summary |
Cargo Cult (talk | contribs) (It's still not quite right...) |
||
Line 19: | Line 19: | ||
Running Hammer from this shortcut will correct the graphic error. | Running Hammer from this shortcut will correct the graphic error. | ||
(This appears to result in displacement maps misbehaving on a GeForce 6600, latest drivers - the alpha for blend textures is inverted!) | |||
'''Windows X64''' | '''Windows X64''' | ||
Unconfirmed reports about hammer not working at all for x64 users. | Unconfirmed reports about hammer not working at all for x64 users. |
Revision as of 12:25, 3 June 2006
The recent engine update potentially broke mod development tools in Steam. If your mod is based on a game other than Half-Life 2, this update causes your mod to run on the new engine. Running the SDK Launcher causes binaries to be copied from the old version of the engine cache.

Until the problem is fixed with an SDK update, use the following workaround:
- Run the game which your mod is based on and exit.
- Make sure the SDKLauncher app is not running.
- Go to that game's \bin directory.
- Copy all files, excluding TrackerNET.dll and TrackerUI.dll.
- Paste these files in your username\sourcesdk\bin directory.


Alternative fix for Hammer (which actually works)
Go to C:\Program Files\Steam\SteamApps\Account_name\sourcesdk\bin\. Create a shortcut to hammer and put -dxlevel 80 in the command line like this : "C:\Program Files\Steam\SteamApps\Account_name\sourcesdk\bin\hammer.exe" -dxlevel 80.
Running Hammer from this shortcut will correct the graphic error.
(This appears to result in displacement maps misbehaving on a GeForce 6600, latest drivers - the alpha for blend textures is inverted!)
Windows X64 Unconfirmed reports about hammer not working at all for x64 users.