AOV and Normal output Filtering Issues #105709

New Issue

Closed

opened 2023-03-13 11:39:42 +01:00 by Mario Tovirac · 3 comments

Mario Tovirac commented

2023-03-13 11:39:42 +01:00

When rendering AOV there is filtering happening but it should not happen on the edges as it gives faulty data, same problem happens with normals, setting the samples at 1 will give a sharp edge, so logically there is an average made, but shooting into "empty space" should not contribute to the end pixel, similar to how index material is working

normals and aovs have the filtering problem, while position or index mat dont have it.

![render_aliasing.png](/attachments/4aee8c26-c2dd-4aa5-820a-eb6a63c34d97) When rendering AOV there is filtering happening but it should not happen on the edges as it gives faulty data, same problem happens with normals, setting the samples at 1 will give a sharp edge, so logically there is an average made, but shooting into "empty space" should not contribute to the end pixel, similar to how index material is working normals and aovs have the filtering problem, while position or index mat dont have it.

render_aliasing.png

24 KiB

Mario Tovirac added the

labels 2023-03-13 11:39:43 +01:00

Iliya Katushenock commented

2023-03-13 14:33:42 +01:00

Member

I think the problem is that filtering should not work for normals and aov.
This data cannot be mixed meaningfully. If you mix 2 normals you will just get a new normal, still not correct. Interpolating between aov ids 1 and 10 will give you 5, which obviously can't be right.
The problem is that these layers must be rendered at maximum resolution and based on their results, the color can be filtered.

I think the problem is that filtering should not work for normals and aov. This data cannot be mixed meaningfully. If you mix 2 normals you will just get a new normal, still not correct. Interpolating between aov ids 1 and 10 will give you 5, which obviously can't be right. The problem is that these layers must be rendered at maximum resolution and based on their results, the color can be filtered.

Iliya Katushenock added the

EEVEE & Viewport

label 2023-03-13 14:33:51 +01:00

Mario Tovirac commented

2023-03-13 15:15:15 +01:00

Author

I think the problem is that filtering should not work for normals and aov.
This data cannot be mixed meaningfully. If you mix 2 normals you will just get a new normal, still not correct. Interpolating between aov ids 1 and 10 will give you 5, which obviously can't be right.
The problem is that these layers must be rendered at maximum resolution and based on their results, the color can be filtered.

correct

> I think the problem is that filtering should not work for normals and aov. > This data cannot be mixed meaningfully. If you mix 2 normals you will just get a new normal, still not correct. Interpolating between aov ids 1 and 10 will give you 5, which obviously can't be right. > The problem is that these layers must be rendered at maximum resolution and based on their results, the color can be filtered. correct

Germano Cavalcante commented

2023-03-14 16:14:34 +01:00

Member

This is known behavior and even mentioned in the manual: https://docs.blender.org/manual/en/3.6/render/layers/passes.html#data

The Z, Position, Object Index, and Material Index passes are not anti-aliased.

Therefore it is not considered a bug.

So closing as this bug tracker is only for bugs and errors.

For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

This is known behavior and even mentioned in the manual: https://docs.blender.org/manual/en/3.6/render/layers/passes.html#data > The Z, Position, Object Index, and Material Index passes are not anti-aliased. Therefore it is not considered a bug. So closing as this bug tracker is only for bugs and errors. For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Germano Cavalcante closed this issue

2023-03-14 16:14:36 +01:00

Blender Bot added

and removed

labels 2023-03-14 16:14:37 +01:00

Sign in to join this conversation.

No Label

Animation & Rigging

Asset Browser Project Overview

Automated Testing

Blender Asset Bundle

Dependency Graph

Development Management

EEVEE & Viewport

Images & Movies

Motion Tracking

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Render Pipeline

Sculpt, Paint & Texture

Video Sequencer

Virtual Reality

Blender 2.8 Project

Milestone 1: Basic, Local Asset Browser

Good First Issue

Animation & Rigging

Development Management

EEVEE & Viewport

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Sculpt, Paint & Texture

Needs Info from Developers

Needs Information from User

No Milestone

No project

No Assignees

3 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#105709

No description provided.