Alembic not importing velocity #95945

Closed
opened 2022-02-21 21:54:20 +01:00 by Juan Gea · 17 comments

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79

Blender Version
Broken: version: 3.1.0 Beta, branch: master, commit date: 2022-02-20 22:00, hash: 1a0a22f95a

Short description of error
When importing an Alembic file, velocity is not being imported, cycles is not using it and GN is incapable of seeing it.

Exact steps for others to reproduce the error
Import given Alembic file and look for velocity.

https://we.tl/t-nq8wwGR6ul

The link will last around 1 week, it's just one frame of a simulation.

**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79 **Blender Version** Broken: version: 3.1.0 Beta, branch: master, commit date: 2022-02-20 22:00, hash: `1a0a22f95a` **Short description of error** When importing an Alembic file, velocity is not being imported, cycles is not using it and GN is incapable of seeing it. **Exact steps for others to reproduce the error** Import given Alembic file and look for velocity. https://we.tl/t-nq8wwGR6ul The link will last around 1 week, it's just one frame of a simulation.
Author

Added subscriber: @juang3d

Added subscriber: @juang3d

#96873 was marked as duplicate of this issue

#96873 was marked as duplicate of this issue
Member

Added subscriber: @OmarEmaraDev

Added subscriber: @OmarEmaraDev
Member

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Member

Can confirm missing velocity attribute. Alembic listing:

/:
StormPoints
/StormPoints:
.geom
/StormPoints/.geom:
.selfBnds   P   .pointIds   .velocities   .widths   .arbGeomParams   /StormPoints/.arbGeomParams:
Cd   emissionPos   emitterId
Can confirm missing velocity attribute. Alembic listing: ``` /: StormPoints /StormPoints: .geom /StormPoints/.geom: .selfBnds P .pointIds .velocities .widths .arbGeomParams /StormPoints/.arbGeomParams: Cd emissionPos emitterId ```

Added subscriber: @SteffenD

Added subscriber: @SteffenD

Added subscribers: @kevindietrich, @brecht

Added subscribers: @kevindietrich, @brecht

CC @kevindietrich

@OmarEmaraDev, bug reports should always be tagged with a module when confirmed, to ensure someone looks at it.

CC @kevindietrich @OmarEmaraDev, bug reports should always be tagged with a module when confirmed, to ensure someone looks at it.

The Alembic contains only points. AFAIK velocities / attributes on points are not yet supported in Alembic import?

The Alembic contains only points. AFAIK velocities / attributes on points are not yet supported in Alembic import?
Member

@brecht Noted. I didn't realize projects might not be modules.

@SteffenD I am not sure, lets wait for Kevin to look into it.

@brecht Noted. I didn't realize projects might not be modules. @SteffenD I am not sure, lets wait for Kevin to look into it.
Author

@SteffenD In the current Alembic implementation points are interpreted as vertices, and velocities should be there for those vertices, other attributes would be ignored basically because there are not read, but velocity is the only one that was read to be able to render it with Cycles.
So even when they are points, when imported they are vertices and those should have velocity if it exists, at least is what I understand, I may be wrong, @kevindietrich would know better :)

@SteffenD In the current Alembic implementation points are interpreted as vertices, and velocities should be there for those vertices, other attributes would be ignored basically because there are not read, but velocity is the only one that was read to be able to render it with Cycles. So even when they are points, when imported they are vertices and those should have velocity if it exists, at least is what I understand, I may be wrong, @kevindietrich would know better :)

It is not strictly a bug in the sense that there is no support yet for reading arbitrary attributes for Alembic point clouds yet.

Although:

  • we do read normals for point clouds (I added this back in the day for somehow to instantiate objects on the points and give them a direction, the example was a fish school)
  • given that we load point clouds as meshes, and that regular meshes do have velocities loaded, this could be considered a bug

I can add support for this, but depending if we consider this a bug or not, it will either go to 3.1 or 3.2.

