![](https://cdn.userecho.com/characters/99.png?1)
0
Fixed
Manually created shaders causes the Inspector extension to throw a warning
Here's a good one:
Once ShaderForge is installed, selecting manually created shaders causes the ShaderForge Inspector extension to try and compile that shader, then throw a warning. Considering that it has a button linking to "Replace with Shader Forge shader" -- this seems dangerous -- maybe there could be a change to the interface.
- Rather than a warning, the inspector notes that the shader is "not a ShaderForge shader".
- The inspector then presents an option to open ShaderForge and replace it - with a popup warning about the destructive editing the user is about to do.
- Maybe stay away from the iconography of warnings for shaders which aren't built in ShaderForge -- reserve it for misconstructed ShaderForge shaders.
Answer
![](https://cdn.userecho.com/characters/70.png?1)
It is dangerous, which is why there is a warning icon :)
There is a popup already when you click that button to confirm clearing the entire shader etc.
![](https://cdn.userecho.com/characters/70.png?1)
Answer
Fixed
I've removed the warning that is thrown into the console, the rest remains the same for now :)
Customer support service by UserEcho
I've removed the warning that is thrown into the console, the rest remains the same for now :)