unwrap hipoly mesh causes crash #35432

Closed
opened 2013-05-19 13:22:57 +02:00 by Michal David · 6 comments

%%%--- Operating System, Graphics card ---
win7 64bit, ati radeon 6900, cpu i7, 16GB ram

- Blender version with error, and version that worked ---

2.67

- Short description of error ---

unwrap hipoly mesh causes crash, it always happen when i try unwrap mesh with 200k+ vertices

I tried post .blend file, but system refused it (too big file?)
%%%

%%%--- Operating System, Graphics card --- win7 64bit, ati radeon 6900, cpu i7, 16GB ram - Blender version with error, and version that worked --- 2.67 - Short description of error --- unwrap hipoly mesh causes crash, it always happen when i try unwrap mesh with 200k+ vertices I tried post .blend file, but system refused it (too big file?) %%%
Author

Changed status to: 'Open'

Changed status to: 'Open'

%%%Try to upload it elsewhere (pasteall.org or another sharehoster) %%%

%%%Try to upload it elsewhere (pasteall.org or another sharehoster) %%%
Author

%%%Here is file to download
http://www.pasteall.org/blend/21473%%%

%%%Here is file to download http://www.pasteall.org/blend/21473%%%
Author

%%%Sorry for the panic. It seems unwrap 78K faces (234k vertices) finally succeeded.
It took 37 minutes!
I have been impatient and I've not wait until the operation completes.
However, I do not understand why it takes so long. It seems that the operation is performed only by one core of CPU.
If there is a good reason why it should take so long, so I suggest that there is a progress indicator.
Throughout calculating operating system reported that the application does not respond.

Is it bug? I say yes :)%%%

%%%Sorry for the panic. It seems unwrap 78K faces (234k vertices) finally succeeded. It took 37 minutes! I have been impatient and I've not wait until the operation completes. However, I do not understand why it takes so long. It seems that the operation is performed only by one core of CPU. If there is a good reason why it should take so long, so I suggest that there is a progress indicator. Throughout calculating operating system reported that the application does not respond. Is it bug? I say yes :)%%%

%%%I fixed on particularly slow part of this, unwrapping this mesh takes 30 seconds now here (but the results isn't particularly useful without seams).

Ideally we should have progress bars for all potentially slow operations but this is basically a known limitation, we should implement a general system once that can show progress for all our tools. I won't consider that a bug, just a todo item.%%%

%%%I fixed on particularly slow part of this, unwrapping this mesh takes 30 seconds now here (but the results isn't particularly useful without seams). Ideally we should have progress bars for all potentially slow operations but this is basically a known limitation, we should implement a general system once that can show progress for all our tools. I won't consider that a bug, just a todo item.%%%

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
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#35432
No description provided.