No problems. As said OBJ works like a charm so I don't know if there are any benefits if you could manage a C4D native format.
So forget my question. :-) It works ok as it is now.

Peace,
Rich_Art. ;-)

Yes it's not to hard, but it would definitely be handy on repetitive projects.
I understand that FBX format can store camera data, maybe it would be an option.

Nice modeling Sirius Btw!

Marc

=Rich_Art =

No problems. As said OBJ works like a charm so I don't know if there are any benefits if you could manage a C4D native format.
So forget my question. It works ok as it is now.


---------

I totally agree with you,Rich
Michael made a great obj exporter..we C4D users could not pretend too much by this Man
....maybe..(i say maybe.... ) a thing like this:

http://www.rhino.io/

Hi Rich_Art,

> No problems. As said OBJ works like a charm so I don't know
> if there are any benefits if you could manage a C4D native format.
> So forget my question. :-) It works ok as it is now.

Yeah the problem is that file formats usually involve a pretty considerable amount of work and testing, it's a pretty major undertaking to support new file formats.

So there kind of needs to be some nice benefit that would be gained from the file format in order to justify the time spent on developing it...

- Michael

Hi Marc,

> I understand that FBX format can store camera data, maybe
> it would be an option.

I've made a note to look into that - I'll probably be doing some work on FBX export at some point here to support materials export as well.

- Michael