EEVEE-Next: Fix Hair and Curves motion vectors #112425
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#112425
Loading…
Reference in New Issue
No description provided.
Delete Branch "pragma37/blender:pull-fix-curves-motion-blur"
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?
Hair and Curves need to call
DRW_curves_update
beforegeometry_steps_fill
, otherwise the copied geometry is just uninitialized data. However, doing so triggers an assertion:This PR ports the
DRW_hair/curves_pos_buffer_get
functions to the newdraw::Manager
API, so it can be called at any arbitrary point.It also changes
VelocityModule::geometry_map
to useuint64
keys instead ofID
pointers, since the same particle system can be used on different objects and have multiple geometries.Notes:
VelocityModule::step_object_sync
on image renders. Using them elsewhere would require modifying the old draw manager to do the init/update/free setup.(I'm not sure if transform feedback is actually supported in the new manager)
05c06a921c
to29804c0552
While this is fine for the time being, this pauses the question to what structure is responsible for all these GPU extraction. Before it was the draw manager. Now the manager is just here for submission and object info tracking. Do we want to put the extraction jobs in the manager itself?
WIP: EEVEE-Next: Fix Hair and Curves motion vectorsto EEVEE-Next: Fix Hair and Curves motion vectorsI think regardless of what structure manages the process, it should be done as part of the equivalent of
DRW_render_object_iter
.It could be part of the Draw Manager, or wrap the manager itself and this kind of functionality into some sort of Engine Manager.
As long as we don't lose the ability of being able to create a disposable Draw Manager at any arbitrary point, I think either way would be fine.