Why things got different when connect to a Null SOP?

[乐琢 Urdro]

Why things got different when connect to a Null SOP?

Hello everyone,

I have used Houdini for 4 years and it's the first time I met this strange thing, and I have no idea why this happen.

Any help will be grateful, thanks.

The popnet works fine, it can create fireworks. (img 1)

 

But when I connect a Null SOP(others like merge SOP, cache SOP also have the same problem) under it, the result has changed.(img 2)

My houdini version is 12.5.316.22
 

And the here is the .hip file :

firework_ud_v001.hip

 

[edward]

The Null SOP by default will try to "instance" the geometry from its input node as to avoid duplicating it. For POPs, it needs to reuse the same geometry every frame. I'm guessing there's some bad interaction between these two behaviours. Try turning off this instancing behaviour by turning on the Null SOP's "Cache Input" parameter.

[Liaoliao]

The Null SOP by default will try to "instance" the geometry from its input node as to avoid duplicating it. For POPs, it needs to reuse the same geometry every frame. I'm guessing there's some bad interaction between these two behaviours. Try turning off this instancing behaviour by turning on the Null SOP's "Cache Input" parameter.

 

I have tried it, It's still not work.

[jennehjenneh]

I opened your file and it seems if you go inside the fireworks node and disable null2 it works fine even when you connect the null to the popnet. 

[乐琢 Urdro]

I opened your file and it seems if you go inside the fireworks node and disable null2 it works fine even when you connect the null to the popnet. 

 

Yes, you are right, and it really confused me.

 

However, if I simply delete the "null2", it is still not working. Only disable it can make it right.

[danw]

It sounds buggy... have you tried out a later production build?  I think 12.5.316.22 was the first release production build of 12.5, wasn't it?  It might be that this issue got fixed later on.

 

(This is assuming jennehjenneh used the same build to test this... if not then disregard :-)

 

Edit: Disregarded :-)

Edited August 8, 2014 by danw

[jennehjenneh]

It sounds buggy... have you tried out a later production build?  I think 12.5.316.22 was the first release production build of 12.5, wasn't it?  It might be that this issue got fixed later on.

 

(This is assuming jennehjenneh used the same build to test this... if not then disregard :-)

 

I opened the file in 13.0.401

 

 

 

Yes, you are right, and it really confused me.

 

However, if I simply delete the "null2", it is still not working. Only disable it can make it right.

 

I noticed that too. I am pretty sure the collect node is causing it though and it has nothing to do with your nulls.

It seems that it gives an error when similar particles are merged into the same stream.

If you change the order in your collect node you'll see it gives an error in another part of the stream, it can't provide more than one input. For some reason though, disabling null 2 seems to fix one of those errors.. no idea why. 

But if you for example plug your null 3 in after the starburst instead of color_dead you see it will give the same errror and disabling won't fix it. 

 

I checked the fireworks otl (old popnet) in version 13 and it gives the same error when you try to get particles from the same stream into one collect node.