[giulioandrea]

I did just a rendering with 9.6PPC and MR 1,
again dark patches in the image...
I do not have a www so I cannot show but I just used basic meshes with the phong tag...
anyone else with the problem?


The funniy thing is that I tried v1 and it worked fine with 9.52...

G.

[Kabe]

The common resons causing this problem are:

• UVs outside the range 0..1 - M~R is dumb when it comes to UV wrapping.
  Flipped normals
  Flipped axes (this can be especially hard to spot!)

However, I have the same problems with a scene, and all the above
reasons are not responsible. Looks like this:


This exact scenes rendered fine with the plugin versions Alpha, Beta, and RC5.
Now with V1.0 they fail. They did so in C4D 9.52 and C4D 9.6, so I would
rather not assume that it was the version change in Cinema causing this.

Are you shure you haven't changed anything else and using the exact
same version of the plugin?

Attention: The plugin version didn't changed with release, but the
plugin did quite a bit! Check Custom Materials to get your version,
if it has a button to start the Material editor, then it's release.

Hope it helps

Kabe

[giulioandrea]

all you say is ok.
I am doing a test: a cube with fillet... not so impressive to model in cinema
I am using artificial light (a flat, rectangular, polygon)

anyway I did change several things to see what was the reason (scale, phong tag...)...
alll the same... position anq quantity of the black patches changes but they are always there...
...
until
...
I reverted to cinema 9.52.
and the problem went away...
is it cinema? what do you think?
what about you?
thanks
G.



PS maxwell, as usual, impresses me with his attention to details why the version in the text file is 0.7c and in cinema says 0.7b??? both coming form the same zip file???? as usual...
anyway it's the lates version, I downloaded it again, right now.

[seco7]

I had this problem with the RCs as well, regardless of the Cinema version. It was a very erradic problem, scenes that worked numerous times would start having this problem. I even deleted and re-added the object and it persisted. If I remember correctly, I had some luck copy/pasting the object to a new, blank scene. The problem objects often showed up in Studio with very odd material names, etc. You might be able to find the problems by examining the scene in studio.

[sunmade]

I have this regularly, and "trying" to fix it is a nightmare...

impossible to solve all the black polys or whatever.

nasty bug? or am I a bad modeller?

did any of the alpha / beta team c4d testers have the same issues?

what's your take on it?

[Kabe]

To the best of my knowledge the A-Team has a single Cinema User...

And yes, at least the cases I've seen are related to suboptimal modeling.

Anyway, this is a lame excuse when it's rendered well in every other
render engine out there.

Kabe

[sunmade]

thanks kabe for the insight.

VERY frightening to hear that...1 c4d user...ookaayy

Then I agree with you:
Suboptimal modeling (bad modelling) is the culprit, BUT lame excuse in deed, because I have never run into this issue in ANY other rendering engine...

So it should be fixed hopefully.

I hope VRay for Cinema 4D won't have this limitation.

What are your thoughts / experiences on this NL Team and users?

Does it only happen with Cinema 4D?

cheers

[seco7]

I'm not sure it has a lot to do with the modeling ... sure if you have the normals backwards etc, but if I'm not mistaken, I have had this problem with VERY simple objects. I cannot confirm this right now, but maybe even primitives. I'm 100% sure I have had it with simple nurbs and simple lathe objects.

At least in the RC, it seemed more like a pointer error or some other code problem because of how erratic it was and how you could delete and re-add the same object (same name etc) and it would still error.

[sunmade]

Yeah, I probably forgot to mention that as well.

I know the traps, ie having normals flipped, axis etc.

So that is not the problem with my case.

And I agree, it can happen to very basic geometry.

Some times I have an object that is rendered ok, than I copy paste that same object and I see the first one still rendering ok and the newly copied one black....I can't understand it at all.

[Kabe]

With suboptimal modeling I didn't meant flipped normals and such thing I've
mentioned above, but especially elongated polygons.

You can get there quite easy with primitives or lathes. And it happens quite
often when working with CAD data.

As long as you calculate with the necessary precision, this is not an issue.

I'll try to isolate the cases that I have, check them in Studio and post
them here. Could be the plugin causing this mess here...

Kabe

[seco7]

That's interesting Kabe, do you mean subdivide an object and it should fix the problem?

[Kabe]

That's interesting Kabe, do you mean subdivide an object and it should fix the problem?

No, subdividing elongated polygons will create even smaller elongated
polygones. Cutting *might* be an option, subdividing certainly is not.

However, IMO this is not a viable option:

It renders fine in *every* renderer except one, so it smells like a bug to me.

Kabe

[seco7]

It renders fine in *every* renderer except one, so it smells like a bug to me.

I cannot resist ... it certainly smells like something!

[Mr. Gog]

I used subdivide and the problem disappear!!!
I' am working on a building, two cases and going. On both of them subdivide solved the problem.

Let you know tomorrow.