Corona interactive render is not responding, then it starts from pass 15-20

[kayaarchitectures]

When I start the interactive render, it does not respond for 30 seconds. Then as soon as it starts working, it has advanced 15-20 passes. From the 1st pass I can't see the interactive render.

(Corona 11, cpu: i9-13900k)

[maru]

Is this happening in any scene? Even very simple?
I would check the following things:
1 - Make sure you are not running out of RAM. Such a freeze and then getting back to normal sounds like something related to RAM.
2 - Are you using the NVIDIA denoiser in IR? If so, try disabling it in Render Setup > Performance > Interactive Render > Denoise during rendering: none
3 - As the last step, you can try limiting your number of CPU threads for IR. You can change that in Render Setup > System > System Settings > Interactive rendering > # of threads override - you can set it to, for example, -4 to leave 4 threads available for other tasks than interactive rendering. The default value is -1.

[kayaarchitectures]

First of all, please excuse my late response.
This problem does not occur when I create a new scene and add a few simple objects. But I have this problem in a 10m polygon outdoor scene. I tried in 2 different outdoor scenes, the problem persisted.
I was not having such a problem in the same scenes with Corona 9.

1- Total RAM usage during interactive rendering; 79%.
2- I am using NVIDIA noise denoiser, but the same problem persists even when I disable this feature.
3- The problem is even worse when I reduce the number of CPU threads.

[maru]

Could you send us any problematic scene where this happens archived with all assets? The easiest way would be by submitting a support ticket here: https://support.chaos.com/hc/en-us/requests/new

[mgolan]

any news regarding this topic?!
im using 3ds max 2022 and corona render 9 - asustor 7110t
loading files, working with them loading textures is impossible.
interactive render does not enter to render stages not working at all.
im lost !! help please.

[maru]

Continued via support ticket #336071.
We contacted Asustor support in the past, but sadly no solution was ever provided.