Difference between revisions of "Failed to load the default scheme file"

From Valve Developer Community
Jump to: navigation, search
(Since steampipe conversion people see this message, added a sentence to try and help them out. Needs work though)
(Expanded Wazanator's edit)
Line 1: Line 1:
 
{{otherlang2
 
{{otherlang2
 
| ru = Failed_to_load_the_default_scheme_file:ru}}
 
| ru = Failed_to_load_the_default_scheme_file:ru}}
{{cleanup|Solution provided is outdated -- Needs revision (Jan 2012)}}
 
 
  "Failed to load the default scheme file. The map views may be missing some visual elements"
 
  "Failed to load the default scheme file. The map views may be missing some visual elements"
 
{{Note|This error is related to the [[Hammer]] editor.}}
 
{{Note|This error is related to the [[Hammer]] editor.}}
  
== Possible causes ==
+
= Possible causes =
 +
== Starting Hammer using shortcuts ==
 
The error is known to occur when trying to start Hammer faster using a shortcut, instead of the Source SDK GUI.
 
The error is known to occur when trying to start Hammer faster using a shortcut, instead of the Source SDK GUI.
Although, it can also happen when openning Hammer from the Source SDK GUI today (Sept 2009).
+
Although, it can also happen when opening Hammer from the Source SDK GUI today (Sept 2009).
  
If you are trying to launch hammer for a Valve game from the Source SDK launcher and are receiving this error try launching hammer.exe from "steam/steamapps/common/gamename/bin"
+
== Starting Hammer in Source SDK (post-2013 SteamPipe update) ==
 +
This error is known to occur when trying to start Hammer from the Source SDK menu after receiving the [[SteamPipe]] update.
  
== Possible fixes ==
+
=== SteamPipe Solution ===
 +
You must navigate to the desired game's common bin folder and run '''hammer.exe''' from there.
 +
 
 +
For example, to run Hammer for Half-Life 2 (includes episodes), run: ''...\SteamApps\common\Half-Life 2\bin\hammer.exe''
 +
 
 +
= Possible fixes =
 
#Get SourceScheme.res from one of the GCF files or create a mod.
 
#Get SourceScheme.res from one of the GCF files or create a mod.
 
#Copy it to the ''...\SteamApps\username\sourcesdk\bin\resource\'' folder, or to the ''...\SteamApps\username\half-life 2\hl2\resource\'' folder.
 
#Copy it to the ''...\SteamApps\username\sourcesdk\bin\resource\'' folder, or to the ''...\SteamApps\username\half-life 2\hl2\resource\'' folder.

Revision as of 12:09, 3 June 2014

Русский
"Failed to load the default scheme file. The map views may be missing some visual elements"
Note:This error is related to the Hammer editor.

Possible causes

Starting Hammer using shortcuts

The error is known to occur when trying to start Hammer faster using a shortcut, instead of the Source SDK GUI. Although, it can also happen when opening Hammer from the Source SDK GUI today (Sept 2009).

Starting Hammer in Source SDK (post-2013 SteamPipe update)

This error is known to occur when trying to start Hammer from the Source SDK menu after receiving the SteamPipe update.

SteamPipe Solution

You must navigate to the desired game's common bin folder and run hammer.exe from there.

For example, to run Hammer for Half-Life 2 (includes episodes), run: ...\SteamApps\common\Half-Life 2\bin\hammer.exe

Possible fixes

  1. Get SourceScheme.res from one of the GCF files or create a mod.
  2. Copy it to the ...\SteamApps\username\sourcesdk\bin\resource\ folder, or to the ...\SteamApps\username\half-life 2\hl2\resource\ folder.

If this doesn't work, then you can use Filemon from sysinternal's to find out where Hammer is actually looking for this file.

Another possible fix (for Orange Box):

  1. Get SourceScheme.res as outlined above
  2. Copy it to \SteamApps\username\sourcesdk\bin\orangebox\bin\resource\

Yet another possible fix :

It is possible that you have deleted this line

"ToolsAppId 211 // Tools will load this (ie: source SDK caches) to get things like materials\debug,"

or only added "//" before in the GameInfo.txt of your mod or game. This can cause this error or an other when you start HLMV.

  1. If so, just rewrite the line or erase the "//".