Material not found!: [texture]
Description:
The error is self-explanatory. Somewhere in your map you have referenced a texture that doesn't exist. Perhaps you used a texture from another modification or game you haven't correctly set your current game up for?
Solution:
Make sure you have your mod paths set up correctly and that you are including all mod contents you need.
The affected object may not work/appear properly
Last contribution: zombie@computer
Material "[texture]" not found
Description:
The error is self-explanatory. Somewhere in your map you have referenced a texture that doesn't exist. Perhaps you used a texture from another modification or game you haven't correctly set your current game up for?
Solution:
Make sure you have your mod paths set up correctly and that you are including all mod contents you need.
The affected object may not work/appear properly
Last contribution: zombie@computer
Found a displacement edge abutting multiple other edges
Description:
A displacement is touching more than one other displacements at the same point along one of its edges; in other words: at some point, three displacements are touching each other along an entire edge. This may cause lighting errors, as vrad doesn't know which displacements need to have their light smoothed out, if you know what i mean. I guess it can also be a wanted situation, in which cause this 'error' can be ignored.
Solution:
The usual cause i can think of is the accidental non-deletion of displacements along the sides of brushes. Eg, if you have two brushes next to each other, and their tops displaced, and you accidentally also displaced the vertical brushsides between these two, you get a T-shaped intersection of three.
image: purple: side that should've been destroyed, red: the edge.
This is no real error, but it could be the cause of lighting anomalies. There is no easy way to find the displacement either, the fastest way would be to go through your displacements one by one.
Generally, this error may be ignored
Last contribution: Anonymous
fastvis = true
Description:
You seem to be running vvis in -fast mode. This is okay for testing purposes, but mind that this will cause:
Strange compile errors, like 'cluster saw into cluster' errors
Strange errors ingame (including unexpected crashes)
Hitting limits ingame, by skipping essential optimization processses
Lower performance ingame
Solution:
If you experience any of these problems, and don't have any specific clues for the cause, please try to compile without the -fast option, see if that helps. If compiling without -fast is taking too long /seems to crash vvis, you may need to optimize your map using func_detail
Last contribution: Anonymous
WARNING: Too many light styles on a face at (
Description:
There's a face with too many different light styles of light shining on it. (more than six). For every switchable light (that is: any light that is named or has a custom appearance) shining on a face, vrad.exe makes a new lightstyle. Basically, it calculates how the face looks like when:
-light 1 is on and light 2 is off
-light 1 is on and light 2 is on
-light 1 is off and light 2 is off
-light 1 is off and light 2 is on
I'm sure you understand how 6 switchable lights make 2 ^ 6 lightstyles, and how this enormous amount of memory has to be saved somehow. and limited.
Solution:
To stop this error, remove lights, dont give the light names unless you need to, make sure certain lights dont shine on the face (max_shining distance or by blocking it with brushes) or simply dont use that much switchable lights. Dynamic lights are not used by vrad.exe thus dont count. Lights with the same names are counted as the same lights. Find the location of the error using the coordinates.
See also:
Reference: Finding the cause of errors
The affected object may not work and/or cause general errors
Last contribution: Anonymous
Error loading studio model "[model]"!
Description:
You have used the wrong model with the wrong entity, or there is another reason the model couldn't be loaded, like an invalid location, errors in the file etc.
Solution:
Either change the model, or the entity (eg. like it says in the error, use a prop_physics, prop_dynamic or prop_physics_multiplayer) or whatever the compiler tells you you should use). Just as a thumb rule:
-anything that can be picked up is prop_dynamic or prop_physics(_multiplayer)
-anything thats completely static is prop_static (you may alsop recognise these with invisible backsides)
-anything with dynamic shapes (eg. bodies, matrasses) is prop_ragdoll.
There are exceptions offcourse, as allways. The GUI model browser shows you exactly what types of entity a model is suited for.
You can find the entity with the offending model using entity report. Enter for key 'model' and for value '[model]'.
See also:
WIKI: Prop types
The affected object may not work/appear properly
Last contribution: Anonymous
Error! prop_static using model "[model]", which must be used on a dynamic entity (i.e. prop_physics). Deleted.
Description:
You have used the wrong model with the wrong entity.
Solution:
Either change the model, or the entity (eg. like it says in the error, use a prop_physics, prop_dynamic or prop_physics_multiplayer or whatever the compiler tells you you should use). Just as a thumb rule:
-anything that can be picked up is prop_dynamic or prop_physics(_multiplayer)
-anything thats completely static is prop_static (you may alsop recognise these with invisible backsides)
-anything with dynamic shapes (eg. bodies, matrasses) is prop_ragdoll There are exceptions offcourse, as allways.
The GUI model browser lists all entity types compatible with a certain model
See also:
WIKI: Prop types
The affected object may not work/appear properly
Last contribution: Anonymous
Material [texture] uses unknown detail object type [model]!
Description:
One of your textures is scripted to emit detail props (the grass thingies that appear on displacements), but the detail props specified are not defined in the mod's data files.
Solution:
Usually this error is caused by mindlessly porting textures from other mods, without porting the detail props file. The fix is to either get these detail props from that other mod, or fix the texture so it emits detail props that exist in the current mod.
See also:
WIKI: Displacement grass
WIKI: Detail_props
The affected object may not work/appear properly
Last contribution: Anonymous
NODRAW on terrain surface!
Description:
You aren't allowed to have the "tools/nodraw" texture one a displacement.
Solution:
There are two possible causes, you accidently covered a displacement face in nodraw or you accidently made a hidden face a displacement. In order to fix it in either cases, uncheck the "auto" visgroup, then check only the "displacements" visgroup. Now, look round the map see if nodraw is anywhere you wanted a real texture. If found open the material browser and find and replace the nodraw texture with any other texture. If there's no vibisible displacement faces with nodraw you'll probably want to destroy them. Open the material browser, check "Only show used textures", select NoDraw and press "Mark". Open up the face edit sheet, and click "Destroy" on the displacement tab.
See also: Reference: Finding the unfindable
The affected object may not work/appear properly
Last contribution: Angry Beaver
--------------------------------------------------------------------------------------------------------------------------------------------------------------
Basically your map has many model errors, texture errors, and lighting problems.
I compiled with everything fast just to take a look at the console log
