Chaos Corona Forum
Chaos Corona for Cinema 4D => [C4D] Bug Reporting => [C4D] Resolved Bugs => Topic started by: bableveske on 2018-01-16, 00:45:35
-
Hi,
I use Trypogen plug-in with C4D r18 and when i make a model the renderer doesn't render the same model as i did.
See screenshots attached.
I hope you can check this and figure out what is wrong.
Thanks!
-
Does the plugin by any chance have an editor and renderer setting? The renderer should of course use the renderer setting, which might differ from what you're seeing in the viewport.
-
I see that you have a SDS surface inside. Could there be the conflict? Is it necessary?
-
The plugin doesn’t have any render settings and it does the same thing when its by itself with a simple cube for example.
-
The plugin doesn’t have any render settings and it does the same thing when its by itself with a simple cube for example.
What do you mean by "does the same thing"?
-
I mean it still doesn’t show the same model in the render window as i see in the model space.
-
What happens if you convert the object to geometry and render that? Does it still look weird? If so, can we have a look at the generated geometry?
-
The Subdivision Surface messes it up as i tested.
When i convert currents state to an object it converts it to the same wrong shape as shown on the render.
-
It only shows similar to the model when i redice polygon count to a certain %. Until than it shows the voronoi surface without the "Trypogen holes".
-
This looks like something is wrong with the plugin then... We can try to contact the original authors, but we cannot guarantee anything of course.
-
And it is completly random as you can see. I just copied the model (it is the same, with the same polygon reduction) and the renderer renders it differently.
-
This looks like something is wrong with the plugin then... We can try to contact the original authors, but we cannot guarantee anything of course.
Thanks...i though it is something with Corona, because the Standard renderer shows "exactly" the same as i see in the perspective view.
-
Anyways...it only happens when i use Subdivision inside the plug-in...I just won't use it inside the Trypogen tree.
Thank you for the kind replies.
Keep up the good work!
-
Anyways...it only happens when i use Subdivision inside the plug-in...I just won't use it inside the Trypogen tree.
Aha, that's what I didn't quite understand from your posts! In that case, just use the Trypogen subdivision. I just looked at their webpage and there's some built-in subdivision in there :-)
-
The plugin doesn’t have any render settings and it does the same thing when its by itself with a simple cube for example.
Then what does "Subdivision Renderer" right next to "Subdivision Editor" stand for?
-
The plugin doesn’t have any render settings and it does the same thing when its by itself with a simple cube for example.
Then what does "Subdivision Renderer" right next to "Subdivision Editor" stand for?
That does the thing. Thanks. All works fine. Sorry for the useless timeconsuming runs guys.
-
The plugin doesn’t have any render settings and it does the same thing when its by itself with a simple cube for example.
Then what does "Subdivision Renderer" right next to "Subdivision Editor" stand for?
That does the thing. Thanks. All works fine. Sorry for the useless timeconsuming runs guys.
Actually that was only one half of the thing...the other half was in Corona Preferences - "Use original Cinema 4D scene" checked in, and now all looks the same.
-
So Merk Vilson confirmed our suspition about the editor vs. renderer settings being the problem:
"[...] It is worth mentioning that the most common mistake is when user works only with Subdivision Editor and leaves Subdivision Renderer unchanged. Subdivision in trypogen is split into two parts. If he has subdivision renderer set to 0, it will not give the same results that he can see in the viewport. [...]"
But I am quite surprised that the "Use original Cinema 4D scene" setting makes a difference! It should only concern the material preview! If it does something else, that's a weird bug that you jsut uncovered.