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.


Messages - jojorender

Pages: 1 ... 16 17 [18]
256
Did you guys notice that these client disconnects happen right around the same time the "low memory" warning pops up?

I tried all settings 20s/150MB - 10s/50MB on a image 4500x3000 using only 1 client machine to rule out a network bottleneck.
Every setting i tried had disconnects. Not easy to test, since it always takes a while till it happens.

257
Gallery / Re: Beaver Lake [FULL CGI]
« on: 2018-12-09, 19:54:05 »
Really well done, great details.
Maybe a good idea to let people know that this whole scene is for sale on your site for a very reasonable price.
I was working on a lake house project 2 months ago and a scene like this would have been a HUGE time saver.
Unfortunately, I work in c4d and all your environment scenes are max only. 


258
If I get this thread right, there's no Cinema4D Corona-Version released for Renderfarms yet:

I have been using RANCH COMPUTING since Beta 1. They even had daily builds installed.
Their c4d plugin works pretty well. Just contact them to make sure you use the same corona version. 
https://www.ranchcomputing.com/en

According to the trello board, CXR saving support in PV is scheduled for v.3
Can somebody let me know if it's already in the current daily?
Thanks.

259
Ok, after rendering a new Project with 20s update interval and 200MB Packet size, it renders way faster.

Hi HFPatzi,
thanks for your feedback.
Can you tell us what you mean by “renders way faster”?
Is it now more like you expected? 10 clients a lot faster than the single i9 7940X
I had to look up speed and core count of the CPU’s you use.
i9 7940X  - 14 cores @ 4.3 GHz
i7 7700 - 4 cores @ 4.2 GHz x 8 = 32 cores + the Mac Pro’s (not sure about the specs)
I would also assume that (inc. overhead, LAN, etc) it should definitely be “a lot” faster than the single 14 core.

Questions for the dev team:
Do different CPU calculate pixels differently and maybe contribute to “noisier’ images?
How about a mix of PC’s and Mac’s in this regard?
Can you shine a little light on the manual TR settings and give us some “best practice” advise?   

Happy Black Friday everyone!

260
Not sure if this is related, but are all materials in your scene Corona materials?
If i have a c4d material in the scene, all clients disconnect but the main machine continues to render.

Are all plugins used, installed on all clients? In c4d preferences TR/ Client/ "Handle Warning As Error" disabled?

261
Thanks Tom,
same CPU, server 64GB, node 32GB ram. I monitored ram usage on node os level - only about 58MB (edit:) swap used.
Both machine benchmark around 4 min.

Test image size: 3000x2000
Tex folder 850MB. Does it make sense to copy project to "Local Repository Path"?
I usually render jobs to 4050x2700px, higher than that and I'm often running out of memory.
What would be better TR config settings for this image size?

262
[C4D] General Discussion / Your experience with teamrender
« on: 2018-11-07, 21:01:39 »
Hi,
I’m currently using Corona version: B2 on mac R18 on server and client.
I’m testing a scene that takes 39:28 min to render to noise level 5% on my main machine.
When adding 1 node in teamrender the render time goes to 29:29 min.
I didn’t expect render times to be cut in half, but definitely better than what I get.
Corona render settings “TR” is set to automatic. Network: wired 1 gigabit LAN.

I plan to use 1 corona license with 3 nodes (if that’s what we’ll get when released)
and send larger jobs that require faster turnaround / more compute power to a render farm. I only do still images.
If the LAN is a bottleneck, would upgrading to a 10 gigabit make sense?
I’m not even sure the gigabit is saturated as it is.

What’s your experience regarding TR?
Any tips on how to minimize overhead / get faster renderings?
How well do additional nodes scale?

Thanks.

263
Okay, so I have tested the file. At first, it didn't work, then I copied your ies to the Corona ies folder on both of my machines. And added it again in the light settings, directing it to Corona's ies folder. The second render worked.

Thanks for testing.
So, that means the TR client can't pull the .ies from the TR server machine like it does with image files in the tex folder. Is this a bug or a feature?
Not very intuitive if the ies file needs to be copied to every single TR machine by hand.
Maybe a note in the corona light ies section avoids confusion.

264
Still not working.
I'm on B2 rc 2 (core 3 (DailyBuild Oct 10 2018). Nothing related in changelogs till RC4
It must be how c4d handles relative paths in TR.
My workaround is to install the .ies file in every content browser.
Please check if attached scene works for you in TR.
Thanks.

265
Version: B2 daily May 30 2018 (core 2 DailyBuild May 30 2018) (same version on all nodes)
Cinema version: CINEMA 4D Studio R18.057
OS: Mac OSX 10.10.5

Hi all,
I'm using a IES file located in the "ies" folder, inside the project folder.
The IES renders fine when "render to picture viewer" on my main machine, but does not render when "team render to PV". Just the corona light renders without using the ies file.
I also tried the IES file placed in the "tex" folder (of course updated the path in corona light).
The ies only renders if the path looks like this "./filename.ies"  or "./ies/filename.ies"
If the dot in front is removed  "/filename.ies" or just "filename.ies" the light will not render.
I would assume with "filename.ies" c4d finds the file in the "tex" folder, but that's not the case.

It might be related to how c4d on mac os handles relative paths?

As a workaround I tried to use the UHD cache saved from "render to pv"
and load the file when using team render without success.
I looks like Corona still needs the ies file to calculate the light.

Can other mac c4d users confirm if ies lights work in team render.
Any ideas for a workaround?

Thank you.

Pages: 1 ... 16 17 [18]