EEVEE Next: Volume render does not count procedurally modified meshes properly #113963
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#113963
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.40
Blender Version
Broken: version: 4.1.0 Alpha, branch: main, commit date: 2023-10-19 22:55, hash:
a53dd6e93cfeWorked: n/a
Volume rendering in EEVEE Next was introduced with
f79b86553aShort description of error
Volume rendering in EEVEE Next does not count procedurally modified meshes properly. Volume only renders inside the original mesh's bounding box.
Test file: eevee_next_volume_test.blend
Same result when using modifiers like Displace.
Can confirm
@HooglyBoogly Basically the bounding box is wrong. Do you have any idea how to fix that?
Hm, it seems result bounding box of mesh is correct. I thought, this is due to incorrectly accessed from render, might be read from original mesh instead of eval/runtime.
Indeed, the bounding box is correct:
I can't reproduce the situation in the report either.
I guess this is an issue with texture space, and that procedurally changes not updating it.
The below is a demonstration with texture space display. If texture space is adjusted automatically (by editing original mesh) and manually (via mesh data panel), volume renders properly inside the bound.
This also causes an issue when rendering (hair) curves with volume shader, since curves, unlike other object types, always retain 1x1x1 (default?) texture space and do not adjust its texture space automatically with manual edits.
hair_curves_volume.blend
Oddly, volume renders correctly when it's rendered in orthographic view.
Fixed by the refactor that used the fragment shader to fill the volume properties.