Regression : Geometry nodes: Time-dependent delete points is not taken into account by velocity pass on render #101462

New Issue

CHET · 2022-09-29T15:04:44+02:00

CHET commented

2022-09-29 15:04:44 +02:00

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 950M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15

Blender Version
Broken: version: 3.3.0, 7a4a6ccad7
Worked version: 3.3.0, d0a552b5c6
Worked: 3.4

Short description
Crash when rendering the particular GN tree if vector pass is enabled

Error:

Vendor: NVIDIA Corporation
Renderer: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2
Version: 4.5.0 NVIDIA 496.49
Context Version: 4.5
Array iterator out of range: (index 1128)

Play steps

Create an object with geometry nodes.
Create some way points geometry.
Create Delete Geometry Node.
Create the Scene Time and Index input nodes.
Compare time (frame) and index and entry this as selection for delete geometry node.
Put points to delete geometry node
Turn on the Vector render pass output.
Start rendering a random frame until a crash occurs.
frame points delet crash.blend

**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 950M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15 **Blender Version** Broken: version: 3.3.0, `7a4a6ccad7` Worked version: 3.3.0, `d0a552b5c6` Worked: 3.4 **Short description** Crash when rendering the particular GN tree if vector pass is enabled Error: ``` Vendor: NVIDIA Corporation Renderer: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 Version: 4.5.0 NVIDIA 496.49 Context Version: 4.5 Array iterator out of range: (index 1128) ``` **Play steps** 1. Create an object with geometry nodes. 2. Create some way points geometry. 3. Create Delete Geometry Node. 4. Create the Scene Time and Index input nodes. 5. Compare time (frame) and index and entry this as selection for delete geometry node. 6. Put points to delete geometry node 7. Turn on the Vector render pass output. 8. Start rendering a random frame until a crash occurs. [frame points delet crash.blend](https://archive.blender.org/developer/F13623676/frame_points_delet_crash.blend)

CHET commented

2022-09-29 15:04:44 +02:00

Added subscriber: @cheteron

CHET commented

2022-09-29 15:19:29 +02:00

Crash when used Vector pass

Crash when used Vector pass ![image.png](https://archive.blender.org/developer/F13592176/image.png)

Iliya Katushenock commented

2022-09-29 17:34:10 +02:00

Added subscriber: @mod_moder

Iliya Katushenock commented

2022-09-29 17:34:10 +02:00

Checking...

Iliya Katushenock changed title from ~~Blender crash~~ to Geometry nodes: Time-dependent offset is not taken into account by velocity pass

2022-09-29 17:53:16 +02:00

Iliya Katushenock commented

2022-09-29 17:53:16 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Iliya Katushenock changed title from ~~Geometry nodes: Time-dependent offset is not taken into account by velocity pass~~ to Geometry nodes: Time-dependent delete is not taken into account by velocity pass

2022-09-29 17:53:43 +02:00

Iliya Katushenock changed title from ~~Geometry nodes: Time-dependent delete is not taken into account by velocity pass~~ to Regression: Geometry nodes: Time-dependent delete is not taken into account by velocity pass

2022-09-29 18:01:45 +02:00

Hans Goudey commented

2022-10-05 18:45:59 +02:00

Added subscriber: @HooglyBoogly

Hans Goudey commented

2022-10-05 18:45:59 +02:00

Changed status from 'Confirmed' to: 'Needs User Info'

Hans Goudey commented

2022-10-05 18:45:59 +02:00

This report is missing steps to reproduce the problem.

CHET commented

2022-10-05 18:55:12 +02:00

In #101462#1428083, @HooglyBoogly wrote:
This report is missing steps to reproduce the problem.

Did you read the whole topic, or do you always close the task, even if the blender crashes? Is this a new developer policy?
I'm an artist, not a beta-tester, and I can't figure out what exactly is wrong.

> In #101462#1428083, @HooglyBoogly wrote: > This report is missing steps to reproduce the problem. Did you read the whole topic, or do you always close the task, even if the blender crashes? Is this a new developer policy? I'm an artist, not a beta-tester, and I can't figure out what exactly is wrong.

Iliya Katushenock commented

2022-10-06 08:41:40 +02:00

Sorry, totally forgot about this.
I thought that a description of the problem and a simple file would be enough (later I found out that it wasn’t, but I forgot about this report), but here is the description

Sorry, totally forgot about this. I thought that a description of the problem and a simple file would be enough (later I found out that it wasn’t, but I forgot about this report), but here is the description

Christophe Leyder commented

2022-10-06 13:35:44 +02:00

Added subscriber: @shotalot

Christophe Leyder commented

2022-10-06 13:35:44 +02:00

This is a known limitation for deformation blur in any renderer, Cycles doesn't know how to calculate the velocity because you are changing the point count frame-by-frame. Unless theres a way to calculate the velocity directly in geometry nodes using some sort of Point ID attribute, but I dont think there is a way to do this currently.

Iliya Katushenock commented

2022-10-06 14:02:32 +02:00

@cheteron Can you still reproduce this in the latest blender build?

This is a known limitation for deformation blur in any renderer, Cycles doesn't know how to calculate the velocity because you are changing the point count frame-by-frame. Unless theres a way to calculate the velocity directly in geometry nodes using some sort of Point ID attribute, but I dont think there is a way to do this currently.

It's ok if it's limited, but it shouldn't crash

@cheteron Can you still reproduce this in the latest blender build? > This is a known limitation for deformation blur in any renderer, Cycles doesn't know how to calculate the velocity because you are changing the point count frame-by-frame. Unless theres a way to calculate the velocity directly in geometry nodes using some sort of Point ID attribute, but I dont think there is a way to do this currently. It's ok if it's limited, but it shouldn't crash

CHET commented

2022-10-06 16:06:43 +02:00

In #101462#1428522, @mod_moder wrote:
@cheteron Can you still reproduce this in the latest blender build?

Crash

> In #101462#1428522, @mod_moder wrote: > @cheteron Can you still reproduce this in the latest blender build? Crash ![image.png](https://archive.blender.org/developer/F13623348/image.png)

Iliya Katushenock changed title from ~~Regression: Geometry nodes: Time-dependent delete is not taken into account by velocity pass~~ to Regression : Geometry nodes: Time-dependent delete points is not taken into account by velocity pass on render

2022-10-06 17:35:33 +02:00

Iliya Katushenock commented

2022-10-06 17:36:02 +02:00

Oh, sorry, I completely forgot about the difference between 3.3 and 3.4. Looks like it's only a 3.3 issue

Pratik Borhade commented

2022-10-07 06:54:35 +02:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2022-10-07 06:54:35 +02:00

Changed status from 'Needs User Info' to: 'Confirmed'

Pratik Borhade commented

2022-10-07 06:54:35 +02:00

Seems crash is replicable in 3.3 only. I think we would need to find the resolving commit from master branch.

Hans Goudey commented

2022-10-07 19:35:22 +02:00

Changed status from 'Confirmed' to: 'Resolved'

Hans Goudey closed this issue

2022-10-07 19:35:22 +02:00

Hans Goudey self-assigned this 2022-10-07 19:35:22 +02:00

Hans Goudey commented

2022-10-07 19:35:22 +02:00

I added 21ed3b3258 to the 3.3 maintenance task, so this should be fixed in 3.3.2. I'll close this as resolved since there isn't more to do for now though. Thanks for the report.

I added 21ed3b3258 to the 3.3 maintenance task, so this should be fixed in 3.3.2. I'll close this as resolved since there isn't more to do for now though. Thanks for the report.

Thomas Dinges added this to the 3.3 LTS milestone 2023-02-08 15:37:44 +01:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Regression : Geometry nodes: Time-dependent delete points is not taken into account by velocity pass on render #101462