← All ideas30 Dec 2019zuorionOpenModelingShading and TexturesInteroperabilityzuorionAlex-DAndrewBulatDarknoodlesDraiseEzyPolyIIIFGIIIJhonR3dJosephbburgLauloqueNick2321NinKorrXZSZeastinadam1alexguirrebramisiusckohl_artdestrosvetdpdpforlifeetufo2fructdwjaxxtrendjohnpdelacruz26kolovedkrisjo01lacina.vojtechlsscpplucianomichele.bedendomiroslavhorvathnekketsukyoujinperludumradumoraru.artreanimaterengglishqsickmonkeydubtesturetom990v.imran2018
What?
Option for UV Map Node that would allow referring to index instead of name.
100%
Development Status:
Open
Upvote41Downvote0
z
zuorion
30 Dec 2019
4 Comments
d
dpdpforlife
It would be great if the index value had an input so you could drive that value procedurally.
1
k
krisjo01
This would be lovely to have! 😀 Especially when creating reusable shader node setups or working with multiple UV channels across many assets. Relying on UV map names can be fragile, since names may differ between files, imported assets, or even after renaming.
Being able to refer to UV channels by index instead of name would make node setups much more robust.
It would also reduce the need for hacks or workarounds and make it easier to share shader groups across projects without having to worry about UV naming conventions.
j
jason
Could this not just be handled with the exporter, where you can assign names to indices there?
z
zuorionAuthor
*
@Jason van Gumster
* Are You talking about this proposal or the other one on UV Channel topic that i made?
If this:
Exporter? I'm not aware of Blender's capabilities of exporting materials. I'm just not using it. In this proposal i just wanna improve workflow on Blender side strictly.
What?
Option for UV Map Node that would allow referring to index instead of name.
4 Comments
It would be great if the index value had an input so you could drive that value procedurally.
This would be lovely to have! 😀 Especially when creating reusable shader node setups or working with multiple UV channels across many assets. Relying on UV map names can be fragile, since names may differ between files, imported assets, or even after renaming.
Being able to refer to UV channels by index instead of name would make node setups much more robust.
It would also reduce the need for hacks or workarounds and make it easier to share shader groups across projects without having to worry about UV naming conventions.
Could this not just be handled with the exporter, where you can assign names to indices there?
* @Jason van Gumster * Are You talking about this proposal or the other one on UV Channel topic that i made?
If this: Exporter? I'm not aware of Blender's capabilities of exporting materials. I'm just not using it. In this proposal i just wanna improve workflow on Blender side strictly.