Messages

226

[C4D] General Discussion / Re: Corona 3 Release License Question

« on: 2019-01-11, 17:17:25 »

Oh, quite the contrary actually! If you don't render the TR job on your workstation, you can still use it and even render on it in Corona.

Hi houska,
not sure I understand this correctly.
I have 1 Workstation and 3 render clients.
if I uncheck the WS (local machine) in the TR machine list and hit “TR to PV” only the 3 clients are rendering but the WS acts as server.
When I open another scene on this WS and try to open IR, I get the pop up “The external renderer is calculating an image. Do you want to stop it?”
What am I missing?

227

[C4D] General Discussion / Re: Corona 3 Release License Question

« on: 2019-01-11, 02:10:26 »

(so that you can continue to use it "full power" as a workstation since it won't be doing any rendering)

Sorry if this strays too far from the original licensing thread.

Just to clarify, you can't use IR / VFB on this "disconnected" workstation or the instanced  setup that nkilar mentioned, while the clients are rendering, correct?
So, "full power” is just for better viewport performance while setting up another scene?

If there is not the advantage to use another VFB instance on this machine, maybe a better choice is to leave it connected but reduce the “custom # of render threads” in prefs, if needed.

228

[C4D] Bug Reporting / Can’t open CXR in CIE 3

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

MacOS 10.13.6 / C4D Studio R18.057 / Corona 3.0 stable

Get “Unexpected attribute type” with any .cxr I try.
The last version that worked for me was Beta 2 stable.

229

[C4D] General Discussion / Re: RoundEdges shader

« on: 2019-01-08, 13:54:01 »

In my experience the default radius of 10 cm is way too large and gives you weird looking shading. Set radius to about 0.2 cm as a starting point.
Set your material preview to cube to see the effect without IR.

230

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

« on: 2019-01-07, 20:17:41 »

I  just realized that "CXR saving in picture viewer" disappeared from the trello board
I didn't yet install/activate my Corona 3 final, but wonder if it made it into this release.
It used to be on the roadmap for C 3, but now it's not mentioned anymore.

The ability to select CXR in render settings is such an important feature for users that send jobs to render farms and need to get a .cxr file back .

Edit:
Oh no, it didn't disappear, it was moved to the "big ideas" pile.... Sorry, missed that.
Does that mean it turned into a big "maybe not"?

Does anybody have an idea for a workaround if you need a .cxr file from a render farm?

231

[C4D] General Discussion / Re: Corona 3 Release

« on: 2019-01-07, 19:52:12 »

I also have a licensing question. 
I just bought C 3 but didn't yet activate it. Once i activate Corona 3, will I be able to go back to Beta 2 stable if I need to?

232

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

« on: 2019-01-02, 19:43:54 »

Hi houska,
thanks for testing.

I actually tried the scene that you are linking and could not get the result that you are sharing.

To clarify, you tested in corona 3 and adjusted the material to make the bump look like in B2 stable?
For me the bump in corona 3 looks like the phong tag gets ignored.
You don’t get that result? Do you use Windows or Mac?

May I ask how long you'll need the B2 version to work to finish your project?

Hard to say. It’s a new development project with the initial marketing images finished, but I’m expecting the client will need more images along the way till construction is finished.
Probably 3rd quarter 2019.
Everyone in archviz knows how painful it sometimes is, to get material approval from architects… Well, painfully slow… Once that’s done, you just pray that there it no more material tweaking necessary.
I don’t really expect you’ll support B2 for another year or so. That’s just the risk of early adoption.

Thanks for all your hard work.
Happy New Year!

Frank

233

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

« on: 2018-12-29, 18:59:25 »

MacOs 10.13.6 / C4D Studio R18.057/ Build timestamp: Dec 14 2018 17:27:33  Version: 3.0 daily Dec 14 2018 (core 3)

Hi,
not sure if you want us to report bugs for the daily here, or in “bug reports”

The new bump implementation looks and behaves completely different from B2 stable, and earlier.
To recreate: I used HFPatzi’s "Corona Teamrender Quality Issue" scene for testing.
https://forum.corona-renderer.com/index.php?action=dlattach;topic=22339.0;attach=94274
See screenshot 1

I’m fully aware that several forum members asked for a better / upgraded bump implementation, but I don’t think it’s a good idea to change something as fundamental as the new bump,  shortly before “hanging on to the B2 stable” might not be an option.

If the new bump makes it into the final release, please consider the option to license the B2 stable version for people that have projects in their pipeline and need additional time to update their materials.

Other things I noticed in the current daily…
In Team Render, rendering does not stop at set noise level or # of passes.
Does not show noise level / # of passes in VFB stats. See screenshot.
Render limits work on single machine rendering.

Corona Image Editor 3:
I get a “Unexpected attribute type” error when trying to open .cxr files.
CXR files saved in "B2 stable" or "B3 daily Dec 14 2018" will not open.

Thank you, and Happy New Year!!!
Frank

234

Gallery / Re: Beaver Lake [FULL CGI]

« on: 2018-12-17, 21:16:56 »

@jojorender

Thanks !
We wanted to respect renders sharing policy of this forum et do not make a promotional post and let only curious people get the whole scene :)

