Viewport gets stuck when two group instances are emitted from one face using dupli-verts #48913
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
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#48913
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
Windows 8.1 Enterprise 64-bit
GPU: Nvidia GTX 670
Blender Version
Broken: 2.77a
abf6f08
Short description of error
view port render gets stuck in loop of restarting, either during caching the BVH or on the first sample, depending on how large the scene is. Note that F12 render still works.
Gif:
Exact steps for others to reproduce the error
Full reproduction steps (from beginning):
Start with a clean .blend
follow the steps in this post:
http://blender.stackexchange.com/a/58304/3127
then grab the group instance empty, shift-D copy it, and move it over.
Switch to view port render mode, the bug will appear.
Blend file based reproduction steps:
Switch to view port render mode, the bug will appear.
Blend file
Stuck Viewport Demo.blend
Changed status to: 'Open'
Added subscriber: @GiantCowFIlms
Added subscriber: @gandalf3
Added subscribers: @Sergey, @mont29
Can confirm the issue…
Cycles keeps aborting its update (synchronize) call back because either
session->ready_to_reset()
orsession->scene->mutex.try_lock()
fail (line 813 of blender_session.cpp).Will let Cycles/depsgraph guy dig further here, @sergey. ;)
Developer note.
it's nothing really to do with dependency graph or the locking/notification mechanism mentioned here. It is to do with how dupli_object.c generates persistent ID: there are two object parented to the plane, yeah of them duplicates two suzannes. This makes the persistent IDs be the following:
0 0 2147483647 2147483647 2147483647 2147483647 2147483647 2147483647
1 0 2147483647 2147483647 2147483647 2147483647 2147483647 2147483647
0 0 2147483647 2147483647 2147483647 2147483647 2147483647 2147483647
1 0 2147483647 2147483647 2147483647 2147483647 2147483647 2147483647
This makes two different instances to have different transformation matrix but same persistent ID, which confuses Cycles.
So this issue is to be solved on
object_dupli,c
level with some careful thoughts how to avoid unnecessary persistent ID changes when geometry changes over the time.This issue was referenced by blender/cycles@29de8bb2a8
This issue was referenced by
c0161a1bab
Added subscriber: @brecht
Here's a simple patch that solves it, making the persistent ID longer to take into account the group/base index.
P385: (An Untitled Masterwork)
In 2.8 we might consider changing dupliverts and duplifaces so that duplicators use a group or object specified in a property, rather than through parenting. That dependency has always been in the wrong direction I think, and then as a side effect we could shorten the persistent ID again.
@brecht, any reason why not to commit this?
I haven't had the time to test this properly yet, just wanted to post something so no one wastes time trying to fix this.
Changed status from 'Open' to: 'Resolved'