Disabled GeoNodes modifier seems to be evaluated when it is disabled #127786

New Issue

kursad k · 2024-09-18T07:26:33+02:00

kursad k commented

2024-09-18 07:26:33 +02:00

System Information
Operating system: Win 11
Graphics card: RTX 2070

Blender Version
Broken: 51e9a36c2f

Short description of error
As you can see in the video, the viewport lag is unbearable even when the modifier is disabled. I am not sure why the geonodes modifier in the setup is evaluating the graph when it is disabled. The subd modifier and the decimate modifier are there to amplify the issue. I have a very complex object that has no decimate or subd modifier with a similar issue. It seems like something about collection instancing in the setup causing this.

Exact steps for others to reproduce the error
Load the attached scene
Repeat the similar actions as in the video

**System Information** Operating system: Win 11 Graphics card: RTX 2070 **Blender Version** Broken: 51e9a36c2f48 **Short description of error** As you can see in the video, the viewport lag is unbearable even when the modifier is disabled. I am not sure why the geonodes modifier in the setup is evaluating the graph when it is disabled. The subd modifier and the decimate modifier are there to amplify the issue. I have a very complex object that has no decimate or subd modifier with a similar issue. It seems like something about collection instancing in the setup causing this. <video src="/attachments/156ff75b-2504-47ba-b1cd-24463c8b16e5" title="blender_JuIe4VQpz6.mp4" controls></video> **Exact steps for others to reproduce the error** Load the attached scene Repeat the similar actions as in the video

blender_JuIe4VQpz6.mp4

1.8 MiB

bug_18092024_0020_55.zip

908 KiB

kursad k added the

labels 2024-09-18 07:26:34 +02:00

YimingWu commented

2024-09-18 08:24:58 +02:00

Hi @kursadk , apparently the performance hit is due to that Decimate modifier not the geometry nodes modifier. If you disable Decimate then it will work smoothly.

Consider this not to be a bug, will close for now.

Hi @kursadk , apparently the performance hit is due to that Decimate modifier not the geometry nodes modifier. If you disable Decimate then it will work smoothly. Consider this not to be a bug, will close for now.

😕 1

YimingWu closed this issue

2024-09-18 08:25:01 +02:00

Blender Bot added

and removed

labels 2024-09-18 08:25:06 +02:00

kursad k commented

2024-09-18 08:28:57 +02:00

Actually that is not necessarily true, like I said I have an object with similar setup without a decimate modifier and still suffers from horrible performance when the geonodes collection instance modifier is disabled. It was there to make the slow down extra visible. The performance of the object in this setup is worse than what I demonstrated with the example above. the "gn.join" is prett much the same type of gn setup as above.

The thing is the collection instancing setup is at the end of the modifier stack in this screenshot and as you see no decimate modifier there. My point is that there seems to be a horrible dependency graph related performance issue lurking in the shadow that is causing this type of horrible performance, and it doesn't look like a feature request to me.

You can gain performance in the scene I provided above by deleting the geonodes modifier. Move objects or the plane object once the geonodes gone without any performance issues. To me they seem to be related and connected in this performance issue.

Actually that is not necessarily true, like I said I have an object with similar setup without a decimate modifier and still suffers from horrible performance when the geonodes collection instance modifier is disabled. It was there to make the slow down extra visible. The performance of the object in this setup is worse than what I demonstrated with the example above. the "gn.join" is prett much the same type of gn setup as above. The thing is the collection instancing setup is at the end of the modifier stack in this screenshot and as you see no decimate modifier there. My point is that there seems to be a horrible dependency graph related performance issue lurking in the shadow that is causing this type of horrible performance, and it doesn't look like a feature request to me. You can gain performance in the scene I provided above by deleting the geonodes modifier. Move objects or the plane object once the geonodes gone without any performance issues. To me they seem to be related and connected in this performance issue. ![image](/attachments/20d6406e-ab03-46d8-aad5-09347392aa40)

image.png

54 KiB

YimingWu commented

2024-09-18 08:36:34 +02:00

I'll reopen this and see if anyone can reproduce.

❤️ 1

YimingWu reopened this issue

2024-09-18 08:36:38 +02:00

Blender Bot added

and removed

labels 2024-09-18 08:36:49 +02:00