Oops, wasn't aware of this rule. My bad.

235

[C4D] Bug Reporting / Re: C4D Crash when closing Corona VFB too fast

« on: 2018-12-17, 20:56:37 »

MacOs 10.13.6 / Build timestamp: Oct 31 2018 17:24:08 / Version: B2 (core 3) / CINEMA 4D Studio R18.057

I  noticed when you click "cancel" in the "missing texture" dialog when starting a render, corona plugin & c4d crash. Might be related.

236

[C4D] Feature Requests / Re: RAM issue when using Team Render

« on: 2018-12-16, 22:40:16 »

MacOs 10.13.6 / Build timestamp: Oct 31 2018 17:24:08 / Version: B2 (core 3) / CINEMA 4D Studio R18.057

Hi,
I have the same ram issue as OP.
This happens every time when team rendering. The ram usage creeps up over time until it reaches, in this case 149GB!!, and C4D becomes unresponsive. (See screenshots)
I have about 650GB available space on my boot drive, but the swap file size must have a “hard” limit.
Not sure what role Apple’s mysterious “kernel_task” plays in all this.

No multi-passes used (I always render multi-passes separately)
Just 1 render client used, on 1 Gb LAN
2 identical machines with 64GB ram
No other major process running.
Around the same time the “low mem” warning pops up, the client always disconnects “greenlights” in machine list.  Uncheck/check brings the client back online and renders for a bit, till it disconnects again…

Could this be some kind of memory leak in Team Render? I was able to save a CXR before C4D crashed, rebooted, “Resume from file” and continued rendering the image.
The render finished at the set 3% noise level  while only using around 27GB of ram the whole time.
“Resume from file” renders only on the main machine, a “Team Render from file” option would be great, once Team Render becomes really “useable”.

For me, the growing ram issue happens with every scene I teamrender, but depending on image size the render might just finish before c4d crashes. 3000x2000 is on the safe side, but 4500x3000 is pushing it.

I’m currently in a bit of a deadline crunch, but I can prepare a scene w/ assets once I have some time, if that helps. I assume I need to strip out all plugins like Laubwerk etc before sending.

Maybe, if the C-Team creates a sticky post with a sample scene that users can download to test TR, with instructions of what you need to see, might even give you a better insight into what’s happening.

Nevertheless, it’s time to say Thank You! for all the wonderful work you guys did so far with corona.
Hope that these team render issues can be ironed out before final release.

All my best.
Frank

237

[C4D] General Discussion / Re: Your experience with teamrender

« on: 2018-12-16, 22:02:55 »

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.

238

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. 

239

[C4D] General Discussion / Re: Post Process Corona Renders From Render Farms

« on: 2018-12-08, 00:49:20 »

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.

240

[C4D] General Discussion / Re: Your experience with teamrender

« on: 2018-11-24, 00:20:03 »

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!