Difference of position of cloth animated mesh between viewport and render result #39195

Closed
opened 2014-03-15 04:51:17 +01:00 by Willi · 6 comments

System Information
Win 7/64, AMD HD 6850

Blender Version
2.70 (Can't remember it ever worked.)

Short description of error
A cloth animated mesh that is part of a group instance is not rendered at the correct location as in the viewport.

Exact steps for others to reproduce the error
Open the attached file and render. Problem: The cloth is rendered at a position different to the viewport.

Test_116.zip

Note that layer 1 contains only a group instance. Switch to layer 2 to see the group definition: The cloth has been animated by a cloth animation, and the cache has been baken. However, as the viewport can display the cloth within the group instance in layer 1 at the expected location, the renderer should be able to do so, too.

**System Information** Win 7/64, AMD HD 6850 **Blender Version** 2.70 (Can't remember it ever worked.) **Short description of error** A cloth animated mesh that is part of a group instance is not rendered at the correct location as in the viewport. **Exact steps for others to reproduce the error** Open the attached file and render. Problem: The cloth is rendered at a position different to the viewport. [Test_116.zip](https://archive.blender.org/developer/F81220/Test_116.zip) Note that layer 1 contains only a group instance. Switch to layer 2 to see the group definition: The cloth has been animated by a cloth animation, and the cache has been baken. However, as the viewport can display the cloth within the group instance in layer 1 at the expected location, the renderer should be able to do so, too.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @willi-2

Added subscriber: @willi-2

Added subscriber: @Sergey

Added subscriber: @Sergey

First guess is that it happens because of order in which object position and cache load happens in case of dupli-stuff physics. Will check whether it's solvable with the current design.

First guess is that it happens because of order in which object position and cache load happens in case of dupli-stuff physics. Will check whether it's solvable with the current design.
Sergey Sharybin self-assigned this 2014-03-21 10:37:23 +01:00

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

Spend quite a while trying to solve the issue. It is actually a limitation of the render database creation in Blender Internal. Technically it's caused by the render pipeline changing object's matrix before evaluating modifier stack. It's possible to support point caches working here, but then file from #38801 wouldn't work.

Some bigger render database refactor is needed. We'll need to do it for granular depgraph and copy-on-write projects anyway, so better solve all the issues all at once.

Added the note in our TODO list: http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Render#Render_Engine

Thanks for the report, but for now will consider this is a TODO.

Spend quite a while trying to solve the issue. It is actually a limitation of the render database creation in Blender Internal. Technically it's caused by the render pipeline changing object's matrix before evaluating modifier stack. It's possible to support point caches working here, but then file from #38801 wouldn't work. Some bigger render database refactor is needed. We'll need to do it for granular depgraph and copy-on-write projects anyway, so better solve all the issues all at once. Added the note in our TODO list: http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Render#Render_Engine Thanks for the report, but for now will consider this is a TODO.
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#39195
No description provided.