Max 3.0.25 crash maxwell when using mxs references instances

18 posts

Re: Max 3.0.25 crash maxwell when using mxs references insta#382884

By zparrish - Tue Sep 09, 2014 8:26 pm

- Tue Sep 09, 2014 8:26 pm #382884

I just finished the MXM test and it had no effect on this issue. I compared three material options within an MXSRef:

1.) Imported from MXM
2.) MXM Reference (embedded in scene)
3.) MXM Reference (path reference to source MXM file)

All options worked correctly.

Regards,
Zack Parrish
-
Maxwell - 4.2.0.3
Maxwell 4 | 3ds Max - 4.2.4
336 capable Maxwell threads!
-
Workstation:
Dual E5-2680v3, 64GB, Quadro K5200
48 threads (HT) @ 139.2GHz
-
Render Farm:
288 threads (HT) @ 835.2GHz

Re: Max 3.0.25 crash maxwell when using mxs references insta#382887

By Mihnea Balta - Wed Sep 10, 2014 9:51 am

- Wed Sep 10, 2014 9:51 am #382887

It's the same bug. I was wrong, emitters are not required to trigger it, and neither are MXS references, for that matter. It's a voxelization problem which can be triggered in several ways. The new scene renders fine with the code from the development branch.

Re: Max 3.0.25 crash maxwell when using mxs references insta#382896

By zparrish - Wed Sep 10, 2014 2:36 pm

- Wed Sep 10, 2014 2:36 pm #382896

That's good news

At least I didn't discover a new bug, and the scene works in the dev branch. I'll just use references somewhat sparingly until the next core update comes out. We have plenty of space on our file server, so the increased disk size isn't really a problem for us. It's just nice to be able to cut down the sequence export time.

Thanks again for looking into this Mihnea! Take care!