Messages

1

[Max] I need help! / Re: CoronaMax2023.DLR and chaosScatter files take too long to load

« on: 2025-07-14, 22:43:19 »

Bumping this topic.

We on 3ds Max 2024 / Corona 12 Update 1 (Hotfix 1) and booting up a blank scene is super slow. The 2 main causes.

CoronaMax2024.dlr and ChaosScatterMax2024.dlt

Is there anyway to speed the process on these files?

Hi,

During v12 daily builds we have significantly improved the loading of Corona plugins. If they are significantly slower to load that other plugins during start up, then you probably need to check internet connection and/or license server, update it preferably. The slow loading of plugins may happen when e.g. Max is started sooner than license server is initiated, say after PC reboot.

2

[Max] I need help! / Re: 3ds Max ACES Color Managment

« on: 2025-07-11, 09:57:44 »

Hi,

When you update/edit a post, there is no notification of it in forums.
In case of important message/attachment, make sure you make it as a new post.
I will have a look soon.

Update: the link is expired. Please reupload it (with a new message in this thread).

3

[Max] General Discussion / Re: Path Tracing always as Secondary GI Solver

« on: 2025-07-09, 15:47:37 »

As it is said, Corona is (un)biased renderer, MSI being one of the main biasing factors. You can see crazy-beautiful things happening with caustics when there is no MSI and there are strong reflective surfaces (keep in mind long render times). I remember forgetting to set render limit for a volumetric caustics scene, and with >1000 passes rendered, beautiful caustics appeared, in places I would not think of them appearing.
I agree that with firefly removal MSI can be tweaked with more confidence. Yet again, be sure you know what you are doing when tweaking the defaults.

4

[Max] Bug Reporting / Re: Number Input Occasionally Fails in Post/LightMix

« on: 2025-07-04, 20:59:57 »

Hi,

I have experienced this multiple times already, happening very rarely. As you mentioned, the workaround is either clicking away from VFB, either reopening it.

So far I have come to the realization that this is 3ds Max hotkeys still taking effect in VFB - even numbers on numpad are shortcuts for 3ds Max. I believe I have experienced this same thing in a non-Corona related UI (I think it was PhysicalMtl) too.
I do think this mostly happened after walk mode was used - does this ring a bell for you?

5

[Max] Bug Reporting / Re: Interactive rendering not expanding when the vfb is resized

« on: 2025-07-04, 12:06:17 »

Hi,

I will note that this very rarely happens to me. Mostly when I get back to VFB after some time of being idle, start IR and resize the VFB.

No reproduction so far, even after it happens...

6

[Max] Bug Reporting / Re: CoronaSky Volume Effect problem in Corona 13

« on: 2025-07-02, 18:48:17 »

We would love to use the sky fog with any hdri.

Yeah, I thought of it too.
Please add the idea here (if not present already): https://chaoscorona.ideas.aha.io/ideas

7

[Max] I need help! / Re: 3ds Max ACES Color Managment

« on: 2025-07-02, 13:38:00 »

Hi,

Does this happen with other textures as well, or this one specifically?
It will be good to get the actual file and test it on our side.

8

[Max] Bug Reporting / Re: CoronaSky Volume Effect problem in Corona 13

« on: 2025-07-02, 13:10:37 »

For the select map taking Map 1 even when another is selected - this seems a separate/older-than-v13-maps bug, yes.

This turned out to be a false positive - the CoronaSelect map in the attached scene has additional parameter (bezier float) plugged to "selected" parameter. This is not visible when map is drag-dropped to material editor, but gets visible once additional parameters are shown. This is a general Max limitation/bug, not a Corona related thing.

9

[Max] I need help! / Re: mesh panel not looking like what i had expected

« on: 2025-07-01, 15:32:49 »

Hi,

I think you are doing everything fine, this is just how it looks, at least from that point and with that lighting.

I would check the materials, just to make sure that the opaque parts do not have any transparency coming from opacity settings.

10

