Maybe you could force it by adding a writegeo downstream. I would imagine that would make nuke evaluate geometry positions upstream?
Maybe adding the positions as metadata in the stream could be a valid alternative. Cheers, Elias 26 feb 2014 kl. 12:56 skrev Carl Schröter <[email protected]>: > Hi guys, > > I've been experimenting with vertexSelection lately (in nuke7) and noticed > something strange (at least it seems strange to me). > > When I run the code below on selected vertices of an animated abc file, Nuke > does not update the vertex-position values in the loop. However, if gives me > the correct position when I execute it on single frames. To make it even > stranger: when I connect a scene-node to the ReadGeo, the code outputs 2 > points for the same selection on different positions in space. > > ########## > temp = nuke.nodes.CurveTool() > for frame in range(1100,1150): > nuke.execute(temp, frame, frame) > nuke.frame(frame) > > selectedVertexInfo = nukescripts.snap3d.selectedVertexInfos() #it's the > same for selectedPoints() > print nuke.frame() > for point in selectedVertexInfo: > print point.index, point.objnum, point.position, point.value > print > > nuke.delete(temp) > ########## > > To make my confusion complete: it sometimes (very rarely) just works as > expected... > > Is there something I am missing here? A way to force update the 3d-system? > Also is there a way to get the geo containing node from selected points (so I > could temporarily disconnect the scene node downstream)? > > Any help is greatly appreciated! > Cheers, > Carl > _______________________________________________ > Nuke-python mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python _______________________________________________ Nuke-python mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
