Alembic doesn't import vertex colors for meshes made of only vertices #109749

Open
opened 2023-07-05 16:21:12 +02:00 by mantissa · 8 comments

System Information
Operating system: Linux-5.15.0-76-generic-x86_64-with-glibc2.35 64 Bits, X11 UI
Graphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 525.125.06

Blender Version
Broken: Version: 3.6.0, branch: blender-v3.6-release, commit date: 2023-06-27 08:08, hash: c7fc78b81ecb
Worked: Never.

Short description of error
When importing Alembic caches, vertex colors are only imported correctly when the imported geometry is made of faces.
When the geometry is only vertices, no vertex colors are imported. (ex. point clouds)

I suspect this has to do with vertex colors encoded as a point attribute instead of a face corner attribute.
I've checked both provided alembic files in other software to make sure they're not the issue and they work fine everywhere else.

Exact steps for others to reproduce the error

  1. Import mesh.abc.
  2. Vertex colors are read correctly and are stored and accessible as a Face Corner attribute.
  3. Import points.abc.
  4. Vertex colors aren't read at all, expected behavior is that they're stored stored as a Vertex attribute.
**System Information** Operating system: Linux-5.15.0-76-generic-x86_64-with-glibc2.35 64 Bits, X11 UI Graphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 525.125.06 **Blender Version** Broken: Version: 3.6.0, branch: blender-v3.6-release, commit date: 2023-06-27 08:08, hash: `c7fc78b81ecb` Worked: Never. **Short description of error** When importing Alembic caches, vertex colors are only imported correctly when the imported geometry is made of faces. When the geometry is only vertices, no vertex colors are imported. (ex. point clouds) I suspect this has to do with vertex colors encoded as a point attribute instead of a face corner attribute. I've checked both provided alembic files in other software to make sure they're not the issue and they work fine everywhere else. **Exact steps for others to reproduce the error** 1. Import mesh.abc. 2. Vertex colors are read correctly and are stored and accessible as a Face Corner attribute. 3. Import `points.abc`. 4. Vertex colors aren't read at all, expected behavior is that they're stored stored as a Vertex attribute.
3.1 MiB
9.6 MiB
mantissa added the
Type
Report
Status
Needs Triage
Severity
Normal
labels 2023-07-05 16:21:13 +02:00
YimingWu changed title from Alembic doesn't import vertex type attribute vertex colors to Alembic doesn't import vertex colors for meshes made of only vertices 2023-07-06 05:41:03 +02:00
Member

Can confirm. Not sure if this a limitation of Blender or it's just a situation that alembic importer fails to handle.

@ideasman42 or @dr.sybren may want to take a look

Can confirm. Not sure if this a limitation of Blender or it's just a situation that alembic importer fails to handle. @ideasman42 or @dr.sybren may want to take a look
Member

It seems alembic don't export attributes other than face-corner domain: #99293
Closing

It seems alembic don't export attributes other than face-corner domain: #99293 Closing
Blender Bot added
Status
Archived
and removed
Status
Confirmed
labels 2023-07-06 06:17:02 +02:00
Pratik Borhade added
Status
Duplicate
and removed
Status
Archived
labels 2023-07-06 06:17:15 +02:00
Member

Not sure why this was closed.

The referenced report is about export (and still open) and the closed report is about import?
Will check on this.

Not sure why this was closed. The referenced report is about export (and still open) and the closed report is about import? Will check on this.
Blender Bot added
Status
Needs Triage
and removed
Status
Duplicate
labels 2023-07-06 10:16:44 +02:00
Member

It is more of a TODO tbh, but will put on my desk

It is more of a TODO tbh, but will put on my desk
Philipp Oeser self-assigned this 2023-07-06 12:00:31 +02:00
Philipp Oeser added
Status
Confirmed
Type
To Do
and removed
Status
Needs Triage
Type
Report
labels 2023-07-06 12:00:48 +02:00
Member

Got it working, now needs a bit of cleanup and discussion in regards to

  • CD_PROP_BYTE_COLOR vs. CD_PROP_COLOR (atm. this is always CD_PROP_BYTE_COLOR and the data in the file looks like that as well, not sure if alembic can do differently as well?)
  • should importing be optional (as in the USD importer)?
  • once we are at it, exporting might be desired as well, not sure if there are any conventions in other apps as to how to handle this on the vertex domain? (the file from the report comes with kVaryingScope -- not kVertexScope -- atm. I only check the data size, if it is the same length as we have vertices, the attribute is created on the vertex domain...)
  • more come up along the way...

image

Got it working, now needs a bit of cleanup and discussion in regards to - `CD_PROP_BYTE_COLOR` vs. `CD_PROP_COLOR` (atm. this is always `CD_PROP_BYTE_COLOR` and the data in the file looks like that as well, not sure if alembic can do differently as well?) - should importing be optional (as in the USD importer)? - once we are at it, exporting might be desired as well, not sure if there are any conventions in other apps as to how to handle this on the vertex domain? (the file from the report comes with `kVaryingScope` -- not `kVertexScope` -- atm. I only check the data size, if it is the same length as we have vertices, the attribute is created on the vertex domain...) - more come up along the way... ![image](/attachments/73b3d952-9d70-45db-bd32-a3efb7a33e01)
878 KiB
Author

Thanks for looking in to this so quickly.

For reference, both alembics were exported from Houdini with default settings. I can have a look at the export options there if there's anything you'd like to know.

Thanks for looking in to this so quickly. For reference, both alembics were exported from Houdini with default settings. I can have a look at the export options there if there's anything you'd like to know.
Member

OK, so apparently we have a much more generic solution in the works (at least for USD), see #109518, will try to coordinate this to have the alembic counterpart (not yet sure if alembic supports all of what USD does) coming along with the same features.

OK, so apparently we have a much more generic solution in the works (at least for USD), see https://projects.blender.org/blender/blender/pulls/109518, will try to coordinate this to have the alembic counterpart (not yet sure if alembic supports all of what USD does) coming along with the same features.
Member

Sorry, will step down to not block others on this matter (as I feel the way to go forward would be something more generic like #109518)

Sorry, will step down to not block others on this matter (as I feel the way to go forward would be something more generic like #109518)
Philipp Oeser removed their assignment 2023-09-26 12:59:22 +02:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
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
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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#109749
No description provided.