FBX and Alembic export does not support instances anymore #49458

Closed
opened 2016-09-26 21:13:26 +02:00 by Daniel Bystedt · 8 comments
Member

System Information
windows 7
nvidia GeForce GTX 660

Blender Version
Broken: 7c53260
works: 2.77 official release abf6f08

When I export multiple object that share the same object data (in other word is instances) the object data connection is lost. After I import the fbx or alembic to blender or maya the object data connection is lost. The objects are not instances anylonger.

Exact steps for others to reproduce the error
Based on a (as simple as possible) attached .blend file with minimum amount of steps

  1. press file>export>fbx/alembic and export to disc
  2. Open new scene in blender or other application
  3. press file>import>fbx/alembic and select the source file
  4. Try to remodel one of the objects. You can now see that they no longer are instances
    instance.blend
**System Information** windows 7 nvidia GeForce GTX 660 **Blender Version** Broken: 7c53260 works: 2.77 official release abf6f08 When I export multiple object that share the same object data (in other word is instances) the object data connection is lost. After I import the fbx or alembic to blender or maya the object data connection is lost. The objects are not instances anylonger. **Exact steps for others to reproduce the error** Based on a (as simple as possible) attached .blend file with minimum amount of steps 1. press file>export>fbx/alembic and export to disc 2. Open new scene in blender or other application 3. press file>import>fbx/alembic and select the source file 4. Try to remodel one of the objects. You can now see that they no longer are instances [instance.blend](https://archive.blender.org/developer/F368717/instance.blend)
Author
Member

Changed status to: 'Open'

Changed status to: 'Open'
Author
Member

Added subscriber: @DanielBystedt

Added subscriber: @DanielBystedt

Added subscribers: @mont29, @kevindietrich

Added subscribers: @mont29, @kevindietrich

Instancing is not, and was never, supported in the Alembic exporter and Alembic is new so I would hardly call it a regression or even a bug. There is also the issue of supporting instancing in the importer (not sure how that would work, given that files might come from software, etc...). So I guess we would have to poke @mont29 for the FBX case.

Instancing is not, and was never, supported in the Alembic exporter and Alembic is new so I would hardly call it a regression or even a bug. There is also the issue of supporting instancing in the importer (not sure how that would work, given that files might come from software, etc...). So I guess we would have to poke @mont29 for the FBX case.

Can’t confirm that here for FBX, it does export and re-import as a single mesh… Are you sure you are using correct version of FBX addon (should be 3.7.7)?

Can’t confirm that here for FBX, it does export and re-import as a single mesh… Are you sure you are using correct version of FBX addon (should be 3.7.7)?
Author
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Daniel Bystedt self-assigned this 2016-09-28 01:53:29 +02:00
Author
Member

Done some research

Alembic in maya does not seem to support instances either

FBX with instances now suddenly works. It failed both at work and at home, but now it works so I must have used some strange setting. Can't reproduce the error again.

So sorry for waisting your time, guys. Keep up the good work. I've set this report to "invalid"

/Bystedt

Done some research Alembic in maya does not seem to support instances either FBX with instances now suddenly works. It failed both at work and at home, but now it works so I must have used some strange setting. Can't reproduce the error again. So sorry for waisting your time, guys. Keep up the good work. I've set this report to "invalid" /Bystedt

Just a note about FBX and instances: if you have modifiers on your objects and export them in FBX, then you obviously export one different mesh per object, maybe that’s what happened for you?

Just a note about FBX and instances: if you have modifiers on your objects and export them in FBX, then you obviously export one different mesh per object, maybe that’s what happened for you?
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
3 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#49458
No description provided.