[JTB]

I use the latest plugin... I made a scene of 100 3d trees and I had problems rendering the scene... Max seems to freeze...
When I set motion blur to "Off" from the plugin, Maxwell starts after 1 second!!!
I will try to verify this.... Is there something I 've missed? Is this a known issue?

[Mihnea Balta]

It's not a known issue. Could you send us a scene which triggers the problem?

[JTB]

There is no specific scene...
So, I send you a file containing a sample scene with a 3d tree, to do what I did... I also send you a demonstration of the problem as a video-exe file... What I want you to see is
1. How long it takes to export the scene from Max... Look how long it takes for the voxelization... and finally... Nothing!!!
2. When I change motion blur to "Off" everything goes so fast...

I use MAX design 2010 and the latest plugin but I don't think that matters...

http://www.divshare.com/download/9577058-56a

[Mihnea Balta]

Motion blur is incompatible with instancing, so when you enable it, the instances are exported as real geometry. That's why the scene takes longer to export when you enable motion blur, and why voxelization is slower. However, there's a bug which causes the instances to disappear when they're forced to real geometry, we're investigating it now.

[Mihnea Balta]

We've identified the bug and it's fixed for the next update. In the mean time, if you want to use motion blur in a scene which contains Max instances, you have to manually uncheck "use instancing" in the render options, otherwise the instances will be invisible.

LE: to make things a bit clearer: if you do not need motion blur, make sure it's off. By default, newly created layers and objects have motion blur off, so you don't need to worry about them. However, in your scene, the objects have per-layer motion blur, and motion blur is enabled for the layer. If you want to render with motion blur, that's OK, but if not, it will increase the render time and disable instancing even if the objects don't actually move.

[JTB]

Thanks a lot, I don't need motion blur but I need instances so Motion blur has to go...
Great news to see that bug fixed so quickly...