Page 1 of 1

weight map error

Posted: Fri Jun 08, 2007 10:51 am
by Pperezu
When I export of C4D to MR, the clip map they don´t work …

Simply, the second layer of the material weight map, must have nd=1 and plugin export=3, then it does not make the transparency.

Replacing in all textures the 3 by 1, already works.

I hope a new revision soon…

Posted: Fri Jun 08, 2007 1:13 pm
by zoppo
same here ... :roll:

Posted: Fri Jun 08, 2007 4:32 pm
by patrikpanda
.yes....the same. :cry:

Posted: Wed Jun 13, 2007 3:22 pm
by spekoun
Hmm i have to confirm this bug. Rally confusing. Why C4D plugin is so buggy??? And why it is broken what worked fine!!!??? :?

Posted: Wed Jun 13, 2007 6:41 pm
by Carl007
I also have this problem!
Who is coding the c4d plugin?
Who is betatesting it?
How come all these bugs?

Posted: Wed Jun 13, 2007 8:32 pm
by Kabe
When I export of C4D to MR, the clip map they don´t work …
Good enough for a rant, but frankly not for a bug report... What kind of clip
map are you using? Could you please post a little bit more as an description?

Thanks

Kabe

Posted: Wed Jun 13, 2007 8:46 pm
by Pperezu
Much explanation is not necessary. I have a C4D material with channel alpha, and when it exports the material to Maxwell, the second layer weight map has nd=3 when it must have nd=1.

So simple…

I supose is very simple to repare...

Posted: Thu Jun 14, 2007 7:26 am
by Kabe
Carl007 wrote:Who is betatesting it?
How come all these bugs?
How come that all the users combined needed several weeks to discover it
while the beta testers haven't spotted it?

You might think a moment about the fact that there are less beta testers
than users, and that they tested an application that had many more bugs
which you never saw.

Unfortunately the current plugin broke a couple of things that used to work,
which is exactly the kind of stuff that can't and won't be tested as hard as the
areas that were changed or introduced new features.

Maybe introducing the plugin as public beta would have changed your temper,
it would not have changed the state of the plugin though.

Kabe

Posted: Thu Jun 14, 2007 9:37 am
by Carl007
Thanks Kabe for your answer.

A bit frustrated, thats all...

Posted: Fri Jun 15, 2007 3:34 am
by leoA4D
Pperezu wrote:I have a C4D material with channel alpha, and when it exports the material to Maxwell, the second layer weight map has nd=3 when it must have nd=1.
Did changing the second layer to nd=1 work for you? By "second layer", do you mean the second BSDF?

My second image is a red-purple color and my alphas are missing the transparency around the leaf in the renders. I changed the nd=3 to nd=1, ran a quick render and it did not change anything.

Posted: Sat Jun 16, 2007 1:43 pm
by Kabe
This is a good example why the tedious work of describing bugs is necessary:

As you see, it was unclear what the problem exactly is, what steps you've
made to get it and what have to be done to reproduce it.

We have a proper case in the meantime. In this case, changing the nD of
the second BSDF layer of the material to 1 fixes it, so it will be fixed in an
upcoming release (quite soon, but not necessarily the next one).

I'm a bit concerned that the stuff leo described might be something different.
To catch that, we would - again - need more info how the Cinema scene
was build.

Cheers

Kabe

Posted: Sat Jun 16, 2007 3:46 pm
by leoA4D
My problem is fixed and probably different then Pperezu's.

When I read this thread, I assumed Pperezu's problem applied to all similar problems. So, I tried the nd=3 to nd=1 solution.

I was using Ivy Generator in C4D where the alpha is made from the color image but when transferred to MWR, the leaves were not clipped. After making a b&w and dropped that in the alpha channel un-checked Image Alpha and Soft, it worked fine.

Posted: Sat Jun 23, 2007 4:17 am
by Eric Lagman
The problem is two things. When exporting objects with clipmaps such as trees the weightmaps on each bsdf are inverted wrong and the nd is set to 3 instead of 1 on the second bsdf clipping layer. I wondered why my trees were coming out wrong on some of the test I have done, and I found that to be the two reasons. Hope this gets resolved.