Change the default Subsurf Viewport Level from 1 to 2 #114108
No reviewers
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#114108
Loading…
Reference in New Issue
No description provided.
Delete Branch "Raimund58/blender:raimund58-patch-1"
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?
This is a PR to change the default value of the Subdivision Surface Modifier.
We frequently get users who wonder why their scene is unrenderable because everything was fine in the Viewport.
On certain meshes, the RAM difference between level 1 and 2 is HUGE.
Currently, it is not "What you see is what you get". Instead, it is "What you see is crashing for some unknown reason if you try to render."
(Blender doesn't tell you what object (modifier) needed too much RAM, causing an "Out of RAM error")
An alternative to #114163
Tagging Pablo for UI and Campbell and Howard as modeling module.
Coming from other software, I'd say 2 for render is fine...
In fact, most software use 2 for viewport as well...
So, if anything, I'd change the viewport default to 2 to match the render, like most software...
I'm okay with that, too.
I just want to prevent a rude awakening.
Change the default Subsurf Render Level from 2 to 1to Change the default Subsurf Viewport Level from 1 to 2Please don't change the default viewport to 2. Blender can just barely keep up with 1 as the default on more complex models right now, and increasing it with 4 times more tris is going to cause a lot more crashes and slowdowns when adding modifers. I know many other industry-standard software defaults to 2, but they also have subdivision that is way faster then Blenders. I think it's better to change the render to 1 by default, like it was originally.
Raimund Klink referenced this pull request2023-10-31 15:05:19 +01:00
Note, while we don't have strict rules for these things, changing defaults is often not especially helpful:
See: https://wiki.blender.org/wiki/Developer_Intro/Advice#Pick_a_Project
Mainly because changing defaults is more of a design decision than something developers aren't able to do.
While it's always possible we need to re-evaluate design decisions, forcing others to discuss opinionated design decisions using the PR's distracts from other developments, from the response to !114163 it seems like it may be best leaving this as-is.
Too bad, I would have liked to have seen the levels equated.
But I understand if this is not the right place.
Pull request closed