[csgo] Lighting on props broken since Wildfire Update? (+ Possible fix)

    Quote from baem123

    You added it at "additional game parameters", cut it and click on "Expert..."

    Now choose the fast configuration in the top left drop down menu. Go to "$light_exe" and paste these parameters there. Then click "GO" to compile.

    lets face it: that was realy noobish from me.

    But it worked and now everything is fine with my map again. Thank you very much!

    Quote from MagnarJ

    Hi there! 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.


    We'll have the full documentation for the upgraded compile tools out early next week.

    Hello there!

    Does the -StaticPropSampleScale x parameter affect the .bsp filesize in any way? My current project just raised around 30-35mb with the latest update and i can't seem to get it down by setting the value to 0.25. I've also tried setting the value to 1 and 4, still ending up with the same filesize.

    I'm not sure if i got something wrong, here's my parameter line for $light_exe:
    -textureshadows -hdr -StaticPropLighting -StaticPropSampleScale 0.25 -StaticPropPolys -game $gamedir $path\$file

    If there is nothing that can be done about the increase in filesize, would it perhaps be possible to use a previous version of vrad.exe? In that case, would you happen to have it available?

    I really need to get my .bsp filesize lower due to the community fastDL servers being capped at 150mb.

    Quote from Wrakk

    With the new Wildfire Update came a whole new Nuke, which included a lot of new assets. So, I go into Hammer and place down a few of the new props, then compile. They're all completely black. I tried to just compile older props from other maps, and they are also all black. Anyone else having this problem?

    Pics:

    Hidden Content

    I have the same problem

    :???:

    Is anyone else having problems with HDR? All of my compiles are turning up with blue shadow highlights. The only solution I have found is compiling without HDR.

    Quote

    I'm kind of having same problem as @MaanMan, but my shadows cast on the floor are solid black. If they carry on over to a wall, that shadow is fine. I also have odd light reflections on walls and anywhere a light source is, the weird, black, inky shadow disappears.

    This has been replicated on @Vaya's machine as well, using his originally non-problematic compile settings:

    http://imgur.com/a/dahc0

    Quote from baem123

    You added it at "additional game parameters", cut it and click on "Expert..."

    Now choose the fast configuration in the top left drop down menu. Go to "$light_exe" and paste these parameters there. Then click "GO" to compile.

    I did this and now it just crashes my vrad. No clue what's going on.

    EDIT: Can someone who got theirs to work give me their settings? I just want to be able to map again without dealing with this. I can't compile anymore without vrad crashing. Thanks valve.

    Quote from MaanMan

    Is anyone else having problems with HDR? All of my compiles are turning up with blue shadow highlights. The only solution I have found is compiling without HDR.

    Hidden Content

    This problem was solved by removing the light_environment and adding a new light_environment with the exact same settings. Looks like the entity was somehow corrupted. Funky stuff.

    Quote

    This problem was solved by removing the light_environment and adding a new light_environment with the exact same settings. Looks like the entity was somehow corrupted. Funky stuff.

    Can confirm this does not work (for me). Still have solid dark shadows with occasional blue bits on props and when viewing shadows at a very shallow angle from large distance.

    Quote from jackophant

    Can confirm this does not work (for me). Still have solid dark shadows with occasional blue bits on props and when viewing shadows at a very shallow angle from large distance.

    I had the same problem here.
    I fixed it, by removing the light_directional,...try to do it, if you have one.

    This is sad. :sad:

    Quote from K

    I had the same problem here.I fixed it, by removing the light_directional,...try to do it, if you have one.

    This is sad. :sad:

    Ah, yeah I'll give that a shot.

    I have to put my hands up and say I don't actually understand what the light_directional is meant to do. It seems to fulfil similar/same role as light_environment.

    I only have it due to taking lighting from another map and didn't take the time to understand what it does. Documentation on it is pretty barren as well.

    Added -StaticPropLighting -StaticPropSampleScale 0.25 to $light_exe parameters in "fast" option in expert compile and this error appear when compiling:

    Code
    Command line: "E:\Steam\steamapps\common\Counter-Strike Global Offensive\bin\vrad.exe" "-bounce" "2" "-noextra" "-game" "E:\Steam\steamapps\common\Counter-Strike Global Offensive\csgo" "e:\steam\steamapps\common\counter-strike global offensive\sdk_content\maps\de_industry" "-StaticPropLighting" "-StaticPropSampleScale" "0.25"
usage  : vrad [options...] bspfile
example: vrad c:\hl2\hl2\maps\test

    And vrad crashes.

    How I can fix it? :c

    put the options before the BSP file


    Code
    -bounce" "2" "-noextra"
    Code
    "-StaticPropLighting" "-StaticPropSampleScale" "0.25"
    Code
    "-game" "E:\Steam\steamapps\common\Counter-Strike Global Offensive\csgo" "e:\steam\steamapps\common\counter-strike global offensive\sdk_content\maps\de_industry"


    or something like that. not 100% on this syntax as i don't touch these often.

    Quote from jackophant

    Ah, yeah I'll give that a shot.

    I have to put my hands up and say I don't actually understand what the light_directional is meant to do. It seems to fulfil similar/same role as light_environment.

    I only have it due to taking lighting from another map and didn't take the time to understand what it does. Documentation on it is pretty barren as well.

    light_directional is like the twin of env_cascade_lighting, the entity that controls the cascade shadow mapping (super accurate real time shadows). The light_environment is what casts the light and sets angles and the other two are what control the shadow maps.

    Saying that, I don't actually think they're necessary to have because the shadow maps get generated without either of the entities.

    Quote from sevin

    light_directional is like the twin of env_cascade_lighting, the entity that controls the cascade shadow mapping (super accurate real time shadows). The light_environment is what casts the light and sets angles and the other two are what control the shadow maps.

    Saying that, I don't actually think they're necessary to have because the shadow maps get generated without either of the entities.

    Good to know, thanks :)

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login