Differences

This shows you the differences between two versions of the page.

--- camera [2021/06/13 03:27] – uninomiconadmin
+++ camera [2025/01/15 04:35] (current) – external edit 127.0.0.1
@@ Line 5: / Line 5: @@
 SetReplacementShader will not render objects if their original materials don't contain any properties required by the replacement shader. For example, if your replacement shader uses _MainTex, and there is an object in the scene that doesn't have _MainTex, it won't be rendered at all.
-The 'tag' argument accepts the name of a tag in the 'Tags' property block of the shader. When provided, Unity will pick a sub-shader from the replacement shader that matches the value of the Tag. So if the tag argument is 'RenderType', you can provide two sub-shaders 'Opaque' and 'Transparent' in the replacement shader, and Unity will pick the sub-shader that matches the original object.
+SetReplacementShader will use the Materials of the existing objects in the scene((all of the textures and instance data is still sent to the replaced)). However, it only seems to apply keywords that are registered as ''multi_compile''. Per-material keywords registered with ''shader_feature'' do not get applied. For example, if you call SetReplacementShader with the default URP ''Lit.shader'', these keywords will all be turned off:
+{{:rider64_ulivqdfbym.png}}
 Shaders can be replaced in the SceneView using ''[[sceneview|SceneView]].SetSceneViewShaderReplace''.