[3dtrialpractice]

WOW I AM DIGGING THIS FIRE!! THANK YOU FOR THIS EXCITING UPDATE...
just a few minor things:

bug a) the slider for WATTS in the Emiter Color+Luminance Tab attribute editor property goes from 40 (default) to a zillion no matter how tiny of a scrub I make.. if i touch the slider it will go off crazy .. so i must set slider by numeric value (so in FIRE rendering its hard to scrub your intensity till you find a nice point to stay at)

bug b) if you have the Camera RESOLUTION GATE displayed in your maya window view.. you can see it(a resoltion gate) in the FIRE window at an INCORRECT POSITION ... and to turn OFF the resolution gate you must UNCHECK "display gate mask" in the Camera's DISPLAY OPTIONS attribute editor tab

bug c) FIRE render don't look 100% as same compostion as what is rendered (looks like vertically it renders more view than in final render IE: so if something is touching the top frame of the resolution gate or the maxwell engine render it is not quite touching the top of the FIRE render frame) - not a big deal ..but if one does screen grab to comp w final render..its gonna require croping


***question/REQUEST: is there a "save jpg" FIRE render window option? or ez way to save what is in our window as a image file other than screen capture it?

using: Maya 2011x64 on Win 7x64

[Mihnea Balta]

bug a) the slider for WATTS in the Emiter Color+Luminance Tab attribute editor property goes from 40 (default) to a zillion no matter how tiny of a scrub I make.. if i touch the slider it will go off crazy .. so i must set slider by numeric value (so in FIRE rendering its hard to scrub your intensity till you find a nice point to stay at)

That's not really a bug, it's because the range of the wattage attribute is huge. The right end of the slider corresponds to a value of 1000000000 watts, so any small movement in the slider causes a large change in the value. Fortunately, Maya allows nodes to specify a "soft range" for a parameter, so that the slider corresponds to a smaller range, but the field still allows large values to be typed in. We're not using this yet, but we will in future versions.

bug b) if you have the Camera RESOLUTION GATE displayed in your maya window view.. you can see it(a resoltion gate) in the FIRE window at an INCORRECT POSITION ... and to turn OFF the resolution gate you must UNCHECK "display gate mask" in the Camera's DISPLAY OPTIONS attribute editor tab

That's correct, the gates displayed on the FIRE viewports are wrong. We'll see how we can fix this.

bug c) FIRE render don't look 100% as same compostion as what is rendered (looks like vertically it renders more view than in final render IE: so if something is touching the top frame of the resolution gate or the maxwell engine render it is not quite touching the top of the FIRE render frame) - not a big deal ..but if one does screen grab to comp w final render..its gonna require croping

That's because the FIRE render resolution is the viewport size, not the resolution specified in the render globals (otherwise we would have to scale or letterbox the image). The resolution mismatch (and, more importantly, aspect ratio mismatch) results in the framing mismatch. It's not a bug, it's a feature. :)

***question/REQUEST: is there a "save jpg" FIRE render window option? or ez way to save what is in our window as a image file other than screen capture it?

Not at the moment, but we will add this option in the future. The FIRE viewport was intended to provide quick feedback when setting up lighting and materials, not necessarily to produce draft renders, which is why the features you mention in this post haven't received that much attention.

[3dtrialpractice]

thank you for your response and attention to our posts!
this is really exciting now to have maxwell fire in MAYA plugin integrated so well!

really thank you all for your work!

>>>RE bug b: "That's correct, the gates displayed on the FIRE viewports are wrong. We'll see how we can fix this."

luckly right now its not a big deal as i wrote above that when I disable the resolution gate MASK in camera attribute editor - the gate display goes away in the FIRE window.. so its easy to get rid of in the FIRE window and really not a big deal for me not to have a gate mask in my viewport window

>>>RE bug c: "That's because the FIRE render resolution is the viewport size, not the resolution specified in the render globals"
hmm it matchs horizontaly .. even if i have overscann turned on ..wouldnt it match viewport if overscan was on/off?
i understand your response..it makes sense that the FIRE would be a match to viewport.

>>>RE save as jpg: i acctually like how the DOF is handeled in the FIRE rendered better than how production looks at times ( its fuzzier) so it would be great to have a save image option in FIRE... OR is there somewhere that the temp file of what is being rendered is stored (im guessing its a temp MXI file)