[feedback] Heavy scene (scattered vegetation) throws IR into a flickering loop.

I’m having big problems with heavy scenes and interactive rendering. I have a few trees (instanced proxies) and a lawn with a corona scatter scattering grass tufts. Sometimes it works, but most of the time Corona just gets stuck in a loop and 3ds max starts flickering and blinking every ten seconds or so. Even if I turn off the scatterer and keep just the trees (20 or so), it’s just stuck. I’ve included a screenshot of my task manager while it happens and as you can see, it loops and never goes above 50% ram.

While this is happening, the VFB and max gets unresponsive and I have to hammer the “Stop” button until it registers.

I think I started another thread about this when I first started trying Corona, but I can’t find it now. When I ran into this problem that time I was on a different computer, using a different operating system, working on a different scene, but got the exact same thing.

Can you create a minidump and send it to me (see my signature)?

Sure. I’ll do it as soon as I can.

Ok, I hade time to make a mini dump. Where should I send it?

Edit: It’s a different scene, I can send a mini dump for the other scene as well, if you need it.

You can send the minidumps (the more the better!) here: Renderer for architectural visualization - Corona | Chaos
Then please notify us in this thread.

Ok, uploaded. I didn’t get a confirmation that everything went well, but I hope it got there.

sorry, we didnt get it. Can you try again (And post the filename here)?

Ok, I uploaded to the dropbox instead. I forgot to change the name, so it’s “3dsmax.dmp”.

Just a tip: it’s usually good to pack the .dmp file into .zip or .rar and give it some distinct name. Packed dmp files can often get 100 times smaller.

Hello again. I’m just curious if you have any idea what is causing this and if there is a fix coming for 1.6? It happens in all projects that are a bit heavy and it’s making IR useless for me, basically.

yep, give us a month or two, fix is definitely planned

Great news, thanks!

are you rendering through a physical/vray camera? Does the problem go away if you use free view or standard camera?

Hi,
are you still having this issue? I see from the minidump that you were using some really old (november 2016) version