Fix: Simplify "Volume Resolution" not updating for non volume objects #117848

Merged
Philipp Oeser merged 3 commits from lichtwerk/blender:117747_simplify_volume_resolution_update into main 2024-02-07 10:32:15 +01:00
Member

This came up in #117747.

Unless an object was of OB_VOLUME type, the setting was not updating the
viewport accordingly since the introduction in 365bf103d1. So if for
example a mesh has a "Mesh to Volume" node, the update did not take
place.

If we use context, we can check the evaluated GeometrySet on any object
type with a geometry nodes modifier though and if it has a volume, we
can also tag for update.

This came up in #117747. Unless an object was of OB_VOLUME type, the setting was not updating the viewport accordingly since the introduction in 365bf103d1f6. So if for example a mesh has a "Mesh to Volume" node, the update did not take place. If we use context, we can check the evaluated GeometrySet on any object type with a geometry nodes modifier though and if it has a volume, we can also tag for update.
Philipp Oeser added 1 commit 2024-02-05 14:35:36 +01:00
95ee1a46d7 Fix: Simplify "Volume Resolution" not updating for non volume objects
This came up in #117747.

Unless an object was of OB_VOLUME type, the setting was not updating the
viewport accordingly since the introduction in 365bf103d1. So if for
example a mesh has a "Mesh to Volume" node, the update did not take
place.

If we use context, we can check the evaluated GeometrySet on any object
type with a geometry nodes modifier though and if it has a volume, we
can also tag for update.
Philipp Oeser requested review from Jacques Lucke 2024-02-05 14:35:53 +01:00
Philipp Oeser added this to the Nodes & Physics project 2024-02-05 14:36:00 +01:00
Hans Goudey reviewed 2024-02-05 14:38:54 +01:00
Hans Goudey left a comment
Member

Checking the evaluated geometry set isn't enough either, since a volume might be an intermediate step in node evaluation that isn't included in the result.

Checking the evaluated geometry set isn't enough either, since a volume might be an intermediate step in node evaluation that isn't included in the result.
Author
Member

Checking the evaluated geometry set isn't enough either, since a volume might be an intermediate step in node evaluation that isn't included in the result.

Hm, OK, thx checking. So is there a GeometrySet that represents the final output?

> Checking the evaluated geometry set isn't enough either, since a volume might be an intermediate step in node evaluation that isn't included in the result. Hm, OK, thx checking. So is there a `GeometrySet` that represents the final output?
Member

geometry_set_eval represents the final output, that's right. But my point was that volumes might be used internally (in a way that should respect the simplify setting) but not be included in the final output.

`geometry_set_eval` represents the final output, that's right. But my point was that volumes might be used internally (in a way that should respect the simplify setting) but not be included in the final output.
Author
Member

geometry_set_eval represents the final output, that's right. But my point was that volumes might be used internally (in a way that should respect the simplify setting) but not be included in the final output.

Ah, OK. Not sure if we should really consider the internal usage when it is not the final output (since this is a viewport setting at least I would not expect it to)

> `geometry_set_eval` represents the final output, that's right. But my point was that volumes might be used internally (in a way that should respect the simplify setting) but not be included in the final output. Ah, OK. Not sure if we should really consider the internal usage when it is not the final output (since this is a viewport setting at least I would not expect it to)
Member

@SimonThommes Also mentioned that he didn't like that the simplification level affects nodes like this, so maybe the solution should go in a different direction. E.g. the simplify level could be an input node that can be used explicitly if desired. Needs some more discussion.

@SimonThommes Also mentioned that he didn't like that the simplification level affects nodes like this, so maybe the solution should go in a different direction. E.g. the simplify level could be an input node that can be used explicitly if desired. Needs some more discussion.
Author
Member

I can see how doing simplification might work better when done differently (not sure if an input node overcomplicates this though), however this fix is just about it not updating at all for non-volume objects. So this PR will not do the whole redesign of simplification of volumes (this is not what it intends to do). Do you think it would block the redesign or make it more complicated?

I can see how doing simplification might work better when done differently (not sure if an input node overcomplicates this though), however this fix is just about it not updating at all for non-volume objects. So this PR will not do the whole redesign of simplification of volumes (this is not what it intends to do). Do you think it would block the redesign or make it more complicated?
Jacques Lucke requested changes 2024-02-06 17:48:16 +01:00
@ -2085,1 +2098,3 @@
rna_Scene_simplify_update_impl(bmain, sce, false);
Scene *scene = (Scene *)ptr->owner_id;
Main *bmain = CTX_data_main(C);
Depsgraph *depsgraph = CTX_data_ensure_evaluated_depsgraph(C);
Member

Ensuring an evaluated depsgraph just to set a property seems a bit too much and could potentially result in double depsgraph evaluation on e.g. render farms that set this property directly after loading the .blend file before evaluation starts.

It's probably ok to just use the result of the previous evaluation, and if that doesn't exist yet, ignore it.

Ensuring an evaluated depsgraph just to set a property seems a bit too much and could potentially result in double depsgraph evaluation on e.g. render farms that set this property directly after loading the .blend file before evaluation starts. It's probably ok to just use the result of the previous evaluation, and if that doesn't exist yet, ignore it.
lichtwerk marked this conversation as resolved
Philipp Oeser added 2 commits 2024-02-07 09:51:27 +01:00
Philipp Oeser requested review from Jacques Lucke 2024-02-07 09:51:55 +01:00
Jacques Lucke approved these changes 2024-02-07 10:07:14 +01:00
Philipp Oeser merged commit b56192b3bb into main 2024-02-07 10:32:15 +01:00
Philipp Oeser deleted branch 117747_simplify_volume_resolution_update 2024-02-07 10:32:19 +01:00
Sign in to join this conversation.
No reviewers
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 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#117848
No description provided.