[Ernesto]

One thing that I have found is that the FIRE window cannot update correctly a scene in which such a objects properties are being changed.
If I stop the FIRE window and relaunch it after each change it worked OK perfectly.

The other thing I have seen is that when the objects are double sided everything works OK, but if some or one of the objects is single sided, unexpected results may appear.
I will create a new model in the complex scene so that all the objects are Double Sided, and will see if that was the problem or not.

Ernesto

[eric nixon]

All surfaces are double sided when rendered, there are no single sided surfaces, it doesnt matter how its modelled.

[gotoxy av-media]

are you aware of this:

Version 2.7.8

the Maxwell-specific attributes are always present in Maya 2012 and above, so they can be manipulated directly with setAttr and they show up in the spreadsheet editor
the UI controls for the Maxwell-specific attributes behave just like the controls for the built-in attributes in Maya 2013 and above, so there's no need to use the Extra Attributes rollup anymore
render flags can be set on transform nodes, overriding the settings for all the children of the transform
FBX import and export supports Maxwell materials
geometry and materials can be imported from MXS files
fixed: the hide to secondary rays, GI and z-clip flags were not working on MXS references
fixed: a Maxwell viewport was created every time the settings window was closed


Note: the FBX import/export feature was added to be able to exchange scenes in FBX format between Max and Maya. In order for it to work, you will need to upgrade the FBX plug-ins in both Max and Maya to version 2013.3 from this page.


Report this post

munch

[hatts]

One thing that I have found is that the FIRE window cannot update correctly a scene in which such a objects properties are being changed.
If I stop the FIRE window and relaunch it after each change it worked OK perfectly.

This is normal. FIRE only updates material/lighting changes. Not sure which application you're using, but there should be a "re-export geometry" button either on the FIRE window or somewhere else. This button does the same thing as closing and re-opening FIRE.

If you change object properties, or geometry, Maxwell basically has to re-send that information to the renderer, which is why it doesn't update instantly; the new geometrical information changes the calculation of the whole scene.

[Ernesto]

Thanks eric nixon
Yes you are right. I didn´t explained very well:
I should have said that most Maxwell Materials needs a closed volume to work properly, with the exception of AGS and perhaps some other material. In case of a closed volume we will have two planes, but is AGS we would have a single plane. In my old version I was using single planes, but the materials were not AGS, so perhaps that could be generating some problems. Now I am changing to double planes to simulate a "solid", expecting that Maxwell materials would behabe better.

Thanks hatts.
It is good to know how it is working the FIRE window. I am using Maya, and will look forward the "re-export geometry" buttton you mention, which will be more confortable than stoping and relaunching fire each time a change is performed.

Thanks gotoxy av-media
No, I wasn´t! I am using Maya 2012.
Very Interesting! This makes things more complex, but we have a wider choise.

Just for the records: It seems that the problem I am facing could have been originated in the process of upgrading. When I start a file from scratch everything seemms to work, but when I use my updated file (from Maya 8 to 2012, and from Maxwell v1.7 to V 2.7, all together) I get inconsistent behaviour. (perhaps It was too much for a single upgrade)
Now I am in the process to create a "clean" file trying not to re-model everything from scratch.
I wonder if we have an easy way to PURGE all the Maxwell V1.7 settings/components/materials etc from an old Maya file (Maya 8) ?
For now I am trying to export Geometry only...

E

[tom]

One thing that I have found is that the FIRE window cannot update correctly a scene in which such a objects properties are being changed.
If I stop the FIRE window and relaunch it after each change it worked OK perfectly.

This is a known issue and it's very confusing for your task. I strongly suggest relying on final render.

[Ernesto]

Good idea Tom!
It will be hard to come back to the old working way, since the Fire is a so GREAT feature, that it changed my workflow and time invested in setting up the scene.

E

[tom]

It will be hard to come back to the old working way, since the Fire is a so GREAT feature, that it changed my workflow and time invested in setting up the scene.

For the record...