Page 1 of 1

Maxwell studio - importing MXS causes a crash

Posted: Thu May 29, 2008 2:59 pm
by jjs
The plugin is now so usable - I have not actually really tried the Studio for some while- but today I wanted to try something and now I try to open an MXS file - I get

"Maxwell Studio has encountered a problem and needs to close. We are sorry for the inconeviance"


What are the common cause of this

Using Win xp64
SW plugin 1.6.6.0 x64

Jonathan

Posted: Thu May 29, 2008 3:10 pm
by JDHill
Hi Jonathan,

I am not aware of anything specific which would cause that. Does this same MXS render ok in MXCL? Are you dealing with a part or an assembly? If it is an assembly, you could try hiding different parts of it to try to find a culprit - if you find one, I would like to see it. Also try creating a different camera, and rendering that to see if there is any difference.

Let me know if you find any clues,

JD

Posted: Thu May 29, 2008 3:14 pm
by jjs
It render fine from the Plugin. Its just the MXS file created by the plugin cannot then be opened in the Studio.

I'll try to isolate the doggy part, starting with the 'Toolbox' parts - I've never trusted them :D


The log file has not indication of a problem and I have not used any 'assembly cuts'.


Jonathan

Posted: Thu May 29, 2008 3:51 pm
by JDHill
Thanks, Jonathan. As far as I know, assembly-cut should work now, except that you may get some strange texture-mapping behavior on parts which have been cut - I think SW has some basic issues with mapping them.

Posted: Fri May 30, 2008 1:09 pm
by jjs
JD - the problem seems to be in the SW Assembly

If I suppress all the parts - I can export the ASM to MXST from the plugin.

If I unsupress any part , it fails to export by crashing after the file has gone through the system .(I will PM the log file - its an NDA project)

If I open the SW part as itis own file - it then does export to the MXST from the plugin.


Shall I email the assembly to you - its a sw 2008 file?


Jonathan

Posted: Fri May 30, 2008 2:08 pm
by JDHill
Yes, I looked at the log you sent and there isn't any clue to be found, so if you can send me the assembly, that would be great.

Posted: Fri May 30, 2008 4:59 pm
by JDHill
Thanks for the files. Can you confirm that this works:

- open MXST
- open an unrelated MXS
- open the MXS which is causing this problem

Is it okay with you if I let one of the NL guys take a look at this MXS so we can try to figure out what's wrong with it?

Posted: Fri May 30, 2008 6:24 pm
by jjs
I'm afraid it did not work.

I opened and mxs file from an old project, then tried to open the 'corrupt' mxs but it caused a crash.

By all means pass on the assembly to Next Limit for dissection, however I have now tried another assembly on another project and it too will not export to MXST. I think it must be something on my system that is screwed.

It does not export Assemblies to MXST - but exporting PARTS works fine

Jonathan

Posted: Fri May 30, 2008 6:40 pm
by JDHill
Thanks Jonathan, I'll pass it on. I did get it to crash here - but only when the 'Vertex Buffers (OpenGL 1.5 required)' MXST OpenGL user-preference was disabled. With it enabled it works fine here - you would need to try different combinations there, depending on your system.

Posted: Fri May 30, 2008 8:21 pm
by jjs
still no luck - I've tried foddling with various preferances in MXST.

However I have noticed that it will import old MXS assembly files from dec 2007. Not that that will help track down the problem as it must be something in the new plug that is disagreeing with my machine


Jonathan