OBJ Import failure (works on 2.79) #64740
Labels
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#64740
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.17763 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 416.94
Blender Version
Broken: version: 2.80 (sub 60), branch: blender2.7, commit date: 2019-05-07 19:17, hash:
3dc9da3a74
(splash screen says 3d9da3a74ee)Worked: 2.79 hash:
f4dc9f9d68
Short description of error
Tryed importing a heavy .obj into blender 2.8 and it crashed 3 times.
worked on the first try on 2.79. Then i opened this file on 2.8 with no problem.
Exact steps for others to reproduce the error
The file is a stupid useless heavy export from that piece of junk called SketchUp (someone put 2 bonsai in it that has 18.000 objects as leaves, each).
Probally deleting this bonsai from the file may help importing into 2.8.
But i wonder, if 2.79 could import it, why 2.8 could't?
The .obj for testing is here : Projeto Ape 2019.obj
Warning. It will take some minutes.
Added subscriber: @HenriqueGonzaga
Added subscriber: @StephenSwaney
You wouldn't want to give us a hint and show us the error message?
There is no message. Blender just closes.
Sometimes you can trick Blender into revealing secrets by running it from the command line.
I can import your .obj on Linux, but it looks like Blender needs over 2 Gb of memory to do so.
You might try running from the command line and looking for messages about calloc or malloc returns nil.
This is a sign of running out of memory.
I have 32 Gb of memory..
And if it refers to my GPU, I think it has 4Gb
I don't know how to use the command line.
Just wondered why 2.79 worked and 2.8 didn't..
That shoots my lack of memory theory. I got nothing...
Added subscriber: @mont29
As for using command line… http://www.letmegooglethat.com/?q=windows+command+line
Monster file imports fine for me as well, we cannot do anything else without more info…
Added subscriber: @Mets
Windows 10, v1607
GTX 1070 latest drivers
16GB RAM
Attempt 1, importing to 2.80, 65168825e0b0:
Huh. I can actually reproduce this. After a minute or two of waiting, blender just closes.
Attempt 2, I started importing to 2.80 and 2.7 at the same time(to save time and test both), this time from command line:
My computer has gone completely haywire, screens started flashing, desktop disappeared, and a few seconds later(not long enough for a reboot) I was greeted by my windows login screen, and all my apps are closed, and only my second monitor works. A PC reboot fixed this.
Attempt 3, importing only to 2.80 again, with command line:
Console output:
Changed status from 'Open' to: 'Archived'
@Mets that’s lack of available RAM (or GPU RAM, code fails to allocate needed memory). Not much to be done here, besides general optimization of Blender. but that is not a bug afaiks.
In any case, no answer from OP since over a month, more than time to archive.