SDK workaround: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
m (revert)
m (standardized)
Line 1: Line 1:
[[Category:Source SDK FAQ]]
[[Category:Source SDK FAQ]]
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. {{note|"other than Half-Life 2" includes HL2DM}}
The recent engine update potentially broke mod development tools in Steam. If your mod is based on a game other than Half-Life 2, including HL2DM, 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:
Until the problem is fixed with an SDK update, use the following workaround:
# Run the game which your mod is based on and exit.  
# Run the game which your mod is based on and exit.  
# Make sure the SDKLauncher app is not running.
# Make sure the <code>SDKLauncher</code> app is not running.
# Go to that game's \bin directory.
# Go to that game's <code>bin</code> directory.
# Copy all files, excluding TrackerNET.dll and TrackerUI.dll.
# Copy all files, excluding <code>TrackerNET.dll</code> and <code>TrackerUI.dll</code>.
# Paste these files in your username\sourcesdk\bin directory.
# Paste these files in your <code>USERNAME\sourcesdk\bin</code> directory.


{{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.}}
Line 15: Line 15:
==Alternative fix for Hammer==
==Alternative fix for Hammer==


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.
Go to <code>..\Steam\SteamApps\USERNAME\sourcesdk\bin</code>. Create a shortcut to Hammer and add <code>-dxlevel 80</code> to it (e.g. <code>"DIRECTORIES\hammer.exe" -dxlevel 80</code>).


Running Hammer from this shortcut will correct the graphic error.
Running Hammer from this shortcut will correct the graphic error.
Line 23: Line 23:


'''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.


==Entry Point Errors==
==Entry Point Errors==


* '''"the procedure entry point commandline_tier0 could not be located in the dynamic link library tier0.dll"'''
==commandline_tier0 & tier0.dll==
when: launching any HL2 modification (from hl2.exe) made from the latest SDK source code.<br>
<code>"the procedure entry point commandline_tier0 could not be located in the dynamic link library tier0.dll"</code>
the fix: instead of launching your mod using "SteamApps\usrname\half-life 2\hl2.exe", use this instead: "SteamApps\usrname\source sdk base\hl2.exe"<br>
If you are experiencing this when launching a mod, try launching it using <code>"\..SteamApps\USERNAME\source sdk base\hl2.exe"</code> instead of <code>"..\SteamApps\USERNAME\half-life 2\hl2.exe"</code>
==spewandlogactivate & tier0_s.dll==
<code>"the procedure entry point spewandlogactivate could not be located in the dynamic link library tier0_s.dll"</code>


* '''"the procedure entry point spewandlogactivate could not be located in the dynamic link library tier0_s.dll"'''
To fix this issue, rename or delete <code>"..\SteamApps\USERNAME\half-life 2\bin\tier0_s.dll"</code>
when: launching HL2 via hl2.exe<br>
the fix: rename or delete this file: "SteamApps\usrname\half-life 2\bin\tier0_s.dll"<br>


==See Also==
==See Also==
[[Failed_to_load_the_default_scheme_file]]
*[[Failed to load the default scheme file]]

Revision as of 18:18, 6 October 2007

The recent engine update potentially broke mod development tools in Steam. If your mod is based on a game other than Half-Life 2, including HL2DM, 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:

  1. Run the game which your mod is based on and exit.
  2. Make sure the SDKLauncher app is not running.
  3. Go to that game's bin directory.
  4. Copy all files, excluding TrackerNET.dll and TrackerUI.dll.
  5. Paste these files in your USERNAME\sourcesdk\bin directory.
Warning.pngWarning: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.pngWarning: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. Shutting down Steam and restarting Hammer will fix the 2D view and model browser, however the ATI-cards are the worst, whereas before it was only affecting models, now it affects the entire 3D window.

Alternative fix for Hammer

Go to ..\Steam\SteamApps\USERNAME\sourcesdk\bin. Create a shortcut to Hammer and add -dxlevel 80 to it (e.g. "DIRECTORIES\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!)

  • This issue (inverted alpha) can also occur on a Radeon 9800 Pro with Catalyst version 6.6.

Windows X64 Unconfirmed reports about Hammer not working at all for x64 users.

Entry Point Errors

commandline_tier0 & tier0.dll

"the procedure entry point commandline_tier0 could not be located in the dynamic link library tier0.dll" If you are experiencing this when launching a mod, try launching it using "\..SteamApps\USERNAME\source sdk base\hl2.exe" instead of "..\SteamApps\USERNAME\half-life 2\hl2.exe"

spewandlogactivate & tier0_s.dll

"the procedure entry point spewandlogactivate could not be located in the dynamic link library tier0_s.dll"

To fix this issue, rename or delete "..\SteamApps\USERNAME\half-life 2\bin\tier0_s.dll"

See Also