Alembic: locations issue #50403

Closed
opened 2017-01-09 14:53:40 +01:00 by paul geraskin · 17 comments
Member

System Information

Blender Version
2.78

Short description of error
I have exported alembic from houdini. But in blender it's imported with strange locations.
test.abc
Selection_012.png
Selection_013.png

Exact steps for others to reproduce the error
Import Alembic

**System Information** **Blender Version** 2.78 **Short description of error** I have exported alembic from houdini. But in blender it's imported with strange locations. [test.abc](https://archive.blender.org/developer/F430572/test.abc) ![Selection_012.png](https://archive.blender.org/developer/F430573/Selection_012.png) ![Selection_013.png](https://archive.blender.org/developer/F430575/Selection_013.png) **Exact steps for others to reproduce the error** Import Alembic
Author
Member

Changed status to: 'Open'

Changed status to: 'Open'
Author
Member

Added subscriber: @PaulGeraskin

Added subscriber: @PaulGeraskin

Added subscriber: @dfelinto

Added subscriber: @dfelinto
Kévin Dietrich was assigned by Dalai Felinto 2017-01-10 11:38:19 +01:00

Assigning to our alembic guru ;)

Assigning to our alembic guru ;)

Added subscriber: @dr.sybren

Added subscriber: @dr.sybren

@PaulGeraskin: Since I don't have Houdini to compare with, can you tell me which locations you expected to see in Blender, and which you are actually seeing? I understand that the clock should actually be on the tower, but having some concrete numbers will make things easier to reproduce & fix.

@PaulGeraskin: Since I don't have Houdini to compare with, can you tell me which locations you expected to see in Blender, and which you are actually seeing? I understand that the clock should actually be on the tower, but having some concrete numbers will make things easier to reproduce & fix.

Added subscriber: @zeauro

Added subscriber: @zeauro

We just have to clear location of empty object named geo1 to obtain a coherent scene in blender.

Does this object have a different scale than the others in Houdini ?

We just have to clear location of empty object named geo1 to obtain a coherent scene in blender. Does this object have a different scale than the others in Houdini ?
Author
Member

I cannot see transforms in Houdini. Sorry.

But in Fusion I imported the file. Possibly it will help you somehow.
See Offset values.
Selection_022.png

I cannot see transforms in Houdini. Sorry. But in Fusion I imported the file. Possibly it will help you somehow. See Offset values. ![Selection_022.png](https://archive.blender.org/developer/F442680/Selection_022.png)
Author
Member

And as was said by Ronan. If you clear position of this empty object - it will be ok.
Selection_023.png

And as was said by Ronan. If you clear position of this empty object - it will be ok. ![Selection_023.png](https://archive.blender.org/developer/F442682/Selection_023.png)
Author
Member

In Houdini Geo1 is a house.
Selection_024.png

Selection_025.png

In Houdini Geo1 is a house. ![Selection_024.png](https://archive.blender.org/developer/F442685/Selection_024.png) ![Selection_025.png](https://archive.blender.org/developer/F442689/Selection_025.png)

The issue most likely comes from the confusing logic that is used to convert data between Blender and Alembic, especially Alembic Y-up matrices to Blender Z-up ones. In the process, to create the Blender matrices, we multiply the matrices of the Alembic object with the one from its parent recursively, so maybe in this case the object matrix is somehow multiplied twice. The relevant function is in abc_util.cc .

I worked on, a few months ago, refactoring the Alembic importer to make use of a hierarchical tree like data-structure to more easily convert data between Blender and Alembic. It made the code easier to follow, and got rid of some special funky cases, but the matrices ended up being "corrupted" in some imported files which I didn't have the time to fully investigate, though chances are it was due to accumulating the same matrix over and over again.

The issue most likely comes from the confusing logic that is used to convert data between Blender and Alembic, especially Alembic Y-up matrices to Blender Z-up ones. In the process, to create the Blender matrices, we multiply the matrices of the Alembic object with the one from its parent recursively, so maybe in this case the object matrix is somehow multiplied twice. The relevant function is in [abc_util.cc ](https://developer.blender.org/diffusion/B/browse/master/source/blender/alembic/intern/abc_util.cc;4580ace4c1fe984f707385ea0318c53389fd2916$213). I worked on, a few months ago, refactoring the Alembic importer to make use of a hierarchical tree like data-structure to more easily convert data between Blender and Alembic. It made the code easier to follow, and got rid of some special funky cases, but the matrices ended up being "corrupted" in some imported files which I didn't have the time to fully investigate, though chances are it was due to accumulating the same matrix over and over again.

Does it mean that problem occurs for every object with a negative Z location in Houdini ?

Does it mean that problem occurs for every object with a negative Z location in Houdini ?

This should be fixed as of commit c684fab8a6

Please test with a build from https://builder.blender.org/download/ (unless you're on MacOS, then wait until the Alembic library on the MacOS build bot have been upgraded).

This should be fixed as of commit c684fab8a6 Please test with a build from https://builder.blender.org/download/ (unless you're on MacOS, then wait until the Alembic library on the MacOS build bot have been upgraded).
Kévin Dietrich was unassigned by Sybren A. Stüvel 2017-04-13 16:45:40 +02:00
Sybren A. Stüvel self-assigned this 2017-04-13 16:45:40 +02:00

Added subscriber: @kevindietrich

Added subscriber: @kevindietrich

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

Marking as resolved. Feel free to leave a comment when there are still issues (but please open up another ticket if it's a different issue).

Marking as resolved. Feel free to leave a comment when there are still issues (but please open up another ticket if it's a different issue).
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
5 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#50403
No description provided.