Animation improvement suggestions
Posted: Fri Mar 25, 2011 5:07 pm
Hey guys,
I just wanted to put a couple of ideas out there, in case it might be possible and not already thought of ( unlikely
).
Idea 1)
Multi-frame Obj export with octane reload instead of restart. The idea is that the scripting tool in the software will export each frame as an obj, and create a large number of obj files with a numerical sequence like frame numbers. Then Octane wouldn't need to close an open repeatedly, but would be set to load the next frames .obj file. If possible this could even be done where only 10 or so obj files are being created, and when octane animation tool is done with the obj, it is automatically deleted to preserve space on long renders.
Idea 2)
Camera data only import. On renders that are using a single scene and just moving the camera. The idea here, would be that the Obj file could remain loaded and voxelized, while the camera data is just re-loaded and the camera is moved. I would assume that this would be done via a separate file from the obj file that the exporter script would have to make.
Hope these can be helpful, and since I don't know what things are happening with the development of the software, please feel free to disregard if these suggestions are contrary to your current direction.
I just wanted to put a couple of ideas out there, in case it might be possible and not already thought of ( unlikely
).Idea 1)
Multi-frame Obj export with octane reload instead of restart. The idea is that the scripting tool in the software will export each frame as an obj, and create a large number of obj files with a numerical sequence like frame numbers. Then Octane wouldn't need to close an open repeatedly, but would be set to load the next frames .obj file. If possible this could even be done where only 10 or so obj files are being created, and when octane animation tool is done with the obj, it is automatically deleted to preserve space on long renders.
Idea 2)
Camera data only import. On renders that are using a single scene and just moving the camera. The idea here, would be that the Obj file could remain loaded and voxelized, while the camera data is just re-loaded and the camera is moved. I would assume that this would be done via a separate file from the obj file that the exporter script would have to make.
Hope these can be helpful, and since I don't know what things are happening with the development of the software, please feel free to disregard if these suggestions are contrary to your current direction.
.
the new developer