Noise with no vector input inconsistent between shader and geo nodes #112249

New Issue

Gurra · 2023-09-11T19:00:40+02:00

Gurra commented

2023-09-11 19:00:40 +02:00

Not really a bug, but a inconsisity that have been bothering me for a while (and I have understood that Blender do not like stuff being inconsequent).
When using Noise in geometry nodes with nothing in the Vector input the coordinate will be object based, but when using Noise in the shader editor with nothing in the Vector input it will be based on Generated coordinates. Personally almost always want it set to Object because it feels more natural with no stretching if the object happened to be long/tall/wide or whatever, but also because it feels more "stable".
It have happened to me multiple times before that I created something with any texture node and later when adding stuff and realizing that the texture on the object all of a sudden look a lot differently because of this. Or even if you create a long box and slap a noise onto it it will look stretched where some people maybe will try to compensate it using a Texture Mapping node changing the scale etc. So both for me and probably many others and especially beginners I think it would be better and more intuitive and more consistent to have texture nodes in the shader editor to be defaulted to Object space instead of Generated. And seeing that 4.0 is a breaking release I thought that this might be a perfect opportunity to "fix" this :)

Not really a bug, but a inconsisity that have been bothering me for a while (and I have understood that Blender do not like stuff being inconsequent). When using Noise in geometry nodes with nothing in the Vector input the coordinate will be object based, but when using Noise in the shader editor with nothing in the Vector input it will be based on Generated coordinates. Personally almost always want it set to Object because it feels more natural with no stretching if the object happened to be long/tall/wide or whatever, but also because it feels more "stable". It have happened to me multiple times before that I created something with any texture node and later when adding stuff and realizing that the texture on the object all of a sudden look a lot differently because of this. Or even if you create a long box and slap a noise onto it it will look stretched where some people maybe will try to compensate it using a Texture Mapping node changing the scale etc. So both for me and probably many others and especially beginners I think it would be better and more intuitive and more consistent to have texture nodes in the shader editor to be defaulted to Object space instead of Generated. And seeing that 4.0 is a breaking release I thought that this might be a perfect opportunity to "fix" this :) ![noise coordinates2.jpg](/attachments/4be2deee-c284-4966-92fd-11075c8908a7)

noise coordinates2.jpg

331 KiB

noise.blend

8.5 MiB

Gurra added the

labels 2023-09-11 19:00:40 +02:00

YimingWu commented

2023-09-12 05:39:03 +02:00

For some reason I can't get color attribute to render in cycles atm... but can confirm that whether to connect object coordinate will affect the size of noise texture in shader nodes.

YimingWu added

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Noise with no vector input inconsistent between shader and geo nodes #112249