Search the Community
Showing results for tags 'context'.
Found 3 results
Hi So I have an asset created at Obj level, and I want it to be avaible in the Sop context, so I tried by changing the the context from Obj to Sop (see attachment) and then matched the current definition and loaded the asset in a new scene, but it still appears in the obj context...any tips on how to sort this out?
Hello! So I have just spent the last few hours trying to understand why I wasn`t able to have my point cloud nodes (pcOpen, pcImport, pcIterate, etc.) running normally. It turns out that my problem had nothing to do with the pc[...] nodes but rather about the fact that I was within a VOPSOP node rather than in an AttribVOP. In the end, what I noticed is that whatever was sent into my "while" loop to be processed with pcIterate would end up going nowhere. my while loop wasn't able to return anything else than null data. When I rebuilt my loop structure within a AttribVOP instead of a VOPSOP, everything started to magically work. It seems to me the problem is similar to another problem I've seen about PointWrangle VS AttribWrangle where some functionality works in one but not the other. From this thread it seems that it's all about context. In the end, I did find a workaround by using the AttribVOP instead but I have to admit that I really don't have a clue about why I should use one or the other... Is AttribVOP always better? Is it just a more generally usable node; VOPSOP being more specific or something? PS: I think I've heard that these nodes changed in H14 but we are using H13 because of production requirements.