blender/blender-manual
23
23
Fork 104
Code Issues 74 Pull Requests 6 Projects 1 Releases Wiki Activity

Compositing node Vector -> Normalize inputs and outputs scalars not vectors #61875

New Issue
Closed
opened 2019-02-23 07:14:48 +01:00 by Finn Bear · 12 comments
Finn Bear commented 2019-02-23 07:14:48 +01:00
Copy Link

System Information
Operating system: Ubuntu 18:04

Blender Version
Broken: 2.8 from February 4, 2019

Short description of error
The Vector -> Normalize node, visible in the compositor, takes/returns scalars (numbers denoted by a grey dot) instead of vectors (two values denoted by a blue dot). It is impossible to normalize scalars (unless you just set them to equal 1), so this shouldn't even be an option. I'm guessing this is a cosmetic issue.

Exact steps for others to reproduce the error
Open the compositor, enable "use nodes," add a Vector -> Normalize node

**System Information** Operating system: Ubuntu 18:04 **Blender Version** Broken: 2.8 from February 4, 2019 **Short description of error** The Vector -> Normalize node, visible in the compositor, takes/returns scalars (numbers denoted by a grey dot) instead of vectors (two values denoted by a blue dot). It is impossible to normalize scalars (unless you just set them to equal 1), so this shouldn't even be an option. I'm guessing this is a cosmetic issue. **Exact steps for others to reproduce the error** Open the compositor, enable "use nodes," add a Vector -> Normalize node
Finn Bear commented 2019-02-23 07:14:48 +01:00
Author
Copy Link

Added subscriber: @finnb

Added subscriber: @finnb
Jacques Lucke commented 2019-02-25 15:05:15 +01:00
Member
Copy Link

Added subscriber: @JacquesLucke

Added subscriber: @JacquesLucke
Jacques Lucke self-assigned this 2019-02-25 15:05:15 +01:00
Jacques Lucke commented 2019-02-25 15:05:15 +01:00
Member
Copy Link

The actual problem here seems to be the documentation, not the implementation.

In the code it says: Normalize single channel, useful for z buffer (https://developer.blender.org/diffusion/B/browse/master/source/blender/nodes/composite/nodes/node_composite_normalize.c$28).

While the manual explains something very different (https://docs.blender.org/manual/en/latest/compositing/types/vector/normalize.html).

The actual problem here seems to be the documentation, not the implementation. In the code it says: `Normalize single channel, useful for z buffer` (https://developer.blender.org/diffusion/B/browse/master/source/blender/nodes/composite/nodes/node_composite_normalize.c$28). While the manual explains something very different (https://docs.blender.org/manual/en/latest/compositing/types/vector/normalize.html).
blender-admin commented 2019-02-25 15:11:19 +01:00
Copy Link

This issue was referenced by 4574

This issue was referenced by 4574
Jacques Lucke commented 2019-02-25 15:22:45 +01:00
Member
Copy Link

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Finn Bear commented 2019-02-26 03:56:37 +01:00
Author
Copy Link

@JacquesLucke Now I'm wondering why this node is in the "Vector" category, and that actually applies to most of the nodes there. These nodes, except vector curves, really stretch the meaning of "vector."

@JacquesLucke Now I'm wondering why this node is in the "Vector" category, and that actually applies to most of the nodes there. These nodes, except vector curves, really stretch the meaning of "vector."
Jacques Lucke commented 2019-02-26 13:38:14 +01:00
Member
Copy Link

Added subscriber: @WilliamReynish

Added subscriber: @WilliamReynish
Jacques Lucke commented 2019-02-26 13:38:14 +01:00
Member
Copy Link

@finnb, you are right. That does not really make sense.

@WilliamReynish, where should this be?

@finnb, you are right. That does not really make sense. @WilliamReynish, where should this be?
William Reynish commented 2019-02-26 13:43:49 +01:00
Copy Link

As @finnb points out, that could be argued for almost all the nodes in the Vector category.

We could put them inside the Converter category? Or we could add a new category called 'Values' or something like that?

Although if we use the logic of the main input or output socket, the Vector category would be almost empty.

As @finnb points out, that could be argued for almost all the nodes in the Vector category. We could put them inside the Converter category? Or we could add a new category called 'Values' or something like that? Although if we use the logic of the main input or output socket, the Vector category would be almost empty.
Jacques Lucke commented 2019-02-26 13:50:01 +01:00
Member
Copy Link

Hmmm, I'm not sure... Maybe this should be discussed in a design task.

Hmmm, I'm not sure... Maybe this should be discussed in a design task.
Finn Bear commented 2019-02-28 07:38:01 +01:00
Author
Copy Link

The vector category wouldn't be almost empty if a true "normalize" node was added. The current "normalize" node could be renamed "normalize channel."

The vector category wouldn't be almost empty if a true "normalize" node was added. The current "normalize" node could be renamed "normalize channel."
Finn Bear commented 2019-02-28 07:39:23 +01:00
Author
Copy Link

Also, where can I find "design tasks?"

Also, where can I find "design tasks?"
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
Meta
Good First Issue

  
Module
Animation & Rigging

  
Module
Core

  
Module
Development Management

  
Module
Eevee & Viewport

  
Module
Grease Pencil

  
Module
Modeling

  
Module
Nodes & Physics

  
Module
Pipeline, Assets & IO

  
Module
Platforms, Builds, Tests & Devices

  
Module
Python API

  
Module
Rendering & Cycles

  
Module
Sculpt, Paint & Texture

  
Module
User Interface

  
Module
VFX & Video

  
Priority
High

  
Priority
Low

  
Priority
Normal

  
Status
Archived

  
Status
Confirmed

  
Status
Duplicate

  
Status
Needs Information from Developers

  
Status
Needs Information from User

  
Status
Needs Triage

  
Status
Resolved

  
Type
Bug

  
Type
Design

  
Type
Known Issue

  
Type
Patch

  
Type
Report

  
Type
To Do

No Label
Meta
Good First Issue
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
Eevee & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds, Tests & Devices
Module
Python API
Module
Rendering & Cycles
Module
Sculpt, Paint & Texture
Module
User Interface
Module
VFX & Video
Priority
High
Priority
Low
Priority
Normal
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Information from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
Jacques Lucke
4 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-manual#61875
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?