Uncorrect FBX import #96179
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#96179
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows-10-10.0.19042-SP0 64 Bits
Graphics card: Radeon RX 5500 XT ATI Technologies Inc. 4.5.14802 Core Profile Context 22.1.1 30.0.14023.1009
Blender Version
Broken: version: 3.0.1, branch: master, commit date: 2022-01-25 17:19, hash:
blender/blender@dc2d180181Worked: any versions of blender does not iport this file
Short description of error
Not Import the file
Exact steps for others to reproduce the error
After open Blender, I use File > Import > Fbx` menu item, I select uploaded file and confirm import, after I cannot see any object or data on viewport or Outline. Imported elements are visible as Orphan Data inside Outliner. At the same time, there are no import errors. After importing the FBX file, absolutely nothing happens, but only unused data appears in the scene hierarchy window in the tab (unused data).
Based on the default startup.
Added subscriber: @Maksim-34
Good afternoon, the FBX file is not imported in the blender.
There are no errors when importing, but the scene is empty, and in the standard Windows viewer everything is displayed correctly, in the 3ds max program - correctly, Autodesk FBX Review - correctly, Unity - correctly. Now I looked at the import in the blender, but there is still an unused data tab. I'll attach the file. Thanks.
Архив ZIP - WinRAR.zip
Removed subscriber: @Maksim-34
Added subscriber: @PratikPB2123
Added subscriber: @OmarEmaraDev
Changed status from 'Needs Triage' to: 'Confirmed'
Can confirm. It seems only the mesh is imported as an orphan and nothing is linked to the scene.
Added subscriber: @mont29
Changed status from 'Confirmed' to: 'Needs User Info'
Unfortunately a 4MB FBX file is not an acceptable reproducible case, investigating relationships etc. in such a monster is not realistic feasible. Please attach a simple reproducible case (like a cube with one or two bones rig or so).
This file is opened by all kinds of programs except blender. I can't post a simple animation club because this file is generated by a script in automatic mode and I can't write any other one. Will I say that the file is correctly displayed and imported into such types of programs as 3ds max, FBX review (Autodesk), Standard 3d viewer windows and others, there is no correct import in one blender program.
Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'
Changed status from 'Needs Developer To Reproduce' to: 'Archived'
Then am afraid there is no point in keeping this report open. Someone may have the time and will to dive into this file and understand what happens, or you may be able to create a investigable reproducible case in the future.
Thanks for the report anyway, please feel free to re-create it should you have new information about the issue.