I finally have some time to look at this, but I want it to work on V6 as well, so I got a bug to iron out first.
@nathanletwory do you know why Cycles restarts for every frame when I make a script like this:
(This is just an initial dummy to see if stuff works like planned)
When Cycles is running and objects are selected I can manipulate them in realtime with gumball, but the moment a script is doing it then it becomes veeery sluggish. I tried with time.sleep(‘seconds’) too, but that too stops cycles from calculating.
Can I get Rhino to wait and still have cycles calculating like Neon did?
#Rotate object, wait and viewcapture
import rhinoscriptsyntax as rs
obj_ids=rs.GetObjects("Select object(s) to rotate while capturing frames")
nr_Frames=rs.GetInteger(message="How many frames for a 360 degree spin?", minimum=1)
renderTime=rs.GetReal(message="Render time for each frame?", minimum=0.001)
for frame in range(nr_Frames):
rs.RotateObjects(dupObjects, center, angle, axis=(0,0,1), copy=False)