![]() |
|
FumeFx Script Properties Questions - Printable Version +- Sitni Sati Forums (https://forum.afterworks.com) +-- Forum: Products (https://forum.afterworks.com/forumdisplay.php?fid=4) +--- Forum: FumeFX [max] (https://forum.afterworks.com/forumdisplay.php?fid=8) +--- Thread: FumeFx Script Properties Questions (/showthread.php?tid=965) |
FumeFx Script Properties Questions - Galagast - 11-07-2009 I'm probably having a very cloudy day in head because I can't seem to find these maxscript properties from the fume UI: Code: -- using this command on a selected fumefx nodeCode: PreviewStartSolverType - Galagast - 11-07-2009 This property is also strange: Code: SolverTypeFor example, Pflow's Position Object location property has 9 items. Executing this code would make it blank.(Index is 0 -based) Code: $'Position Object 01'.location = 10ExportRenderingParams - Galagast - 11-07-2009 I also noticed this: Code: ExportRenderingParams )What is this function for? SystemScale - Galagast - 11-07-2009 By far, this property is the most interesting one as it seems to have a direct effect on the sim. Pretty simple setup, using 3 identical sim grids (default settings).. the only difference is the systemScale value set via maxscript: ![]()
Re: FumeFx Script Properties Questions - superhypersam - 11-07-2009 that last test is interesting. So would it be possible to have a fume grid at one physical scale ( matching scene geo) but act as if it at another scale Via the maxscript command? cheers sam Re: FumeFx Script Properties Questions - Galagast - 11-07-2009 Yeah, looking at the comparison sims above, the effect probably goes like this: Smaller Values = Large Scale (Plumes) Bigger Values = Small Scale (Candle) The scene above all have 1.5 spacing. My system units is in centimeters. Here's a larger render: ![]() It would be interesting to do an experiment to see if there are differences when scaling it using these: Code: $.scaleRe: ExportRenderingParams - sitnisati - 11-07-2009 Galagast Wrote:I also noticed this: This will export all rendering params, including gradients and TM to a file. It is here because some companies use their own shaders, or even RMan and with this command they can export all relevant params. Re: FumeFx Script Properties Questions - sitnisati - 11-07-2009 Hello, Some params that are visible from MXS and not documented are not officially supported, and/or they're used internally. Kresimir Re: FumeFx Script Properties Questions - Galagast - 11-07-2009 >Some params that are visible from MXS and not documented are not officially supported, and/or they're used internally. Thanks for the info regarding that, I guess it leaves us users to play with it at our own risks.
Re: FumeFx Script Properties Questions - sitnisati - 11-09-2009 You're welcome
Re: FumeFx Script Properties Questions - jrand - 11-10-2009 Interesting discovery/concept Jeff
Re: FumeFx Script Properties Questions - Galagast - 11-25-2009 Quote:Interesting discovery/concept JeffThanks Johnny! It's feels like a new feature that we could play around with. hehe Quote:This will export all rendering params, including gradients and TM to a file.I was just wondering, it seems to always return false, even though the file was successfully created. Code: $.ExportRenderingParams @"c:\test.txt"Re: FumeFx Script Properties Questions - sitnisati - 11-27-2009 Thanks for you finding - I will check why it always returns false. Re: FumeFx Script Properties Questions - amelnychuk - 07-20-2010 OOOOOOOOOOOOooooooooooo yes yes yes you confirmed my suspicions about systemscale. yes yes yes yes.... |