Plane track ignores absolute scaling of image #47539

Closed
opened 2016-02-23 07:52:23 +01:00 by Gottfried Hofmann · 5 comments

System Information
Ubuntu 15.10 64big Geforce 970M

Blender Version
Broken: Blender 2.76b official

When using a scale node for an image the plane track deform node will still use the original image bounds for the plane track deform, thus for example scaling the image further down.

The bug appears to happen in the scale node. It does scale the image, but does not change the image bounds, even when set to absolute.

Exact steps for others to reproduce the error
In the attached file, when the top of the 3 image nodes is plugged into the upper scale node, you see the effect. The middle image is exactly 275 x 275 and thus not effected.

planetrack.bug.zip

**System Information** Ubuntu 15.10 64big Geforce 970M **Blender Version** Broken: Blender 2.76b official When using a scale node for an image the plane track deform node will still use the original image bounds for the plane track deform, thus for example scaling the image further down. The bug appears to happen in the scale node. It does scale the image, but does not change the image bounds, even when set to absolute. **Exact steps for others to reproduce the error** In the attached file, when the top of the 3 image nodes is plugged into the upper scale node, you see the effect. The middle image is exactly 275 x 275 and thus not effected. [planetrack.bug.zip](https://archive.blender.org/developer/F285383/planetrack.bug.zip)

Changed status to: 'Open'

Changed status to: 'Open'

Added subscriber: @GottfriedHofmann

Added subscriber: @GottfriedHofmann

Added subscriber: @Sergey

Added subscriber: @Sergey

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Sergey Sharybin self-assigned this 2016-02-23 10:37:49 +01:00

Unfortunately, it's just the way compositor currently works and there's no simple fix for this: the system don't know resolution in advance (because size are actually sockets) and it's not really possible to evaluate the tree when detecting the resolution.

Thanks for the report, but considering it a general TODO related on making the whole system properly canvas aware.

Unfortunately, it's just the way compositor currently works and there's no simple fix for this: the system don't know resolution in advance (because size are actually sockets) and it's not really possible to evaluate the tree when detecting the resolution. Thanks for the report, but considering it a general TODO related on making the whole system properly canvas aware.
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 project
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#47539
No description provided.