Geometry Nodes result looks a lot different in viewport vs. render #88557

New Issue

Manu Järvinen · 2021-05-25T14:29:48+02:00

Manu Järvinen commented

2021-05-25 14:29:48 +02:00

System Information
Operating system: Linux-5.4.0-58-generic-x86_64-with-glibc2.31 64 Bits or Linux Mint 20.1
Graphics card: GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.73.01

Blender Version
Broken: version: 2.93.0 Beta, branch: master, commit date: 2021-05-24 15:29, hash: 1a69d491e5

Short description of error
This is what I would like to have and what I get in viewport:

But this is the render:

Exact steps for others to reproduce the error

Open the .blend, press F12
I used vertex weight proximity modifiers to make the vertex groups for the path and the road
In the timeline by scrubbing you can see how the vertex groups form up

.Blend:
geometry_nodes_bugreport2.blend

**System Information** Operating system: Linux-5.4.0-58-generic-x86_64-with-glibc2.31 64 Bits or Linux Mint 20.1 Graphics card: GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.73.01 **Blender Version** Broken: version: 2.93.0 Beta, branch: master, commit date: 2021-05-24 15:29, hash: `1a69d491e5` **Short description of error** This is what I would like to have and what I get in viewport: ![image.png](https://archive.blender.org/developer/F10141170/image.png) But this is the render: ![image.png](https://archive.blender.org/developer/F10141173/image.png) **Exact steps for others to reproduce the error** - Open the .blend, press F12 - I used vertex weight proximity modifiers to make the vertex groups for the path and the road - In the timeline by scrubbing you can see how the vertex groups form up **.Blend:** [geometry_nodes_bugreport2.blend](https://archive.blender.org/developer/F10141177/geometry_nodes_bugreport2.blend)

Manu Järvinen commented

2021-05-25 14:29:49 +02:00

Added subscriber: @ManuJarvinen

Himanshi Kalra commented

2021-05-25 17:00:08 +02:00

Added subscriber: @Calra

Himanshi Kalra commented

2021-05-25 17:00:08 +02:00

On 3.0.0 the viewport and rendered image looks consistent with respect where the grass(?) is on the ball. I am on Windows 10. It is not exactly supported by 2.83 and 2.92, I don't have 2.93 at the moment.

On 3.0.0 the viewport and rendered image looks consistent with respect where the grass(?) is on the ball. I am on Windows 10. It is not exactly supported by 2.83 and 2.92, I don't have 2.93 at the moment. ![image.png](https://archive.blender.org/developer/F10141383/image.png) ![image.png](https://archive.blender.org/developer/F10141385/image.png)

Manu Järvinen commented

2021-05-25 17:12:22 +02:00

Ah yes, true. When you first open the file, the situation is like so - but as soon as you scrub the timeline, the viewport result looks as it should.

Pratik Borhade commented

2021-05-25 20:35:02 +02:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2021-05-25 20:35:02 +02:00

I can not reproduce the issue for version version 2.93.0, Hash: 1a69d491e5, commit date: 2021-05-24

but as soon as you scrub the timeline, the viewport result looks as it should.

So can I assume the problem is fixed for you already?

I can not reproduce the issue for version version 2.93.0, Hash: `1a69d491e5`, commit date: `2021-05-24` > but as soon as you scrub the timeline, the viewport result looks as it should. So can I assume the problem is fixed for you already?

Manu Järvinen commented

2021-05-25 22:18:30 +02:00

So can I assume the problem is fixed for you already?

No, because I want the render to look the same as in viewport. Weird, we tried the exact same Blender version even. I wonder if this is a Linux-only issue hmm.

> So can I assume the problem is fixed for you already? No, because I want the render to look the same as in viewport. Weird, we tried the exact same Blender version even. I wonder if this is a Linux-only issue hmm.

Leon Schittek commented

2021-05-25 23:13:46 +02:00

Added subscriber: @lone_noel

Leon Schittek commented

2021-05-25 23:13:46 +02:00

I can reproduce the behaviour described by @ManuJarvinen on mac os.
In the viewport it looks fine and the animation plays as expected, but when rendering I only get the circular patch without grass.

I can get the viewport to display the same as the render by disabling and enabling collections or modifiers on the "pathway_GEO" object, but as soon as you force some update in the scene (e.g. by scrubbing the timeline, moving objects) it gives the expected result again:

point-distribute-bug.mp4

My System Information
Operating system: macOS-10.14.6-x86_64-i386-64bit 64 Bits
Graphics card: Intel Iris OpenGL Engine Intel Inc. 4.1 INTEL-12.10.16

My Blender Version
Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-05-24 18:46, hash: 0606a37e1a

I can reproduce the behaviour described by @ManuJarvinen on mac os. In the viewport it looks fine and the animation plays as expected, but when rendering I only get the circular patch without grass. ![point-distribution-bug.png](https://archive.blender.org/developer/F10141874/point-distribution-bug.png) I can get the viewport to display the same as the render by disabling and enabling collections or modifiers on the "pathway_GEO" object, but as soon as you force some update in the scene (e.g. by scrubbing the timeline, moving objects) it gives the expected result again: [point-distribute-bug.mp4](https://archive.blender.org/developer/F10141884/point-distribute-bug.mp4) **My System Information** Operating system: macOS-10.14.6-x86_64-i386-64bit 64 Bits Graphics card: Intel Iris OpenGL Engine Intel Inc. 4.1 INTEL-12.10.16 **My Blender Version** Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-05-24 18:46, hash: `0606a37e1a`

Philipp Oeser commented

2021-05-26 15:14:58 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2021-05-26 15:14:58 +02:00

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

Philipp Oeser commented

2021-05-26 15:14:59 +02:00

There is a dependency cycle here:

Dependency cycle detected:
  OBEarth_GEO/Geometry Component/GEOMETRY_EVAL() depends on
  OBpathway_GEO/Geometry Component/GEOMETRY_EVAL() via 'WeightVGProximity Modifier'
  OBEarth_GEO/Geometry Component/GEOMETRY_EVAL() via 'Shrinkwrap Modifier'
Detected 1 dependency cycles

Of course the dependency graph could be more specific/granular to not be alarmed here, but in theory it could really be an issue (if the Earth got deformed by the vertexgroup for example)

The easiest way out of this is probably to shrinkwrap on to a copy of the Earth that is not participating in the setup in another way, like so:
geometry_nodes_bugreport2_no_depscycle.blend

Does this work for you?

There is a dependency cycle here: ``` Dependency cycle detected: OBEarth_GEO/Geometry Component/GEOMETRY_EVAL() depends on OBpathway_GEO/Geometry Component/GEOMETRY_EVAL() via 'WeightVGProximity Modifier' OBEarth_GEO/Geometry Component/GEOMETRY_EVAL() via 'Shrinkwrap Modifier' Detected 1 dependency cycles ``` Of course the dependency graph could be more specific/granular to not be alarmed here, but in theory it could really be an issue (if the Earth got deformed by the vertexgroup for example) The easiest way out of this is probably to shrinkwrap on to a **copy** of the Earth that is not participating in the setup in another way, like so: [geometry_nodes_bugreport2_no_depscycle.blend](https://archive.blender.org/developer/F10143101/geometry_nodes_bugreport2_no_depscycle.blend) Does this work for you?

Manu Järvinen commented

2021-05-27 04:48:59 +02:00

Does this work for you?

Works perfectly, who knew! :) Okay, so have to check next time about those dependency cycles, alright. Too bad it didn't pop up an error about that.

Thanks for the workaround!

> Does this work for you? Works perfectly, who knew! :) Okay, so have to check next time about those dependency cycles, alright. Too bad it didn't pop up an error about that. Thanks for the workaround!

Philipp Oeser commented

2021-05-27 07:04:53 +02:00

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

Philipp Oeser closed this issue

2021-05-27 07:04:53 +02:00

Philipp Oeser commented

2021-05-27 07:04:53 +02:00

The error is written to the console, I remember there has been a discussion about letting this end up in the UI instead, but it was decided against (I would have liked to see this in the UI as well, it is source for countless bug reports...).

Anyways, thx getting back, will close.

The error is written to the console, I remember there has been a discussion about letting this end up in the UI instead, but it was decided against (I would have liked to see this in the UI as well, it is source for countless bug reports...). Anyways, thx getting back, will close.

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

Geometry Nodes result looks a lot different in viewport vs. render #88557