Imported curves lag behind one frame. #49447

Closed
opened 2016-09-25 14:57:58 +02:00 by - · 13 comments

System Information
Linux Mint 17.3
I5 3550 - 32gb RAM , Asus Geforce 750Ti OC

Blender Version
Broken: release candiate 2.78

Short description of error

Tested the import export from Houdini to Blender via Alembic abc format. There is a problem with curve objects.

Exact steps for others to reproduce the error

I tried to export Fur from Houdini to Blender via Alembic. When i exported it everything works fine. Blender converted this polylines or even Nurbs Curves to Blender Nurbs Curves. So far so good. But. When you play the animation sequence the curve Objects in Blender (fur Curves) lagging a Frame . Means. You need to push one frame forward to get the Curves in the correct possition then you need to step one frame back to get the geometry back to where it has to be. The curves dosent move. .. In Short Words there is a Frame Redraw Lag or Reading lag for Curves.

My Solution was to convert all Lines in Houdini to Polyllines then i extruded them to get a real Polygone. I exported the polygone Hairs again -> everything works fine with real geometry. Hope this gets fixed soon.

For still import (no Sequence the import of Alembic even with Nurbs curves works perfectly)

BIG THANKS TO ALL THE INVOLVED DEVELOPERS FOR the ABC INTEGRATION!!!!!

Cheers

Alex

**System Information** Linux Mint 17.3 I5 3550 - 32gb RAM , Asus Geforce 750Ti OC **Blender Version** Broken: release candiate 2.78 **Short description of error** Tested the import export from Houdini to Blender via Alembic abc format. There is a problem with curve objects. **Exact steps for others to reproduce the error** I tried to export Fur from Houdini to Blender via Alembic. When i exported it everything works fine. Blender converted this polylines or even Nurbs Curves to Blender Nurbs Curves. So far so good. But. When you play the animation sequence the curve Objects in Blender (fur Curves) lagging a Frame . Means. You need to push one frame forward to get the Curves in the correct possition then you need to step one frame back to get the geometry back to where it has to be. The curves dosent move. .. In Short Words there is a Frame Redraw Lag or Reading lag for Curves. My Solution was to convert all Lines in Houdini to Polyllines then i extruded them to get a real Polygone. I exported the polygone Hairs again -> everything works fine with real geometry. Hope this gets fixed soon. For still import (no Sequence the import of Alembic even with Nurbs curves works perfectly) BIG THANKS TO ALL THE INVOLVED DEVELOPERS FOR the ABC INTEGRATION!!!!! Cheers Alex
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @AlexanderWeide

Added subscriber: @AlexanderWeide

Added subscriber: @kevindietrich

Added subscriber: @kevindietrich

Thanks for the report but we would need a simple Alembic archive that demonstrates the issue.

Thanks for the report but we would need a simple Alembic archive that demonstrates the issue.
Kévin Dietrich self-assigned this 2016-09-25 15:11:45 +02:00
Author

Bugreport_Alembic_Curves.zip This File provides the Houdini Export File, the ABC File and the Import Blender file. Its the same problem with Nurbs curves. Hope that helps

[Bugreport_Alembic_Curves.zip](https://archive.blender.org/developer/F367909/Bugreport_Alembic_Curves.zip) This File provides the Houdini Export File, the ABC File and the Import Blender file. Its the same problem with Nurbs curves. Hope that helps
Author

Ps When you play the animation foward step by step you see the lagging of the curves.

Ps When you play the animation foward step by step you see the lagging of the curves.

Thanks for the files, can confirm the issue.

Thanks for the files, can confirm the issue.
Author

First of all very nice with Blender 2 78b it works nice. But is it possible to store point color dats on those curves? I think thats not possible but is it possible to import alembic files of point clouds with stored color data what alembic is exporting in houdini. Its stored but blender dosent import it..

If this is not possible it would be nice when blender can import polylines with stored vertex color information right now every curve even polycurves from houdini are Imported as bezier/nurbs Curves.
Maybe a import option could help

Best regards Alexander Weide..

First of all very nice with Blender 2 78b it works nice. But is it possible to store point color dats on those curves? I think thats not possible but is it possible to import alembic files of point clouds with stored color data what alembic is exporting in houdini. Its stored but blender dosent import it.. If this is not possible it would be nice when blender can import polylines with stored vertex color information right now every curve even polycurves from houdini are Imported as bezier/nurbs Curves. Maybe a import option could help Best regards Alexander Weide..

Vertex colors are a mesh property in Blender, so it is not possible to import/have them on curves at the moment. Making use of polylines (or edges in Blender terms) would be possible, but then things like rendering in Cycles might not be possible or very limited. The fact that Houdini polylines/polycurves are imported as curves in Blender is because they are written as being curve objects in the Alembic archives.

Vertex colors are a mesh property in Blender, so it is not possible to import/have them on curves at the moment. Making use of polylines (or edges in Blender terms) would be possible, but then things like rendering in Cycles might not be possible or very limited. The fact that Houdini polylines/polycurves are imported as curves in Blender is because they are written as being curve objects in the Alembic archives.
Sybren A. Stüvel changed title from Release Candidate 2.78 Alembic Bug with Polylines or Nurbs Curves to Imported curves lag behind one frame. 2017-04-20 12:05:58 +02:00

Added subscriber: @dr.sybren

Added subscriber: @dr.sybren

This issue (lagging of imported curves) is a known problem, which is caused by limitations of the current modifier system in combination with Alembic. The modifiers are made to either construct a new object or deform an existing object. Since Alembic curves can change topology from one frame to another, the Mesh Cache modifier needs to do both (i.e. create a new object when the curve topology changes, and deform an existing object when it doesn't). To fix this properly, we'll have to modify the modifier system to allow both. I don't know if I can do this (or work around this issue another way) in time for 2.79; if not, we'll work it out in 2.8 (in which case there will be a different, more elegant approach to handling cached data).

In #49447#416546, @AlexanderWeide wrote:
But is it possible to store point color dats on those curves?

Please stay on the topic of the ticket, and open a new ticket for a new topic.

This issue (lagging of imported curves) is a known problem, which is caused by limitations of the current modifier system in combination with Alembic. The modifiers are made to either construct a new object or deform an existing object. Since Alembic curves can change topology from one frame to another, the Mesh Cache modifier needs to do both (i.e. create a new object when the curve topology changes, and deform an existing object when it doesn't). To fix this properly, we'll have to modify the modifier system to allow both. I don't know if I can do this (or work around this issue another way) in time for 2.79; if not, we'll work it out in 2.8 (in which case there will be a different, more elegant approach to handling cached data). > In #49447#416546, @AlexanderWeide wrote: > But is it possible to store point color dats on those curves? Please stay on the topic of the ticket, and open a new ticket for a new topic.
Author

Removed subscriber: @AlexanderWeide

Removed subscriber: @AlexanderWeide

Closed as duplicate of #58704

Closed as duplicate of #58704
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
4 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#49447
No description provided.