1
[Max] Resolved Bugs / Re: object transform bug during IR
« on: 2025-05-10, 01:22:19 »
Woah
2025-06-17, 12:34:41
News:
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.
2
[Max] Bug Reporting / **** Corona 12.2 BUG ******
« on: 2025-05-10, 01:21:30 »
Hi Corona Team,
Animated Object Visibility does not work when scrubbing in IR.
Object Properties>Rendering Control>Visibility
Animated Object Visibility does not work when scrubbing in IR.
Object Properties>Rendering Control>Visibility
3
[Max] General Discussion / Unify Corona and Vray assets
« on: 2025-02-03, 23:17:39 »
Hi Corona Team,
We frequently use both Corona and V-Ray interchangeably, along with Chaos Vantage. I was wondering if there are any plans to unify materials between Corona and VRay, perhaps a shared Chaos Material, since they essentially serve the same functions.
The same could apply to proxy meshes; instead of maintaining two separate versions, having a single ChaosProxy for both would be much more efficient.
Has the development team considered this for future updates?
We frequently use both Corona and V-Ray interchangeably, along with Chaos Vantage. I was wondering if there are any plans to unify materials between Corona and VRay, perhaps a shared Chaos Material, since they essentially serve the same functions.
The same could apply to proxy meshes; instead of maintaining two separate versions, having a single ChaosProxy for both would be much more efficient.
Has the development team considered this for future updates?
4
[Max] Bug Reporting / Re: ***BUG*****Chaos Vantage doesn't Stop
« on: 2025-02-03, 23:11:20 »
It happens in merge/starter-scene we typically use to start scene development.
5
[Max] Bug Reporting / ***BUG*****Chaos Vantage doesn't Stop
« on: 2025-01-31, 04:22:30 »
Chaos Vantage doesn't Stop and it gets stuck 13 mins
its 10:50 mins in the image:
its 10:50 mins in the image:
6
[Max] General Discussion / Re: ***BUG Corona Render****Chaos Corona Action.
« on: 2025-01-28, 00:55:12 »
Hi Maru, I'm surprised by this. I thought it was a common issue. I've experienced it on previous machines, but I’m not sure of the exact cause or how to replicate it. It's a bit annoying, but it doesn't really interfere with my work. I appreciate your insight!
7
[Max] General Discussion / ***BUG Corona Render****Chaos Corona Action.
« on: 2025-01-21, 23:21:21 »
This bug has been around for years. In some cases, users can work around it by clicking "OK," then pressing the render button, stopping it, and switching back to interactive rendering.
However, at times, there is no workaround, clicking "OK" does nothing, and if the user tries to start interactive rendering again, the message reappears in an endless loop.
Additionally, the error message is often incorrect, as Corona is not actually rendering when it appears, making the warning misleading.
Possible Fix:
When the user clicks "OK," the system should check for any active CPU cores running a render process and force them to stop, allowing new commands such as rendering or interactive rendering to proceed.
However, at times, there is no workaround, clicking "OK" does nothing, and if the user tries to start interactive rendering again, the message reappears in an endless loop.
Additionally, the error message is often incorrect, as Corona is not actually rendering when it appears, making the warning misleading.
Possible Fix:
When the user clicks "OK," the system should check for any active CPU cores running a render process and force them to stop, allowing new commands such as rendering or interactive rendering to proceed.
8
[Max] General Discussion / Best Practices for Corona Proxy
« on: 2024-11-27, 05:06:45 »
Hello Corona Team,
I have a question regarding best practices for using CoronaProxy. Like most users, I would like my file to open as fast as possible and also efficiency to transform vertices and parsing while in the rendering process.
Would you recommend enabling the "Keep in Memory" option for all proxies? My render servers are quite powerful, with half of the farm equipped with 128GB and the other half with 256GB.
Thank you.
I have a question regarding best practices for using CoronaProxy. Like most users, I would like my file to open as fast as possible and also efficiency to transform vertices and parsing while in the rendering process.
Would you recommend enabling the "Keep in Memory" option for all proxies? My render servers are quite powerful, with half of the farm equipped with 128GB and the other half with 256GB.
Thank you.
9
[Max] Bug Reporting / Re: Forrest Pack and Lightmix/Select not working in Corona 12 update 1, as before
« on: 2024-11-26, 06:26:16 »
I use this workflow at times, but my current projects don't require it at the moment.
I'll stay tuned to see what the result is. I would expect that everything that worked in 12H1 should work on 12U1.
I'll stay tuned to see what the result is. I would expect that everything that worked in 12H1 should work on 12U1.
10
[Max] Bug Reporting / Re: Light Mix ****BUG****
« on: 2024-11-26, 06:17:50 »
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?
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?
11
[Max] Bug Reporting / Light Mix ****BUG****
« on: 2024-11-09, 06:55:01 »
Hi Corona Team,
When lightmix is enabled and if the user sets a Kelvin color (e.g., 4800K) using the Corona Color Picker, closing and reopening the color picker causes it to default back to 1700K.
When lightmix is enabled and if the user sets a Kelvin color (e.g., 4800K) using the Corona Color Picker, closing and reopening the color picker causes it to default back to 1700K.
12
[Max] Resolved Feature Requests / Alternative display option for unsupported materials
« on: 2024-11-08, 07:46:00 »
Hi Corona Team,
The 'red warning override material' can quite disruptive during rendering production. While I understand it’s intended to help identify missing materials, it can be easy for users to overlook. Archvizers often don’t have the time to address every material issue that comes in from external models, like those from Revit, SketchUp and Vray. Additionally, the Corona Converter doesn’t always handle the conversion of every material, which can leave us with the red warning material in final renders.
While I appreciate the warning feature, perhaps this red glow could appear only in Interactive Rendering (IR) rather than in production renders. In production, it would be more helpful if missing materials defaulted to a gray, which many of us commonly use when we don’t have time to texture a model fully. I believe this would align with how many Archvizers work. Also I would exclude the warning material from Lightmix or eliminating the light glow.
Possible solutions could include:
Improving the converter’s capability to convert all materials from Revit, SketchUp, and V-Ray.
Making the 'red warning override material' visible only in IR.
Adding a checkbox in the converter to automatically convert unknown materials to gray.
Thanks for considering these suggestions!
The 'red warning override material' can quite disruptive during rendering production. While I understand it’s intended to help identify missing materials, it can be easy for users to overlook. Archvizers often don’t have the time to address every material issue that comes in from external models, like those from Revit, SketchUp and Vray. Additionally, the Corona Converter doesn’t always handle the conversion of every material, which can leave us with the red warning material in final renders.
While I appreciate the warning feature, perhaps this red glow could appear only in Interactive Rendering (IR) rather than in production renders. In production, it would be more helpful if missing materials defaulted to a gray, which many of us commonly use when we don’t have time to texture a model fully. I believe this would align with how many Archvizers work. Also I would exclude the warning material from Lightmix or eliminating the light glow.
Possible solutions could include:
Improving the converter’s capability to convert all materials from Revit, SketchUp, and V-Ray.
Making the 'red warning override material' visible only in IR.
Adding a checkbox in the converter to automatically convert unknown materials to gray.
Thanks for considering these suggestions!
13
[Max] General Discussion / Re: Corona 12 - Recommended Scripts to avoid crashing
« on: 2024-11-07, 23:49:59 »
Thanks! I’ve submitted a support ticket and shared several dump files. Hopefully, these can help you pinpoint the crash module. My file is quite large, with assets from my personal library, Chaos, AXYZ Anima, and Poliigon, so it’s pretty massive. But If it needs to be transferred I can do that.
To work around the issue, I constantly use Prune, Forensic, and merge the objects into a new scene, which temporarily fixes it. However, the problem returns. Almost every time I start an Interactive Render (IR), it crashes; then I reopen the file and try again, and it might work.
I suggest for the Corona Team to create a public poll in this forum to gather basic feedback. Questions could include:
Is Corona generally stable?
Does it often crash during rendering?
Is it slow when connecting Corona materials in the Slate Material Editor?
This would help gather valuable insights to incorporate in the next update.
To work around the issue, I constantly use Prune, Forensic, and merge the objects into a new scene, which temporarily fixes it. However, the problem returns. Almost every time I start an Interactive Render (IR), it crashes; then I reopen the file and try again, and it might work.
I suggest for the Corona Team to create a public poll in this forum to gather basic feedback. Questions could include:
Is Corona generally stable?
Does it often crash during rendering?
Is it slow when connecting Corona materials in the Slate Material Editor?
This would help gather valuable insights to incorporate in the next update.
14
[Max] General Discussion / Re: Corona 10/11 - Corona Render Assets loading very slow
« on: 2024-11-07, 23:39:05 »
Hi Corona Team,
Has there been any progress on this? Has Autodesk been able to help the Corona team resolve the issue? It seems like a significant problem.
Has there been any progress on this? Has Autodesk been able to help the Corona team resolve the issue? It seems like a significant problem.
15
[Max] General Discussion / Re: Corona 12 - Recommended Scripts to avoid crashing
« on: 2024-11-05, 07:33:29 »
I get about 20+ crashes a day. With errors all over the place.
I get one where the screen is black and it doesn't do anything. And another weird error that says internal error.
I get one where the screen is black and it doesn't do anything. And another weird error that says internal error.