[choo-chee]

couldn't resist to try it (yeah I'm still with 1.7- waiting for budget for 2)
3 problems I noticed:
1) if fire is running then material library is very slow to appear
2) if sun is used with "track object" then you have to click "track object" again and again to refresh fire
3) i think that "not affected by Z-clip" flag is ignored or something
it looks promising i think i'm gonna upgrade ...

[Mihnea Balta]

1) if fire is running then material library is very slow to appear

Try telling FIRE to use fewer threads than the number of cores in your machine, to leave one or two cores free for Maya, the library browser etc.

2) if sun is used with "track object" then you have to click "track object" again and again to refresh fire

This is going to be fixed in the next update.

3) i think that "not affected by Z-clip" flag is ignored or something

We'll look into this.

[choo-chee]

great. is there a new promo planned for fire ? maybe worth waiting a bit more ...

[Mihnea Balta]

I have no idea about any upcoming offers, but even if there were plans like this, I don't think I'd be allowed to talk about them. :)

I've tested the zclip flag now and it seems to work here. Can you give me more details about how to reproduce the problem?

[choo-chee]

ah, I just tried one of my own scenes so maybe it was some issue with 1.7 --> 2.5 trial ?
the check mark for "unaffected by Z clip" simply didn't work for some objects and they got clipped.

[choo-chee]

btw I've noticed (long time ago with maxwell in general), when you launch a (maxwell) render and then close maya- the maya process remains running in the task manager. I don't know if it's maya bug or maxwell bug ... but you have to close it manually to get the lost memory back .

[Mihnea Balta]

That's because the plug-in wants to manage running renders, so that it can read back images, clean up temporary scene files and so on. There's a problem which prevents it from detaching the running renders when you try to close Maya, we will look into it.