Messages

31

[C4D] Resolved Bugs / Re: ACES OT Settings ignored by Teamrender Server

« on: 2023-02-09, 15:34:22 »

What happens if you delete the ACES OT operator? (Not saying the situation you report shouldn't be investigated, just wondering if this provides a workaround for now).

Yep, you where right. If the whole operator is deleted it works. But you have to delete it in the corona vfb to really delete it. If you just delete it in the rendersettings and you a corona camera tag it is still there.
So i opened the corona vfb, deleted the operator there and then it was also gone in the camera tag's settings.

I recognized that this maybe fixed in the newest CR10 daily:

"- Fixed problem with tone mapping from camera not being applied when rendering via Render Server"

Unfortunatly since i am employed in a bigger company, its not so easy to test as before where i was the CGI one man show in my old company ;)

Greetings,
Moritz

32

[C4D] Resolved Bugs / Re: ACES OT Settings ignored by Teamrender Server

« on: 2023-02-09, 15:22:44 »

Yeah, just as i posted this, i thought about that.
I'll test it and let you know.

33

[C4D] Resolved Bugs / [RESOLVED] ACES OT Settings ignored by Teamrender Server

« on: 2023-02-09, 08:46:40 »

Good Morning!

Since the ACES OT setting was implemented in CR9 we have a problem with our renderfarm. The Renderserver seems to render with ACES OT always on. Even when we uncheck it in the VFB, Camera Tag, etc.
We have one Computer, running cinema's team render Server and two computers running the teamrender clients. All of them are running under windows with the latest cinema/corona Versions.
I'll attach a comparison image and also the cinema project for your convenience (Maybe change the light material to another HDR file, sincethe one i used is too big for upload ;) ). Just render it locally and on a farm. ACES OT should be switched off.

Greetings,
Moritz

34

[C4D] Resolved Bugs / Re: Corona Plugin Crashes

« on: 2022-11-15, 11:04:16 »

Hey all,

thank you for all your help. With corona 8 now, everything works fine.
Even our renderserver is way more stable now.

Again, thank you all for your great support!


Greetings,
Moritz

35

[C4D] Resolved Bugs / Re: Corona Plugin Crashes

« on: 2022-08-30, 16:18:02 »

Hey Bengamin,

thank you for your answer. And also sorry for the late reply ;)
Upgrade to Corona 8 is planned for mid september.
I'll keep you updated if that will solve my issue.

Greetings,
Moritz

36

[C4D] Resolved Bugs / Corona Plugin Crashes

« on: 2022-08-16, 15:36:12 »

Hey There!

I know the thread-title is not very clear, but i don't know what else to write there ;)
So I have a Scene which is crashing all the time when i hit render. Unfortunatly I can't send you the scene-file, but maybe you can take a look at the bug (attached) report to give me some clue what could probably be the cause for these crashes.

My System:

CPU: AMD Ryzen Threadripper 3960X 24-Core
RAM: 64GB @3200MHz
GPU: NVIDIA GeForce RTC 2060
OS: Windows 10
Corona version: 7 hotfix 2
Cinema version: R25.117 Cinema 4D

I hope you can give me a hint, since i'm running out of Ideas.

Greetings,
Moritz

37

Work in Progress/Tests / Coffee

« on: 2022-05-25, 17:12:20 »

A little spretime project. just need something to fill the empty space back left :)

38

[C4D] Feature Requests / Disable Render Region in Render Settings

« on: 2022-02-08, 09:57:37 »

Hey!

Since I experience this more and more while rendering on our renderfarm, here is a (hopefully small) request:

As right now, render region can only be disabled/removed in the corona VFB. Would it be possible to integrate a checkbox or something in the rendersettings itseslf, with wich one can simply disable render region (RR)?

The reason for my request is, that i don't see if RR is enabled or not, without opening the corona VFB and start rendering. Since i use our internal renderfarm with the maxon team render server, I set my rendersettings as usual and upload the c4d file to the server. When i used RR before for some local testrenderings and forgot to disable it again, the renderserver will take it into account.
This is pretty annoying, especially on very big renders because with the renderserver i don't see the result until the render has finished.

I hope my request makes any sense. If you have any questions, don't hesitate to ask ;)

