Out of memory loading solid

From Valve Developer Community
Revision as of 01:39, 7 February 2012 by Pitt1993 (talk | contribs)
Jump to: navigation, search

This error appers while loading a VMF. Caused by invalid vertices data in solid structure. It is rarely seen but can appear if there are too many solids at once tied to an entity or the world. Simply just try to save your project as many times as you can and reload hammer while creating complicated solids that are combined with func_details. It can also appear while rtating func_details entities that contains a lot of construction blocks (meanwhile during rotation this entity will disappear from the world because Hammer has misplaced vertices) To do: write a better description


Here is an example how to erase WRONG solids:

1. Open your map file with Notepad++ and go to line that Hammer tells you where ERROR:7 exist. 2. You should find a SOLID group there. 3. While looking at it's settings it will look like this (notice invalid vertex positon data in the plane line):

solid
	{
		"id" "33026"
		side
		{
			"id" "21912"
			"plane" "(1.#QNAN 1.#QNAN -132) (1.#QNAN 1.#QNAN -168) (1.#QNAN 1.#QNAN -168)"
			"material" "TOOLS/TOOLSNODRAW"
			"uaxis" "[1 0 0 0] 0.25"
			"vaxis" "[0 -1 0 0] 0.25"
			"rotation" "0"
			"lightmapscale" "16"
			"smoothing_groups" "0"
		}
		side
		{
			"id" "21911"
			"plane" "(1.#QNAN 1.#QNAN -140) (1.#QNAN 1.#QNAN -176) (1.#QNAN 1.#QNAN -176)"
			"material" "TOOLS/TOOLSNODRAW"
			"uaxis" "[1 0 0 0] 0.25"
			"vaxis" "[0 -1 0 0] 0.25"
			"rotation" "0"
			"lightmapscale" "16"
			"smoothing_groups" "0"
		}
		side
		{
			"id" "21910"
			"plane" "(1.#QNAN 1.#QNAN -132) (1.#QNAN 1.#QNAN -132) (1.#QNAN 1.#QNAN -140)"
			"material" "TOOLS/TOOLSNODRAW"
			"uaxis" "[0 1 0 0] 0.25"
			"vaxis" "[0 0 -1 0] 0.25"
			"rotation" "0"
			"lightmapscale" "16"
			"smoothing_groups" "0"
		}
		side
		{
			"id" "21909"
			"plane" "(1.#QNAN 1.#QNAN -176) (1.#QNAN 1.#QNAN -176) (1.#QNAN 1.#QNAN -168)"
			"material" "TOOLS/TOOLSNODRAW"
			"uaxis" "[0 1 0 0] 0.25"
			"vaxis" "[0 0 -1 0] 0.25"
			"rotation" "0"
			"lightmapscale" "16"
			"smoothing_groups" "0"
		}
		side
		{
			"id" "21908"
			"plane" "(1.#QNAN 1.#QNAN -168) (1.#QNAN 1.#QNAN -132) (1.#QNAN 1.#QNAN -140)"
			"material" "TOOLS/TOOLSNODRAW"
			"uaxis" "[1 0 0 0] 0.25"
			"vaxis" "[0 0 -1 0] 0.25"
			"rotation" "0"
			"lightmapscale" "16"
			"smoothing_groups" "0"
		}
		side
		{
			"id" "21907"
			"plane" "(1.#QNAN 1.#QNAN -176) (1.#QNAN 1.#QNAN -140) (1.#QNAN 1.#QNAN -132)"
			"material" "TOOLS/TOOLSNODRAW"
			"uaxis" "[1 0 0 0] 0.25"
			"vaxis" "[0 0 -1 0] 0.25"
			"rotation" "0"
			"lightmapscale" "16"
			"smoothing_groups" "0"
		}
		editor
		{
			"color" "0 219 116"
			"visgroupshown" "1"
			"visgroupautoshown" "1"
		}
}

4. By the look there is no such location as written above "1.#QNAN".

Confirm:(it is probably the solid with QUERY NO ASSINGED to NORMALS)

5. Simply erase all wrong solid data from your VMF and that ought to bring your level back to usable form.

--Pitt1993 02:37, 4 February 2012 (PST)