3dome

I took the route of using 2 circles, might be a way too complicated solution but haven't had my morning coffee yet dm_normal_along_geo.hipnc

crappiest motion in history of odforce but this was a 5 min setup to show one way of aligning packed prims to velocity the harsh turns in orientation come from my extremly sophisticated force set-up^^ dm_alignPackedPrimAlongVelocity.hipnc

which is interesting since a solver is a dopnet + bottom right it is selected as the current one. maybe a bug? RFE it?

here's another way hou.currentDopNet().parm('resimulate').pressButton()

feels like the first time using VOPs in years for other things than noise anyway, see the attached file with two "modes", tick on the checkbox and move around the point to see what happens dm_porcupine_force.hipnc

yeah i had a few of them too, but in a million points if you blast those guys away no one will notice dropping down a timeblend and timewarp gives me pretty nice slowmotion

can you attach your scene? ID should always be unique, unless you create it yourself in VEX and mess up lol just tried it myself, IDs get assigned as expected

it doens't work because if you look in the very helpful Houdini python documentation you see that the argument unique_name defaults to False. So the script tries to create a node with a name that already exists (created in the first iteration of the loop). 2 ways to fix that: 1) import csv file = hou.ui.readInput('Enter the full path of the csv file.', buttons=('OK', 'Cancel')) if(file[0]==0): with open(file[1], 'rb') as f: doc = csv.reader(f) for idx,row in enumerate(doc): #using enumerate to get the iteration node = hou.node('/obj').createNode('geo') node.parm('px').set(row[0]) node.parm('py').set(row[1]) node.parm('pz').set(row[2]) node.parm('prx').set(row[3]) node.moveToGoodPosition() node.setName('test_' + str(idx)) #adding the iteration number to the string to create unique names 2) node.setName('test_', True)

use id attrib to track a point over time

here's a simple demo scene left is original anim and right one is new anim with pyro "attached" dm_transferPyroToNewAnim.hip

I don't think you can directly read columns with the python csv module. You gotta do some search in the documentation or on stackexchange, etc You mean something like directly accessing a cell like B3? https://stackoverflow.com/questions/5757743/how-can-i-get-a-specific-field-of-a-csv-file See first answer, Update 2

yes the one from @VFXArabia is nice and simple I also know of this one https://www.sidefx.com/forum/topic/51730/ While I didn't (yet) run it myself, I think it's more close to real world scenario with precaching and splitting tasks, etc as explained by creator @tricecold Would be cool to see some results to this benchmark aswell. I actually might give it a shot over xmas holidays. Edit: maybe the benchmark could be run up until rendering, as we all know: more Threads > few Threads

you could go to your camera, add Lens Curvature (vm_curvature) from the Rendering Paramters and adjust that, or you use a ASAD lens shader (or build your own). To use it, camera under View -> Projection from "perspective" to "lens shader"

seems like point() is a function added in H17. At least I can't find it in the 16.5 docs (which is the version I tried it with myself and got the same error) - can't try and confirm though as I don't have 17 so if that's the case, you are stuck for now with the overhead of using points() [returning a tuple] and then accessing your desired index of that tuple

import csv file = hou.ui.readInput('Enter the full path of the csv file', buttons=('OK', 'Cancel')) if(file[0]==0): with open(file[1], 'rb') as f: doc = csv.reader(f) for row in doc: node = hou.node('/obj').createNode('geo') #create instances of your HDA here instead node.parm('px').set(row[0]) #set the correct parameter of your HDA node.parm('py').set(row[1]) node.parm('pz').set(row[2]) node.parm('prx').set(row[3]) node.moveToGoodPosition() edit: attached sample CSV to go along with code testtable.csv