issue with duplicated MXS references

issue with duplicated MXS references#369276

By choo-chee - Sun Jul 14, 2013 3:01 pm

- Sun Jul 14, 2013 3:01 pm #369276

well when motion blur is ON only the original MXS referenced object is rendered.
Duplicated (special) objects are not.

visit us at N-TRACE.com

Re: issue with duplicated MXS references#369288

By Mihnea Balta - Mon Jul 15, 2013 9:11 am

- Mon Jul 15, 2013 9:11 am #369288

There is a bug in the engine related to instanced MXS references when motion blur is on. The only workaround is to disable "Maya Instances to Maxwell Instances", but in that case the references will be copies, and will use more memory.

Re: issue with duplicated MXS references#369289

By choo-chee - Mon Jul 15, 2013 9:17 am

- Mon Jul 15, 2013 9:17 am #369289

can you tell me is there a fix coming for that bug...?
duplicating all the trees and other stuff I have will probably make my computer explode ...

visit us at N-TRACE.com

Re: issue with duplicated MXS references#369290

By Mihnea Balta - Mon Jul 15, 2013 9:24 am

- Mon Jul 15, 2013 9:24 am #369290

I don't know at this moment, but I will ask.

Re: issue with duplicated MXS references#369292

By AlexP - Mon Jul 15, 2013 10:44 am

- Mon Jul 15, 2013 10:44 am #369292

Is it related with camera motion blur or with object motion blur?

For sale: V3 node locked + V3 floating + 10 rendernodes
mastersfinger.com

Re: issue with duplicated MXS references#369294

By choo-chee - Mon Jul 15, 2013 10:56 am

- Mon Jul 15, 2013 10:56 am #369294

I have a car moving from left to right.
When the car is rendered without motion blur all the other refs. are good
When motion blur enabled than most of the refs. are gone and become small emitters ...

visit us at N-TRACE.com

Re: issue with duplicated MXS references#369295

By Mihnea Balta - Mon Jul 15, 2013 11:56 am

- Mon Jul 15, 2013 11:56 am #369295

It doesn't matter if the camera or object are moving. The issue appears when motion is exported for instances of MXS references, even if the motion is very small.

The problem could be avoided by turning off motion export for those instances, but the plug-in doesn't have this option at the moment. We'll try to add it for the next build, but I don't have an ETA for it yet.