By M_podgorczyk
#351105
hi,

I have just exported scene made on MAx 2011 nad Maxwell 2.6.12, i did by export Pack And GO and their are textures missing.
Now i try to run this scene od MAX 2012 and Maxwell 2.6.14 and this is what happens when i try to render:

Image

Uploaded with ImageShack.us
Any ideas what could i do to fix it?
#351180
The problem you have in your scene is that there are some proxy objects that point to nothing and the plugin assume they have to point to something (which is stupid) and it tries to do stuff and it crashes. I've found a workaround until we'll fix the problem in the next update. Try to delete all the proxy objects that point to nothing.

Here's the list of objects I found:
MxProxyObject001
MxProxyObject796
MxProxyObject797
MxProxyObject798
MxProxyObject799
MxProxyObject800
MxProxyObject801
MxProxyObject802
MxProxyObject803
MxProxyObject804
MxProxyObject891
MxProxyObject891

Thanks for sharing the scene.
By piranesi
#352069
Bogdan,

I have the same error. Same software. I haven't got any proxies in my scene.
max crashes when adding a multi/sub material to an object and I try to render.
I even get the same error when I try to export the file to a MXS file.

Please help because I can't figure it out.

Thanks!!

Jeroen
User avatar
By Bubbaloo
#352071
piranesi wrote:Bogdan,

I have the same error. Same software. I haven't got any proxies in my scene.
max crashes when adding a multi/sub material to an object and I try to render.
I even get the same error when I try to export the file to a MXS file.

Please help because I can't figure it out.

Thanks!!

Jeroen
Maxwell won't render a multi-sub material if it has an emitter material in it. Is that the issue you are having?
#352112
piranesi wrote: I have the same error. Same software. I haven't got any proxies in my scene.
max crashes when adding a multi/sub material to an object and I try to render.
I don't think it's the same error. The original crash was caused by a bug in the proxy code which we've fixed for the next update, so this must be different. Does Max crash when you try to render or export, or does Maxwell crash after that when rendering? Could you send us a simple scene which crashes?
By piranesi
#352145
I still have got the error I tested a very simple scene (attached to this post). I upgraded to 2.6.18 still the same error. There are no emitters in the scene.

Don't know if it's the same error mentioned above or not. I get the same message over and over. Only with multi-sub materials

I tested the scene on a 64bit windows comp with 3dsmax 64bit. On this computer the scene works fine!

What could be the problem?


The scene:http://www.box.com/s/35m7ofis8j34psv8ndl2

the error: http://www.box.com/s/zs4cv2nu9g0x3rahkcs6


Thanks for your replies!!

ps. If it is really an other error as mentioned in the title of this post, should I start a new post?
#352184
I can't reproduce the crash, your scene renders fine on my computer (Win7 64-bit, Max 2012, Maxwell 2.6.10, plug-in 2.6.18). Do you have regular Max, or Max Design? Do you have any other plug-ins installed aside from Maxwell?

When Max crashes, it creates a file called 3dsmax_minidump.dmp in your temporary directory. This temporary directory is usually C:\Users\NAME\AppData\Local\Temp, and can be reached easily by typing %temp% in the start menu search box. Please remove that file if it exists, trigger the crash again and send me the file that is written. It contains a snapshot of what the code was doing at the moment of the crash so it should be useful in tracking down the problem.
Help with swimming pool water

Hi Andreas " I would say the above "fake[…]

render engines and Maxwell

Other rendering engines are evolving day by day, m[…]