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 4 ... 60
16
This daily build contains fixes intended for upcoming Hotfix for Corona 12 Update 2.

Please check this article covering the risks of using daily builds: Daily Builds FAQ
If you are familiar with the daily builds and know how to use them, download the newest one here:
chaos-corona-13-3dsmax-daily-2025-05-07.exe

User-Facing Improvements
  • Simplified trial obtaining process.

Bugfixes
  • Fixed crash on Max start for old CPUs without AVX support.
  • Fixed a bug where material drag&drop from Cosmos would not work in Max 2025 and newer.
  • Fixed issue where Scan materials imported from Cosmos were blank if the user did not have Scans license.
  • Fixed issue with the slow import of the Scan materials from Cosmos.
  • Fixed issue where Rotate and Select&Place tools would behave erratically during IR.
  • Fixed issue where aspect ratio lock was not working in Corona Bitmap.

17
Yes, it should be either hidden (per camera or for a view), as lightmix cannot "unsee" a lightmix layer simply by turning it off. Or the workarounds I shared above.

18
If you are using 1 object with 2 different lights/material, then you need to animate this (or animated with 2 different objects), there is no way to do it through lightmix.

19
I got your point.

Not sure how it works in VRay, but please tell me if what you are describing was ever possible in Corona, in some version.
It may become a feature request in the end.

20
I believe there's a bug:

https://youtu.be/pBMelae7118

To replicate it:

1- Open a scene, create somthing, render and save CXR.
2- the the VFB clear, open the CXR from history and edit it.
3- Draw a region and click render.

The image in the VFB goes away.

In any case, an "open" option under the little disk icon in the regular (not history) VFB would be better in my opinion.

EDIT: 3ds Max 2025.3, Windows 11 latest update AFAIK.

3 - instead of Render, draw a region and do Resume in rendering (play button for history item).

21
[Max] Daily Builds / Re: Camera Inside Volumes Playground!
« on: 2025-05-02, 15:56:25 »
Not sure if this is the best thread for this, but I'm discovering that the "camera physical size" parameter of a coronacamera is always oriented the same way regardless of rotation of camera (with or without target), meaning that if you have your camera for example pointing at 45 degrees instead of directly up, down, left or right, it will clip the apex of the "box" that it lives within.

This is with 11HF2. Is this fixed in 12.x? Or is there a workaround so that it properly follows the orientation of the camera?



Many thanks,

Hi Alex,

Thanks for the bump. This has been fixed at least as of v12 update 1, maybe even in v12.
This was somehow missed from the changelog, will add it.

Not only it takes into consideration the camera transformations but also accounts for camera tilt.

22
[Max] I need help! / Re: Problem with edges
« on: 2025-05-02, 14:35:05 »
This can rarely happen with normal scenes too.

Workaround is - enable viewport clipping, and move the bottom slider slightly higher (this enables clipping at some distance in front of the camera/perspective viewport).

23
[Max] I need help! / Re: Arranging Lights in Lightmix
« on: 2025-05-02, 14:30:51 »
Hi,

A new render element is added at the end of the list, I don't think Corona controls that, it's Max thing.
When you add a new lightmix (CShading_LightSelect) layer, other layers should stay intact, unless you re-create the lightmix.

If you do this manually through render elements dialog, old values should stay intact. Just make sure that the light you add to a new lightmix layer is not in another layer (exception is, of course, the rest).

24
Open/Load CXR has been there, plus a more convenient, including multiple, drag-and-drop also.

25
Hi,

I have logged this as a feature request in our system to be further reviewed by our devs.

(Report ID=CMAX-1449)

Hi Avi.
was this reviewed?
Waiting several seconds or up to a minute just to load a CXR file on the VFB is ridiculous.

Hi,

Region drawing was enabled for load CXR since 02-28 DB, it is in Corona 12 Update 2 as well:
https://forum.corona-renderer.com/index.php?topic=43295.msg231652#msg231652

Quote
VFB - Region draw is enabled when editing CXR, but only when edited CXR is of the same size as current/last rendering, which is necessary for resume render.

26
[Max] I need help! / Re: Problem with corona select map
« on: 2025-05-01, 15:28:26 »
Hi,

We already have, specifically, clouds shadow bug fixed with select map use case, internally.
I am checking if the rest (volume effect and some others) can be fixed with this as well.

27
Glad to hear that and you are welcome.

That one specific .gup file is actually not expected to be extracted.

(Report ID=CMAX-1621)

28
Confirmed and logged, thank you.

(Report ID=CMAX-1620)

29
Hi,

I handle the software deployments for a small studio.  For whatever reason, deploying the latest version of Corona (12 update 2) breaks the maxinternal2024.gup plugin.  I have tried the standard deployment using auto and the unpack and overwrite methods.  Both produce the error. Replacing the maxinternal2024.gup file with the previous one has not helped.

This has happened on 3 separate computers.  Is there a problem with the maxinternal2024.gup, possibly?

Thank you.

Hi,

This .gup file normally should not be installed, it is for internal stuff.
You can ignore that message, and it should be safe to simply delete it.

30
[Max] General Discussion / Re: Corona 12.2 LUT Errors
« on: 2025-04-29, 11:55:42 »
it is a workaround, but all previous LUTs paths should have been automatically converted to the new ones with Corona 12 Update 2.

Anyway, glad to hear the issue is gone.

Pages: 1 [2] 3 4 ... 60