2025.31760: POPs not updating when changed upstream

Bugs
1

Hi Guys,

It seems there’s a bug when updating the number of POPs upstream (for example adding in a merge) some POP’s downstream are sometimes not updating correctly until you re-create the POP.

It’s pretty impossible to re-create as re-opening the project will fix the issue. I’m running an RTX5090 with driver version 581.80. I’ve tried re-creating a simple example with a point generator POP but that doesn’t seem to work either unfortunately.

Here’s a screenshot of it happening with the switch POP and I’ve also seen it happen on the delete POP too. The top switch POP was created first then plugged into whilst the second switch POP was created after then plugged into. Both switch POPs input parameters are set to 1. The viewer you see in switch1 is what the input POP looked like before I merged it with itself later. It just didn’t update when the input geometry was updated.

Screenshot 2025-12-01 121100
Screenshot 2025-12-01 1211001920×1250 113 KB

3

Thank you for reporting the problem. I wasn’t able to replicate the issue using your example. Could you clarify what warning appeared on switch1 when this occurred?

The viewer you see in switch1 is what the input POP looked like before I merged it with itself later.

Can you elaborate on this and provide all the steps to reproduce the behavior?
Also, are the switch operators configured with Blend Between Inputs enabled?

4

Hi Guillaume,

I think what’s actually happened is there’s been a difference in point numbers so the switch example was actually a red-herring but I have seen the issue on the delete POP too. I will try and replicate the behavior with the delete POP instead and see if I can get an example I can re-create.