Page 1 of 4

Petition from C4D community

Posted: Wed May 17, 2006 7:06 pm
by noseman
I want to start a petition from the C4D community towards NL.

Dear Nextlimit
Please provide us ASAP with a plugin for C4D that has FULL Maxwellrender functionality. Announcing and releasing a Version 1 Maxwellrender that has minimum functionality in Cinema 4D is - yet - a new way to dissapoint us.

I emailed NL with my concerns on May 3rd but I have NOT received an answer.

My email:

"Hi there Maya.
I am afraid I'm very disappointed from Version 1 of Maxwellrender.
I am a dedicated Cinema 4D user and I don't have the intention to learn the use of another software because I am too busy to do so.
I already have hundreds of scenes setup in Cinema 4D and it is too hard for me to export all to Maxwell Studio in order to work with the full capability of Maxwell Render.
I was under the impression that the Cinemaxwell plugin was being tested and expanded during the last few months. Unfortunately the specific plugin is under NO circumstances a finished product.
I would please like an honest answer from you about the specific plugin for Cinema 4D.
I have prepaid Maxwellrender from last year and I would like you to answer my question without "politics".
When will you have a Cinemaxwell plugin that will function properly?
Please, please, please be honest. If it is not in your plans, give me the chance to choose NOT to use Maxwellrender again.
Don't torture your customers with false promises.

Thank you.
Athanassios Pozantzis
Nexlimit client"


Anyone else intrested in signing this?
Thanks

Posted: Wed May 17, 2006 8:01 pm
by Kabe
I'm really unhappy to report that this won't change a thing.

The answer - if any - will be "soon". So wither use what we have or
concentrate on other things. That's what I tried to do the last weeks
and it helps a bit.

The users have put much more energy in this mess than can be justified.

Kabe

Posted: Wed May 17, 2006 11:27 pm
by jc4d
Nico.fr wrote: They forgot that we are not engineer... why don't we have a button for exemple, an mulilight button.... not to type -ml.
You hit in the nail, I´m not an engineer either and we are in the 21 century with the most advance software in render world, I don´t want typewriting I want push buttons :D :D , this remind me ACAD :?

Posted: Wed May 17, 2006 11:34 pm
by Carl007
Yes! Give me those check boxes, in the plugin also

Posted: Thu May 18, 2006 12:46 am
by sunmade
When will there be a new c4d plug in ?

any of NL Team ready to shed some light on the roadmap?

thanks

Posted: Thu May 18, 2006 5:57 pm
by lllab
as you see most plugins seem one the way to get updates ( lightwave archicad already released) i guess the c4d plugin too.

the question for me is how much better it will be. hopefully tyron as our only betatester will look for it.

to be honest i dont find the plugin THAT terrible, i can work quite ok with it.
rather some things in maxwell itsself have to be smoothed out i think, netrednering, -hd, -ml for bigger images, glare for bigger images etc.

an inportant thing for workflow for me would be to keep the cinema grouping when exporting it to studio, and also a direkt exprt to studio button p.e.

i think it is important to exactly say WHAT bothers you instead of just overall complaining, that doesnt help anything. a detailes buglist or a good description of the problem helps much more.

cheers
stefan

Posted: Thu May 18, 2006 6:10 pm
by sunmade
as stated numerous times:

Cinema 4D Plug-in "MUST HAVES":

- keeping polygon selections (and their textures/mats) from c4d to mxcl ! it's a must for larger scenes!

- look into the issue with "black polygons" (bad modelling aside, why can other engines handle the geometry? )

there are a lot of references to these issues on this forum (c4d).

I hope you are right stefan, maybe we are next ;)

chris

Posted: Thu May 18, 2006 6:35 pm
by Eric Lagman
I would sign it also if I thought it would change things, but the fact is NL bit off way more than they can chew. I dont think they need a petition to know that many people are frustrated and pissed with them. They are understaffed to deliver on what they promised as far as a functional plugin for c4d, and most of the other ones.

I am able to use Studio with the other modelling packages I use now, but would prefer to do all my rendering with maxwell inside c4d. I suppose the max plugin will get the most attention first, then c4d somewhere down the road. Kabes advice is the best. Try to concentrate on other areas until they get this mess sorted out. Dwelling on it will just make you more upset which is not healthy. Lets try to hope for the best and see what happens. I feel everyones pain on this.

Posted: Thu May 18, 2006 6:43 pm
by lllab
well the poly selection was said is already worked on.
also some other bugs, i really hope the fix all know listed...

the black poly bug is new to me, never had that, although i work all the time in MW, when does this happen?

cheers
stefan

Posted: Thu May 18, 2006 6:49 pm
by beppeg
For me the most important things are:
1-black polys issue
2-mxm to poligon selection
3- animation

I'm very huppy with the new work-flow, no need to open studio at all, only mxed and mxm tag, for me they could delete the presets tags like diffuse ecc.
Now I can stay with both render engines (m~r and cinema AR), the mxm tag don't need to modify the cinema material tags like in beta and Rc.

sorry for my poor language :oops:

Posted: Thu May 18, 2006 7:04 pm
by sunmade
for the so called "Black Poly" or "Black Patches" Bug:

http://www.maxwellrender.com/forum/view ... hp?t=15640

http://www.maxwellrender.com/forum/view ... black+poly

http://www.maxwellrender.com/forum/view ... lack+patch

couldn't find more, but I remember reading more.

I myself have this problem, not all of the time, thank god.

But it is very unpredictable!!

Posted: Thu May 18, 2006 7:10 pm
by arch4d
beppeg wrote:For me the most important things are:
1-black polys issue
2-mxm to poligon selection
3- animation

I'm very huppy with the new work-flow, no need to open studio at all, only mxed and mxm tag, for me they could delete the presets tags like diffuse ecc.
Now I can stay with both render engines (m~r and cinema AR), the mxm tag don't need to modify the cinema material tags like in beta and Rc.

sorry for my poor language :oops:
and: groups !!!
and then, for studio: subgroups !!!

Posted: Sat May 20, 2006 11:57 am
by lllab
yes groups,
and correct material and camera names
and correct group names
and sub groups
and subsubgroups
.
.
.
and did i say group exporting?;-)
cheers
stefan

Posted: Sat May 20, 2006 7:28 pm
by Rochr
I think Next Limit need to wake up from the coma regarding the plugins. This damn thing have been flawed from start and 1.0 is just total garbage.

Apart from hd-option and the old idiotic tagging system where you need to tag EVERYTHING, there are more things for them to deal with.

Having to turn everything editable to be able to render the stuff out is one thing. Fixing transfer of Cinemas material channels so that we don´t need to use Maxwells materials editor is another. Btw, who the hell designed it anyway, the village idiot...?

Since we never bought a Studio, i expect NL to keep their end of the deal and deliver a complete plugin. Fully functional, that means with ALL the features included in Studio. And while NL is at it, they can also focus on the speed. 1.0 is almost twice as slow as RC5.
Are we going backwards now?

NL, you can try forcing Studio on us until you choke on it, but personally, i find it to be something you can keep, throw away or whatever.

Posted: Sun May 21, 2006 2:18 am
by Rochr
xander wrote:Yes, a real plugin and more speed.

After 16 hours, Without textures...

http://crase.free.fr/test-maxwell/chapitre02.jpg

Image Image
That´s a nice scene man. 8)

But at least it´s a detailed scene. This one is ridiculously simple and pretty much made up of a few primitives. Still it takes v1.0 10 hours with 3 basic mxm´s and some white diffuse tags to come up with this bs. And you can´t even use it for anything with this crappy resolution... :cry:
Image