thanks for the answer radiance.

i'm sorry if my words sounded a bit arrogant, surely i don't ask for a tech demo ready for commercial market.
i'm just discussing about import features, simply because the success of a standalone renderer depends 50% on the ability of exchanging data.
so, i want to ...

actually i think critics are positive.

they are going commercial, so this rendering engine has to face at least small studios requirements, not only some university research stuff (no offence on university research at all, i work both on private and university labs).

we have 4 nodes maxwell ...

i think he means that if you have a mesh named "Camera" during import it will be substituted with a camera in octane.
and probably if you have cube, cube.001, cube.002 they will be considered instances.

smart workaround, but there's plenty of limitations:
- you lose cameras' parameters, only ...

that's nice, and I've also seen .dae import planned for version 1.0.

thanks for the info.

thanks for the info enrico,
but i think it must be solved for all softwares, not just a blender-related solution.

i'm really excited about this new project, but the import-expport feature seems greatly underestimated to me.

obj doesn't export cameras, lights and more important instances (without instances a render engine is pretty useless as a professional tool, good only for testing).

renderman exporters are ...