Page 1 of 3
new cinema v10
Posted: Wed Oct 04, 2006 3:17 pm
by lllab
cool new c4d update, i hope maxwell is compatible?
has a beta tester chance to try it already?
cheeers
stefan
Posted: Wed Oct 04, 2006 3:29 pm
by mashium123
Beta Tester? What Beta?
If you mean C4D, then go and download the demo. In the last demos of C4D maxwell plugin worked without limitation. Maybe that didn't change.
Heh, btw: I tell you to go and download but am standing in the queue myself, 'cause dl-serverlimit is reached... hehe
Greets. Mesut.
Posted: Wed Oct 04, 2006 5:57 pm
by seco7
I'm downloading now, but I expect the Maxwell plugin to have serious issue with R10 and visa versa (apart from the plug crashing Cinema on every exit). Maxon changed alot in the Manager with Layers etc. At least since animation was never implemented, it won't be effected by the changes.
You're right about the beta testers (if you mean the beta testers for Cinema and not the beta testers for the NEW Maxwell plug).

Although maybe some of the developers of the plugin (since it has been getting so much love for months) have an idea of how the new features of R10 are/will effect it.
Posted: Wed Oct 04, 2006 6:36 pm
by macray
Still waiting to download and test c4d 10 (with maxwell).
Can it be that the maxon site looks really bad today?
Posted: Thu Oct 05, 2006 2:37 am
by mashium123
Yeah, surely the one or the other interested will have a look at it.
I got my download and tried it with maxwell-plug, i use for my "normal" 9.6bundle.
As far as I can tell from the first views, everything works with the cinemaxwell, besides (oh yes... besides):
it seems, as if no(!) camera input is transported to mxcl.
I mean the input you define with the CameraTag. No shutterspeed, no ISO value, fstop... nothing. I didn't check, what comes out when you open the written mxs in studio... but who cares? As I try to avoid studio where I can, for me the camera values should of course be transported.
The rest seems to work as usual...
Posted: Thu Oct 05, 2006 8:39 am
by noseman
The rest seems to work as usual...
work?... does the cinemaxwell plugin work?

Posted: Thu Oct 05, 2006 12:51 pm
by lllab
it seem to work here but i cannot write a mxs(due to demo limitations of the demo) so i dont know if it renders correct.
cheers
stefan
Posted: Thu Oct 05, 2006 1:42 pm
by Maximus3D
The new C4D version is very yummy

i been playing with it since last night (demoversion ofcourse) and it's great so far!
Lovely update by Maxon this time.
/ Max
Posted: Thu Oct 05, 2006 1:44 pm
by seco7
I think I broke it ... I'm not sure if it is because of the Cinema demo or incompatabilities with the plug or selection sets. But, I was playing with layers and selection sets in one object manager and had the original object manager open and hit render, everything crashed. Now everytime I hit render (or write mxs) in the plug it crashes Cinema and Maxwell, no matter what the scene is. Even a clean one with just a cube and one standard disfuse material. I'll try and uninstall /re-install Maxwell again and see if that helps.
Posted: Fri Oct 06, 2006 12:13 pm
by glypticmax
If R10 doesn't play well with Cinemaxwell (make a good mxs to be opened in Studio for textures & rendering) its a deal killer for me.
Please keep us updated with experiences.
Edit: Until its a working combination. Next week, next year, whatever.......
Its obviously just a matter of time.
Posted: Fri Oct 06, 2006 2:32 pm
by arch4d
i was playing a bit now with version 10 demo.
here everything works fine with cinemaxwell.
mats are being exported as expected, no crash...

Posted: Fri Oct 06, 2006 3:50 pm
by mashium123
Hi arch4d.
What about the camera data? I couldn't manage to get the camera data out of the tags. The renderer alsways used standard values...
Does this work for you in a normal way?
Thanks.
Mesut.
Posted: Fri Oct 06, 2006 5:14 pm
by Kabe
glypticmax wrote:If R10 doesn't play well with Cinemaxwell (make a good mxs to be opened in Studio for textures & rendering) its a deal killer for me.
The demo is out now for 3 days, the program will be delivered in 3 weeks, so
maybe a bit of patience is appropriate, don't you think?
Kabe
Posted: Sat Oct 07, 2006 3:00 am
by glypticmax
Hi Kabe,
I posted an edit above and thought is would appear below your post.
Wrong.......
I understand it may take time to get R10 and Cinemaxwell to work well together. I'm just not going to invest in R10 until all the issues are resolved.
Buying R10 now and waiting on the NL crew to upgrade a clean fit just isn't something I choose to do.
I can wait. My current workflow with R9.5/Cinemaxwell>Studio is working just fine.
Posted: Sat Oct 07, 2006 10:56 am
by Kabe
Well, on the Mac a lot of people will update slowly anyway. The R10 is a universal binary, which means that the whole plugin architecture changed. It's not a huge thing, but all plugins must be recompiled in XCode, using the Apple compiler.
So people like me who have LOADS of plugins have to wait until at least the workhorses are available as UB.
Considering the M~R Plugin, I don't expect any major obstacles. The layer architecture might not work yet. That depends a bit on how Maxon implemented it, as the Cinema R10 SDK isn't available yet, we just don't know.
But in the crucial sections Maxon has a good history of keeping backward compatibilty.
Kabe