-
Not sure why I need to write UnityTexture2D and UnitySamplerState in custom function node - can’t you just parse it and add the “Unity” bit on the front if you really need it (not sure why you do!)?! Then Texture2D and UnityTexture2D are interchangeable.
-
Mentioned before you should be able to generate an hlsl starting file by filling in the inputs and outputs and function name. Then you can forget the semantics and skip a minute or so and start with an empty function to work with.
-
Converting a standard node into a custom function should be a thing. Like I needed to add extra functionality to the triplanar node so I have to look in the docs, find the example code, build a custom function node and then… finally add my adjustments. Speed it up for us!