Graphics (Skins) being displayed incorrectly (lower quality/messed up normal maps)

[Degeso]

Your system information

• System information from steam (Steam -> Help -> System Information) in a gist:
• Have you checked for system updates?: Yes

Please describe your issue in as much detail as possible:

Skins and graphics seem to be displayed incorrectly. Despite using the highest available graphics options, the game uses lower quality textures for skins (pretty sure the rest of the game too, but I can't really tell there.).

Following up with this, normal maps are not being shown correctly. Especially Econ gloves are affected by this, their normal maps seem either messed up, read incorrectly, or shifted (my assumption is they're being read incorrectly). This happens on all econ gloves and is not exclusive to a specific kind.

Please check the attached screenshots to see the issues. The AWP is using a lower quality texture on the linux version, and the gloves have stripes instead of being represented correctly.

The interesting bit about this is, when using Proton to launch the Windows version of the game (using -insecure as trusted mode won't work with Proton), these issues do NOT happen.

I am assuming this may be related to OpenGL.

Steps for reproducing this issue:

For me this happens without any special steps being taken. This has happened on three different installations of Manjaro (GNOME and KDE Plasma were used) on the same computer. Proprietary Drivers were always used.

Due to this, I can consistently reproduce the error, but I am unsure if this happens to others as well, my google searches and github issue searches haven't been successful so far.

Screenshots

Screenshots are attached in this order: Windows Version Linux Version

[stopnoanime]

Hi. I have the same exact issue.

System information from steam: gist

Using Proton to run the game also solves the issue. I have a AMD GPU and this issue also exist so I don't think it is driver related. Currently I am running Fedora 35 but the same issue existed on Fedora 34 too.

Screenshots:

Proton: Linux Native: Proton: Linux Native:

[ilievi187]

Wow so I have never been able to see CS:GO with high quality even that they are enabled and using same resources... Nice work !

[SupinePandora43]

Does same happen with -vulkan?

[ghost]

I can confirm the behavior is the same using linux opengl or -vulkan.

I gathered some more info while developing artwork for a custom map:

• This affects all texture files in the game.
• Client does not load any texture's mipmaps larger than resolution 1024x1024.
• Client will load the high resolution textures, if TEXTUREFLAGS_NOLOD is set in the vtf file.

I hope this information is useful! -hgn

[cassaundra]

Same issue with AMD Radeon RX Vega 64. This has been a bit of a pet peeve of mine for a while now...

[wojgie]

@kisak-valve it has been literally a year, the problem is still here. i can reproduce it on latest linux. Doesn't happen on windows. Maxed out settings. might be the same problem as cascade/primetime texture thing. -vulkan doesn't help; -allow2048 doesn't

[Monkatraz]

Also have this issue. Here is my gist. I did my own testing of the issue.

First, using -vulkan doesn't affect this. I tried combinations of things to see if I could get something to change, but nothing worked. I couldn't use Proton to compare, as that broke for CSGO recently.

Second, using mat_showmiplevels 1 reveals that certain weapons have their mipmap level too high, at least for me with a 4K monitor. I used libstrangle to force the mip LOD bias setting to -16 and it definitely improves some weapons... but unfortunately the weapons most affected by this bug had no change whatsoever. It's really weird that some weapons are fine and aren't affected by this bug (the mipmap level thing I think is unrelated), but others are.

[wojgie]

https://github.com/ValveSoftware/csgo-osx-linux/issues/2834#issuecomment-1763191309

[wojgie]

@kisak-valve the issue is still here. i must have been blind (high settings everywhere)

[wojgie]

@kisak-valve sorry for double mention but heres an image:

[wojgie]

@kisak-valve any update? anything that i can debug with? anything?