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

Pages: 1 ... 10 11 [12] 13
166
Ok, I will check it out. It seems to be gamma-related - can you write your LWF / colorprofile settings? Also, is the result correct when you set Gamma to 2.2 in PV / Filter tab?

As of missing frames in animation, this seems strange as animations are mostly handled directly by C4D (most of Corona-related TR work is because of single-image rendering). Do you have some specific scene where you have problems?

167
This should be fixed in A5 and A5.1 - it was related to similar problem with perfect sphere.

168
Sorry this bug remained there for so long - it is fixed in both A5 and A5.1.

169
[C4D] Resolved Bugs / Re: A5 Bug reports
« on: 2016-04-15, 18:35:17 »
To address other parts, colormapping was readded in A5.1 (but was moved from plugin menu directly into menu in picture viewer). As of infinite floor, it is unfortunatelly not supported at this moment (we have it in our feature requests). As of IR, I know it is not much stable at this moment, but we are working on it.

170
There was some discussion about wheter we should have this dialog or not. The result of discussion was readding dialog in A5.1, but moving it directly to menu in picture viewer.

171
[C4D] General Discussion / Re: A5 memory problem
« on: 2016-04-15, 18:26:39 »
Hi,
could you send me some more info about what renderings were you doing? I was not abble to reproduce it - I tried to render a lot of various scenes (from very simple scenes to some using 12GB of RAM) and let C4D open for 2 days but once I closed all documents, C4D was taking only 500MB - same amount of RAM it took after closing first scene.

172
There was a bug which caused TR not to correctly set color profile of rendered image (it was always saved in linear rgb). It should be fixed in A5.1.

173
Using Corona with TR should'n be any different from using it with C4D - simply setup render machines and hit "Team Render to Picture Viewer". If the renderer does not start on nodes, there are few things to check:
 1. (Obvious) Check you installed plugin on each of your nodes - Corona should print short message with info in log of TR client
 2. Check you have active licence on nodes - plugin won't show any activation window on nodes by default (to prevent problems with some automatization softwares), so you can either activate from full version of C4D or use Corona licence server (it is installed in plugin folder). Another way is described in https://coronarenderer.freshdesk.com/support/solutions/articles/5000618549-activating-corona-on-renderfarms-and-computers-without-3ds-max-gui.

If the plugin is both installed and activated and it still doesn't work, please let me know your C4D version and your specs.

174
We've re-added colormapping dialog in A5.1 (should be out today), we only moved command to open it directly into menu inside PV.
To those having problem with changing colormapping, dynamic colormapping works only when using global colormapping options, it won't change values inside active camera. If you want to change dynamic colormapping while you have active camera, you can check "Override camera colormapping" in render settings (you can do that also during rendering).

The reason for this behavior is that could be hard to determine where exactly should be colormapping modified when you change some value (e. g. when you change exposure, should it be stored in active camera? or should set colormapping override in render settings? etc).

175
[C4D] Resolved Bugs / Re: A5 Bug reports
« on: 2016-04-13, 16:01:07 »
Just to give you some update, problem with DOF is already fixed and the fix will be released in A5.1 within few days.

The problem was with synchronization of Focus Distance value - it uses stored value for scenes saved with previous versions (regardless of any changes in A5), and default value of 100 if you create new scene / new camera.

176
Another way of changing colormapping is directly in render settings - that will also change preview in PW (sorry we didn't mention this in changelog). As of the old dialog, the reason we removed it was there was quite a lot of places to edit colormapping, but I agree that when using PW, changing it in render settings is not ideal.
We will discuss about the GUI and possibility of adding the dialog back (there will probably be A5.1)...

177
[C4D] Resolved Feature Requests / Re: License Server
« on: 2016-03-09, 11:54:23 »
I added Licence server to installer for C4D version.
I plan to examine the possibility of integrating with C4D own license server during A6.

178
[C4D] General Discussion / Re: Some info about next alpha?
« on: 2016-01-27, 20:03:07 »
The problem with shaders is there is no way to know what exactly will be needed to evaluate before actual rendering, so the shaders are being continuously evaluated during rendering. The reason you can close current document without interrupting rendering is that C4D internally copies the scene, but it is still C4D representation with all its shaders. To allow DR without C4D on nodes, there are basically only three options what to do - we might

  1. reimplement/replace all shaders - this is already done with some shaders (e. g. Layer shader or Bitmap Shader), but reimplementing all shaders C4D has would take very long time and would be nearly impossible for some complex shaders.

  2. bake shaders before rendering - this would result in inaccuracies during rendering and wouldn't work at all with some specific shaders (e. g. some thirdparty shader similar to AO shader)

  3. support Corona shaders only - obviously the worst possibility...

I we decide to add support for DR without C4D on nodes, we would probably reimplement common C4D shaders where the baking wouldn't suffice and bake other shaders...

As of material editor and sharing materials between different software - this is possible when you use only Corona materials and shaders (and we will probably add support for this), the problem is when you connect any C4D materials, this is basically the same problem as with DR... you can only reimplement C4D shaders, bake them or not support them...

179
[C4D] General Discussion / Re: Some info about next alpha?
« on: 2016-01-27, 13:06:44 »
Hi,

here is a few notes to Team Render / DR support:

1. Right now, we are integrating distributed rendering with Team Render, but we also plan to implement Corona own DR (it won't be in A5 though)
2. With Team Render, there shouldn't be any limitation with shaders or features (everything that works in normal rendering should also work in TR).
3. Right now, even if we add our own DR, plugin will still be tied to C4D (many shaders are evaluated by C4D), meaning there wouldn't be any advantage in terms of C4D licensing. We have been talking about possibility to allow render nodes without C4D (i.e. use Corona standalone), but it would bring some limitations (some shaders would need to be baked etc..). Anyway, this is still in phase of discussion.

As of AO / other Corona shaders in OGL, I am working on some improvements to show something reasonable in viewport, e. g. in case of AO, it will simply show unoccluded shader (and will work even inside layer shader).

180
[C4D] General Discussion / Re: Alpha v4
« on: 2015-10-06, 03:36:58 »
Hello.
I have got a problem with v4. previous version works fine. When I start render, it just write "preparing scena data.." and no more. When I try stop render my c4d stop working and freeze.
C4D R15.008

Any solution?
Thx

Hi,
could you send me the problematic scene?

Cheers,
Aleš

Pages: 1 ... 10 11 [12] 13