Exposed Texture Input for Image Texture Node
I think this didn't get enough attention last time this problem was mentioned by v.imran2018
As for now you should manually pick a texture in Image texture node input. Because of that you cannot really use Image Texture Nodes inside custom Node Groups.
Two Solutions:
- Add a Texture input and Texture datatype and be able to map Texture to an object coordinates via Image Texture Node as shown below:
2. Add a File input and File datatype. The same as above but now you input a filename instead of a texture:
2 Comments
The texture node system should get a redesign. The redesign has been mentioned a few times and would be something we want to address in 2022.
I think it's good idea to split image texture node into 2 nodes: image mapping and image data like discussed in this thread on devtalk: devtalk.blender.org/t/input-socket-for-image-texture-shader-node/19601/5
Right now box projection textures are very annoying to work with since projection settings are part of image datablock.