Messages

1

[C4D] Bug Reporting / Re: Teamrendering - Clients do not start next job in queue after some time

« on: 2025-03-11, 13:12:59 »

Hey bnji,

thank you for your reply. I submitted a support ticket with a test scene. Ticket number is: 355782.

And yes, this happens everytime we put several jobs in the queue. Most of the times, the first few jobs are working fine. Lets say, we have a queue with 10 jobs, then it mostly happens after job 6 or so.
Looks like one rendernode is failing at first and then one or two jobs later the next one stops working the queue.

Looking forward to hear from you!

Greetings,
Moritz

2

[C4D] Bug Reporting / Re: Teamrendering - Clients do not start next job in queue after some time

« on: 2025-03-10, 09:43:05 »

And on we go with this monologue. I just started some renders on our farm. Then i monitored the license server for a bit and it seems that the renderclients only aquire a license, when they have to render something. My assumption was, that as soon as the teamrender client software is started, it will keep a licesnse active for as long as it is running. But it looks like, when a renderjob is finished, the licenses on the clients are getting released. Even if there are more jobs in the renderqueue. Is there a way to give the renderclients some kind of permanent license or maybe another way to fix this?

Greetings,
Moritz

3

[C4D] Bug Reporting / Re: Teamrendering - Clients do not start next job in queue after some time

« on: 2025-03-04, 11:55:02 »

I guess i celebrated too early. While arbitrated mode seems to work fine with the regular image, there is a huge problem with the multipass image. Allthough, the job has rendered and finished correctly (Statusbar at 100% and green), the multipass result looks like it stopped somwhere in the initial pass (lots of black squares, etc...) and does not show the final image.

So after testing around with different versions of corona, we're now back to square one. Cinema 2025.0.2 and corona 12 hf2 seem to render correct results with manual mode, but the clients again are refusing to start the next job in the active queue after some time. Only solution for now is to restart the clients when this is happening. Thats not ideal, especially when rendering over the weekend.

Looking forward to hear from you!

Greetings,

Moritz

4

[C4D] Bug Reporting / Re: Teamrendering - Clients do not start next job in queue after some time

« on: 2025-02-24, 16:31:35 »

Hey,

over the weekend, I tested some different variations of the Teamrender Settings of corona (Document Rendersettings this is).
Looks like the problem that clients stop working the queue, is solved with the Arbitrated mode.

So in Arbitrated mode, all jobs of my test queue (10 jobs) have been rendered.
Unfortunatly, another problem appeared: As said, all jobs rendered and all jobs have a correct result.
Some jobs however have the Status "Am zusammensetzen", I am missing the correct translation in english here. But i think you can translate it with "assembling" maybe.
These jobs are also in the inactive queue and have render results.

According to the Logfiles, it seems that these jobs do get the "assembling successful" status, but right after that they again get the Status "assembling". Not sure what causes this, but it would be nice if it can get fixed somehow.


Here is a log where the status is set back to "assembling" after successful assembling it:

Code: [Select]

2025/02/24 15:20:19  Created 'Testjob_CR_arbitrated_TR_05s_250MB_09' by 'XXXXXXX'
2025/02/24 15:21:24  Eingereiht
2025/02/24 15:21:24  Started Job by User XXXXXXX
2025/02/24 15:21:24  Eingereiht
2025/02/24 15:21:24  Am Vorbereiten
2025/02/24 15:21:24  Am Vorbereiten
2025/02/24 15:21:25  Am Rendern
2025/02/24 15:21:31  RENDER-CLIENT01: Downloaded Asset(s) in 4.779 seconds
2025/02/24 15:21:31  RENDER-CLIENT02: Downloaded Asset(s) in 4.900 seconds
2025/02/24 15:21:32  RENDER-CLIENT03: Downloaded Asset(s) in 5.908 seconds
2025/02/24 15:21:33  RENDER-CLIENT01: Rendering frame 0 of job 'Testjob_CR_arbitrated_TR_05s_250MB_09'
2025/02/24 15:21:33  RENDER-CLIENT02: Rendering frame 0 of job 'Testjob_CR_arbitrated_TR_05s_250MB_09'
2025/02/24 15:21:34  RENDER-CLIENT03: Rendering frame 0 of job 'Testjob_CR_arbitrated_TR_05s_250MB_09'
2025/02/24 15:26:46  Am Zusammensetzen
2025/02/24 15:26:50  Rendern erfolgreich
2025/02/24 15:26:50  Zusammensetzen erfolgreich
2025/02/24 15:26:50  Am Zusammensetzen

