LightmappedReflective: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
(Added example vmt)
(Adding proxies to a lightmappedreflective causes the texture to not be drawn. This is very weird, and probably suggests there are some automatically included proxies, which arent documented yet. probably.)
Line 28: Line 28:
  "$bumpframe" "0"
  "$bumpframe" "0"
  }
  }
{{bug|Adding proxies to a lightmappedreflective causes the texture to not be drawn.}}
{{todo|Could this be because it includes some default proxy in order for it to work, and once there is a user-defined proxy, those "behind the scenes" proxies are no longer there?}}

Revision as of 18:54, 1 June 2019

Stub

This article or section is a stub. You can help by expanding it.

LightmappedReflective is the shader used by func_reflective_glass. This shader renders real-time reflection and refractions similar to Water (shader).

Example

The example shown here is materials/glass/reflectiveglass001.vmt

"lightmappedreflective"
{
	"%tooltexture" "dev/flat_normal"
	"$refracttexture" "_rt_WaterRefraction"
	"$refractamount" "0"
	"$refracttint" "[.5 .5 .6]"

	"$reflecttexture" "_rt_WaterReflection"
	"$reflectamount" "0"
	"$reflecttint" "[1 1 1]"

	"$fresnelpower" "0"
	"$minreflectivity" "0.8"
	"$maxreflectivity" "1.0"
	
	"$normalmap" "dev/flat_normal"

	"$surfaceprop" "glass"
	"$bumpframe" "0"
}
Icon-Bug.pngBug:Adding proxies to a lightmappedreflective causes the texture to not be drawn.  [todo tested in ?]
Todo: Could this be because it includes some default proxy in order for it to work, and once there is a user-defined proxy, those "behind the scenes" proxies are no longer there?