Ambient Occlusion / Tonemapping bug with Intel HD Graphics

[incognico]

This affects Intel HD Graphics 520 and 530 (and maybe more Intel GPUs).

I've noticed that in CS:GO in maps which make use of the Ambient Occlusion / Tonemapping feature, like de_lake or de_canals the maps are way too dark when playing. The maps display correctly when dead/spectating or watching gotv. As soon as you die, the whole map brightens up like it always should be, after spawning it darkens down to an almost unplayable level.

After researching this a bit it seems CS:GO, L4D2 and probably other Source games are affected by this issue, and maybe even more Intel Graphics Chipsets.

The workaround is to add the following to video.txt:
"setting.mat_tonemapping_occlusion_use_stencil" "1"

I have a Intel HD 520 (i5-6300U) using Intel Graphics Drivers Version: 15.60.2.4901 (Latest)
OS: Windows 10 Pro (Fall Creators Update)

Here are some links for reference:
ValveSoftware/csgo-osx-linux#443 (it's also affecting Windows not only Linux)
https://www.reddit.com/r/l4d2/comments/4rm90g/darkness_bug/
http://steamcommunity.com/app/550/discussions/0/357287935541576094/
https://steamcommunity.com/app/730/discussions/0/1471967615861847420/
https://steamcommunity.com/app/730/discussions/0/412446890551220183

[kisak-valve]

Hello @incognico, you should also bring this issue to the attention of your video driver vendor.

[incognico]

I am feeling uncomfortable to register at the Intel forums just to report a bug related to the Source Engine. If anyone wants to do it, this seems to be the correct place: https://software.intel.com/en-us/forums/graphics-driver-bug-reporting

Aren't Valve game developers supposed to work together with GPU vendors in such cases? I don't have the game code and can't tell whats exactly happening so my bug report will be a non-specific "x does not work in game y" instead of being able to tell the specific functions used or being able to put a code reference or example there.

The original issue (posted on osx-linux tho not specific to osx/linux) ValveSoftware/csgo-osx-linux#443 is over 2 years old now and nothing happened. IMO Valve should work together with Intel to get this issue resolved and in the meantime change video auto configuration to include the mat_tonemapping_occlusion_use_stencil workaround for the affected GPUs (which does not seem the case either, at least not in CS:GO).

Maybe the bug is described in https://en.wikichip.org/w/images/3/33/intel-gfx-prm-osrc-skl-vol16-workarounds_0.pdf but that stuff is too technical for me.

Sometimes I have the feeling Intel users are treated a lower priority than AMD/Nvidia users, especially in such cases (for no real reason). Later Gen. Intel GPUs are powerful enough to run moden games just fine, maybe not at 300 but at 90 FPS so they deserve the same support as other GPU Vendors. I don't want to get into a rant here so I just kindly ask you to internally forward the issue to the corresponding team :)

Regarding this specific issue, I think there are many people affected (also without them knowing it, just thinking the game is that dark at some maps). From what I've read now all CS:GO, L4D2, Insurgency and Black Mesa players using Intel GPUs of at least 3 generations are affected. Probably even more Source based games.

• Broadwell: Confirmed by [Linux] Incorrect rendering with intel broadwell gpus  csgo-osx-linux#443
• Skylake: Confirmed by myself
• Kaby Lake: https://steamcommunity.com/app/222880/discussions/1/1618346571421559859/ (Game Insurgency)

Black Mesa: https://steamcommunity.com/app/362890/discussions/0/358415738209258977/

The more I google the more affected games and threads about "darkness bug" / "brightness issue" come up.

BTW: As CS:GO is affected you could the CS:GO Label too. Well "Source 1 Engine" probably is the most correct :)

[incognico]

Speaking about CS:GO now: I've just checked https://github.com/SteamDatabase/GameTracking-CSGO/blob/master/csgo/cfg/moddefaults.txt and saw that there actually is a forcing of mat_tonemapping_occlusion_use_stencil for some older Intel GPUs but appearantly it is missing tons of newer device IDs for Intel HD Graphics, namely all currently supported Intel GPU models (Generation 4,5,6,7,8).

[JacksonHill]

Coffee lake is affected too:
Intel® UHD Graphics 630

Confrimed by myself for: Left for dead 2, CS:GO

[incognico]

The last newer 2 versions of Intel gpu drivers still do not fix the problem, I guess it's time for valve to update that moddefaults file for the affected games /sigh/

[incognico]

For reference:

mat_info tells me:

vendor id: 0x8086
device id: 0x1916

the autogenerated video.txt includes (seems to be decimal there):

	"VendorID"		"32902"
	"DeviceID"		"6422"

the last entry in the moddefaults.txt file is:

	"833"
	{
		"name" "Intel Unknown"
		"vendorid"	"0x8086"
		"mindeviceid"	"0x0000"
		"maxdeviceid"	"0xffff"
		"makemelast"	"1"
		"setting.csm_quality_level"	"3"
		"setting.mat_software_aa_strength"	"1"
		"setting.defaultres"	"2560"
		"setting.defaultresheight"	"1600"
		"setting.gpu_level"	"2"
		"setting.mat_forceaniso"	"1"
		"setting.mat_grain_scale_override"	"1"
		"setting.mat_tonemapping_occlusion_use_stencil"	"1"
	}

Theoretically this entry should match the IDs and the correct settings would be applied, but it does not.

[magikmw]

Still occuring on Kaby Lake HD Graphics 620.

[chinoto]

I am/was* also affected by this issue.
CPU: Intel(R) Core(TM) i5-5200U
GPU: Intel(R) HD Graphics 5500 (Broadwell GT2)
OS: openSUSE 15.1
Mesa: git20191227 (happens with standard repo version as well)
Driver: i965

*I'm affected by another issue preventing L4D2 from starting and happened to spot this one while looking.

[hashar]

Note someone filed it a couple years ago at https://community.intel.com/t5/Graphics/Well-known-Valve-Source-1-engine-bug/td-p/556000

Unclear whether it is a bug in the Intel driver or in the Source 1 engine though. Thank you very much to have mentioned setting.mat_tonemapping_occlusion_use_stencil

[oolongtea]

still happening on a brand new thinkpad 2022; more details here: ValveSoftware/csgo-osx-linux#443 (comment)