Messages

1

[Max] Daily Builds / Re: Chaos Corona 13 for 3ds Max - Daily Builds Discussion

« on: 2024-11-29, 18:07:35 »

Hi,

Currently on daily build 2024-11-04 I'm getting odd behavior with my lighting in IR - essentially the lighting is all wrong between camera switches, a restart is necessary each time. Never seen this before.

I have an env override on and some varied camera tonemapping overrides, but nothing else is special.

Please see video and attachments. Thanks.

ab_channel=AnotherAngle3DVisuals

I believe it is the camera tone mapping overrides which need a restart to get updated for IR, just like camera object visibility.
You can try doing batch rendering of few cameras which have different tone mapping. They should all come out with expected tone mapping overrides.

2

[Max] I need help! / Re: Forest Ivy not rendering animation

« on: 2024-11-28, 20:58:16 »

Hi again. I cant find Corona 12 hotfix 1. its not available on the download page. and the topics here on the forum just refers to the website. latest I can find is 11 with hotfix

It is already available in older version download page.

3

[Max] Daily Builds / Re: Corona 13 daily builds IR/viewport slowdown

« on: 2024-11-27, 20:07:05 »

The sluggishness is known for high core machines and is being investigated.
Backward compatibility was never guaranteed - Corona 12 Update 1 saved scenes are not guaranteed to work with Corona 12 Hotfix 1, so please back up the scenes. Corona 12 Hotfix 1 saved scene should work fine with Corona 12 Update 1.

Please, whoever is investigating this: please check if IR is faster (more rays/s), for any given scene, in Corona 12 Update 1 than in Corona 12 Hotfix 1. If so, please confirm it, so we know that we are on the right track.

Can you provide a link for V12 HF 1?  It's not listed under 'older versions' on the chaos download page and the changelog forum pages don't link directly to it that I can find.  Going to try rolling back from the July 30 build to see if my VRAM drops like Sepia's results.
 Thanks

I will try bumping this, so it appears in older download options in the website.

4

[Max] Daily Builds / Re: Corona 13 daily builds IR/viewport slowdown

« on: 2024-11-27, 17:28:06 »

The sluggishness is known for high core machines and is being investigated.
Backward compatibility was never guaranteed - Corona 12 Update 1 saved scenes are not guaranteed to work with Corona 12 Hotfix 1, so please back up the scenes. Corona 12 Hotfix 1 saved scene should work fine with Corona 12 Update 1.

Please, whoever is investigating this: please check if IR is faster (more rays/s), for any given scene, in Corona 12 Update 1 than in Corona 12 Hotfix 1. If so, please confirm it, so we know that we are on the right track.

5

[Max] Bug Reporting / Re: Forrest Pack and Lightmix/Select not working in Corona 12 update 1, as before

« on: 2024-11-26, 13:16:33 »

This behavior may or may not be correct or wanted?

If LightSelect element has a forest object selected, I would expect that all the forest objects are in this element - this is the case for Corona 12 Update 1.
While if a only a single light is added to LightSelect element, I would expect only that light to be in the lightselect, not also all its instances in Forest object.
If this was somewhat useful, this - light source and all its instances in Forest object in the same lightSelect element - can be brought back.

But selecting forest object as lightselect element should definitely have the complete Forest object in it.

Let me know what you guys think.

6

[Max] Bug Reporting / Re: Light Mix ****BUG****

« on: 2024-11-26, 11:29:58 »

This seems like a bug, let me explain why.

If you select a color, say 4800K, and then reopen the color picker, it should stay at 4800K. This consistency is important for artists who might want to make subtle adjustments to the Kelvin color. For example, if it was 4800K and you want to bump it up to 5000K, you’d need the original value as a reference.

While this might not seem like a big deal at first, you would expect that numerical parameters like these should remain consistent in most Windows applications, right?

Yes, but it is how, unfortunately, the Color picker works now.

In the meantime, here is a good workaround for you using OSL maps. Please see attached image.
Hope this helps.

7

[Max] Daily Builds / Re: Corona 13 daily builds IR/viewport slowdown

« on: 2024-11-26, 11:25:11 »

I did a test with a scene on my work PC (with an RTX 3070) and my home PC (with an RTX 3090). On the work PC, the Vram usage is 7.5 GB out of 8 GB and I will encounter a lot of slowdowns during interactive renders or even in material editor for a few seconds. On the home PC, the VRAM usage is 4.6 GB out of 24 GB and I don't encounter slowdowns. Both are on the latest version of 3ds Max and are using Corona's latest release. No other program is running in the background. I don't recall having issues like this using any of the previous versions of Corona and even on my home PC, 4.6 GB of VRAM usage for a scene that simple is a bit much. I will try to test the same scene on another PC running an older version of the Corona with an RTX 2070 Super and will report back.

Can you please also check the GPU usage with IR, if any of the AI denoisers are enabled for IR? Check optionally with earlier versions (v12 hf1, v11 hf2 etc.) too.

