[kraemerJK]

I found time to play around with 1.1 and the new C4d plugin. I have a scene with several cameras, all have maxwell tags. I open up the plugin, hit WRITE MXS, open the darn thing in Studio and only find one camera, which shows exactly the view that was active while writing the MXS. Is that correct ? That would mean I had to write a different MXS for every camera that I use ? Or is there some switch that I did not find that says "Export each and every camera" ?

[Tyrone Marshall]

The plugin only exports the current selected viewport as a camera. You will need to export additonal MXS views and import these into your main MXS file to get the additonal cameras.

I'll pass along a suggestion to allow for easier method to adding additional cameras.

[dyarza]

As long as you are passing things along, I would like to see how many people were happier with the camera selection in the old plug-in.

There were certainly lots of things to fix, but I did not think this was one of them. I think that being able to choose a render camera at the plug-in makes a lot of sense for those of us that have multiple cameras in the scene.

Anybody else?

Thanks,

D

[mashium123]

Oh yes, please. Freedom of choice.

[noseman]

So it's time for a nag session.

The way I see it is that since NL is very secretive and has a temper of a spoilt 5 year old, they have very few platform beta testers.

I would make a wild guess that you could count C4D testers on the fingers of captain hooks right hand. (for the sake of simplicity we will call him Tyrone , not the captain, but the beta tester)

Anyway, the fact is that little input gives little output.
The problem is that if NL would involve more in this, they would have more exposure of their bad inside doings.

As you all remember, most of MR's money was made on vaporware. The less details get out in the open, the better = less testers = longer delivery times = less clients = less possible people to help out.

One and a half year after the "supposed-to-be" release of the C4D plugin and functionality is still not as expected.

[kraemerJK]

Thanks Tyrone, I will try that.

Without really wanting to join this so-called "nag session" : Camera selection indeed was much more comfortable before than it is now, and I (for one) can´t see any advantages for the user, maybe there are certain things within the software that made this step necessary.

I think there are a lot of different issues on the wish list for many people. I think the biggest problem (at least for me) is the rather slim documentation of the plugin. It does not really say what has been changed, which cinema tags are supported (e.g. clones ???) or which tags are supported if you consider this and that. Since I do not have infinite time while delivering my projects on time I hate to have to find out things by trial and error. So it might be a good idea to actually give out some kind of list with all the cinema tags/functions (or at least the major ones) and next to it the information if they are supported by maxwell or not.

I really want to start using Maxwell for professional jobs (which I currently don´t do because of all the issues), and solid documentation would be great. The new manual itself is a huge step towards that, the specific plugins should be better documented. To be fair : it´s better already than it was with the previous version.

So, I am looking forward to all the changes that are to come.

[noseman]

... just imagine how bad it would be if Tyrone wasn't putting all this effort for the C4D community.

[kraemerJK]

I agree. I just think that we all are witnessing a software development that might have been just a little bit too ambitious from the start. As far as I can recall I have seen not one single render engine that tried to integrate into so many different packages like maxwell does. A lot render engines only support one platform. So, the speed of development must be slower than with average programs.

Still, the results that are achieved do speak for themselves. I have a lot of things that I would really love, but I can see that using C4D and not 3DS I chose a less common program. From a democratic point of view I can understand everything that comes with that decision.

But I see improvement. Of course I would love to have a fully operationable program with seamless C4D integration; regarding animation, flawless translation of numerous tags, a easy to manage sun system (like a north arrow that you can actually manipulate) . But I am pretty confident that this will come.

And Tyrone is doing a great job regarding C4D. That´s for sure.

[firebird]

As long as you are passing things along, I would like to see how many people were happier with the camera selection in the old plug-in.

yes, please bring a camera choice back in the next update! it happened the whole week end to me, that I hit the render button and ended up in the wrong viewport! this gets a bit annoying by the time!

so freedom of choice please!!!

thx

[Rochr]

As long as you are passing things along, I would like to see how many people were happier with the camera selection in the old plug-in.

There were certainly lots of things to fix, but I did not think this was one of them. I think that being able to choose a render camera at the plug-in makes a lot of sense for those of us that have multiple cameras in the scene.

Anybody else?

Thanks,

D

Me agree!
I´m also tired of nagging, but can´t help wondering if this is just another way to try forcing users towards Studio.
If multiple cameras was such a bad thing that NL fealt they have to remove them from the plugins, how come that feature is still present in Studio?

I also couldn´t help noticing in that poll-thread, that most A-teamers seem to be using Studio about 100% of the time.
I´m definitely curious on how much time the A-team/beta testers actually spend with the plugins. Do you honestly put enough time testing them, or are you just using them as an exporter for Studio?

This is not an attempt of nagging, i´m simply curious to find out.