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

Pages: 1 ... 287 288 [289] 290 291 ... 409
4321
[Max] Resolved Bugs / Re: Vignette bug
« on: 2019-01-19, 21:53:55 »
Interesting! If you have the scene to share, we could take a look, may still be something that can be fixed. Cheers!

4322
BTW, rendering straight to a video format is never a good idea, best to render to PNG and then composite to video afterward. The two biggies are:

- If the machine crashes, the power goes out, etc., ALL of your render is lost when rendering to a video format and you have to render everything again from the beginning. With stills like PNG you can just pick up and continue where you left off
- Video compression is baked in at render time if rendering to a video format. If it turns out to be inadequate, you have to redo the render from the start. With rendering to stills, you can just redo the video encoding part of the process

Just as an fyi :)

4323
[Max] Resolved Bugs / Re: Vignette bug
« on: 2019-01-18, 20:57:54 »
Ok - if possible, could you test with a camera created natively in Max (preferably a Corona Camera), and also clearing the VFB between renders? Would be interested to know if either (or both in combination) made a difference. Thanks!

4324
[Max] Resolved Bugs / Re: Vignette bug
« on: 2019-01-18, 20:39:43 »
Unable to duplicate here, can you give more info?

Is it a Perspective view, max Camera, or Corona Camera? Is the Vignette set in the VFB, in the render settings, or in the camera? Is "Clear VFB between renders" checked or unchecked? Can you share one of the scenes (private uploader is available)?

Also, what render resolution for the final render?

4325
News / Corona Renderer 3 for Cinema 4D (Hotfix 1) released!
« on: 2019-01-18, 19:52:38 »
Corona Renderer 3 for Cinema 4D (Hotfix 1) released!

A few small but important fixes in this one:
  • Fixed the issue when Corona Image Editor showed "Unexpected attribute type." on macOS
  • Fixed broken licensing of Corona Image Editor in some cases
  • Fixed the black non-active multi-pass layers when saved from Picture Viewer during rendering
  • Fixed memory leak when rendering hair
  • Fixed memory leak in Team Render server
  • Animations rendered in Team Render can now be interrupted
  • Fixed rendering of Corona Light with IES in Team Render
  • Fixed a bug in the installer that was causing crashes in libwx_osx_cocoa.dylib

Download this latest version from https://corona-renderer.com/download

4326
Probably a strong argument for not using such a low value of MSI (which is not recommended - the default should be fine in most cases).

4327
PS - great Corona training available at https://corona-academy.com/ ;)

4328
Still not a good idea, for the reasons mentioned - in exceptional situations maybe this would be of use. If it was the right setting for most cases though, it would be what was in the default. As ever, the rule with Corona Renderer is "don't change the defaults, that we've carefully selected, unless you have a very specific reason for doing so" :)

4329
Chaos Corona for Blender / Re: Official Blender add-on
« on: 2019-01-17, 18:08:08 »
It has been dealt with, under "Why there won't be Corona for Blender..."
https://forum.corona-renderer.com/index.php?topic=792

Sorry.

There is the third party exporter though :) See https://forum.corona-renderer.com/index.php?board=28 for the Blender section of the forum.

4330
But you are sacrificing physical accuracy, and will get a darker image with less intense reflections and caustics. The defaults are in fact chosen for a very good reason, as the best balance between speed and realism :)

https://coronarenderer.freshdesk.com/support/solutions/articles/5000515636-what-is-max-sample-intensity-msi-

4331
[Max] I need help! / Re: VolumeGrid VDB file not loading
« on: 2019-01-17, 17:06:51 »
Shouldn't be, the only change in the daily builds relating to the CoronaVolumeGrid is "Fixed occasional flickering of CoronaVolumeGrid when using velocity-based motion mblur".

EDIT - here's what my statistics look like on loading, what does yours show?

4332
[C4D] Bug Reporting / Re: Layers are black
« on: 2019-01-17, 16:03:28 »
Known issue, was a change made to prevent IR flickering and slowdown, as a temporary measure until something more permanent could be done. Does not affect final render of course, as they are then updated at that point. Can't find the link at the moment :)

EDIT - here's one place it was reported and answered, though there was another too: https://forum.corona-renderer.com/index.php?topic=23095

4333
[Max] I need help! / Re: VolumeGrid VDB file not loading
« on: 2019-01-17, 15:38:02 »
Works for me, attached after some small tweaks just for appearance (changed to channel mapping, used autoscaling in the Channel color mapping, lowered the scale) Corona 4 Daily Build Jan 10th.

Which version of Corona are you using, btw?

4334
*** Is there a way to render several frames and save them all as CXR ?
Not at present, not automatically. You'd have to render, and save to CXR from the VFB, then do the next render. Since the CXR format isn't in the C4D save dialog, you can't set up a way that I can think of to render and save to that format automatically.

*** Also, When rendering several frames, I don't see any way\option to select a previous render in the VFB history and change some of it's attributes directly in the VFB
Any changes to tonemapping, post processing etc. will be applied when you save from the VFB history - so you could left click on the history to make it the "A" and bring it into visibility, adjust the tone mapping so you can see how it looks for that history version, and then use the disk icon "Save selected element of this snapshot to disk" below the image in history to save it (to a non-CXR format).

EDIT - as a note, for development of the Corona core we are looking at ways of having images with different post processing saved to the history; that is, the history would save the tone mapping for it too, to allow the same render with different post processing to be compared, which is not currently possible since the current tone mapping is applied to all history elements. So in the future, this last situation would change, but this would work for now :)

4335
For more info, is denoising being used? And if so, the NVIDIA one or our High Quality one, and what GPU and image resolution if the NVIDIA one? EDIT well I guess just NVIDIA since you are talking about IR :)

Pages: 1 ... 287 288 [289] 290 291 ... 409