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 - shane_w

Pages: 1 2 3 [4] 5 6 ... 9
46
[C4D] Resolved Bugs / Re: B1 r2 and TeamRender Problem
« on: 2018-01-16, 18:29:07 »
It seemed to process the passes differently but had no effect on performance.  Local time = 2:29    five clients = 3:21

Thanks,

-Shane

47
[C4D] Resolved Bugs / Re: B1 r2 and TeamRender Problem
« on: 2018-01-16, 15:31:52 »
Hi Nikola, yes the job was rendered using server and clients.  Here is a screenshot from the server.

Thanks,

-Shane

48
[C4D] Resolved Bugs / Re: B1 r2 and TeamRender Problem
« on: 2018-01-15, 22:05:13 »
Can you please change the "Render Settings -> Corona -> Team render -> Maximum size of packet" to some high value, e.g. 100 MB and tell me how Team rendering behaves after the change? I am also interested in console outputs from all Team render clients.
Thank you
Nikola

Hi Nikola, I tried your suggestion of increasing packet size to 100mb with no improvement.  Rendering local = 2:20,  rendering using TeamRender and five clients = 2:50.  I could not figure out how to copy from the clients console so I included a screenshot from one client.

Thanks,

-Shane

49
[C4D] Resolved Bugs / Re: B1 r2 and TeamRender Problem
« on: 2018-01-15, 21:18:29 »

Regarding the single frame rendering, I tested how Cinema behaves when I start rendering of scene with one frame (using Cinema4D Physical renderer) from Team render server, and it distributes the single frame across multiple machines the same as Corona (actually we don't control this, Cinema simply calls the relevant functions which we implement in our rendering engine).


Dang Nikola you are right!  Thanks for looking into this.  I haven't used Cinema's render engine in ages I wonder when they changed this?  I am going to inquire with Maxon and see what they say about this.  I will try the "Maximum size of packet" suggestion and report back with my results.

Thanks,

-Shane

50
[C4D] Resolved Bugs / Re: B1 r2 and TeamRender Problem
« on: 2018-01-12, 17:55:44 »
I can confirm the issues BigAl3D is having.

Can the behavior when launching a single frame using TeamRender server be changed or provide a check box option?         TEAMRENDER MODE:    |  X  | USE SINGLE SERVER        |     | DISTRIBUTE TO ALL SEVRERS

Cinema's default behavior when launching a single frame using server is one machine will take the job and render the entire image.  I think Corona is trying to distribute the single frame across multiple machines.  I can see how this would be a feature, but in our workflow we rarely want this.  As we complete images we send them to the farm and would like a single machine to render a single image.

Our current work-around is to send two frames.  Out entire scene is in a keyframed null that hides everything for the second frame so it renders very quickly.  We then just delete the dummy frame.  This works but is quite a pain when launching many renderings.

Thanks,

-Shane

51
Here are some images.  In the side by side comparison you can see quite a difference.  A slight difference in the dark areas when the images are saved out.

52
You have to enable it in the preferences :) Developer / Debug mode :)


Can we please get the ability to turn off Shadow Terminator? [...]



It's something that needs to be fixed in the core, but you can tweak the settings of the terminator handling in the development settings. It should already be there in the current daily.

Just a sidenote: as always if you change anything in Development/Experimental stuff, you are on your own and anything can and will break! It is strongly discouraged to change the settings there to anything other than default settings!

I don't see this setting on the Mac?

I get the developer tab.   I have everything but Shadow Terminator?  It is completely missing....

Never mind.  I just updated to the newest build and it is now there.

53
You have to enable it in the preferences :) Developer / Debug mode :)


Can we please get the ability to turn off Shadow Terminator? [...]

It's something that needs to be fixed in the core, but you can tweak the settings of the terminator handling in the development settings. It should already be there in the current daily.

Just a sidenote: as always if you change anything in Development/Experimental stuff, you are on your own and anything can and will break! It is strongly discouraged to change the settings there to anything other than default settings!

I don't see this setting on the Mac?

I get the developer tab.   I have everything but Shadow Terminator?  It is completely missing....

54
Can we please get the ability to turn off Shadow Terminator? [...]

It's something that needs to be fixed in the core, but you can tweak the settings of the terminator handling in the development settings. It should already be there in the current daily.

Just a sidenote: as always if you change anything in Development/Experimental stuff, you are on your own and anything can and will break! It is strongly discouraged to change the settings there to anything other than default settings!

I don't see this setting on the Mac?

55
I can confirm.  This little bug has been present for a long time.

-Shane

56
[C4D] Resolved Bugs / Re: Crash before rendering starts
« on: 2017-11-09, 19:26:47 »
I haven't noticed it in the latest build.  Everything seems to run much more stable.

Thanks,

-Shane

57
I keep having a weird bug we're upon doing a undo command the texture preview in the viewport goes blank and I essentially get a wireframe view. This has happened several times to me and different case scenarios when playing around with different noise shaders and layers shaders.

- Shawn

i have the same problem, i reported it few posts back not sure if got noticed or not, this start to happen from the last 3 builds i think, the solution i found for the materials to appear is to select and unselect something in the material editor, like the difusion slot or something. anyway seems a bug yeah!

Same thing here, I use the same workaround.  An easy way to reproduce the problem is paste a material from another scene.

58
[C4D] General Discussion / Re: Viewport
« on: 2017-10-13, 16:01:36 »
I have this issue pasting from one scene to another.  If I make any change to the material like checking then unchecking volume it will re-appear in the viewport.

59
Yep, big thumbs up to the devs. I used the latest version this afternoon for a couple of hrs without a single crash. Plenty of playing with geometry, variation shader, uv editing, etc and it was flawless and really fun using the IR.

I've found a bug I haven't seen elsewhere but might have missed it.

The environment tab in settings with the overrides for background, etc doesn't work when using the IR. Still seems to work fine when doing a final render as before.

Well looking forward to the next build.

Something to add on to this.  Global material override does not work correctly on objects that use selection tags.

60
[C4D] Resolved Bugs / Crash before rendering starts
« on: 2017-10-10, 22:48:32 »
I have been getting this crash a lot.  It happens just before the renderings starts, seem to only happen after rendering a few times.  This is not using interactive rendering.  Crash reports included.

Mac OS X 10.12.6
Cinema R19
 

Pages: 1 2 3 [4] 5 6 ... 9