As soon you you start adding automatic smart detection like that, people will rely on it. The issue is that there is no 100% certain way of making sure textures going into the normal slot are definitely to be used as a normal map, especially not when doing dynamic / real-time construction of normals. Not sure about this really!

By default the Unity material inspector doesn't support that, and SF is currently not using a custom material inspector. This might change down the line though!

Yeah I'm closing this now, there are other threads for a custom inspector!

That's for when you're using the color property, not the Vector4 property :)

By default the Unity material inspector doesn't support that, and SF is currently not using a custom material inspector. This might change down the line though!

I'm pretty sure this is the same issue as this now: http://shaderforge.userecho.com/topic/315967-alpha-014-panner-node-sometimes-disconnects-and-break-shaders/

I'll close this thread and let the other one be open :)

Thanks for the report!

Not really, but you can make a manual panner :)