Geometry Node: Add Projection setting to Image Texture node #104548

Closed
opened 2023-02-10 00:51:21 +01:00 by Iliya Katushenock · 2 comments

Add Projection setting to Image Texture node.
Documentation about texture space projections Shader: Image Texture: Properties: Projection.

Steps to implement this:

  1. Add int8_t projection; in structure of node storage.
  2. Reuse rna declaration of this property from shader (optionally create new function to unifi this rna declaration).
  3. In node: Not just add some more specific cases to implementation of texture sampling math. Projection is just opeeration on position. This have to implement as preprocessing of input position field. This can be implemented by field operation and multi functions. As example: Sample Curve node, SampleFloatSegmentsFunction.
Shader Image Texture Geometry node Image Texture
image image
Add Projection setting to Image Texture node. Documentation about texture space projections [Shader: Image Texture: Properties: Projection](https://docs.blender.org/manual/en/latest/render/shader_nodes/textures/image.html#properties). Steps to implement this: 1. Add `int8_t projection;` in structure of node storage. 2. Reuse rna declaration of this property from shader (optionally create new function to unifi this rna declaration). 3. In node: Not just add some more specific cases to implementation of texture sampling math. Projection is just opeeration on position. This have to implement as preprocessing of input position field. This can be implemented by field operation and multi functions. As example: Sample Curve node, `SampleFloatSegmentsFunction`. | Shader `Image Texture` | Geometry node `Image Texture` | | -------- | -------- | | ![image](/attachments/410c517e-503c-4a9f-8ddd-7a20f3c57db5) | ![image](/attachments/b5585e24-bef6-4276-965e-65b670f7a6a2) |
Iliya Katushenock added this to the Nodes & Physics project 2023-02-10 00:51:22 +01:00
Member

I remember discussing this briefly in the past. IMO it would be better for the image texture node to do basic image sampling from image-space coordinates. Projection and mapping geometry to those image coordinates should be a separate built-in node.

They could later be combined as a group, it's better to avoid unnecessarily combining features in building block nodes, compared to building an "uber node" that has to also think about geometry concepts.

For the specifics of replacing this feature in geometry nodes, I'd suggest making sure we have the necessary math/input nodes and possibly shipping them as node groups at some point.

I remember discussing this briefly in the past. IMO it would be better for the image texture node to do basic image sampling from image-space coordinates. Projection and mapping geometry to those image coordinates should be a separate built-in node. They could later be combined as a group, it's better to avoid unnecessarily combining features in building block nodes, compared to building an "uber node" that has to also think about geometry concepts. For the specifics of replacing this feature in geometry nodes, I'd suggest making sure we have the necessary math/input nodes and possibly shipping them as node groups at some point.
Blender Bot added the
Status
Archived
label 2023-02-10 02:00:33 +01:00
Author
Member

Basically, I proceeded from the fact that would have a similar built-in functionality as in shader/
And also, if only the necessary minimum is left in the nodes, then the interpolation methods also seem to excessive/
But yes, unified space projection methods would be much more extensible.
But having this as a other node, adding its implementation as a customization to the texture node will be even easier/
Although I remember that the radial projection node was, but still not accepted/

But yes, if we accept this as a change, and not a pre-conceived and already added feature, then its excessiveness has a greater influence on the decision

Basically, I proceeded from the fact that would have a similar built-in functionality as in shader/ And also, if only the necessary minimum is left in the nodes, then the interpolation methods also seem to excessive/ But yes, unified space projection methods would be much more extensible. But having this as a other node, adding its implementation as a customization to the texture node will be even easier/ Although I remember that the radial projection node was, but still not accepted/ But yes, if we accept this as a change, and not a pre-conceived and already added feature, then its excessiveness has a greater influence on the decision
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
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
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info 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 Milestone
No Assignees
2 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#104548
No description provided.