cycles mapping node rotation order #43120
Labels
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 project
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#43120
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
System Information
Operating system and graphics card
Blender Version
Broken: 2.73.2
Short description of error
cycles mapping node rotation order is reversed for viewport and for render
Exact steps for others to reproduce the error
opend attached blend{F135089}
Changed status to: 'Open'
Added subscriber: @kopias
Win7x64 GTX660M 337.88
Added subscriber: @Psy-Fi
This is pretty horrible one actually. it's caused by the wrong logic in Cycles itself: https://developer.blender.org/diffusion/B/browse/master/intern/cycles/util/util_transform.h;89b654dc56b38a332e5bc4f82109152e21f0a5b6$219
Will look into some ways to make it proper behavior without introducing regressions for existing files here.
This issue was referenced by
a1ffb49e49
Changed status from 'Open' to: 'Resolved'
Closed by commit
a1ffb49e49
.This issue was referenced by blender/cycles@69a14ff147
Added subscriber: @moak
Question: in most situations (objects, bones) where the rotation order is ambiguous, there's usually an option to let the user set the rotation mode. Would that have not worked here?
From my (non-developer) perspective, it seems like the cleanest solution might be to provide a drop-down menu on the mapping node, with all of the six permutations of XYZ-Euler available (maybe not quaternions and axis-angle if changing the number of inputs would be a problem.) Then the user could know (and define!) exactly how the mapping node is going to behave without having to, say, guess how adding a new mapping node to an old-version file will work.
I mean, the mapping node already has four modes depending on what type of vector is being used as an input. I don't think adding a "rotation mode" option would make things too much more complex on the user's side.
Rotation order is not ambiguous, it is expected to be XYZ-euler by BI and viewport. Just by accident Cycles used flipped order. It is possible to support different orders, but it ends up in totally hairy code because of specifics how this mapping works internally for glsl. Just sticking to XYZ-euler is easier for everyone.