[Max] Bug Reporting / Re: Corona Renderer 13 doesn’t detect installed versions of 3ds Max 2024 and 2025

« on: 2025-07-01, 15:29:24 »

Selecting manually is something else and is fine. Having the max version(s) greyed out in Corona installer when they are installed is not fine.

My guess is not proper installation of these 3ds Max versions.

11

[Max] Bug Reporting / Re: CoronaSky Volume Effect problem in Corona 13

« on: 2025-06-30, 14:03:18 »

when in pre 12.2 it was possible to use Volume effect with any HDRi freely.

What if volume effect is not wanted for the HDRI?

It was no problem to set it to zero value then. So we use this "bug" in all our scenes to enhance aerial perspective and all scenes now unusable in C13. It's unfortunate. No way to use it as "legacy" mode?

I get that it could have been used as a feature, but what if you have two sky maps, one with volume and one without. In that case the volume would affect the other sky map and HDRIs. It is a clear bug which is now resolved.
I am not sure what your workflow is, but I would recommend fixing the scenes so they follow the fixed/correct behavior, as you open and decide to migrate them to v13. Hopefully the tweaks are not much. E.g. there can be new features coming to sky map and supporting this "feature" would possibly affect the new ones too, which is definitely unwanted.

12

[Max] Bug Reporting / Re: CoronaSky Volume Effect problem in Corona 13

« on: 2025-06-28, 22:11:07 »

when in pre 12.2 it was possible to use Volume effect with any HDRi freely.

this - having CoronaSelect with e.g. Sky map with volume effect and some HDRI, and volume effect from CoronaSky being present in HDRI, even when not selected - was widely considered a bug and has been fixed. What if volume effect is not wanted for the HDRI?

For the select map taking Map 1 even when another is selected - this seems a separate/older-than-v13-maps bug, yes.
UPD: the above was confusion because of missed out:

Map 0 is wired to CoronaLight target custom properties.

No bug whatsoever.

13

[Max] Bug Reporting / Re: CoronaSky Volume Effect problem in Corona 13

« on: 2025-06-27, 20:19:00 »

Hi,

I have checked the scene.
The issue seems to be in CoronaSelect map, as the one used in your scene simply cannot have 0th map selected (any other than Map 1), even when done manually - it switched back to Map 1, which is black color.

Interestingly, newly created CoronaSelect maps work fine.
Workarounds are using Sky map as Map 1 in CoronaSelect map (Environment) or creating new ones, if that fits.

This is reported now and I will definitely keep you posted when this gets fixed.
Thanks for reporting it.

(Report ID=CMAX-1737)

14

[Max] General Discussion / Re: Updated to Corona 13 - DR wont Render

« on: 2025-06-27, 19:28:29 »

Hi,

Haven't any of the machines (including master) received a notification for missing/non-engaged licenses?
We have an internal report for improving the notifications with DR, and I want to make sure that this is one of the cases which are covered in the improvements.

15

[Max] Daily Builds / Re: Camera Inside Volumes Playground!

« on: 2025-06-27, 18:36:58 »

Glad to see this align-with-camera is now working. But one issue remains that we ideally need the "camera" to be a rectangular cuboid i.e. ability to separately control it's 3 x dimensions. Because right now if you want to do this half-in-water effect you're forced to determine it with a cube, so if you want a close cut (say 10cm away from camera) it means you can still see the far faces of the cube in the render causing artifacts. We need to be able to make the width and height separate from the depth basically. As of right now I'm still having to overcome this by using a custom invisible box that I use as a coronaslicematerial to cut out of the water. Sorry no preview to share as it's under NDA.

Given the vast customization of the slicing volume with slicer material (custom shape, linking to camera, animating if needed), I don't think it is worth adding the same functionality (which will clutter the UI for a simple thing) into camera. Camera physical volume is intended for the general-use-case quick medium cuts aligned with the camera. I believe it does the same thing as slicer material under the hood, so good thinking on the workaround :)