Hi C4D users,
I've got a question:
The exporter version 0.12 will have the ability to save/update animated textures. The way how that it's done is, that the exporter checks during the export if a texture image is animated and if that's case, creates a copy of the current frame in a sub-folder "<project name>_files".
Someone (I think it was Roubal) asked for the option to pull all used image textures into one folder relative to the OCS file. I plan to add this, too, i.e. all image textures would then be stored in the above mentioned sub-folder, too.
With one of the next releases I plan to add the possibility to export selected objects as separate OBJ/MTL files plus a CSV files which then allows you to place objects/instances of those objects using the CSV file.
Now to the question: Would it make sense to store the main OBJ/MTL files there, too? This would mean, that every OCS export would create an OCS <project dir>\<project name>.ocs and everything else in the sub-folder <project dir>\<project name>_files\.
Does that make sense? Any problems I'm not seeing?
Cheers,
Marcus
quick question
Moderators: ChrisHekman, aoktar
- Floating.Point
- Posts: 34
- Joined: Sat May 29, 2010 7:11 am
- Location: Australia
This sounds like a perfectly viable solution. I'm all for it!
It wil be interesting to see if this workflow is incompatible with anyones pipeline,
To me it seems to tie everything together, making it all succinct and clean.
It wil be interesting to see if this workflow is incompatible with anyones pipeline,
To me it seems to tie everything together, making it all succinct and clean.
1 x 3930K | 1 x TitanX | 1 x GTX 970
+1, collecting all the files is a very useful solution also for transferring the scene to a different machine
ciao beppe

does this mean that we could send animations with the new expoter to the 301 instancing version?With one of the next releases I plan to add the possibility to export selected objects as separate OBJ/MTL files plus a CSV files which then allows you to place objects/instances of those objects using the CSV file.
ciao beppe
I'm not exactly sure what you mean. The plan is to allow you to export and animate instances (but the old way with re-opening Octane for each new frame). The only problem is that you still have to manually set up the scene using separate mesh and scatter nodes. After that is done, the exporter will be able to communicate changes in the instance positions via the CSV files and the instance mesh changes via the instance OBJ files.bepeg4d wrote:+1, collecting all the files is a very useful solution also for transferring the scene to a different machine
does this mean that we could send animations with the new expoter to the 301 instancing version?With one of the next releases I plan to add the possibility to export selected objects as separate OBJ/MTL files plus a CSV files which then allows you to place objects/instances of those objects using the CSV file.
ciao beppe
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
sorry for my poor english, yeah it's exactly what i want to say, can't wait
ciao beppe

ciao beppe