[lllab]

"1.0 is almost twice as slow as RC5."

hmmm. i dont see that here with my scenes, in contrary it seems a bit faster.

cheers
stefan

[Rochr]

Glad it works for someone. It´s slower than ever here.

[lllab]

have you sent the scene to NL?

did you use new materials or old rc5/beta stuff?

sorry to hear that.

cheers
stefan

[Rochr]

It´s not just this scene, even a simple primitive with a gray diffuse tag in daylight takes much longer to render out with 1.0.

The one above was a brand new scene created after installing 1.0. I wanted a really simple scene just for trying out materials, and even skipped the glass in the windows. Not that it will be used for that purpose with these render times...

I thought i used more mxm´s, but now that i look at the scene, it´s only the "Blackcarpaint.mxm" (1.0). The rest is just diffuse and metal tags, physical sky+sunlight and an emitter 10W. (photos in post)
So it´s an extremely simple scene that shouldn´t take this long to render.

I don´t mind using RC5, but since i can´t render out anything highres with it without hd-support, and non of the (so far, non-existant patches) will support RC5, i´m basically stuck with an application i´ll never be able to use for printing purposes. Sucks.

[lllab]

rochr,

but that sounds really wierd, then there must be somehting wrong with your system/settings/scale or whatever?!

a simpel cube with grey diffuse+skylight is not at all slower here, and from what i read and see from others also not for the majority.

p.e. i render here a competition of mine, after 6 minutes i have sl10 and a very nice image @800x600. it uses grey diffuse and a metal with physical sky+sun. after 1-2h i have a good image of printsize in that case.

maybe you still send some examples to NL so that it can be figurted out what the problem is?

cheers
stefan

[Rochr]

Thanks Stefan, but i think it´s simply 1.0 that doesn´t like my system. I don´t have these problems with RC5, well apart from the resolution issue.

I sent them an email some time ago, but never got a responce, so i wont bother with that any more. Although i doubt anything would change with the plugin. The development on that has pretty much been dead for the last year.
I´ll just continue working with AR instead and use RC5 for stuff that doesn´t require printing.

[goncalo]

WHERE IS THE ANSWER FROM NEXT LIMIT ???

[noseman]

I am aware (from various hints of NL affiliates) that a new version of the Cinemaxwell plugin is underway.
The problem is that from the day NL released the "final" version 1 of MR and after many "congratulations", "at last we did it", "thank you for the patience" e.t.c. no official has dealed with any of the occuring problems like BAD plugins.

This is the same shamefull situation all over again.

Bad NL.

[Rochr]

I would be very surprised if they would finally fix the plugins tagging system. That alone would save days in scene setup.

[jeso]

change the nl-team then we become a working plugin

[Kabe]

I would be very surprised if they would finally fix the plugins tagging system. That alone would save days in scene setup.

What do you mean by that? Sure, it has it's flaws, but the general concept
tp attach custom information to objects in Cinema is tagging.
There is nothing wrong with that.

If you expect that you can render a Cinema file without any setup, then you
are lost: You can't do this for quite a number of reasons, the most obvious
of them that the concepts behind material systems are quite different.

What is a major issue though, is that scene setup information like which
camera to render, qulity and size, the sky parameters etc. are not saved with the Cinema file.

Kabe

[Rochr]

I don´t have a problem with tags, but having to tag EVERY single piece is one idiotic system. Let´s say that you have 500 models in a group, requiring the same material. Now, what´s the point of having to tag ALL the 500 children in the group, instead of just the group?
Feel free to explain in what way this speeds up the workflow.

Judging by your gallery here, i can understand why you wouldn´t find any problems with the current system. Although complex modeling, you have very few objects in a scene.
Now, try putting together a scene with 3-4000 objects, and you´ll quickly find out that Cinemaxwells current system is a complete pain in the ass to work with.

Another flaw, yeah, i call it a flaw, is the inability to render out objects that aren´t fixed. If an object is not made editable, Maxwell simply refuse to render it, no matter how many tags you use.
Some models are pretty much required to be left uneditable(splines, sweep nurbs etc) or you´ll have major problems if they require changes. Pulling one point to alter a cable, is hell of a lot easier that pulling 100 or 200. Again, a flaw that prolongs the workflow.

I did one scene with this damn system, and the setup alone almost took
me longer than modeling the entire scene. Take the scene here for example:
I would love to run this through Maxwell, but it would probably take me a week just to setup the damn thing so that Maxwell would accept all the objects. AND, i would have to make duplicates of every single wire and cable if i would need to change something.

So yeah, i call this one of THE major issues with the plugin.
But like i said, i doubt they will do anything about it. Why bother with the plugins and draw attention from their precious Studio, right?

[beppeg]

Rochr, simply grop all objects with the same material, apply the custom mxm tag to the fother and then rigth-click on the tag and choose “Copy tag to childs". After that you only need to adjust the .mxm for all the objects.
You can also choose "Select all identical childs tag" for changing all the tags in one click.
This is the beauty of C4D and has nothing to do with m~r for me

P.S. thery good scene you have, I'd like to see it with m~r

[noseman]

the plug should propagate the maxwell tag properties to the children just like cinema materials do.
The good thing about this whole s**t situation is that C4D has many ways to select multiple tags and modify them.
Just as beppeg says.



BTW Rochr, GREAT scene!!

[Rochr]

Thanks beppeg, but i´m aware of the "copy to child" function.
And i still find it idiotic having to tag everything. What if you need to delete the tags on some or all objects? Then you´ll have to do that one by one(or as many as you can select simultaneously. Happened to me quite a lot on my last Maxwell render and it´s damn annoying, especially when you have a lot of objects.

I find that the beauty with Cinema is that you can use 1 materials tag for an entire group, and if you should need another one, simply add it to the desired object. Simple, and efficient.

And btw, you still have the problem with Maxwell not rendering uneditable objects.

I don´t know about you guys, but i´ld really like to see exactly what type of scenes the person working with the plugin, is working with on a daily bases. Either he uses Studio, or it sure as hell can´t be anything overly complex or these issues would´ve been fixed a long time ago.
They update with bs features like glare, something that´s quicker achieved in Photoshop, and leave out basics.