Maxwell Render | Official public forum

Finally I have RC5 working, and from the renderer it looks good.

However, visibility dots still don't work correctly after half a year of development.
These object mustn't be rendered, but it is:


Sometimes I'm really wondering if the guys doing the plugin
are able to read a tree recursively.

What's the matter here??? This is dead simple logic and could be fixed
within an hour if you know what you're doing!

Sorry if this sounds harsh, but I'm fed up to change most of my scenes
because of this stupidity or lazyness...

Kabe

As the object kist show, the concept of an object tree seems to be
completely lost on the creators of the plugin

They really dump out the whole object tree in one looooong list, do
that with a couple of hundred meshes and you know why I'm frustrated...

As the Studio app support grouping of objects, there is really no justification
for this mess.

Then each mesh has it's own material tag, though you can assign materials to groups... which isn't terribly intelligent either...

Kabe

I tried it once with 4000+ objects. grouping them back to ~25 object groups took me half a day because of maxwell crashes. Now it works, but I'll not do it again.

....waiting for this to be fixed.... It's not a big bug, but something really bad for the workflow. If it's up to me - discard the studio and concentrate on the plugins and the material editor. Would be great to have the material editor starting from cinema, just like the cinema-materials. Put the maxwell dialog in the render settings, like radiosity is, or perhaps in the post effects dialog. Perhaps have a different window for the materials but that's it - assign and treat everything just like in cinema.

Hi Kabe, in my tests seems that the propagation works only if there is only one level from father to childs, for example uno null object with inside some childs at the same level
The good news is that in this case also the green dot work

Well, if it works one level deep then it was ok for their test case I guess

However, if it works one level deep then still the whole tree parsing is
broken. This is all about scope and how to render a node tree. It's not
rocket science...

Kabe

i think the programmerof the c4d plugin is some student or youngster with not much programming experience.

or he gets paid nothing and its just a sparetime project. it is VERY unprogessionaly made, sorry to say.

he (or she) had sooo much time to solve all the cinema related problems, its ridiculous that still it suffers so much problems.

i REALLY hope NL find someone who can programm this plugin correctly.

cebas made a very deep pluginconnection for their rendeerengine in few month! it allmost feels like cinema itself. NLK should take this as an example how a renderplugin connection can be made in cinmea4d.

cheers
stefan

Is this the same issue as N13.

Seems to me to be the same issue.

If it is it is a known issue. Please let me know as this is on the MacOS, and I do not have MAC.

NL is aware of the plugin issue, time only allowed them to update our plugin to work with the RC5.

Please allow them time to focus on getting M~R more complete, they have already mentioned that the plugins are a priority but not before some of the other remaining issues for M~R can be cleared.

I am very sad to suppose that probably one of the Maxwellrender coders is doing the plugin coding too.
Hire someone to do it please!
Someone that knows.

well then at least he has not much time used to programm this plugin.

stefan

Tyrone Marshall wrote:Please allow them time to focus on getting M~R more complete, they have already mentioned that the plugins are a priority but not before some of the other remaining issues for M~R can be cleared.

This is the birth defect of doing it all on your own, instead of contracting
someone who knows how to code Cinema plugins. I'm shure they would
already have a better plugin if they would place it into open sourse...

If you don't have the resources yourself, find someone who know.

Kabe

Here is a better visual explanation of the problem.



The render dots propagate correctly only for the immediate child of a parent object, it does not correspond when the parent is a child of a another parent.

This bug is a new issue and as such is now known as N18.

See CIRI 0.7b for more details

ref: http://www.maxwellrender.com/forum/viewtopic.php?t=9793