And here is a log, where everything worked as it should and the status is set to "completed":

Code: [Select]

2025/02/24 15:17:27  Created 'Testjob_CR_arbitrated_TR_05s_250MB_10' by 'XXXXXX'
2025/02/24 15:21:24  Eingereiht
2025/02/24 15:21:24  Eingereiht
2025/02/24 15:21:24  Started Job by User XXXXXX
2025/02/24 15:21:25  Am Vorbereiten
2025/02/24 15:21:25  Am Vorbereiten
2025/02/24 15:21:27  Am Rendern
2025/02/24 15:26:58  RENDER-CLIENT02: Downloaded Asset(s) in 5.035 seconds
2025/02/24 15:26:59  RENDER-CLIENT01: Downloaded Asset(s) in 5.373 seconds
2025/02/24 15:26:59  RENDER-CLIENT03: Downloaded Asset(s) in 5.965 seconds
2025/02/24 15:27:00  RENDER-CLIENT02: Rendering frame 0 of job 'Testjob_CR_arbitrated_TR_05s_250MB_10'
2025/02/24 15:27:01  RENDER-CLIENT01: Rendering frame 0 of job 'Testjob_CR_arbitrated_TR_05s_250MB_10'
2025/02/24 15:27:01  RENDER-CLIENT03: Rendering frame 0 of job 'Testjob_CR_arbitrated_TR_05s_250MB_10'
2025/02/24 15:32:56  Am Zusammensetzen
2025/02/24 15:33:00  Rendern erfolgreich
2025/02/24 15:33:00  Am Zusammensetzen
2025/02/24 15:33:00  Zusammensetzen erfolgreich
If you need any further informations, just ask ;)

Greetings,
Moritz

5

[C4D] Bug Reporting / Re: VFB drop-down menu position on second monitor on WIN 11

« on: 2025-02-20, 11:50:48 »

Hey!

I've got the same problem. Both on my monitors at home and on the ones in the office. I am pretty sure it hast something to do with the scaling. On my main monitor i have 100% scaling and everything is fine. On the Secon one i have 125% scaling and the drop down is all over the place. Same as in the office.

6

[C4D] Bug Reporting / Teamrendering - Clients do not start next job in queue after some time

« on: 2025-02-20, 11:46:57 »

Hey there,

first of all, here are our Renderfarm Specs:

Teamrender Server Machine:

CPU: 32 x 2,4 GHz (I think its an intel, but not sure about that)
RAM: 512 GB
System: Windows 10
Teamrender Server and Corona are on the latest version. No other 3rd party plugins besides corona are installed.



Teamrender Clients (3x):

CPU: AMD Threadripper 24 x 4,0 GHz
RAM: 64 GB
System: Windows 11
Teamrender Client and Corona are on the latest version. No other 3rd party plugins besides corona are installed.


The Machines are all connected via a dedicated 10 Gigabit Switch.


Since quite some time now, we have problems with our renderfarm.
For example, i put 10 jobs (Still images) in the servers queue and start them all at once.

The first jobs are running fine and every client is participating. Then at some undefined time the clients dont start the nex job in the queue. In fact, not all clients stop at once. There might be one machine which switches to idle after completing a job and not starting the next one. Machines that turn idle, will stay there until you add and start a new renderjob. The jobs which are pending in the active Queue seem to be ignored. So after a few Jobs, no client machine is rendering anymore, status is idle and there are still jobs in the active queue with status pending. There is no error or warning in any log what so ever. It almost semms, that the clients don't see anymore jobs in the queue after turning idle. Only "Workaround" is to restart the clients software (i.e. via the Temarender Webinterface). Once restarted, the clients start immediatly with the next job in the queue. We will contact the maxon support parallel to this post. But i have some theories what could cause this issue:

While monitoring the Rendering process on the farm i saw, that one machine renders a bit slower than the other two. When the "faster" machines are done with their part, they directly start with the next job in the queue while the slower machine still renders the old job. When this machine has finished, it will also start on the job, the other machines already are rendering. Maybe at some point, the gap between the faster machines and the slower one is too big and the machine doesn't know where to continue. But on the other hand, the two faster machines also switch to idle eventually.

Another theory would be, that maybe the teamrender software counts a job a finished before denoising starts and therefore there will be an expanding gap between what the machine thinks means finished and when it is actually finished. This might also explain why the web interfaces progress bar goes over 100% (around 120% mostly).

Another point might be the different Windows versions. But AFAIK the Server-Machine can not be upgraded to win 11. Maybe there is a general problem with teamrendering on win11?

