Fatal error loading pixel shader vertexlit_and_unlit_generic_ps30 (096F2140)

[overdo$e]

Im getting this error when joining my map and it makes csgo crash. Reminds me of the error people were getting in september which was eventually fixed by valve. Not sure what to do here. Has anyone been encountering this error? 

Thanks in advance

[grapen]

You have a material with incompatible parameters. You can cordon compile the map until you find it, or just go through each vmt with for instance VMT Editor if you don’t have a lot of custom content.

[overdo$e]

1 hour ago, grapen said:

You have a material with incompatible parameters. You can cordon compile the map until you find it, or just go through each vmt with for instance VMT Editor if you don’t have a lot of custom content.

Honestly I do have a lot of Custom content, almost all of it is custom. Weirdly enough I finished this map in august and it didnt have this error. When I wanted to release it this week it showed it. 

Anyways, ill try to cordon compile it a few times, thanks.

[overdo$e]

I think its worth mentioning that this only occurs when the details and shaders are set to Low ingame. So im not sure its actually due to the parameters of certain VMT's.

[grapen]

42 minutes ago, overdo$e said:

Honestly I do have a lot of Custom content, almost all of it is custom. Weirdly enough I finished this map in august and it didnt have this error. When I wanted to release it this week it showed it. 

Anyways, ill try to cordon compile it a few times, thanks.

Yeah they changed how the engine handles these incompatible errors this fall, before they would not even give you a warning, though some users would experience visual glitches. These days the game just straight up crash.

 

Also, the fact that there's an issue with an unlit generic shaders should give some helpful info, you probably don't have a lot of those?

Edited January 9, 2018 by grapen

[overdo$e]

1 hour ago, grapen said:

Also, the fact that there's an issue with an unlit generic shaders should give some helpful info, you probably don't have a lot of those?

Not really sure what classifies as an unlit generic shader. Sorry, I havent been mapping for a while now, just want to fix this map and put it out. Thanks again for the help

[grapen]

10 hours ago, overdo$e said:

Not really sure what classifies as an unlit generic shader. Sorry, I havent been mapping for a while now, just want to fix this map and put it out. Thanks again for the help

The first line of your material files reference the shader, such as vertexlitgeneric, lightmappedgeneric, unlitgeneric, water etc.

Edited January 10, 2018 by grapen

[Swaggernaut]

remove some of your custom models in your map to see which one is causing the error. start with one, test, if its good, add another until you get the error again. Then you'll know which one is causing the error.

 

I would also say to check your .qc file to see you are referencing the correct model in the LOD lines of code. you might have mistyped a model's name or forgot to add a line