Difference between revisions of "Static Props show up black"

From Valve Developer Community
Jump to: navigation, search
(Added Valve statement)
m (fix)
Line 1: Line 1:
--[[User:Petethegoat|Petethegoat]] ([[User talk:Petethegoat|talk]]) 06:19, 20 February 2016 (UTC)After the Operation Wildfire update, many people have run into issues with static props not receiving lighting.
+
After the Operation Wildfire update, many people have run into issues with static props not receiving lighting.
  
 
To solve this issue, go to the expert compile window, and select the $light_exe command. Then, in the 'Parameters' textbox, prepend <code>-StaticPropLighting</code>.
 
To solve this issue, go to the expert compile window, and select the $light_exe command. Then, in the 'Parameters' textbox, prepend <code>-StaticPropLighting</code>.

Revision as of 06:19, 20 February 2016

After the Operation Wildfire update, many people have run into issues with static props not receiving lighting.

To solve this issue, go to the expert compile window, and select the $light_exe command. Then, in the 'Parameters' textbox, prepend -StaticPropLighting. For the default compilation settings, your parameters should be -StaticPropLighting -game $gamedir $path\$file.

This will fix your static props, and allow them to receive lighting correctly again.


See also:

"We released an update to VRAD in the latest update. To get proper lighting on static props, you will need to run with -StaticPropLighting in VRAD, which sadly isn't updated (yet) in Hammer for the default, quick compile settings. This flag will increase compile times, but to help with iteration we also included the ability to tweak the quality of the new lighting by adding -StaticPropSampleScale x parameter (16 = slow, high quality, 4 = default and 0.25 = fast, low quality) which is useful if you want to speed up compile times. Note that adding -final is the same as having -StaticPropLightingScale 16."