Greetings,
Moritz

39

[C4D] I need help! / Re: Team render SERVER problem

« on: 2021-07-12, 11:09:55 »

I only had this problem when using the "Photographic Exposure" feature in combination with a corona camera tag. That only worked when you manually copy the settings (iso, exposure, shutter speed, etc) from the camera tag to the main corona render settings.

40

[C4D] General Discussion / Re: Opacity texture in viewport

« on: 2021-07-12, 08:49:34 »

Hi,

from my understanding, corona utilizes the Diffuse channel to be displayed in the viewport. what i do is cpoying the opacity texture to the diffuse channel for placement. after that i simply set the mix strenght to 0% or delete the texture in diffuse. Not sure if you have to deactivate the opacity channel while placing your decal though.

Not the smoothest way of doing it but i see no other solution right now.

Maybe this helps ;)

Greetings,
Moritz

41

[C4D] Bug Reporting / Re: Render server (web client) crashes when launching multiple jobs with 1 frame

« on: 2021-05-03, 08:54:36 »

Hey JPeters!

Just stumbled over this post. I recently revived your old post with that problem. The Problem is solved with the v6 hotfix 2.

Here's the link to your old bug report:

https://forum.corona-renderer.com/index.php?topic=30041.0


I also maybe have a solution there with your problem regarding different results in the rendering.
Hope this helps a bit ;)

Have a nice day!

Greetings,
Moritz

42

[C4D] Bug Reporting / Re: Team Render server crashing when rendering 1 frame on multiple clients

« on: 2021-04-30, 17:11:44 »

Ok, for the second issue i found something out. It seems that the Settings for Photographic exposure are not really linked between the corona camera tag and the actual render settings. In my scene i had photographic exposure ticked on in the camera tag but these settings (exposure, iso, f-stop, etc) where completely ignored by the teamrender server / temarender clients. I had to manually set the same settings in the global rendersettings although they where already set in the camera tag and the little icon behind every box says that these settings got overwritten by the camera tag. In my opinion this is pretty dangerous and tideous especially if you have more than one camera in a scene and you always have to set the exposure settings manually in global rendersettings again.

Nevertheless, have a nice weekend! ;)

Greetings,
Moritz

43

[C4D] Bug Reporting / Re: Team Render server crashing when rendering 1 frame on multiple clients

« on: 2021-04-29, 11:01:23 »

Hi Tom & Jan,

we tested it and it works almost fine. Two things though:

1. Let's say i have two render clients and one job rendering on both clients and one job is in queue. If One of the clients is done faster than the other, it immediatly grabs the next job in queue and starts to render, which is fine. But when the other client is done rendering the first job it won't start rendering the next job wich is already started by the other client. It just stays on idle and the second job is only rendered by the one client which grabbed it right away.

2. I'm not sure if there's already a thread about this. But the render results are quite different compared to when i render the same job on my local machine. The result from the render server looks pretty overexposed and seems to be way more saturated compared to the local machine render. See attached screenshot. I did another test where i put all used image textures in the corona bitmap shader, but the result is the same. I Uploaded my test scene via dropbox. The filename is "showreel_wall_04.zip"

Thanks for your support!

Greetings from Germany,

Moritz

Edit: All Computers involved are PCs with windows 10.

44

[C4D] Bug Reporting / Re: Team Render server crashing when rendering 1 frame on multiple clients

« on: 2021-04-28, 17:16:14 »

Damn, that was fast :D

Allright, as soon as we tested, I'll get back to you.

Thank you!

45

[C4D] Bug Reporting / Re: Team Render server crashing when rendering 1 frame on multiple clients

« on: 2021-04-28, 15:39:23 »

Hi Tom,

I'd like to revive this thread since we are setting up a render server right now and have the same problems with the crashing clients when starting two jobs right away. When using cinema's standard render the second job queues as expected when started. Seems like corona is starting the second job right away. Is there anything we can do to prevent this issue, other than wait until a job finishes and then start the next one?
Would be really great to have the queueing working, since it is pretty complicated to always communicate with all users and also as jpeters mentioned, after the client crashes, the actually running job is marked as finished without any output.

Thanks in advance!

Greetings from germany,

Moritz