kursad k commented

2024-09-18 08:41:21 +02:00

I'll reopen this and see if anyone can reproduce.

Also the performance is not super smooth once the decimate modifier is deleted. It improves the interaction speed but not like one would expect from a similar performance from the regular collection instancing.

> I'll reopen this and see if anyone can reproduce. Also the performance is not super smooth once the decimate modifier is deleted. It improves the interaction speed but not like one would expect from a similar performance from the regular collection instancing.

Pratik Borhade commented

2024-09-18 12:45:14 +02:00

Hi, unable to confirm either when Decimate modifier is disabled.

like I said I have an object with similar setup without a decimate modifier and still suffers from horrible performance

I feel this is related to #73199 . Can you send the other file?

Hi, unable to confirm either when Decimate modifier is disabled. > like I said I have an object with similar setup without a decimate modifier and still suffers from horrible performance I feel this is related to #73199 . Can you send the other file?

👍 1

Pratik Borhade added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2024-09-18 12:45:23 +02:00

kursad k commented

2024-09-18 18:47:10 +02:00

Here is without the decimate modifier. As you can see it is quite laggy (better performance than the decimate one). The issue is not really the decimate modifier or the subd modifier, I added them to demo and magnify the issue. You won't be able to see this type of speed hit without complex setups. Modifier stack is definitely triggered unnecessarily.

We have three issues (based on the first file and the second file I shared)

The performance is bad because the whole stack is recalculated at each update even though the geometry never changes upstream
The performance is still bad when the last geonodes modifier is disabled
- This is the worst offender to me (ie the first .blend setup), removing the decimate mod helps, but why does disabled geonodes modifier is triggering updates? At least this one should be considered as a bug. I get that some of these modifiers are historic and hard to fix the issues in them
The performance is still bad when high calculation modifiers are disabled (ie decimate mod)

Disable the geonodes in this second file, it feels much better naturally but you can see there might be very slightly performance hit, not as visible if you are not paying attention.

I can't give you my project file but here a modified version that is in the second video.

bug_18092024_0020_55_2.zip

Hi, unable to confirm either when Decimate modifier is disabled.

like I said I have an object with similar setup without a decimate modifier and still suffers from horrible performance

I feel this is related to #73199 . Can you send the other file?

Here is without the decimate modifier. As you can see it is quite laggy (better performance than the decimate one). The issue is not really the decimate modifier or the subd modifier, I added them to demo and magnify the issue. You won't be able to see this type of speed hit without complex setups. Modifier stack is definitely triggered unnecessarily. We have three issues (based on the first file and the second file I shared) - The performance is bad because the whole stack is recalculated at each update even though the geometry never changes upstream - The performance is still bad when the last geonodes modifier is disabled - This is the worst offender to me (ie the first .blend setup), removing the decimate mod helps, but why does disabled geonodes modifier is triggering updates? At least this one should be considered as a bug. I get that some of these modifiers are historic and hard to fix the issues in them - The performance is still bad when high calculation modifiers are disabled (ie decimate mod) Disable the geonodes in this second file, it feels much better naturally but you can see there might be very slightly performance hit, not as visible if you are not paying attention. <video src="/attachments/4799e2a4-2d09-4d0d-a1a9-dfc76efd63dd" title="blender_EOc5B1pbeE.mp4" controls></video> I can't give you my project file but here a modified version that is in the second video. [bug_18092024_0020_55_2.zip](/attachments/902918a5-c218-475a-8374-bb5a1265b6c5) > Hi, unable to confirm either when Decimate modifier is disabled. > > like I said I have an object with similar setup without a decimate modifier and still suffers from horrible performance > > I feel this is related to #73199 . Can you send the other file?

blender_EOc5B1pbeE.mp4

496 KiB

bug_18092024_0020_55_2.zip

907 KiB

Pratik Borhade commented

2024-09-19 05:03:51 +02:00

Thanks, this is indeed related to #73199. AFAICS, If we remove the referenced object/collection from the disabled modifier (i.e. collection info node), performance is back.

Pratik Borhade closed this issue

2024-09-19 05:03:55 +02:00

Blender Bot added

Status

Archived

and removed

Status

Needs Information from User

labels 2024-09-19 05:05:22 +02:00

Sign in to join this conversation.