Chaos Corona for 3ds Max > [Max] Resolved Bugs

corona 12 VFB 2.0

(1/2) > >>

JG_monomiru:
Is it a normal behavior that heavy scenes (corona warning memory etc) rendered in corona 12 vfb2.0 will be unresponsive as long as the rendering happens?

So far i experienced when doing IR i can set up lightmix and switch between renderelements. When rendering production i'm unable to do anything in VFB2.0 ... it even stays black (showing nothing) unless the max "rendering progress" dialoge is moved by mouse.

I've not yet tested corona 12 with the old vfb and if the experience is the same or as it used to be before corona 12.
--- I did a short test with chaning vfb 2.0 to vfb under system settings. But it showed no difference - still the issue with black vfb as long as you move the rendering dialoge, also no interaction with vfb possible.

Avi:
so your scene is running out of available RAM on your system?

JG_monomiru:
Not really.... Its just a warning that 128GB ram is maybe running low, because the scene is quite heavy and lists possible Objects/Textures which needs lot of ram. But else than that there is enough swapping RAM available to the rendering is working.

But the frozen VFB is also present, when its just a normal scene with lots of objects.

I tried to merge the whole scene (which was created in v10 or v11 some time ago) and start fresh with rendering settings but its the same - VFB is frozen and you can't change tone-mapping/Lightmix or even switch between render-elements while its rendering.

I went back to V11 now - as i have to work. Might be able to test it in september again.

Working on a Ryzen 5950 with 128GB ram, windows 10, max 2024.2.1 and corona v12 (but now went back to v11, as it was working as i used to)

JG_monomiru:
Its not that the scene is rendering above 100GB ram...

I tested various scenes from different older and current projects - open in max24 with v12 and its all the same. Sometimes with heavy scene warning, sometimes without.
But even those without a warning, the new VFB is "frozen" or better its UI is not accessible. Once you moved the render-dialogue a image appears in the VFB 2.0 window, but you cant move that window or interact with it in any way as long as its rendering.
But the render progress is visible in that frozen VFB ... so i guess its some sort of interaction-problem.

JG_monomiru:
well i tried one last thing.

I openend a scene in Max 2025 with corona 12 ... and its rendering in corona 12. But the max 2025 installation is almost clean.
So I dont have any scripts and plugins installed (except for batch camera render 1.18 but that doesnt seem an issue)

But this Max hasn't those plugins installed yet - so i dont know if its caused by any of these, or if my max2024 is somehow messed up. I might test an older scene on another machine with max 2024 and corona 12, if i find time for that.

Navigation

[0] Message Index

[#] Next page