Source SDK Known Issues: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
(official SDK known issues)
 
m (formatting fixes)
 
(52 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[Category:Steam]]
This is a list of known and verified issues with the Source SDK release, and potential workarounds.
This is a list of known and verfied issues with the Source SDK release, and potential workarounds.


=== Expert Compile Settings deleted after update ===
== General issues ==


There is an issue with the Hammer Editor where Expert Compile mode settings are deleted for some users after the update. To restore the default settings, follow this procedure:
=== Visual Studio 2002 is no longer supported (Since 8/4/2006)===


# Delete the file <code>CmdSeq.wc</code> from your <code>sourcesdk\bin</code> directory.
As of this SDK Release Visual Studio 2002 is no longer supported. We are sorry for the inconvenience that this causes our customers.
# Choose '''Refresh SDK Content''' from the Source SDK launcher window.


This issue will be addressed in another SDK Beta update.
For those who are brave there is a patch that allows for [[Compiling under VS2002|VS 2002 compilation]].


=== "Steam validation rejected" Error ===
{{note|This patch is provided here as a convenience. Valve does not maintain or support it.}}
* Users may get this Steam error when loading a multiplayer map from Hammer. A fix for this issue is being developed. The current workaround is to start a local LAN server by adding <code>+sv_lan 1</code> to the command-line when launching the game. Hammer users can find information about how to add this command-line parameter in [[Additional_game_parameters|this SDK FAQ article]].


