OTOY Forums

I am using C4D and Octane 2.57

Here is what happens. I export my scene form within c4d using the official plug in to set my materials ect, everything works as expected. I then go back to C4D and set my export parameters for a full animation within the plugin dialogue telling it to use an existing .ocm file instead of creating a new one with reset materials. I press "render animation"... the scene loads all image textures and voxelizes fine, but then an error pops up saying ( Node "desert_house" is no mesh node ) I can click on the mesh node in the node editor and the scene loads like any other project and starts to render. The problem is this error essentially stops the animation process from happening and that's lame

Just to recap I am using c4d R12 on windows 7 64 bit and Octane 2.57
Any help would be appreciated
Thanks

EDIT

I re-exported my project from scratch, and assigned materials again. It worked. I guess it does have to do with the .ocs file link to the obj. file. I believe at one point I exported a obj file with different geometry and manually loaded it into an exhisting octane project and from there things got confused.

Bulwerk wrote:I am using C4D and Octane 2.57

Here is what happens. I export my scene form within c4d using the official plug in to set my materials ect, everything works as expected. I then go back to C4D and set my export parameters for a full animation within the plugin dialogue telling it to use an existing .ocm file instead of creating a new one with reset materials. I press "render animation"... the scene loads all image textures and voxelizes fine, but then an error pops up saying ( Node "desert_house" is no mesh node ) I can click on the mesh node in the node editor and the scene loads like any other project and starts to render. The problem is this error essentially stops the animation process from happening and that's lame

Just to recap I am using c4d R12 on windows 7 64 bit and Octane 2.57
Any help would be appreciated
Thanks

i had that once, but can't exactly remember what caused it. it seems like the exporter only overwrites .ocs settings, which were not already changed by the user (the .ocs scene stores this information), and if the present .obj (in the .ocs) was different from the mesh provided via the commandline, this error occurred. imo it happens, if you manually load another obj. to the scene, and later try to use the same scene with the exporter - but i can be completely wrong here...

This error is because of inconsistant naming.
Octane can contain several mesh nodes so it is always a good idea to give the mesh node and .ocs scene the same name as the obj.
Otherwise the animation exporter does not know wich mesh node to adress.

Thanks! I will try to start clean and see if I can get this thing animated.