sculpting performance in viewport #41753

Closed
opened 2014-09-08 18:10:32 +02:00 by Marios Makris · 6 comments

Core I5
ATI Graphics card 6370m 1G
6GB RAM

Blender version: 2.71
Hash: 9337574

Sculpting performance in viewport MIGHT have been solved by unableing a feature.

When I started sculpting for the first time my viewport was lagging and I thought i needed more ram, but after a while (2 days) lag dissapeared.

My 90 thousand verts sculpt was going smooth.
Modifier used: Moltires

I started a new blender project and the lag is back, not only for my new project but for my old one's too.

So after reading on forums for hours to find the solution, I found nothing.

After switching on and off every thing in Blender, I found out that under the sculpting menu (where brushes and etc. are found)
on the options tab on "Threaded sculpt", when I switched it off the smoothness was back. Finally.:)

I tested most of the brushes on my sculpt for 5 to 10 minutes just to be sure on a 200 thousand + verts sculpt and it was very smooth.

After subdividing once more, my 800 thousand + vert sculp in viewport started lagging very slightly and after that on
3 million + verts the lag was visible, which that problem I guess comes from my Ram.

Sorry for posting this as a bug and not somewhere else. It's my first time on the blenders site.
I hope this will help and I am sorry if this bug was already solved and i wasted your time.

Core I5 ATI Graphics card 6370m 1G 6GB RAM Blender version: 2.71 Hash: 9337574 Sculpting performance in viewport MIGHT have been solved by unableing a feature. When I started sculpting for the first time my viewport was lagging and I thought i needed more ram, but after a while (2 days) lag dissapeared. My 90 thousand verts sculpt was going smooth. Modifier used: Moltires I started a new blender project and the lag is back, not only for my new project but for my old one's too. So after reading on forums for hours to find the solution, I found nothing. After switching on and off every thing in Blender, I found out that under the sculpting menu (where brushes and etc. are found) on the options tab on "Threaded sculpt", when I switched it off the smoothness was back. Finally.:) I tested most of the brushes on my sculpt for 5 to 10 minutes just to be sure on a 200 thousand + verts sculpt and it was very smooth. After subdividing once more, my 800 thousand + vert sculp in viewport started lagging very slightly and after that on 3 million + verts the lag was visible, which that problem I guess comes from my Ram. Sorry for posting this as a bug and not somewhere else. It's my first time on the blenders site. I hope this will help and I am sorry if this bug was already solved and i wasted your time.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @Marmak8

Added subscriber: @Marmak8
Antonis Ryakiotakis was assigned by Bastien Montagne 2014-09-08 19:33:52 +02:00

Added subscriber: @mont29

Added subscriber: @mont29

Assigning to Antony for final decision, but see no bug here.

Issues with multi-threading (actually, OpenMP library) are long-known ones under OSX, and since VS2013, under windows as well…

Note you may try a build from our buildbot, we are about to release 2.72 and things changed quite a bit, in particular regarding OMP and Windows, since official 2.71…

Assigning to Antony for final decision, but see no bug here. Issues with multi-threading (actually, OpenMP library) are long-known ones under OSX, and since VS2013, under windows as well… Note you may try a build from [our buildbot](https://builder.blender.org/download), we are about to release 2.72 and things changed quite a bit, in particular regarding OMP and Windows, since official 2.71…

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

After so many reports related to openmp I think it's clear that the problem is OpenMP itself. We should just replace it with our own threading system but I don't think this is considered a bug anymore, rather a TODO.

After so many reports related to openmp I think it's clear that the problem is OpenMP itself. We should just replace it with our own threading system but I don't think this is considered a bug anymore, rather a TODO.
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#41753
No description provided.