It is not strictly a bug in the sense that there is no support yet for reading arbitrary attributes for Alembic point clouds yet. Although: - we do read normals for point clouds (I added this back in the day for somehow to instantiate objects on the points and give them a direction, the example was a fish school) - given that we load point clouds as meshes, and that regular meshes do have velocities loaded, this could be considered a bug I can add support for this, but depending if we consider this a bug or not, it will either go to 3.1 or 3.2.

I posted too quickly, if we do not consider this a bug and this should go to 3.2, then it will be probably handled by D11591: Alembic: import arbitrary attributes (which currently lacks unit tests).

I posted too quickly, if we do not consider this a bug and this should go to 3.2, then it will be probably handled by [D11591: Alembic: import arbitrary attributes](https://archive.blender.org/developer/D11591) (which currently lacks unit tests).

I just gave some point clouds with velocity vectors coming from different source software a try (in Blender 2.93, 3.01 final and in 3.2 master) and never could get motion vectors to import. I also tried animated point clouds with static and changing point counts and a (particle) point cloud exported from Blender that successfully exports its motion vectors to an Alembic but doesn't load them back in. They're actually there, I confirmed it in 3rd party software.
So apart from a patch by @kevindietrich I think Blender never supported velocity on points / vertices?

I just gave some point clouds with velocity vectors coming from different source software a try (in Blender 2.93, 3.01 final and in 3.2 master) and never could get motion vectors to import. I also tried animated point clouds with static and changing point counts and a (particle) point cloud exported from Blender that successfully exports its motion vectors to an Alembic but doesn't load them back in. They're actually there, I confirmed it in 3rd party software. So apart from a patch by @kevindietrich I think Blender never supported velocity on points / vertices?

Support for reading velocity for meshes was added in 2.92 I think (when I added motion blur support). Back then, Cycles could not render point clouds so I was useless to import velocity for them, and no other tool could really make anything with point clouds imported from Alembic. The only use case was scattering/instancing.

Support for reading velocity for meshes was added in 2.92 I think (when I added motion blur support). Back then, Cycles could not render point clouds so I was useless to import velocity for them, and no other tool could really make anything with point clouds imported from Alembic. The only use case was scattering/instancing.
Author

That's why I assumed that we should have velocity, since the actual import of the points is a mesh with vertices, I could swear that I saw it working at some point, and I even remember using Alembic to export particles from Mantaflow and reimport them to have motion blur, but I may be totally wrong, I have many things in my head.

The thing is that if what it's being imported is a mesh, and we have a place in the modifier to read the velocities, why is that not being imported?

Anyways, this could be a feature and not a bug, I'll leave this up to you, for 3.1 I think it's pity to not have velocities in points now that we have point cloud rendering, but as I said, I'll leave this up to you, whatever you decide will be what it's done, from my POV it's a bug because meshes has velocities support and points are imported as mesh :)

That's why I assumed that we should have velocity, since the actual import of the points is a mesh with vertices, I could swear that I saw it working at some point, and I even remember using Alembic to export particles from Mantaflow and reimport them to have motion blur, but I may be totally wrong, I have many things in my head. The thing is that if what it's being imported is a mesh, and we have a place in the modifier to read the velocities, why is that not being imported? Anyways, this could be a feature and not a bug, I'll leave this up to you, for 3.1 I think it's pity to not have velocities in points now that we have point cloud rendering, but as I said, I'll leave this up to you, whatever you decide will be what it's done, from my POV it's a bug because meshes has velocities support and points are imported as mesh :)

Added subscriber: @Funnybob

Added subscriber: @Funnybob
Bastien Montagne added this to the Pipeline, Assets & IO project 2023-02-09 15:40:38 +01:00
Philipp Oeser removed the
Interest
Pipeline, Assets & IO
label 2023-02-10 08:54:05 +01:00
Blender Bot added
Status
Resolved
and removed
Status
Confirmed
labels 2024-01-04 09:25:40 +01:00
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 Assignees
6 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#95945
No description provided.