Messages

496

[C4D] General Discussion / Does Corona allow a "reflection coating layer" now in layered mtl?

« on: 2019-06-18, 11:38:46 »

hi

i wonder if Corona now in v4 allows for a coating reflection layer in the layered material?
so far i still see only a simple mask or slider for mixing one mtl with the others.

but it seem impossible to create some added reflection layer, like a clear painted wood or concrete etc

does this not work on corona or do i have to think this different?

thanks for help, i hope there is a way?

we try to port some materials from our vray libs to make them also for corona,
but the c4d corona mtl yet has some limits yet with layering materials maybe?

in v-ray the mtl opacity lets the mtl shine through to see the material below in blend shader, which is the expected result.
in (c4d) corona the base material gets also transparent, so an unwanted weird "mixed" material that is half transparent instead of layered/coated is the result.

thanks for help!:)
Stefan

p.s the more i try i guess this might be a bug? in case move the thread pls to bug section:)

497

[C4D] Feature Requests / Re: Corona for C4D glossiness mix strength feature in reflection channel

« on: 2019-05-08, 15:13:03 »

yes please,
that would be great for more or less every texture slot (as in vray or in max vray/corona)

498

[C4D] Feature Requests / Re: Support for several UVW-Tags

« on: 2019-05-08, 15:12:13 »

super important yes, pls +1

499

[C4D] General Discussion / Re: Render nodes on c4d prime

« on: 2019-03-21, 19:00:25 »

"Team Render is not an option for me.. too slow, to buggy, "

>>same for me....

500

[C4D] General Discussion / Re: SOLVED ---- TeamRender error "Aborting synchronization: dumpExr failed"

« on: 2019-01-28, 14:48:55 »

gr8 thx! :)

i test it this week asap

501

[C4D] General Discussion / Re: SOLVED ---- TeamRender error "Aborting synchronization: dumpExr failed"

« on: 2019-01-26, 09:31:07 »

i see what happens next week in office:)
if it happens again i tell you.

great would be if the teamrender lic woudl be more flexible and realisze the lic server is running:)

thx!
Stefan

502

[C4D] General Discussion / Re: SOLVED ---- TeamRender error "Aborting synchronization: dumpExr failed"

« on: 2019-01-23, 19:57:30 »

ok after restarting ALL machines, incluning the local one with server, it seems to work now.

but that seems a quite "unstable" or dangerous setup yet, if the nodes for some reason not want to connect to server they can reconnect to it, i hope this can be fixed. if it re appears again i post it here.

503

[C4D] General Discussion / Re: SOLVED ---- TeamRender error "Aborting synchronization: dumpExr failed"

« on: 2019-01-23, 19:50:39 »

yes  full and legal licenses i have from render legion.

i added now a 4th node now to test, this also refuses to work. so from 4 nodes 2 cant render:/

corona lic server runs of course as it runs local and on 2 of the 4 nodes,
all 4 have internet connection and connection to the main machine where the lic server runs.

lic server runs before i installed and started the nodes. i installed all 4 today, all in same way, 2 refuse to work, the others are ok.
some seems wrong yet sadly in TR....

the same nodes runs fine in other renderers or c4d internal. so it seems some corona specific.

504

[C4D] General Discussion / Re: SOLVED ---- TeamRender error "Aborting synchronization: dumpExr failed"

« on: 2019-01-23, 19:04:48 »

i do get the same error, "Aborting synchronization: dumpExr failed..."" on one node of several machines in same network.
it has internet and works fine with other engines.

i use the latest v3 hotfix.

any idea how to fix this?
i tried manual and automatic TR settings in corona settings both make the same issue

THX for help!
stefan

p.s the hack above with the txt file placed in corona hidden folder didnt help

505

[C4D] Feature Requests / Re: corona lights seen as lights by c4d

« on: 2019-01-10, 11:54:09 »

+1

it is a big drawback for our use for several use that corona lights are no c4d lights too (like control lights via mograph effectors p.e for things like media facades, or use in light listers)

506

[C4D] Feature Requests / Re: Support for several UVW-Tags

« on: 2019-01-10, 11:52:37 »

it would be great to support UV channels, so each shader can use its own UV by choosing the according channel.
as in max possible or also c4d vray;)

507

[C4D] Feature Requests / Re: Node improvements | Additional Node Shaders

« on: 2019-01-10, 11:51:20 »

yes +1 for me too to the above:)

508

[C4D] General Discussion / Re: Corona & Team render

« on: 2019-01-10, 11:37:47 »

actually most did work with vray dr, and a lot more things that not work on TR.
only the internal c4d shaders cant run on v-ray standalone, which i for example not are fond to use anyway as most are inferior to my use.

anyway we obviously seem not to need the same things for the work, which isnt a problem i guess.
i also not asked to replace TR but to add DR as options, for pro users. so i guess no worries, i am sure tr will stay:)

509

[C4D] General Discussion / Re: Corona & Team render

« on: 2019-01-09, 11:08:16 »

you not see the image, only after long time small stripes on bottom, via a real Dr you see after seconds the full image. on teamrender you wait hours on big images until you see all.
on comparence to a real DR system it is quite slower also in total, i assume the TR system has more overhead, in the way maxon designed it.(being separate renders just stiched together in PV)

certain particle and motionblur things, randomisation tools/shaders, etc or other dynamic effects not work via TR without extra caching or baking. this is as c4d in effects splits the render in parts, using copies of the c4d file, not the original data on each node, and then composes this parts together in the PV. this kills many features, same as it does in c4d internal renderers.

TR also often decides to stop or never finish, on an 8 or 10k image this is very bad finding our after hours it wont finish ok. (see cg talk for the many errors users have with TR, in any renderer, this is not corona specific, so they also cant do much about it)
a real dr system, like corona render normally has natively, can add nodes while rendering and also release nodes without affecting the final result. you always get a good render.

a standalone system seems to use a lot less ram here and rendering faster than the renderer inside c4d. here we see almost the double ram with c4d than on a pure standalone.

we also miss corona features(in shaders p.e or volume features) that max corona has, to make corona only with thew limited c4d shaders, and not offering both we feel is a shortcoming, and artificial limitation, that hopefully will get overcome in future updates.

510

[C4D] General Discussion / Re: Corona & Team render

« on: 2019-01-09, 10:54:08 »

"Teamrender over something like a VRay DR equivalent. "

it really shoudl have both.
we do big archviz and design projects and teamrender is unusable for that and very bad workflow, in my opinion. TR is a severe bottleneck.
it cant be used for proper speed related workflows where you need to see a progressive result immediate, and often it hangs at all, among many other TR typical issues(a lot of things need to be extra backed or chached to render ok on several TR machines), which a DR system not has.

if both ways exist, users can choose them.
some like you are happy with TR, but others not at all.

i mean a real DR like also corona on max has, with also all corona shaders that exist on max corona.