Subsurf slow performance #29348

Closed
opened 2011-11-21 07:03:36 +01:00 by Grigore Florin · 5 comments

%%% Blender 2.6x revision 41987 win7 64 bit Ati Radeon Mobility 5650 1gb Core i7 1.7 (2.6ghz turbo boost)

Runing Blender over the demo files (demo loop 26 archive) i found that bmw249 , sintel_lite , cataphract , blenderella_topology performs
very slow ranging like :

  • bmw249 3 fps
  • sintel_lite 5 fps
  • cataphract 20 fps
  • blenderella_topology 20 fps

If loading blenderella_topology.blend and apply the subsurf modifier i get 60 (modified only the framerate of the blend to get more fps counted from maximum 24 ) fps instantly from 20-23 max (that with turbo boost on).

If i put on it armature modifier , add a bone , add a vertex group to it and press ALT-A to animated , guess what ? I get from 60 fps down 29 fps instantly and that with only one bone.

What happens with Modifiers that are so cracking down the performance ?! It happens with subsurf LVL 1 and optimal display does nothing.

Guess what if i add subsurf modifier (20 fps) then add smoth modifier then go to subsurf and set lvl 6 view i get 60 fps on two views on screen. Same happens if i add mirror modifier , edge split instead of smoth modifer. Edit mode performance is steady at 30 and looks not afffected so much.

It clearly something happening with subsurf modifer.

I hope this will be solved.

  • I did not want to report it but found that i can import a mesh of 1.7 m verts and can`t animate a mesh of 100k going down after 1 subsurf lvl 1.%%%
%%% Blender 2.6x revision 41987 win7 64 bit Ati Radeon Mobility 5650 1gb Core i7 1.7 (2.6ghz turbo boost) Runing Blender over the demo files (demo loop 26 archive) i found that bmw249 , sintel_lite , cataphract , blenderella_topology performs very slow ranging like : - bmw249 3 fps - sintel_lite 5 fps - cataphract 20 fps - blenderella_topology 20 fps If loading blenderella_topology.blend and apply the subsurf modifier i get 60 (modified only the framerate of the blend to get more fps counted from maximum 24 ) fps instantly from 20-23 max (that with turbo boost on). If i put on it armature modifier , add a bone , add a vertex group to it and press ALT-A to animated , guess what ? I get from 60 fps down 29 fps instantly and that with only one bone. What happens with Modifiers that are so cracking down the performance ?! It happens with subsurf LVL 1 and optimal display does nothing. Guess what if i add subsurf modifier (20 fps) then add smoth modifier then go to subsurf and set lvl 6 view i get 60 fps on two views on screen. Same happens if i add mirror modifier , edge split instead of smoth modifer. Edit mode performance is steady at 30 and looks not afffected so much. It clearly something happening with subsurf modifer. I hope this will be solved. * I did not want to report it but found that i can import a mesh of 1.7 m verts and can`t animate a mesh of 100k going down after 1 subsurf lvl 1.%%%
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

%%%This bug plague armature modifier , subsurf ....%%%

%%%This bug plague armature modifier , subsurf ....%%%
Author

%%%Tested more and looks it plagues even Edit mode and can go to 10 fps from 60 fps (after applying sub surf) %%%

%%%Tested more and looks it plagues even Edit mode and can go to 10 fps from 60 fps (after applying sub surf) %%%

%%%Fixed what I think is the main cause of slowdown now in the blenderella file. For the other files, if something draws slow, that's not a bug necessarily, and small performance differences are expected with/without subsurf modifier. Adding an armature modifier for example might mean the mesh is now animated, so needs to be recomputed every frame.%%%

%%%Fixed what I think is the main cause of slowdown now in the blenderella file. For the other files, if something draws slow, that's not a bug necessarily, and small performance differences are expected with/without subsurf modifier. Adding an armature modifier for example might mean the mesh is now animated, so needs to be recomputed every frame.%%%

Changed status from 'Open' to: 'Resolved'

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