Alembic Import: Visibility #69191

Open
opened 2019-08-26 23:51:12 +02:00 by Kevin C. Burke · 20 comments
Contributor

System Information
Operating system: Microsoft Windows 10 Pro, 10.0.18362 Build 18362
Installed Physical Memory: 64.0 GB
Graphics card: NVIDIA GeForce GTX Titan Black, Driver 26.21.14.3064

Blender Version
Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: f6cb5f5449, type: build date: 2019-07-29, 09:44 AM

Short description of error
When importing Alembic files, visibility is not recognized by Blender as it is in other 3D applications. This is important when using multiple proxy objects in another application that need to be invisible when imported.
Alembic_Visibility.jpg

Example Alembic with Visibility
Alembic_Visibility.abc

Exact steps for others to reproduce the error

  1. Turn off the visibility of an object in the Outliner (I tried this with Cinema 4D and Blender)
  2. Export Alembic
  3. Import the file
    Blender does not recognize the Visibility properties

Example Blend file with Example Alembic attachment above
Alembic_Visibility.blend

Implementation of other Alembic Properties may also be considered as in Cinema 4D's Alembic Import Dialog
{F7705176}

**System Information** Operating system: Microsoft Windows 10 Pro, 10.0.18362 Build 18362 Installed Physical Memory: 64.0 GB Graphics card: NVIDIA GeForce GTX Titan Black, Driver 26.21.14.3064 **Blender Version** Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: f6cb5f54494e, type: build date: 2019-07-29, 09:44 AM **Short description of error** When importing Alembic files, visibility is not recognized by Blender as it is in other 3D applications. This is important when using multiple proxy objects in another application that need to be invisible when imported. ![Alembic_Visibility.jpg](https://archive.blender.org/developer/F7705144/Alembic_Visibility.jpg) *Example Alembic with Visibility* [Alembic_Visibility.abc](https://archive.blender.org/developer/F7705151/Alembic_Visibility.abc) **Exact steps for others to reproduce the error** 1. Turn off the visibility of an object in the Outliner (I tried this with Cinema 4D and Blender) 2. Export Alembic 3. Import the file Blender does not recognize the Visibility properties *Example Blend file with Example Alembic attachment above* [Alembic_Visibility.blend](https://archive.blender.org/developer/F7705153/Alembic_Visibility.blend) *Implementation of other Alembic Properties may also be considered as in Cinema 4D's Alembic Import Dialog* {F7705176}
Author
Contributor

Added subscriber: @KevinCBurke

Added subscriber: @KevinCBurke

Added subscriber: @AbidMaqbool

Added subscriber: @AbidMaqbool

Latest Blender 2.81 ce2368cf69 same behavior...
IMO, not a bug/error yet a feature/improvement or so on..

Latest Blender 2.81 ce2368cf69 same behavior... IMO, not a bug/error yet a feature/improvement or so on..
Member

Added subscribers: @dr.sybren, @lichtwerk

Added subscribers: @dr.sybren, @lichtwerk
Sybren A. Stüvel was assigned by Philipp Oeser 2019-08-27 10:54:33 +02:00
Member

In a way this is similar to the lack of importing e.g. Focal Length (#54050 (Alembic: Camera properties (focal length, focus distance, ...) animation not importing)), or Custom Properties (#50725 (Alembic export doesn't take 'Custom Properties', as alembic non-standard data.)).

Right now, Alembic in blender is based on modifiers and constraints, so that streaming will work and everything is updated when the .abc gets updated (well not entirely, but almost).
So (for me), this looks like a similar problem: If support for visibility is to come, it should work with something like D2324: Alembic: F-Curve cache modifier to lookup arbitrary property animations. (supporting animations and doing the disc read automatically without the need to reload an .abc manually if anything in there changed...).
@dr.sybren: what do you think? Of course reading visibility once could be an option [but I think the F-Curve cache modifier sounds like the way to go, no?]

That all being said, this is not really a bug, but a feature request, question is if we keep this as TODO for {#69058}?

Will let @dr.sybren decide...

In a way this is similar to the lack of importing e.g. Focal Length (#54050 (Alembic: Camera properties (focal length, focus distance, ...) animation not importing)), or Custom Properties (#50725 (Alembic export doesn't take 'Custom Properties', as alembic non-standard data.)). Right now, Alembic in blender is based on modifiers and constraints, so that streaming will work and everything is updated when the .abc gets updated (well not entirely, but almost). So (for me), this looks like a similar problem: If support for visibility is to come, it should work with something like [D2324: Alembic: F-Curve cache modifier to lookup arbitrary property animations.](https://archive.blender.org/developer/D2324) (supporting animations and doing the disc read automatically without the need to reload an .abc manually if anything in there changed...). @dr.sybren: what do you think? Of course reading visibility once could be an option [but I think the F-Curve cache modifier sounds like the way to go, no?] That all being said, this is not really a bug, but a feature request, question is if we keep this as TODO for {#69058}? Will let @dr.sybren decide...

Added subscriber: @SerjMaiorov

Added subscriber: @SerjMaiorov

We have the same problem:
Rig Test_02-Comparison.mp4
As you can see, the rigger used "Write visibility" option to swap between face parts. In Blender - all planes are visible.

We have the same problem: [Rig Test_02-Comparison.mp4](https://archive.blender.org/developer/F7713916/Rig_Test_02-Comparison.mp4) As you can see, the rigger used "Write visibility" option to swap between face parts. In Blender - all planes are visible.

Here are the Alembic file and the texture for the swapping face parts.
dad7.abc
dad_grid_05.png
Moreover, in the beginning, the rigger used moving UV's as a way to stay with the same plane and still swap between the faces texture grid, but it also didn't work in Blende...

Here are the Alembic file and the texture for the swapping face parts. [dad7.abc](https://archive.blender.org/developer/F7713925/dad7.abc) ![dad_grid_05.png](https://archive.blender.org/developer/F7713929/dad_grid_05.png) Moreover, in the beginning, the rigger used moving UV's as a way to stay with the same plane and still swap between the faces texture grid, but it also didn't work in Blende...

This is indeed not a bug, it's simply a property that's written to Alembic and that's not read by Blender. Alembic is quite bad in this respect, in that there is no well-documented open standard in which such properties are defined. I'd be very happy if you can prove me wrong on this one.

Features like this one and the others @lichtwerk mentioned should probably wait until #69046 (Cache loading via animation system) has been implemented. That will give us a much better way to load arbitrary properties from Alembic.

This is indeed not a bug, it's simply a property that's written to Alembic and that's not read by Blender. Alembic is quite bad in this respect, in that there is no well-documented open standard in which such properties are defined. I'd be very happy if you can prove me wrong on this one. Features like this one and the others @lichtwerk mentioned should probably wait until #69046 (Cache loading via animation system) has been implemented. That will give us a much better way to load arbitrary properties from Alembic.

Added subscriber: @PixelTrader

Added subscriber: @PixelTrader
Member

Added subscriber: @LukasStockner

Added subscriber: @LukasStockner
Member

In case anyone's interested, here's a quick and dirty patch for importing static visibility: P1264

Does not support animated visibility or reloading when the file changes due to the mentioned design challenges.

In case anyone's interested, here's a quick and dirty patch for importing static visibility: [P1264](https://archive.blender.org/developer/P1264.txt) Does not support animated visibility or reloading when the file changes due to the mentioned design challenges.
Author
Contributor

In #69191#876351, @LukasStockner wrote:
In case anyone's interested, here's a quick and dirty patch for importing static visibility: P1264

Does not support animated visibility or reloading when the file changes due to the mentioned design challenges.

So exciting to see progress on this!!!!!

> In #69191#876351, @LukasStockner wrote: > In case anyone's interested, here's a quick and dirty patch for importing static visibility: [P1264](https://archive.blender.org/developer/P1264.txt) > > Does not support animated visibility or reloading when the file changes due to the mentioned design challenges. So exciting to see progress on this!!!!!
Sybren A. Stüvel removed their assignment 2021-01-14 18:00:55 +01:00
Author
Contributor

This comment was removed by @KevinCBurke

*This comment was removed by @KevinCBurke*

Added subscriber: @zrp

Added subscriber: @zrp

Added subscriber: @Mentales

Added subscriber: @Mentales

Added subscriber: @ChrisR-2

Added subscriber: @ChrisR-2
Philipp Oeser removed the
Interest
Pipeline, Assets & IO
label 2023-02-10 08:54:21 +01:00

This issue has been flagged more than 3 years ago and it's a real show stopper in VFX. Badly need a fix please

This issue has been flagged more than 3 years ago and it's a real show stopper in VFX. Badly need a fix please

Is there any progress or plans for this issue?
Currently there is no way to send visibility keyframe animations.
USD is not possible either. The problem is even worse when importing a scene into blender with complex visibility animations.
This is one of the hardest parts of using Blender in production.
It becomes too much of a problem when importing scenes animated in other DCCs into Blender for lighting and rendering.

Is there any progress or plans for this issue? Currently there is no way to send visibility keyframe animations. USD is not possible either. The problem is even worse when importing a scene into blender with complex visibility animations. This is one of the hardest parts of using Blender in production. It becomes too much of a problem when importing scenes animated in other DCCs into Blender for lighting and rendering.

Is there a solution for this? No news..

Is there a solution for this? No news..
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
13 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#69191
No description provided.