Resolved Globally suppress pow(f,e) negative f warning

How can I suppress this warning, I get many of them spammed on each compilation of my shaders.

The warning even says it is only a suggestion, in many cases, I'm not concerned with negative values and don't wish to add an abs here.

Shader warning in 'ShaderName': pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them at line XXXX (on d3d11)

 

Yeah, these are from custom shaders I have authored using AmplifyShaderEditor. I have attached a culprit

 

That's a pretty poor suggestion as it changes the semantics of the shader.

I can make my own copy of the template file from ASE, then recompile all my shaders via ASE to updating it to the abs/clamped etc input. Though in this case, I do not care about negative values, the warning even says "if you expect them" which I don't.

Ideally, Unity wouldn't implement developer assists that can result is so much crap going into the console with no straight forward option to take. In this case, the ideal solution is to exclude this warning from ever logging, something I can do in c# but not shaders

 

Yep, that has suppressed the warning immediately, perfect!

 

I had no idea we could suppress warnings like this. You're a life lifesaver.
Many Thanks

 

Is there any chance you also know the "Implicit Truncation of vector type" warning code to disable.
I searched but couldn't find it on the internet.

 

Just to add that abs() has zero cost in shaders, because it isn't an actual instruction but a flag passed to other instructions which tells them to drop the sign. Same for saturate().

 

@aleksandrk is there somewhere list of all warning codes?

 

Found it, thanks

https://docs.microsoft.com/en-us/windows/win32/direct3dhlsl/hlsl-errors-and-warnings

 

Is there a way to suppress warnings coming from a shader graph?

I've tried out creating a custom node with `#pragma warning disable` but no luck.

 

hello sir
similar subject
do you have one to disable "automatically setting target of LOD_FADE_CROSSFADE to 3.0"

cheers

 

yup i know its harmless
in 2019.4.14 standard even setting shader model 3.0 does not stop it

 

thank you it is filed in Case 1358042


cheers thank !!!

 

How would I include that in Shadergraphs?

 

in SG i would suspect if it does not have a way to add it you could just use a saturate or a few max nodes to insure it does not nan

 

Thank you for the error code and the warning itself. If I use it, I will only use when I finished the shader and also when I am sure the truncation is not a problem anyway.
Thanks again

 

a follow up to show progress
they will close the ticket without fixing as they say we can clear the warning thru the clear option in console
I only wish Unity had more people like you sir,, as some of them just don't seam to have pride in the work at the same level ... thank you for trying to help, Cheers

--------------------------
Hi,

This warning, just like it says in the information you sent, is harmless. This warning is meant to show what is happening upon activating LOD Crossfade for the first time. If you turn it on and press Play, you will get that warning, but if you clear the console and leave Play mode, you won't get that same warning anymore. However, I've attached a video showcasing how you can stop warnings from showing up on your console. It's a toggleable option so you can turn it on and off on your whim. That being said, we will be closing this case and if the solution does not suffice regarding your issue, don't hesitate to contact us again and we will reopen this case. That being said best of luck with your projects!

Thanks,
xxxxxxxxxxxxxxxx
Customer QA Team
--------------------------

 

if its still open Case # 1358042