For IR sluggishness in v12 update 1 - it may be due to slightly higher CPU than v12 hf1, so you should see higher speed (ray/s) stats for IR in v12 update 1 than in v12 hf1. If you can confirm this, I will appreciate it and it will help with troubleshooting too.

8

[Max] I need help! / Re: Corona Rendering Black in Animation

« on: 2024-11-26, 11:22:01 »

The fix in article is, if I am not mistaken, just disabling all volumetrics in materials. I think it can be improved (or another one maybe) to check for non-enclosed objects only, and disable volumetrics for those only.

9

[Max] Bug Reporting / Re: Lightmix bug when first opening scenes

« on: 2024-11-25, 14:11:59 »

Thanks.

Please create a very simple scene where this can be reproduced easily, and send it over. A video recording will be even better and make things quicker.
We will investigate it surely.

10

Hardware / Re: Color space/mode

« on: 2024-11-25, 09:25:10 »

I don't mean just internal rendering-space or respecting input. Is there anything output wise? Any check-box in Framebuffer? Does Corona saves the file with embedded color-profiles?
I didn't see any announcement, so this would be good news to me.

And DCI-P3 (and custom ICC) would be the useful one for design/graphic industry.

Can you link me to where it states what is supported?

Corona does not embed color profile information, unfortunately, I am not even sure if with 3ds max save dialog (Corona uses it under the hood) it is possible.

For 3ds Max color management - everything should be supported by Corona, unless there is a warning message about it (e.g. specific rendering color space).

11

[Max] Bug Reporting / Re: Lightmix bug when first opening scenes

« on: 2024-11-25, 09:22:24 »

Hey
We have an issue where lightmix won't kick in, when we first open a scene and do an interactive render.
We have to tick off a lightmix layer then on again for it to work.
This happens 100% of the time when using multiple HDRI's in lightmix.

Corona version: 12 (Hotfix 1)
Full-speed, Non-debug, MaxSDK 2024
____________
Edition   Windows 10 Enterprise
Version   22H2
Installed on   ‎28-‎05-‎2024
OS build   19045.5131
Experience   Windows Feature Experience Pack 1000.19060.1000.0

Hi,

Do you mean when selecting lightmix render element, it is not displaying what lightmix layers are setup to show, and you need a single enable-disable of some layer for it to show the expected result?

12

[Max] Daily Builds / Re: Corona 13 daily builds IR/viewport slowdown

« on: 2024-11-22, 21:47:21 »

I wonder if anyone experiencing this sluggishness has looked at their GPU VRAM usage in Task Manager?  That's when my viewport\slate\UI seems to come to a screeching halt for me lately.  Scenes that shouldn't really be maxing out VRAM still sometimes do.  Very odd.  Saying things are sluggish is an understatement, and when IR starts it can get nearly unusable.  Even in isolation mode with one object I still get 95% VRAM usage, although perhaps Max doesn't clear VRAM in isolation mode, can't say I've tested that before.

Windows 10
Max 2025
Corona 13 DB from July 30
Latest Forest Pack
RTX 2080 Ti driver 32.0.15.6094

If possible, please try with the latest stable release - Corona 12 update 1 - and let us know if you are still experiencing the sluggishness.
There is already a similar report being investigated.

13

[Max] General Discussion / Re: Frame buffer and Color Management settings

« on: 2024-11-22, 14:34:28 »

You're welcome!

14

[Max] General Discussion / Re: Frame buffer and Color Management settings

« on: 2024-11-22, 13:28:48 »

I'm not really up to date on the OCIO implementation in Max and how Corona handles it but judging from the screenshot your OCIO setting already use an ACES view transform, which is already passed along to the Corona VFB. If that's the case, applying the ACES Operator in the VFB will result in a double application of ACES tone mapping, which probably why it's throwing the error/warning in the log. Again, only an assumption but probably the reason why the warning comes up.
I agree that a 404 is not helpful :D, and Corona could probably automatically set the correct settings in the VFB (and probably let you choose whether to apply them or not).

Yes, this.

It is not deleted/changed automatically, because in some cases it can actually give artistically good results, so Corona just informs that there may be an issue.
OCIO should be very well supported (besides some rendering color spaces and very minor stuff), gamma workflow is "recommended" just to keep things as they used to be.

15

[Max] General Discussion / Re: What is the workflow with Corona image editor it does not have the new features

« on: 2024-11-21, 18:08:18 »

Also If I load the CXR into history and start to edit the image the auto exposure and white balance don't function.

I am not sure what you are doing, but it absolutely works when I load a CXR from 3 years ago - auto EV and White balance work as if it was a render

Resume render is tricky yes - it assumes that what you load as a starting point, is an actual copy of what you will be rendering. Anything else would not be supported, as it is a different thing to render.

I am not going to go through the ticket system I have done that before with bugs and its like pulling teeth.

That is still the best bet for getting an issue resolved. I am sorry if you have had not the most pleasant experience with ticketing system.