Chaos Corona for 3ds Max > [Max] Resolved Bugs

Corona Distance Map not updating when rendering a sequence.

(1/2) > >>

rozpustelnik:
I have found a bug in Corona 8 for 3ds max 2015.
When rendering a sequence of files (by setting the Active Time Segment or Range or Frames in Render Setup) and the object affecting the corona distance map is moving - the renderer only registers the initial position of moving object and doesn't update it in corona distance map on the next frames.
It works only when manually selecting the next frame and starting the renderer again with setting the time output as "single".
I know the next version is dropping the support for 2014, 2015, but please provide the hotfix still having the support for mentioned max'es.

rowmanns:
Hi,

Reporting the bug in multiple places doesn't help, in fact it can slow us down.

We will investigate, would you be able to provide an example scene?

Thanks,

Rowan

rozpustelnik:
Yes, sorry for multiple places, can You delete the post in Daily Builds forum?
I'll try to share the scene tonight.

rowmanns:
Hi,

Thanks, I just managed to reproduce it also in max 2022 in a simple scene. However an extra scene always helps :)

Cheers,

Rowan

(Internal ID=908970704)

rozpustelnik:
Hi

I'm sending the scene.

Run rendering - Time Output is set to RANGE (or Active Time Segment or Frames) from 0 to 10, observe corona VFB in alpha mode.
The goal: distance map should update from frame to frame accordingly to changing positions of Target1 and Target2.
The result: distance map is calculated for the first frame only and isn't re-calculating the changed position of node inputs in following frames.

Affected material name: "shadow"

Thanks,
TT

Navigation

[0] Message Index

[#] Next page