CoronaMapOutput and procedural textures

[VelvetElvis]

I'm mentoring some students on using various render engines, and since I'm using Corona more and more for personal work, I pushed them to test this one out. One of my students put a CoronaMapOutput on everything in the scene, including procedural maps (ie noise, cellular, etc) and when that is applied it virtually kills the entire scene. It takes forever to load and if you can get in max, it becomes so slow and sluggish it's unusable.

Why they did this, I'm not sure yet. I wouldn't think to do it that way, but leave it up to students to find new ways to use maps.

If it is a limitation of the CoronaMapOutput, perhaps a warning could appear before it kills your scene?

[Ondra]

it should not do this, how many maps were there approximately in the scene, so I can reproduce it? And how serious was the slowdown?

[VelvetElvis]

There was quite a few. Off the top of my head, I can't say how many. But it took about 2 hours to open the file and about 30-45 minutes just to select the material.

When I ran a test on a scene with just a cube with a noise map applied to the output, it pretty much shut down my max file for a while. It wasn't overly bad with the material editor or in the scene, though there was some slowdown. The real slowdown came when I enabled shaded mode and show maps in viewport.

[Ondra]

heh, ok, can you get me such scene?

[Ondra]

ok, I found probable source for this behaviour, it will be fixed in the next release.

[VelvetElvis]

Awesome! Thanks! Let me know if you want that scene and I can get it to you.

[Ondra]

if you can get it, send it to me, just to make sure this was the problem