Blender sculpt mode no Update image while under display active preview #48780

Closed
opened 2016-07-02 22:32:00 +02:00 by Carl Foreman · 10 comments

Linux mint 18 64 bit, Nvidia Geforce GTX 770Blender VersionBlender 2.77 and 2.76BShort description of errorWhile in Blender sculpt mode using the cube after it was subdivided several times I would sculpt the object but when I tried to view the object in "Display render preview" there would be no updating on the monitor. If I was in Texture or material view. The sculpting would update nicely and I could all of the strokes of the sculptingExact steps for others to reproduce the error**
While in blender
I tried to fix this using other renders "Cycles or internal, with no affects. I went back to an earlier version hoping that it would make a different but no help. I would like to assign this to the right person but under the listing of name. There is nothing to tell you how handles "what". You are force to just select someone at random. I'm sorry guys!!!

**Linux mint 18 64 bit, Nvidia Geforce GTX 770**Blender Version**Blender 2.77 and 2.76B**Short description of error**While in Blender sculpt mode using the cube after it was subdivided several times I would sculpt the object but when I tried to view the object in "Display render preview" there would be no updating on the monitor. If I was in Texture or material view. The sculpting would update nicely and I could all of the strokes of the sculpting**Exact steps for others to reproduce the error** While in blender I tried to fix this using other renders "Cycles or internal, with no affects. I went back to an earlier version hoping that it would make a different but no help. I would like to assign this to the right person but under the listing of name. There is nothing to tell you how handles "what". You are force to just select someone at random. I'm sorry guys!!!
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @CarlForeman

Added subscriber: @CarlForeman

Added subscriber: @ideasman42

Added subscriber: @ideasman42

Added subscriber: @SpectreFirst

Added subscriber: @SpectreFirst

Added subscriber: @Sergey

Added subscriber: @Sergey

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Sergey Sharybin self-assigned this 2016-07-27 11:21:42 +02:00

Wouldn't really consider this a bug. You don't usually use rendered viewport during sculpt because of perofrmance issues (each stroke would require render database update which is not cheap at all). Additionally, there's no quick way to know whether there's any rendered viewports or not.

I would think we should increase BPR factor of GLSL shading and use it for sculpting. And not try supporting rendered shading, since that would affect on regular sculpting as well due to extra checks.

So thanks for the report, but not really a bug.

Wouldn't really consider this a bug. You don't usually use rendered viewport during sculpt because of perofrmance issues (each stroke would require render database update which is not cheap at all). Additionally, there's no quick way to know whether there's any rendered viewports or not. I would think we should increase BPR factor of GLSL shading and use it for sculpting. And not try supporting rendered shading, since that would affect on regular sculpting as well due to extra checks. So thanks for the report, but not really a bug.

Added subscriber: @thomas-40

Added subscriber: @thomas-40

As a user of blender who sculpts I also consider this a bug. It is reasonable to expect an up to date mesh when you hit shift-z while sculpting (to e.g. check how the model looks in chosen lighting setup) , there is no indication, explanation or, honestly, logic to its current behaviour and it's inconsistent with how Blender works in other modes.

Please reopen for future fix.

As a user of blender who sculpts I also consider this a bug. It is reasonable to expect an up to date mesh when you hit shift-z while sculpting (to e.g. check how the model looks in chosen lighting setup) , there is no indication, explanation or, honestly, logic to its current behaviour and it's inconsistent with how Blender works in other modes. Please reopen for future fix.

Added subscriber: @Dogway

Added subscriber: @Dogway
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
6 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#48780
No description provided.