Messages

31

[C4D] General Discussion / Re: RoundEdges shader

« on: 2019-01-11, 00:08:33 »

in this video it looks certainly way better...
is there something wrong in the setup?

i scaled all down, 20x20x20 cubes, with rounding 0.5, 1, 2cm
looks a bit better, but nowhere like in the video

for me it looks a bit like something is broken with the roundshader.

32

[C4D] General Discussion / Re: CXR saving in picture viewer support

« on: 2019-01-10, 23:39:40 »

i also hoped this would make it into the release...
perfection would be if renderfarms like rebus would be able to deliver cxr files

33

[C4D] Daily Builds / Re: Corona Renderer 3 for Cinema 4D daily build

« on: 2019-01-10, 13:40:38 »

just wanted to report that the officially released v3 crashed here after 5min playing with the node editor/materials
just made 2 materials and connected some dots (shared shaders)
macos 10.12 sierra, cinema4d r19

did you guys experience crashes, too?

34

[C4D] General Discussion / Re: ** Yes It Does** New Corona = New User Manual?

« on: 2019-01-07, 19:49:37 »

+1

altough i dont expect one
every renderer has its oddities
corona doesnt like to do manuals :):)
(peace) :)

35

[C4D] General Discussion / Re: Corona won the render race...!

« on: 2019-01-02, 10:27:14 »

is there a discussion on their forum?
you have a link?

and yes, we'll see in summer/autumn if vrayforc4d has a comeback,
but by then a lot of users will have switched (to corona/redshift/octane/etc)
for me the future of vrayforc4d is not very clear..

well.. hope we get a "final" corona soon

36

[C4D] General Discussion / Re: Corona won the render race...!

« on: 2019-01-01, 12:50:00 »

i wonder where vrayforc4d is going now.
i'm pretty sure chaosgroup needs to fix/rewrite a lot of the code and
i wouldn't be surprised if there won't be an update for a longer time,
with huge changes somewhen later in 2019.

corona development hasn't been as fast as i hoped and i stopped working with
it in last summer. i'll give it a try again when there is finally a release.

37

[C4D] General Discussion / Re: Corona won the render race...!

« on: 2018-12-29, 20:06:41 »

in my experience such tests give just a limited view of the reality.
to decide for a renderer also depends strongly on what you do.
for motion graphic clips you probably choose octane or redshift,
if you do complex interiors maybe vray or corona.
and next to the rendertime and quality there are also other
aspects like how well and bug free it is integrated in the host app
or simply how likely it is that this software still exists in 5 yrs.

38

[Max] Corona Goodies - User Contributions / Re: HDRi rig for corona

« on: 2018-09-21, 09:32:33 »

what is "Cyc" ?

39

[C4D] General Discussion / Re: Filmic Blender

« on: 2018-09-17, 21:08:14 »

yes tx,
i already got it from another place that a lot of things are wrong in this video
well, maybe still good the thread is here for the c4d guys who dont know it, yet.
best, index

40

[C4D] General Discussion / Filmic Blender

« on: 2018-09-15, 10:45:42 »

hi,

i stumbled on this interesting video:

https://sobotka.github.io/filmic-blender/

wonder if this does apply in any way to corona too...
anyone with thoughts on this?

:)index


ps. the subject was discussed here, too (for octane)
https://render.otoy.com/forum/viewtopic.php?f=9&t=59738

41

[C4D] General Discussion / Re: Using Rebus Render Farm...

« on: 2018-09-15, 09:29:10 »

rebus has B1 installed
it works fine, i used it quite a lot.

my projects are a few weeks back, so you could check with rebus,
but i'm sure they didn't install any B2 alphas.

which leads to the question where we are in the roadmap...
B2 seems to take way longer than anticipated :/

42

[C4D] Feature Requests / corona shared problem

« on: 2018-09-09, 20:51:47 »

hi,

this is not a bug but a gui problem in my view...

if you work in the normal mat editor
and you instance a shader by using a corona shared shader in another slot
then the original shader also gets a corona shared as parent shader

i understand the concept that there is no source and target,
but both slots now share the same source

the problem is that
1. you cant select and copy/paste the original shader anymore (to copy it to another place without instancing it)
2. you cant unlink the connection if you dont want it anymore

at least there should be an unlink button which removes the corona shared shader
and puts the original shader back in the slot.

how to handle the copy/paste problem i'm not sure

best, index

43

[C4D] Daily Builds / Re: Corona for Cinema 4D Beta 2 daily build

« on: 2018-08-28, 23:16:41 »

well i wait for a final corona beta2 installed on rebus, that will make my happy for some time O:-)

44

[C4D] Daily Builds / Re: Corona for Cinema 4D Beta 2 daily build

« on: 2018-08-27, 21:55:04 »

I was wondering - are you guys planning to set the new Trello for next versions of Corona for C4D? What about Corona 2.0, and so on?

corona 2.0 ??
we dont even have a finished beta2. if we are lucky the rc will get released in august,
but this still wont be the final beta2 (which was supposed to be released at the beginning of august, by the way)
so we are still weeks or months away from a final beta2 which will be production ready and installed on render farms.
by the way 1.0 is on the trello, release date tba.

45

[C4D] Daily Builds / Re: Corona for Cinema 4D Beta 2 daily build

« on: 2018-08-08, 22:31:05 »

Lol kind of surprised to find out this is not normal, since that's how it is in Max - the Slate editor is just another way of editing the same materials as the Compact editor, and is a "world view" of whatever you show in it.

BTW, for grouping things in the Corona Node editor, one option is to create separate views. Again, they aren't separate nodes or materials, just a blank canvas into which to drop whatever you are working on at the time. Not sure if that does the same thing you were thinking of, for wrapping up a group of materials into one node, or if you had something else in mind?

well yes, what is normal? :) :) it was just that all other node editors in c4d renderers i know work per material. but your concept is welcome ofc, it offers cool possibilities!

what i mean by grouping is what you can do in xpresso as well (and also in the new c4d nodes):
group a setup of multiple nodes into a "master" node (with input/output slots) see the new uber material for r20, for example.
this could also be used to display one material as one node, which would maybe let u keep a bit more order
(i imagine 50 materials all with input multiple node chains... grouping would allow to keep things in order)

i didnt get what "create separate views" means, yet
... must play more :)