Geometry Nodes not using MeshSequenceCache data while rendering #112075

Open
opened 2023-09-07 11:14:57 +02:00 by Amélie Fondevilla · 9 comments

System Information
Operating system: Linux-5.4.0-153-generic-x86_64-with-glibc2.31 64 Bits, X11 UI
Graphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.47.03

Blender Version
Broken: version: 3.6.2, branch: blender-v3.6-release, commit date: 2023-08-16 16:43, hash: e53e55951e7a
Worked: (newest version of Blender that worked as expected)

Short description of error
During the rendering, the geometry contained in the Object Info node in geometry nodes does not take into account MeshSequenceCache modifiers of the corresponding object.

Exact steps for others to reproduce the error
Here is a simple blender file containing a 3D animated sketch made in VR with Quill, and imported through an Alembic file : bug_mesh_cache_geo_node.blend.
The sketch has 2 keyframes, with each exactly one stroke.

A geometry node is applied to the mesh to add a sphere at the position of the first vertex of the curves.

geonode.png

A rendering of the second keyframe (frame 10 for example) shows that the geometry node is using the data of the first keyframe of the curve, since the sphere is located at the beginning of the curve in the first keyframe.

diff_viewport_rendering.png

**System Information** Operating system: Linux-5.4.0-153-generic-x86_64-with-glibc2.31 64 Bits, X11 UI Graphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.47.03 **Blender Version** Broken: version: 3.6.2, branch: blender-v3.6-release, commit date: 2023-08-16 16:43, hash: `e53e55951e7a` Worked: (newest version of Blender that worked as expected) **Short description of error** During the rendering, the geometry contained in the `Object Info` node in geometry nodes does not take into account `MeshSequenceCache` modifiers of the corresponding object. **Exact steps for others to reproduce the error** Here is a simple blender file containing a 3D animated sketch made in VR with Quill, and imported through an Alembic file : [bug_mesh_cache_geo_node.blend](/attachments/17ebf72a-d8a2-41e3-aa74-815e0fc7fe7c). The sketch has 2 keyframes, with each exactly one stroke. A geometry node is applied to the mesh to add a sphere at the position of the first vertex of the curves. ![geonode.png](/attachments/4edff0ba-d945-43cb-8a93-6b628bb49c72) A rendering of the second keyframe (frame 10 for example) shows that the geometry node is using the data of the first keyframe of the curve, since the sphere is located at the beginning of the curve in the first keyframe. ![diff_viewport_rendering.png](/attachments/6de0c26f-5123-483e-8dd1-4e9d784cdfb9)
Amélie Fondevilla added the
Type
Report
Priority
Normal
Status
Needs Triage
labels 2023-09-07 11:14:57 +02:00
Member

Thanks for the report. I can confirm.

Thanks for the report. I can confirm.
Member

Probably related to #58704

Probably related to #58704
Author
Member

Yes, probably.. I suspected it was such kind of issue. I guess there's no hope to solve this then ?
I guess it would be nice to at least have a workaround on this. For example be able to bake the MeshSequenceCache, even if it means creating multiple objects, idk.

Yes, probably.. I suspected it was such kind of issue. I guess there's no hope to solve this then ? I guess it would be nice to at least have a workaround on this. For example be able to bake the MeshSequenceCache, even if it means creating multiple objects, idk.
Member

Maybe @dr.sybren has an idea about the possible workaround if problem is related to Alembic

Maybe @dr.sybren has an idea about the possible workaround if problem is [related to Alembic](https://projects.blender.org/blender/blender/wiki/Module:%20Pipeline,%20Assets%20&%20I/O#:~:text=%23alembic,%40dr.sybren)

@amelief Can you check, if you add Scene Time node to node tree, have this fix bug?

@amelief Can you check, if you add `Scene Time` node to node tree, have this fix bug?
Author
Member

hi @mod_moder
You mean adding the Scene Time somewhere in the geometry nodes so that it gets evaluated ?

This :

geonode_scene_time.png

does not solve the issue, but I am not sure that is what you suggested.

hi @mod_moder You mean adding the `Scene Time` somewhere in the geometry nodes so that it gets evaluated ? This : ![geonode_scene_time.png](/attachments/73033ecc-3e7c-4baf-a6f8-b557d0e7783c) does not solve the issue, but I am not sure that is what you suggested.

@amelief No need to connect to something, just existing is enough

@amelief No need to connect to something, just existing is enough

Is it known whether this is any of these issues?

  • GN doesn't evaluate on the next frame
  • GN does evaluate, but caches the output of the Mesh Cache Sequence modifier (MCSM)
  • GN does evaluate, but asks MCSM for geometry on the wrong frame/timecode
  • GN does evaluate, and asks MCSM for geometry, but the modifier doesn't realise things are animated, and thus always returns the same thing
Is it known whether this is any of these issues? - GN doesn't evaluate on the next frame - GN does evaluate, but caches the output of the Mesh Cache Sequence modifier (MCSM) - GN does evaluate, but asks MCSM for geometry on the wrong frame/timecode - GN does evaluate, and asks MCSM for geometry, but the modifier doesn't realise things are animated, and thus always returns the same thing

@amelief hey,I also meet this problem but maybe you can try this.(blender 3.6) click this and final render is correct!

@amelief hey,I also meet this problem but maybe you can try this.(blender 3.6) click this and final render is correct!
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
5 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#112075
No description provided.