Cannot scale textures in compositor #51070

New Issue

Dwight Martin · 2017-03-28T18:55:23+02:00

Dwight Martin commented

2017-03-28 18:55:23 +02:00

System Information
Windows 7 and 10

Blender Version
Broken: 2.78c
Worked: (optional)

Short description of error

Exact steps for others to reproduce the error
Based on a (as simple as possible) attached .blend file with minimum amount of steps
Create a new texture in the texture tab. Make the type noise. Open the compositor, add a Texture node, select the noise texture, connect Texture node to a scale node and the scale node to a viewer node. Adjusting the X and Y values have no effect on the texture. Other texture types(distorted noise, marble, etc) can be scaled along X, but not Y.noise_scale.blend

**System Information** Windows 7 and 10 **Blender Version** Broken: 2.78c Worked: (optional) **Short description of error** **Exact steps for others to reproduce the error** Based on a (as simple as possible) attached .blend file with minimum amount of steps Create a new texture in the texture tab. Make the type noise. Open the compositor, add a Texture node, select the noise texture, connect Texture node to a scale node and the scale node to a viewer node. Adjusting the X and Y values have no effect on the texture. Other texture types(distorted noise, marble, etc) can be scaled along X, but not Y.[noise_scale.blend](https://archive.blender.org/developer/F526595/noise_scale.blend)

Dwight Martin commented

2017-03-28 18:55:23 +02:00

Changed status to: 'Open'

Dwight Martin commented

2017-03-28 18:55:23 +02:00

Added subscriber: @dwightmartin

Jeroen Bakker commented

2017-03-28 21:30:36 +02:00

Added subscriber: @Jeroen-Bakker

Jeroen Bakker commented

2017-03-28 21:30:36 +02:00

Hi Dwight,

the noise texture uses a randomizer for generating the noise; this makes it not consistent at all to do scaling etc. This is by design.
If you need to scale a noise typically you would be using Clouds or Distributed Noise. Or you should use an pre-calced image

Jeroen

Hi Dwight, the noise texture uses a randomizer for generating the noise; this makes it not consistent at all to do scaling etc. This is by design. If you need to scale a noise typically you would be using Clouds or Distributed Noise. Or you should use an pre-calced image Jeroen

Dwight Martin commented

2017-03-28 22:54:09 +02:00

Jeroen,

If that's the case, okay. But, this was possible in version 2.73a. I don't know when this changed. But here's a tutorial where it was still working: https://www.youtube.com/watch?v=Ra-E0JVkXEI

Thanks,
Dwight

Jeroen, If that's the case, okay. But, this was possible in version 2.73a. I don't know when this changed. But here's a tutorial where it was still working: https://www.youtube.com/watch?v=Ra-E0JVkXEI Thanks, Dwight

ronan ducluzeau commented

2017-04-03 19:32:32 +02:00

Added subscriber: @zeauro

ronan ducluzeau commented

2017-04-03 19:32:32 +02:00

Change of behaviour is probably relative to a fix in compositor.

You can benefit of auto-regeneration of noïse texture at each frame and scale it by adding a corner pin node between texture node and scale node.
So, I would not say that change is annoying.

Change of behaviour is probably relative to a fix in compositor. You can benefit of auto-regeneration of noïse texture at each frame and scale it by adding a corner pin node between texture node and scale node. So, I would not say that change is annoying.

Aaron Carlisle commented

2017-04-15 23:33:36 +02:00

Added subscriber: @Blendify

Aaron Carlisle commented

2017-04-15 23:33:36 +02:00

Changed status from 'Open' to: 'Archived'

Aaron Carlisle closed this issue

2017-04-15 23:33:36 +02:00

Aaron Carlisle self-assigned this 2017-04-15 23:33:36 +02:00

Aaron Carlisle commented

2017-04-15 23:33:36 +02:00

Closing because this is intended behavior as pointed out by @Jeroen-Bakker

Dwight Martin commented

2017-04-16 01:46:38 +02:00

In #51070#428398, @Blendify wrote:
Closing because this is intended behavior as pointed out by @Jeroen-Bakker

If anyone wonders why I'm not a member of the Blender Cloud, look at this rude, condescending post. It took you a over a month to be a dick. This is why professionals don't use Blender. Great explanation why this was changed. I love both you and jbakker's work. You are wonderful artists.

> In #51070#428398, @Blendify wrote: > Closing because this is intended behavior as pointed out by @Jeroen-Bakker If anyone wonders why I'm not a member of the Blender Cloud, look at this rude, condescending post. It took you a over a month to be a dick. This is why professionals don't use Blender. Great explanation why this was changed. I love both you and jbakker's work. You are wonderful artists.

Aaron Carlisle commented

2017-04-16 05:45:16 +02:00

Changed status from 'Archived' to: 'Open'

Aaron Carlisle reopened this issue

2017-04-16 05:45:16 +02:00

Aaron Carlisle commented

2017-04-16 05:45:16 +02:00

Added subscriber: @Sergey

Aaron Carlisle commented

2017-04-16 05:45:16 +02:00

@dwightmartin thank you for your concerns, we have been a little short-handed as far a people to work on the bug tracker but after your comment, I went back and looked and the different Blender versions and also have a few questions. @Jeroen-Bakker I can you, as the compositing expert, explain your reasoning a bit more? I went back and checked Blender versions 2.73a to master and found the issue only started appearing after 2.77. I also checked the release logs (both user and bug fixes and did not see anything that obvious as an intended change) I am also CC'ing @Sergey as most of the changes done in this time period were your own.

Aaron Carlisle removed their assignment 2017-05-18 20:39:36 +02:00

Sergey Sharybin commented

2017-05-18 21:15:26 +02:00

Scaling down can not work within the current compositor design. Fixing this issue would mean changing the design completely, which is out of the scope of the bug tracker.

Added note to our TODO list tho.

Thanks for the report, but this is something we have to live with for now.

Scaling down can not work within the current compositor design. Fixing this issue would mean changing the design completely, which is out of the scope of the bug tracker. Added note to our TODO list tho. Thanks for the report, but this is something we have to live with for now.

Sergey Sharybin commented

2017-05-18 21:15:33 +02:00

Changed status from 'Open' to: 'Archived'

Sergey Sharybin closed this issue

2017-05-18 21:15:33 +02:00

Sergey Sharybin self-assigned this 2017-05-18 21:15:33 +02:00

Aaron Carlisle commented

2017-05-18 21:16:37 +02:00

@Sergey but why did it work in 2.77?

Sergey Sharybin commented

2017-05-19 10:41:00 +02:00

Changed status from 'Archived' to: 'Open'

Sergey Sharybin reopened this issue

2017-05-19 10:41:00 +02:00

Sergey Sharybin commented

2017-05-19 10:41:00 +02:00

@Blendify, so "squished" part i think we can investigate (as in "resolution" if you wish).

But the aliasing we can't fix.

So basically will try to bring behavior back to what is used to be.

@Blendify, so "squished" part i think we can investigate (as in "resolution" if you wish). But the aliasing we can't fix. So basically will try to bring behavior back to what is used to be.

Sergey Sharybin commented

2017-05-19 11:00:06 +02:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue

2017-05-19 11:00:06 +02:00

Sergey Sharybin commented

2017-05-19 11:00:06 +02:00

Brought behavior back to how it was before. But i find this all weak, and some cleaner design (which follows artists' expectations instead of dictating them how to use something) is really needed in compositor.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Cannot scale textures in compositor #51070