This right here is the reason texture nodes deserve to be treated better. We shouldn't be using the compositor for texture-based image manipulation.
1
c
cgvirusAuthor
*
@mauriziovit
* Hi can you clarify a bit? What is
"texture nodes"
"texture-based image manipulation" ?
Thanks.
Edit: If you are talking about shader editor then are you interested to use it? We can develop it within 1 week. But the question is:
Can your GPU handle 32K*8 (at least) buffer? Ours can chug around 16K.
Will it be used for scanned data or cheap camera data?
Blender has everything but users have limited hardware. Let us know. Thanks.
m
mauriziovit
*
@contact.cgvirus
* Texture nodes are a feature blender has which is being deprecated because of no maintenance. It lacks basic image manipulation nodes, such as offsetting, blurs and whatnot, which the compositor has. Expanding on these and directly piping it to a shader would be incredible. This workflow is definitely a reason to expand and maintain the texture nodes.
c
cgvirusAuthor
*
@mauriziovit
* I get it now. Yes, I wish that would start to be developed further more. Actually our first target was texture node editor.
Devs have some target for everything node with it as well. Also here are my proposal points why and how compositor can become the most powerful procedural texture pipeline for texture artists and vfx artists as well:
4 Comments
This right here is the reason texture nodes deserve to be treated better. We shouldn't be using the compositor for texture-based image manipulation.
* @mauriziovit * Hi can you clarify a bit? What is
Thanks.
Edit: If you are talking about shader editor then are you interested to use it? We can develop it within 1 week. But the question is:
Blender has everything but users have limited hardware. Let us know. Thanks.
* @contact.cgvirus * Texture nodes are a feature blender has which is being deprecated because of no maintenance. It lacks basic image manipulation nodes, such as offsetting, blurs and whatnot, which the compositor has. Expanding on these and directly piping it to a shader would be incredible. This workflow is definitely a reason to expand and maintain the texture nodes.
* @mauriziovit * I get it now. Yes, I wish that would start to be developed further more. Actually our first target was texture node editor. Devs have some target for everything node with it as well. Also here are my proposal points why and how compositor can become the most powerful procedural texture pipeline for texture artists and vfx artists as well:
blender.community/c/rightclickselect/DHdbbc/
Here is the devtalk: devtalk.blender.org/t/blender-2-8-design-flaw-the-texture-node-editor/6499/7