All Map Black (Vis)

[Wangon]

Hello, my map is all black when i using Vis on Fast or Normal, when i use expert mode with these 2 commands: -StaticPropLighting -StaticPropSampleScale 0.25 Theres only few like very big shadows/stains on some walls mountains and house but still. Anyone know to fix it? I was making this map long time and i was always rendering it without vis only for testing now when i want send this map to the workshop theres this problem. (Sorry for my bad english)

[Wangon]

Screenshots:
https://zapodaj.net/faa8056a89791.jpg.html
https://zapodaj.net/8ddddc9692d2c.jpg.html
https://zapodaj.net/104b86c5c4b55.jpg.html
https://zapodaj.net/a3694c79a02e9.jpg.html
https://zapodaj.net/86712ac1cff9a.jpg.html

[Wangon]

@up

[pivotman319 (Trans Rights FTW!)]

Originally posted by Wangon (Sdk):

i was always rendering it without vis only for testing now

VVIS is required for a map to show correctly. Without it, you and your other users will experience serious lag, and make it unplayable for most CS: GO users.

Please read this extract from the Valve Developer Community.

Originally posted by Map Compiling Theory page from VDC:

It is critical that this tool be run on every .bsp you create. If it is not run then the entire level will be visible all the time which would, in all but the simplest of box maps, make the map unplayable due to video-lag.

If you compile with VVIS, and the lighting problem doesn't go away, you have a leak inside your map.

Originally posted by Valve Developer Community:

When a leak occurs, the tools cannot know which part of the level is inside, and what part is outside, and VVIS cannot be run. If VVIS is not run, several effects may not work or look right including water and some surface properties like dust puffs.

[Wangon]

I don't have any leaks :/ Before i mean i didn't used vis because i only testing (when i publicate map i always use Normal Vis option).

[pivotman319 (Trans Rights FTW!)]

Originally posted by Wangon (Sdk):

I don't have any leaks :/ Before i mean i didn't used vis because i only testing (when i publicate map i always use Normal Vis option).

VIS is still required if you want to test your map for you and your playtesters. Playtesters may experience extreme lag on heavily detailed maps, and that could lead to heavily unplayable maps.

[Wangon]

I don't have playtesters, on other my maps while my friend was playtesting there was no lags soo i don't know what you talking about. Do you know any fix for these big black shadows? I also have new problem, 1 days ago my map was rendering like in 5 minutes, now i wanted render it again and its taking long time on portal flows (like 7h), i didn't change anything on map.

[pivotman319 (Trans Rights FTW!)]

Originally posted by Wangon (Sdk):

Do you know any fix for these big black shadows?

There is a solution, though. You'll have to change the light_environment values to those found in the Valve Developer Community CS: GO sky lists, and obviously change the skybox texture so that nobody would see a mistake in the skybox. You can find some night-time skyboxes in CS: GO's sky list, but I'd doubt it since there's mostly temporary images on the new current operation's skies.

[Wangon]

I done it already

[pivotman319 (Trans Rights FTW!)]

Originally posted by Wangon (Sdk):

I done it already

Well, since I couldn't find a solution to a seriously large map like this with super black shadows, I assume that my discussion ends here. Sorry if I couldn't help you much.

[Wangon]

Ok, thanks for trying :)

[Patriot_[GER]]

Maybe there could be another solution for this problem.
Since Valve f***ed up the lighting calculation in the Wildcard update, some people saved the responsible vrad.exe before the update.
Sadly the original post at interlopers has been deleted, but I uploaded it again here:

https://www.sendspace.com/file/evi7f6

Just extract the archive to

...\common\Counter-Strike Global Offensive\bin\

so that the vrad.exe and its dll-files are located at

common\Counter-Strike Global Offensive\bin\vrad_old\bin

Then you just need to change the vrad.exe path in hammer editor.

Note that you don't need "-StaticPropSampleScale", vrad.exe will even crash when using this compile option.


I hope this could fix your problems and if you have some questions, feel free to add me :)

[Peter Brev]

Valve fixed the lighting issue recently.

[Peter Brev]

The reply was for the user above, not you.

Your issue is may be related to improper usage of lighting entities.

Else, pitch black maps are often caused by cascade lighting which you would need to kill with ent_kill env_cascade_light or the compile process did not finish.

[Patriot_[GER]]

If you meant me, the lighting fix didn't receive me. Still having black props when compiling without -StaticPropLighting, but with it the lighting my map is still f**ed up after compiling it for 267 hours.

Thats why I am using the old vrad, it works for me.

[Peter Brev]

Originally posted by Counter-Strike: Global Offensive Dev Blog Updates:

* Fixed a regression in lighting for old community maps that interacted badly with new lighting features. Newer maps with lighting problems can be fixed by recompiling them in Hammer.

If you have CSGO and its SDK updated, it shouldn't be causing you any problems whatsoever.