I have a for loop nested inside another for loop. In this child for loop I have some logic that needs to know what iteration I'm currently through the parent for loop.

However returning ( “../../each1/attribval1” ) is returning the same number as ( “../each1/attribval1” ) which breaks my scene.

I've created a simple example of this ‘bug’ occuring in the ForEach.hip

To get a better context of what I'm doing, take a look at BuildingGenerator2.hip
Maybe what I'm trying to do is an illogical way of going about it, so if anyone could point me in the direction of a solution it'd be much appreciated!

Thanks.

Simple example of the problem

I have not seen your scene but probably simple answer for the problem is in first help TIP
http://www.sidefx.com/docs/houdini13.0/nodes/sop/foreach [sidefx.com]

Yes - to confirm, I opened up your file and both of your loops are using “FORVALUE” and “FORIDXVALUE”, so they will be overwriting each other's iterators. You will want to change both stamp names on at least one of the loops (I usually just tag a little identifier on the end). Not sure if there are other bugs in your scene, but that is definitely one.

Ah, thanks so much! Can't believe it's such a simple fix, I will look out for that from now on.

Yeah, this is an awful bug with ForEach. I ran into it myself a couple weeks ago and spent hours trying to figure out why things were recooking in a completely bonkers order and with nonsense output. It'd be really nice if the scoping on the stamp variables was respected, but apparently it has to be broken for some esoteric reason that I don't know if I really trust.

ndickson
Yeah, this is an awful bug with ForEach. I ran into it myself a couple weeks ago and spent hours trying to figure out why things were recooking in a completely bonkers order and with nonsense output. It'd be really nice if the scoping on the stamp variables was respected, but apparently it has to be broken for some esoteric reason that I don't know if I really trust.

I too spent a few hours on this bug years ago, and was surprised no one complained about it before. I suggested a potential solution in the other thread