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 - Aram Avetisyan

Pages: [1] 2 3 ... 67
1
Hey,

Thanks for bumping this, even though it has been bumped many times.

I will just say that anything regarding the file output is, unfortunately, handled by 3ds Max, we use its dialog for the output. We are limited to its capabilities. View transform may be quick to implement, but a whole new independent output dialog is not.

Let's hope that 3ds Max development handles this at some point, and there will be minimal work to sync on our side. If not (like when we implemented ACES OT for the sake of it, then Color Management with various view transforms got introduced :)), then the only way is having our own output dialog. We do have some, though indefinite, plans for this for future versions.

2
Hi,

We may have a clue what is causing it, may be related to instruction set for specific CPU types.
If there is an implemented fix, it will most probably be in the next preview (daily build), so stay tuned to check it.

3
With CIE every time I try to do a 'save all' to jpeg I get an instant crash.

Known problem? I can provide crash report if this is new?

Edit:
CIE seems to be all types of messed up? Is this all known? See example below of how a lightmix pass looks in CIE vs how it is saved as jpg. What's going on?

Hi,

These are known and already reported. I wonder if you had any issue specifically with the UI/UX.

(Report ID=CMAX-1878)
(Report ID=CMAX-1877)

4
Hi,

From my experience, specifically with large files over the past few years, big files just take long to load. And i have seen this pattern with other software too, e.g. Revit. A 500MB file for Revit can be considered big, and I had one which opened for 35 minutes. My max files usually do not go longer than 5 minutes to open, but I guess they are not big enough :)
I would suggest XRefing the scene to parts and opening each of them to see which one takes long.

Surely, if any of them have a specific Corona related object, which you think takes long to open (e.g. we had optimization for Volume objects, which in rare cases could load quite long), report it and we will have a look.

5
[Max] Bug Reporting / Re: Memory leak
« on: 2025-09-10, 12:56:22 »
Hi guys, im on a dealine but im experience this issue too, for me this happens with distribute rendering, no matter if the materials are physical or legacy, as soon as i turn on the dr the 3dsmax send a bad allocation error, all my servers are AMD Rysen with 128 to 256 of ram, this scene was rendered 5 months ago with version 12 without issues and also one of the 13 versions, dont remember the exact release, after i finish i will try to upload the scene and create a ticket, on a single machine it renders fine but takes mote time than before to render (previous corona versions), here a crop of the error, and yes, this machines was rendering this scene with 128 gigs of ram without warnings or memory issues.

Hi,

The scene, details machine specs (both hardware and software) will be necessary to troubleshoot. So far you state, to paraphrase - "a scene renders fine with Corona 12 and less RAM, renders fine with Corona 12 with DR, renders fine with with Corona 13 locally, crashes/throws bad allocation with Corona 13 with DR" - correct?
Make sure to attach the ticket number here so it can be tracked easily. Thanks.

6
[Scatter] Feature Requests / Re: Avoid objects
« on: 2025-09-09, 15:38:18 »
Hi,

Not sure what's your case, but there is CoronaDistance texture, which can be used to set objects, define a distance and use it as distribution map for scatter.
Other workarounds, like vertex paint, volume select etc. are also possible.

The idea to have this directly in Scatter as "Avoid objects" is nice though. You can put it to Aha, if you want: https://chaoscorona.ideas.aha.io/ideas

7
Hi,

The only "accuracy" with photographic exposure is that you can mimic a real world camera. That's all there is to it.
Personally for me, simple exposure is the way to go, I don't remember when was the last time I used photographic exposure.

8
#413824

Thanks, the scene with reproduction steps has been attached to the task.
It is when volume material is plugged as global volume material, right? Or there are other steps which lead to crash in your case?

9
[Max] I need help! / Re: different results with HDR
« on: 2025-09-08, 09:48:24 »
But this problem doesn’t necessarily occur with all HDRs, which is very frustrating. It seems that with certain HDRs it inevitably happens!

Yes, because some HDRIs can have a single pixel as a very bright light source, and some don't.

10
Wetransfer and other filesharing services are fine. You upload and share the link.
You can submit it with a ticket as well - make sure to share the ticket number here to track it better.

11
I cant prove but i am sure scenes with volume material are very unstable (frequent 3dsmax crashes)

I can't promise, but attaching minidumps makes reports better.

Hi,

We will need the scene to reproduce and fix the issue properly.
Please send it over (or a simplified version where the crash can be reproduced) as soon as you can.

12
latest daily, max 2026.  Crashes everytime i use the spinners in the interactive mix.

This is reported and already fixed internally. Next preview should have it.

13
[Max] Bug Reporting / Re: Memory leak
« on: 2025-09-02, 15:25:59 »
I just updated to Corona 13 Hotfix 1 today and encountered the same issue. You're definitely not alone.

In my case, it happened in an old scene that contains many legacy materials. While using  IR Rendering, I adjusted the displacement value in the Material Editor, and suddenly experienced a memory leak. RAM usage spiked to 128 GB, and then 3ds Max crashed.

This seems similar to an issue I encountered in Corona 12 Update 1
https://forum.corona-renderer.com/index.php?topic=44083.0&utm_source=chatgpt.com
https://forum.corona-renderer.com/index.php?topic=43296.msg230075#msg230075, but with a slightly different trigger:

Corona 12 Update 1: The crash occurred while using IR and moving objects in the scene.
Corona 13 Hotfix 1: The crash happened when adjusting displacement settings during IR in a scene with legacy materials.

This issue never occurred with:

Corona 13 (initial release)
Corona 12 Update 2
Corona 12 Update 2 Hotfix 1

My cpu is  AMD Ryzen 9 7950X

Hope this helps narrow things down.

Just like fire and smoke, there is no crash without minidump. Minidump helps more than a reference to an issue.

14
I cant prove but i am sure scenes with volume material are very unstable (frequent 3dsmax crashes)

There seems to be some proof. We will investigate it. Thanks.

(Report ID=CMAX-1868)

15
Report Corona 13 Hotfix 1 : I just updated today and then tested with some project while using IR rendering I got back the same problem with sudden memory leaking. (Corona 12 Update 1) https://forum.corona-renderer.com/index.php?topic=44083.0
It never happens when I use Corona 12 Update 2 and Corona 13.

Please note, this is v14 previews thread.

You can open a new thread in 3ds Max Bug reporting/I need help groups

Pages: [1] 2 3 ... 67