Compositing scale node border error #43784

New Issue

ratty redemption · 2015-02-22T23:20:07+01:00

ratty redemption commented

2015-02-22 23:20:07 +01:00

- Operating System, Graphics card ---

cpu: intel core i3 2350 2.3 ghz
ram: 4 gb
gfx: intel hd graphics 3000
os: windows 7 home premium sp 1

- Blender version with error, and version that worked ---

error found in: 63b0a7f win64.
was working in: f65b369 win64.

- Short description of error ---

blender internal compositing scale node border error.

- Steps for others to reproduce the error (preferably based on attached .blend file) ---

please compare the two attached screencaps, and you should see a very simple node layout... of which the newer builds are rendering a 1 pixel border on the left and bottom edges of the rendered and preview images.

and although not obvious in these screencaps, my other tests look as if the whole render is shifted up and to the right by 1 pixel, so previous render layers like alpha channels no longer align perfectly.

if the scale node is muted or deleted, the error does not happen as far as i can tell.

- Operating System, Graphics card --- cpu: intel core i3 2350 2.3 ghz ram: 4 gb gfx: intel hd graphics 3000 os: windows 7 home premium sp 1 - Blender version with error, and version that worked --- error found in: 63b0a7f win64. was working in: f65b369 win64. - Short description of error --- blender internal compositing scale node border error. - Steps for others to reproduce the error (preferably based on attached .blend file) --- please compare the two attached screencaps, and you should see a very simple node layout... of which the newer builds are rendering a 1 pixel border on the left and bottom edges of the rendered and preview images. and although not obvious in these screencaps, my other tests look as if the whole render is shifted up and to the right by 1 pixel, so previous render layers like alpha channels no longer align perfectly. if the scale node is muted or deleted, the error does not happen as far as i can tell. ![Untitled3.jpg](https://archive.blender.org/developer/F145321/Untitled3.jpg) ![Untitled4.jpg](https://archive.blender.org/developer/F145323/Untitled4.jpg)

ratty redemption commented

2015-02-22 23:20:07 +01:00

Changed status to: 'Open'

ratty redemption commented

2015-02-22 23:20:07 +01:00

Added subscriber: @rattyredemption

Julian Eisel commented

2015-02-23 20:17:04 +01:00

Added subscriber: @JulianEisel

Julian Eisel commented

2015-02-23 20:17:04 +01:00

Can reproduce. Simple .blend to test size_node_bug.blend

Can reproduce. Simple .blend to test [size_node_bug.blend](https://archive.blender.org/developer/F145484/size_node_bug.blend)

Julian Eisel changed title from ~~blender internal compositing scale node border error.~~ to Compositing scale node border error

2015-02-23 20:17:26 +01:00

ratty redemption commented

2015-02-23 20:35:49 +01:00

@JulianEisel thanks for confirming this.

was it redundant of me to include in the title "blender internal"?

i've never used cycles so wasn't sure if this would affect both renderers.

@JulianEisel thanks for confirming this. was it redundant of me to include in the title "blender internal"? i've never used cycles so wasn't sure if this would affect both renderers.

Julian Eisel commented

2015-02-23 20:41:07 +01:00

It could just lead to the misconception that this is a bug that only occurs in BI, which isn't the case. If you don't know it, just leave it out, this is a thing that developers can test without big difficulties. So don't worry, all fine, I just wanted to make sure there are no misconceptions ;)

Sergey Sharybin was assigned by Julian Eisel

2015-02-23 21:06:28 +01:00

Julian Eisel commented

2015-02-23 21:06:28 +01:00

Caused by 02fad7dca4 so it goes to Sergey! ;)

Caused by 02fad7dca4adc5 so it goes to Sergey! ;)

ratty redemption commented

2015-02-23 21:35:28 +01:00

@JulianEisel understood and i'll keep that in mind, thanks.