Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - devotikuenne

Pages: [1]
I'm not sure if this is a Daily Build Problem.

I have just realized that the materials shown in the Cosmos Browser in the internet ( contain a lot more materials than in my cosmos browser which I start from within C4D.

I guess there's still a lot of materials only available for vray? If so are you going to make them available also for Corona/C4D?



I encounter a problem when installing the package on my mac. At first everythning seems to work well. I get asked where to install and for which C4D-Versions I want to install the plugin. After confirmation the installation starts but after a while I get an error saying that an error has ocurred and that I shall contact the software developer.

I already tried to re-download the installer. But still the same error.

I work on a Mac Pro running MacOS 12.6

I can only provide a German Screenshot of the error message (attached).

Hope you can help me.

[C4D] Daily Builds / Compatibility to C4D 2023
« on: 2022-09-09, 17:10:50 »
Do I guess right that you are working on the compatibility to the recent C4D-version 2023?

At least the installer doesn't recognize the newly installed C4D version when I install the plugin.
Though I haven't yet  tried just copying the plugin-directory to the new c4D-versions plugin-folder.


I have a strange behaviour which I cannot explain to myself:
I have made a simple Animation of sweep nurbs (circle along a spline) which grow with increasing time. There are two sweeps: one with a smaller circle which runs a little bit ahead. This one has a simple Corona Physical Material, light blue with a 50% opacity. The other one has a little larger circle and runs a little bit behind the other one. This ha a light material with animated emission and animated opacity.

Now on my 475 frame animation there are some frames on which the light material behaves diffenrently and I cannot say why. On some frames the rendered light material seems to have less opacity and then on the next frame it is normal again. Definitely on these frames there is no animated keyframe or anything similar. This results in the animation to flicker on some frames. Strange is, that its seems to affect only some of the Sweeps on different frames. I have put  different sweeps in one group and habve assigned the material to the group. So I would think that all sweeps should act the same and have the "flickering" on the same frame. But it's not so.

I have attached an example where there are three consecutive frames. On frame 322 everything is fine, on frame 323 one can see that through the light material you recognize the thinner sweep, on frame 324 everything is fine again.

When I copy those two sweeps into a new C4D-file it's still the same: on frame 322 and 324 everything is fine, on frame 323 the inner sweep shines through.

I also have attached those two C4D-scenes.

I use Corona Renderer Version 8 Daily Build RC 3, but didn't check if on Version 7 it's also like that.
Rendered it on Cinema 4D R25 117

Would be happy if someone could help.



When importing a 3D-model from Chaos Cosmos the default place in which the proxy file is stored, is the user folder.
As my user folder contains a mutated vowel ("ö") it seems that this is not supported. In C4D (on windows) in the URI of the file the "ö" is substituted by "ᅢᄊ", so the link doesn't work.
Seems that ö is not supported by default. I can change it manually to make the link work.


I'm rendering an animation containing Bloom and Glare.
The animation is 300 frames long. After rendering I noticed that not in all images the bloom and glare is visible. So I have to render all the single frames once again. In most cases the bloom and glare on these re-rendered images can be seen. I output single EXR-images (no multipass-image).
I'm not sure if this is related to the daily build.

I'm using the daily build 2022-01-07 on C4D R25.117 on Windows 10



I have the following issue:

I downloaded i. e. the following material from the corona materials Website:

Obviously this material has been made with a prior version of corona. In the bump channel there is a "corona shared" texture loaded (showing only black!). When I now click on "select shader" Cinema 4D crashes.

I tried this with R21, S22 and R23 using the daily build 7 of corona renderer 6 on Mac OS 10.14.6.

When I open the Material in Node editor the corona shared texture isn't shown at all.
Actually I must admit that I don't quite know what this corona shared shader is good for. Obviously not all used textures are loaded properly…

I just checked: same problem if I try this on a whole new corona material which I created from scratch…

Hey guys,
as already stated by stereoV in this post:

there still seem to be a problem relinking textures using the asset inspector. This seems to be only a problem with textures inside of Corona Materials.
Is this problem known? Is there already a solution?



Pages: [1]