Corona Renderer 6 for 3ds Max - Daily Builds Discussion

[1equals2]

Hey all,

Has anyone had any success rendering motion blur with tyflow? I set up a basic flow with raindrops and it crashes max right after the scene parsing.

TY Flow motion blur does not work here as well - 3ds max 2018.4 +Corona 5.  Crashes on parsing. I had high hopes on Corona 6 daily builds that it solves this.
If recall accurately someone submitted similar issue  onto chaosgroup forum - there is something related with velocity of particles when using triangle mesh.

I decided to check if there is a workaround  for rendering just motion blur out of the particles generated with TY Flow.
With Vray Next a simple scene works fairly well. Same scene with Corona - crashes at parsing.

 "Export particles to objects" within TY flow seems to help rendering motion blur with Corona. Have not messed around with all the available options there, but at least it renders without crash.

Can you guys send any example scene? https://corona-renderer.com/upload
In my quick tests it worked fine, but it probably depends on what exactly you are motion-blurring.

Uploaded scene via the provided link. Have not tested with Corona 6 latest builds.

[maru]

Uploaded scene via the provided link. Have not tested with Corona 6 latest builds.

It works fine here:
- Max 2020
- 16.04 V6 Corona daily
- TyFlow newest version (downloaded literally yesterday)

I rendered a few frames from the animation, no crashes.

[1equals2]

Uploaded scene via the provided link. Have not tested with Corona 6 latest builds.

It works fine here:
- Max 2020
- 16.04 V6 Corona daily
- TyFlow newest version (downloaded literally yesterday)

I rendered a few frames from the animation, no crashes.

Are You sure You are rendering the TYFlow, not the geometry generated . TYFlow has been disabled in rendering from object properties menu.
Tried once again with Corona V6 16.04 and latest TYFlow, but 3ds max 2018 - crashes persist.

[maru]

Uploaded scene via the provided link. Have not tested with Corona 6 latest builds.

It works fine here:
- Max 2020
- 16.04 V6 Corona daily
- TyFlow newest version (downloaded literally yesterday)

I rendered a few frames from the animation, no crashes.

Are You sure You are rendering the TYFlow, not the geometry generated . TYFlow has been disabled in rendering from object properties menu.
Tried once again with Corona V6 16.04 and latest TYFlow, but 3ds max 2018 - crashes persist.

Ah, ok, thanks for clarifying, I will try again!

[rowmanns]

Triplanar not working in the latest daily build.

Can you provide some example of it not working? It seems to be functioning correctly in my tests.

Thanks,

Rowan

[v.p.vlasenko]

Triplanar not working in the latest daily build.

Can you provide some example of it not working? It seems to be functioning correctly in my tests.

Thanks,

Rowan

Sorry guys - my mistake. Didn't find out true problem the first time.

It working but the problem occurs when uvw randomizer plugged into triplanar. Seems like existing mapping used instead of triplanar in such case.

Screenshots.
1. Latest daily - I can change mapping by UVW Xform or UVW map.
2. 03/16 daily - everything works as expected.

[annkos]

Hi guys i dont know if anyone else has that issue but in the vfb,  in the lightmix list the last one will reset itself to 1 every time i will reopen the scene. I have the issue in a lot of scenes not in just one scene etc.

[danio1011]

Hi guys i dont know if anyone else has that issue but in the vfb,  in the lightmix list the last one will reset itself to 1 every time i will reopen the scene. I have the issue in a lot of scenes not in just one scene etc.

Yes, I have noticed this too.  I thought it was just the ‘unassigned’ lightmix but it could just be the last in the list.

[rowmanns]

Triplanar not working in the latest daily build.

Can you provide some example of it not working? It seems to be functioning correctly in my tests.

Thanks,

Rowan

Sorry guys - my mistake. Didn't find out true problem the first time.

It working but the problem occurs when uvw randomizer plugged into triplanar. Seems like existing mapping used instead of triplanar in such case.

Screenshots.
1. Latest daily - I can change mapping by UVW Xform or UVW map.
2. 03/16 daily - everything works as expected.

Thanks,

We will investigate.

Rowan

(Internal ID=499287672)

EDIT:
I have just tested this and it is already fixed. It will be in the next DB which will be out soon.

Cheers,

Rowan

[Bormax]

Hi
DB 2020-04-16 max 2014
ShadowCatcher blurs backplate picture. Amount of blur depends on distance between camera and ShadowCatcher object. After some test found out that it caused by map filtering. If it's switched off in Max's Bitmap then backplate is not blurred. Solution for CoronaBitmap is to change Blur amount to 0.01

[romullus]

Yeah, but it has nothing to do with shadowcatcher, any texture that is mapped on a geometry would act like that.

[Flavius]

Hi, has something changed in the latest daily build regarding displacement and IR ?

The displacement seems NOT to be recalculated if I move the camera around, I have to restart the IR. Previously, moving the camera would make the displacement map to be calculated again.

I have only tried this with Phoenix Ocean Map though, but it wasn't the same in the previous versions.

Thanks!

[TomG]

If you are using screen space for displacement, then things that are out of the view are not displaced (or not displaced with as much fine detail), and moving the camera in IR does not recalculate this. With world space for displacement, everything is displaced equally whether in shot or not. Could be that you had one scene using screen, and another using world, and this is why you saw a difference?

[Flavius]

If you are using screen space for displacement, then things that are out of the view are not displaced (or not displaced with as much fine detail), and moving the camera in IR does not recalculate this. With world space for displacement, everything is displaced equally whether in shot or not. Could be that you had one scene using screen, and another using world, and this is why you saw a difference?

Hi there Tom,

Yes I am using screen space, but I am almost certain that in previous versions moving the camera would make corona recalculate the displacement to fit the new camera view, which would make sense I think? Well it's not big deal, I can switch to world space I guess or just restart the IR

EDIT: HOLY S**T at the new sky. Outstanding!!

[TomG]

Howdy! No, moving the camera in IR never caused displacement to be recalculated when set to screen space. Perhaps it's just more obvious in your current scene :) We actually use this to demo how screen space works, by starting IR, then moving the camera elsewhere, to show that displacement is done at increasingly less detail outside the initial view. Of course, it gets recalculated if you adjust the displacement settings though.

Glad you like the new sky model, got to admit it's awesome having been playing with it!