Messages

1

[Max] General Discussion / Re: Problem with corona render 7

« on: 2021-10-07, 18:24:11 »

Hi,

There is a good chance that this issue was fixed in the latest v8 daily build. Would you be able to install it and try it out?

You can find it here: https://forum.corona-renderer.com/index.php?topic=33839.msg190524#msg190524

Thanks,

Rowan

I can confirm that the problem is fixed in V8 Daily build.

Thank you Rowan

2

[Max] General Discussion / Re: Problem with corona render 7

« on: 2021-10-07, 03:17:56 »

Hi,

I have several bottles on my scene that caused this problem. Since my main scene is too large, I can send you test scene on which I've managed to recreate the problem. This works in interactive as well, so no need to actually render the scene.
I used max 2022, my friend tested it in 2018 with the same issue.
Btw, I installed V8 daily build and that fixed the issue.


I am not sure whether there is official way to send you the scene or not, but I hope dropbox link is ok. Let me know
https://www.dropbox.com/s/hywkzcuerx7jgk5/CORONA_ERROR.zip?dl=0

3

[Max] I need help! / Re: RAM problem

« on: 2021-10-06, 18:50:08 »

Hi Rowmanns,

I am testing v8 daily buildright now. It seems like there are no issues now. I will test it more later, but for now, no problem. All works well. Wooohooo.

Cheers

4

[Max] I need help! / Re: RAM problem

« on: 2021-10-06, 15:28:27 »

I posted the solution that worked for me in another thread, but here it is again.

The problem in my case was the map in Base IOR slot of Corona Physical Mat. It was coronamix map with falloff map hooked in mix ( not sure if it matters in which spot it is hooked).
Anyway, I copied the object to a new scene, tried it without coronamix with falloff, and it worked, but as soon as I connect the map to Base IOR slot, in about 10-15 seconds, render stops, memory consumption goes through the roof, and 3ds max stops working.

I hope this helps. Check the materials after importing it to a new scene to save yourself from pain :D

5

[Max] General Discussion / Re: Problem with corona render 7

« on: 2021-10-06, 14:31:43 »

I think I got the solution.
I found out that some materials (corona physical in my case) have a CoronaMix map (with Falloff map hooked in the mix slot) in Base IOR. I can't remember whether I converted those from Vray or Corona Legacy. I tested the scene with one simple object (bottle in my case), and the problem was there almost immediately.
3ds max starts to ramp up in memory consumption until the whole ram is gone. CPU stops as soon as memory consumption starts to ramp up and max is unresponsive. (Happened on rebus farm as well)

God damn, lost hours and a lot of hair trying to figure this one out. Had to copy few by few objects from the main scene to an empty scene and render test it until I found an issue.

I really hope this will help

Cheers

6

[Max] I need help! / Re: RAM problem

« on: 2021-10-06, 11:17:21 »

I have the same issue.
It all starts ok with 26-28 gm of ram free until it just starts eating ram at a random time. Sometimes at pass 30, sometimes 70, 82... and CPU utilization goes way down ( 5% or so ). I must kill the process manually.

I used corona 7 when this happened first time, and tried hotfix 1 as well, but no luck.

I have absolutely no idea what the problem is. I completely disabled all displacement on the scene, although I doubt that is the problem.

7

[Max] General Discussion / Re: Problem with corona render 7

« on: 2021-10-06, 05:47:04 »

I have similar (or the same ) issue. My render starts with around 24-25gb free ram memory. At certain point memory usage starts to rise untill I am left with 300-400mb of free memory, and cpu goes down to 0% utilization, after which I have to kill the process manually. This happened to me on the same scene 3 times at around pass 80. First part of rendering goes smooth. I rendered substantially complexed scene without any issue.
Usually, I get excessive ram usage message at the very beggining of the scene is not optimized, but the render still continues ( no crash so far ).
I optimized the scene a bit. Let’s see if it happens again.

Btw, this happened to me on v7 and v7 hotfix1