SDK workaround: Difference between revisions
Jump to navigation
Jump to search
Warning:All SDK tools must now be run from within explorer or from a command-line window; running the SDK Launcher app will cause this problem to occur again and these steps must be repeated.
Warning:by TorQue[MoD] - This will also make the 2D views in Hammer disappear and the model browser will crash if you try to browse the models in Hammer.
mNo edit summary |
No edit summary |
||
Line 11: | Line 11: | ||
{{warning|All SDK tools must now be run from within explorer or from a command-line window; running the SDK Launcher app will cause this problem to occur again and these steps must be repeated.}} | {{warning|All SDK tools must now be run from within explorer or from a command-line window; running the SDK Launcher app will cause this problem to occur again and these steps must be repeated.}} | ||
{{Warning | {{Warning|by TorQue[MoD] - This will also make the 2D views in Hammer disappear and the model browser will crash if you try to browse the models in Hammer.}} |
Revision as of 18:20, 27 May 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.

