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

[Guest]

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:

Edited February 19, 2016 by Wrakk

[baem123]

cumfirmed

 

[Aztk]

Unfortunately yes, i have this bug too :c

[jackophant]

did a compile last night. My props were OK, but all my shadows were a weird harsh inky black.

[Guest]

For some reason, this only happens with the default compile settings.  Doing a full compile makes everything work again. Strange issue, considering default compiles always worked before. 

Edited February 19, 2016 by Wrakk

[ElectroSheep]

Default compile settings are forbidden on this website, sorry bro... 

[FMPONE]

I notice that this brings high quality and low quality visual settings in line with each other. Maybe this was intentional?

[Quotingmc]

I notice that this brings high quality and low quality visual settings in line with each other. Maybe this was intentional?

That is an interesting idea. I presume you have some contact with VALVe due to Cache and Santorini having made the operation. Could you ask them?

[Guest]

Default compile settings are forbidden on this website, sorry bro... 

I thought default was just faster to compile? I guess I'm nothing but a fool. A dirty, disgusting fool.

Edited February 19, 2016 by Wrakk

[ElectroSheep]

Haha, ho you !

You just need to know that when it's question of render, fast lighting make things really gross, but this case seemas a bit too far for a classic fast compile.

[JustFredrik]

I just got a problem but the other way around, with brushes black and props normal. Maby not connected to the update but worth mentioning.

Edit: After some compiles and changes to the map, it worked fine, And looks normal again. Still don't know if it was connected to the update or what fixed it.

Edited February 19, 2016 by JustFredrik
fixed it

[tomm]

I've noticed static props aren't lit properly in my case, info_lighting seems to be ignored or not as effective as it used to.

also computing static prop lighting takes a lot longer than it did before the update, yet the props look the same or maybe even worse.

[JustFredrik]

After the update my shadows on the map is extreamly sharp, compared to pre-update compiles without changing any compile settings. They probably made some changes to make maps look better and on some systems this update resulted in broken lighting.

But hey, it wouldn't be a true CSGO update without bugs and glitches!

Edited February 19, 2016 by JustFredrik

[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.

[El Moroes]

Cool, thanks ! 
And also, thanks for fixed the "3D Shaded Textures Polygons" view of Hammer 

Edited February 19, 2016 by El Moroes