I'm not sure, if the Teamrender settings in the corona rendersettings could help solving this problem. With our old farm (same server machine, two older client machines) i figured out the values for fastest rendering (60s / 150MB). On our old Farm we didn't have the clients "idle" problem.

I hope, I explained our issue somewhat understandable ;)
If you have further questions, let me know!

Have a nice day!

Moritz

7

[C4D] Bug Reporting / Re: VFB 2.0 - Scroll through Passes Dropdown

« on: 2024-11-20, 10:21:20 »

If the VFB 2 in C4D is the same as in 3ds Max, then you have to click once on render elements dropdown before you can scroll through items with the mouse wheel. I agree with you that the old system was more convenient when you could scroll without additional click.

Hey romullus,

Thanks for the tip. just tried this. I click to open the dropdown and then scrollwheel down. Unfortunatly the menu just closes ;)

Oh, I Forgot to mention: I'm working on Win11, Corona 12 hf2 and Cinema 2025.0.2.

@John_Do You're right. The LUT-Menu works the same as before.

8

[C4D] Bug Reporting / VFB 2.0 - Scroll through Passes Dropdown

« on: 2024-11-20, 08:46:43 »

Hey there,

Not sure if this is intended or not. In the old Corona VFB, I was able to use my mousewheel to easily scroll through the passes in the passes dropdown menu.
I found this quite handy and used it all the time, since my focus could stay on the image while scolling through passes.

In the new VFB this "feature" isn't available anymore, plus the menu moved from top center to top right. So my eyes always have to move between the menu and the actual image wich is pretty tideous, especially on ultrawide screens.
Is there any way to get the old behaviour back?

Thank you!

Have a great day!

Moritz

9

[C4D] General Discussion / Re: Team Render machine not reachable

« on: 2024-11-13, 09:09:14 »

Hey petrue,

there's one thing that could cause this: Are you sure you are running on port 1? Unless you canged it, it should say something like: "192.168.1.204:5401"

Greetings,
Moritz

10

[C4D] General Discussion / Re: render region

« on: 2024-11-05, 16:14:11 »

Hey celmar,

Haven't tried cinema's render region but corona's render region works with team render.
I use it all the time.

Have a nice day,

Moritz

11

[C4D] Bug Reporting / Re: Keyframe Tone Mapping settings in camera tag

« on: 2024-10-30, 09:20:46 »

Hey bnji!

Thanks for your answer...and sorry for the delay ;)

Maybe then it will be best to remove the little Keyframe diamonds on this parameters, to avoid confusion, won't it?
(If this is the case with newer version of corona, ignore my suggestion ;) )

Have a great day!
Moritz

12

[C4D] General Discussion / Denoising on Renderfarm (With Team Render Server)

« on: 2024-10-30, 08:31:49 »

Hey There,

just out of interest: Can you tell me where the denoising on a renderfarm setup (1 Temrender Server Machine and several clients) is happening?

On a still image, does every client denoise their part or is denoising done on the Server Machine after all chunks are assembled back to one image?

Same question for animation renders: Is it happening on the client machines or on the server machine?

Thanks in advance!

Have a great day!
Moritz

13

[C4D] I need help! / Re: shadow has weird maps

« on: 2024-10-21, 10:47:38 »

Hey there,

you could also try to convert you psd to a different color profile. At least the one used in the multipass image (linear color profile or something) is kinda weird.

14

[C4D] Bug Reporting / Keyframe Tone Mapping settings in camera tag

« on: 2024-09-25, 09:14:06 »

Hey there!

A colleague of mine just tried to animate the exposure value in the corona camera tag. Turns out, that the only parameter you can keyframe are the enable and override. Even though there's the little keyframe-diamond in front of all settings.
I tested it on my machine => outcome is the same.

We both use cinema 2024.4.1 and corona 11 (hotfix 1). He's on a mac pro m1 and I am on a PC with windows 10.

Would be cool if you could take a look (maybe this is fixed in newer versions?)

In a new scene just drop a corona camera and try to keyframe said settings.

Thank you!

Greetings,
Moritz

15

[C4D] General Discussion / Re: Multilayer PSD with alpha

« on: 2024-04-29, 08:15:16 »

Hey there,

not sure if i understood correctly, but to save the alphachannel as actual channel and not as a layer, the "Alpha Cannel" checkbox under the regular image settings has to be ticked on even if you only save the multipass image.
See screenshot attached. Maybe this helps.

Greetings,
Moritz