# \*\*\*BUG Corona Render\*\*\*\*Chaos Corona Action.

**URL:** <https://forums.chaos.com/t/bug-corona-render-chaos-corona-action/159231>\
**Category:** General\
**Created:** [January 21, 2025, 10:21pm UTC](https://forums.chaos.com/t/bug-corona-render-chaos-corona-action/159231 "2025-01-21T22:21:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![alekzab\_gmail.com](https://avatars.discourse-cdn.com/v4/letter/a/b782af/32.png) [@alekzab\_gmail.com](https://forums.chaos.com/u/alekzab_gmail.com)\
**Post date:** [January 21, 2025, 10:21pm UTC](https://forums.chaos.com/t/bug-corona-render-chaos-corona-action/159231/1 "2025-01-21T22:21:21Z")

</div>

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.

 ![ChaosCoronaAction.JPG](https://europe1.discourse-cdn.com/chaosprd/original/3X/5/2/52680fdf1e6a8fc06e1b31ecf43b3f4d64a09f53.jpeg)

---

<div class="post-metadata">

**Author:** ![maru](https://dub1.discourse-cdn.com/chaosprd/user_avatar/forums.chaos.com/maru/32/15975_2.png) [@maru](https://forums.chaos.com/u/maru)\
**Post date:** [January 27, 2025, 3:45pm UTC](https://forums.chaos.com/t/bug-corona-render-chaos-corona-action/159231/2 "2025-01-27T15:45:17Z")

</div>

I have never seen this message and I do not recall any user reports. Are there some solid repro steps for it, or is it random?  
Perhaps you could try running this maxscript command before starting rendering - it should stop any ongoing render:  
CoronaRenderer.CoronaFP.stopRender()

---

<div class="post-metadata">

**Author:** ![alekzab\_gmail.com](https://avatars.discourse-cdn.com/v4/letter/a/b782af/32.png) [@alekzab\_gmail.com](https://forums.chaos.com/u/alekzab_gmail.com)\
**Post date:** [January 27, 2025, 11:55pm UTC](https://forums.chaos.com/t/bug-corona-render-chaos-corona-action/159231/3 "2025-01-27T23:55:12Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![jpjapers\_1](https://avatars.discourse-cdn.com/v4/letter/j/e9bcb4/32.png) [@jpjapers\_1](https://forums.chaos.com/u/jpjapers_1)\
**Post date:** [February 4, 2025, 3:01pm UTC](https://forums.chaos.com/t/bug-corona-render-chaos-corona-action/159231/4 "2025-02-04T15:01:35Z")

</div>

Ive had this happen when ive accidentally started IR in a viewport that i no longer have visible rather than in the VFB. Im not sure if its the same issue youre experiencing though. Ive never had it happen when using the VFB.