=== Issues on 64-bit systems ===
== Hammer Editor issues ==
* There are some issues with running the Source SDK on the 64-bit version of Windows. A permanent fix for these issues is being developed. The current workaround is to run the SDK in 32-bit mode, as described in this [http://www.chatbear.com/board.plm?a=viewthread&t=428,1136490004,14719&id=946641&b=4986&v=flatold SDK forum post].


=== Incorrect alpha value on displacements ===
=== Direct shortcuts to hammer will not work (Since 8/4/2006)===
* On some user's systems, especially users with DX8 or lower video cards, the alpha blend values of displacements are reversed in Hammer, although they are correct when the .BSP is viewed in the engine. The alpha values are correctly saved in the map -- the rendering in Hammer is incorrect.


The current workaround is follow these step when the map is ready to be compiled:
With this version of the SDK you will get an error if you attempt to run hammer.exe from the 'sourcesdk\bin' directory. Here is the best way to work around this issue:
# Click the '''Auto''' tab on the '''Visgroups''' bar to switch to the Auto Visgroups view.
# Select the '''Displacements''' entry from the list of Visgroups.
# Click the '''Mark''' button to select all Displacements.
# Press Shift+A to open the '''Face Edit''' dialog and then click the '''Displacements''' tab.
# Press the '''Invert Alpha''' button.
# Choose '''Run Map...''' to compile the map and see the results in the game.
# Repeat this process to restore the displacement visualization inside Hammer, and continue editing.


This will be fixed in an Source Engine update.
# Right-click on the '''Source SDK''' item on the '''Tools''' tab in Steam.
# Select '''Create desktop shortcut'''.
# Add <code>-runhammer</code> to the end of the steam.exe command line.
#:For example: <code>C:\Program Files\Valve\Steam\Steam.exe -applaunch 211 -runhammer</code>
# Rename the desktop shortcut to something appropriate, such as "Hammer Editor".
 
This has the added benefit of actually launching the SDK Launcher before Hammer, making sure it is the latest version.
 
{{note|Shortcuts for Model Viewer and FacePoser can be created by following the same procedure and replacing <code>-runhammer</code> with one of these command line arguments: <code>-runmodelviewer</code> or <code>-runfaceposer</code>.}}
 
=== 3D Lighting Preview View in Hammer causes strange behavior and crashes (Since 8/4/2006)===
There is a main menu item for 3D Lighting Preview that should not be exposed at this point. Please do not use it as it does not work.
 
''This issue is addressed and the fix will be available in the next release.''
 
=== 3D View in Hammer appears empty (Since 8/4/2006)===
The newest release of Hammer requires that at least on Camera be placed in the map in order for the 3D Views to work. If you are experiencing empty 3D views simply [[Hammer_Camera_Tool|place a camera]] in your map.
 
=== Error when running maps from within a mod (Since 8/4/2006)===
When attempting to run a map from within Hammer you may come across the following error message:
 
[[Image:MountAppFilesystemFailed.JPG]]
 
Here is the process for working around this issue until it is addressed in the SDK:
 
# On Hammer's Tools > Options > Build Tools page change the '''Game Executable''' to be:
#: <code>$SteamDir\steam.exe</code> instead of <code>$SteamUserDir\half-life 2\hl2.exe</code><br /><br />
#: [[Image:SteamFSError-Sol1.JPG]]
# From the '''Run Map''' dialog, prepend the <code>-applaunch 215</code> parameter for the '$game_exe' command:
#: [[Image:SteamFSError-Sol2.JPG]]
 
What this will do is run Steam and instruct it to launch 'Source SDK base' and point it to the map defined by the remainder of the <code>$game_exe</code> parameters. One thing to look out for is that you will need to build the DLL's for your mod before running it.
 
== SDK code issues ==
 
=== Error running a new mod (Since 8/4/2006)===
[[Image:Couldnotloadclient.JPG]]
 
In the new SDK it is necessary to build the client and server DLLs before running the mod. Please build them if you see this message when trying to run the mod.
 
=== From scratch mod exits when launching from Steam Menu (Since 8/4/2006)===
Launching a (Make a mod from scratch) mod from the Steam menu enters the game, shows the game menu, dings, and then exits, no error. Although, launching from a command line works fine.
 
: Well actually it should work fine. Though note that if you have compiled your DLLs in debug mode you have to add <code>-allowdebug</code> to the mod's launch options! The <code>run_mod.bat</code> already adds it.


== See also ==
== See also ==
* [[Source SDK Release Notes]]


* [[Source SDK Release Notes]]
[[Category:Steam]][[Category:Changelists]]

Latest revision as of 18:30, 2 December 2006

This is a list of known and verified issues with the Source SDK release, and potential workarounds.

General issues

Visual Studio 2002 is no longer supported (Since 8/4/2006)

As of this SDK Release Visual Studio 2002 is no longer supported. We are sorry for the inconvenience that this causes our customers.

For those who are brave there is a patch that allows for VS 2002 compilation.

Note.pngNote:This patch is provided here as a convenience. Valve does not maintain or support it.

Hammer Editor issues

Direct shortcuts to hammer will not work (Since 8/4/2006)

With this version of the SDK you will get an error if you attempt to run hammer.exe from the 'sourcesdk\bin' directory. Here is the best way to work around this issue:

  1. Right-click on the Source SDK item on the Tools tab in Steam.
  2. Select Create desktop shortcut.
  3. Add -runhammer to the end of the steam.exe command line.
    For example: C:\Program Files\Valve\Steam\Steam.exe -applaunch 211 -runhammer
  4. Rename the desktop shortcut to something appropriate, such as "Hammer Editor".

This has the added benefit of actually launching the SDK Launcher before Hammer, making sure it is the latest version.

Note.pngNote:Shortcuts for Model Viewer and FacePoser can be created by following the same procedure and replacing -runhammer with one of these command line arguments: -runmodelviewer or -runfaceposer.

3D Lighting Preview View in Hammer causes strange behavior and crashes (Since 8/4/2006)

There is a main menu item for 3D Lighting Preview that should not be exposed at this point. Please do not use it as it does not work.

This issue is addressed and the fix will be available in the next release.

3D View in Hammer appears empty (Since 8/4/2006)

The newest release of Hammer requires that at least on Camera be placed in the map in order for the 3D Views to work. If you are experiencing empty 3D views simply place a camera in your map.

Error when running maps from within a mod (Since 8/4/2006)

When attempting to run a map from within Hammer you may come across the following error message:

MountAppFilesystemFailed.JPG

Here is the process for working around this issue until it is addressed in the SDK:

  1. On Hammer's Tools > Options > Build Tools page change the Game Executable to be:
    $SteamDir\steam.exe instead of $SteamUserDir\half-life 2\hl2.exe

    SteamFSError-Sol1.JPG
  2. From the Run Map dialog, prepend the -applaunch 215 parameter for the '$game_exe' command:
    SteamFSError-Sol2.JPG

What this will do is run Steam and instruct it to launch 'Source SDK base' and point it to the map defined by the remainder of the $game_exe parameters. One thing to look out for is that you will need to build the DLL's for your mod before running it.

SDK code issues

Error running a new mod (Since 8/4/2006)

Couldnotloadclient.JPG

In the new SDK it is necessary to build the client and server DLLs before running the mod. Please build them if you see this message when trying to run the mod.

From scratch mod exits when launching from Steam Menu (Since 8/4/2006)

Launching a (Make a mod from scratch) mod from the Steam menu enters the game, shows the game menu, dings, and then exits, no error. Although, launching from a command line works fine.

Well actually it should work fine. Though note that if you have compiled your DLLs in debug mode you have to add -allowdebug to the mod's launch options! The run_mod.bat already adds it.

See also

Retrieved from "https://developer.valvesoftware.com/w/index.php?title=Source_SDK_Known_Issues&oldid=96642"