![]() |
|
[Bug] Maxscript Access to Smoke and Temprature Buoancy - 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: [Bug] Maxscript Access to Smoke and Temprature Buoancy (/showthread.php?tid=1145) |
[Bug] Maxscript Access to Smoke and Temprature Buoancy - Jordan - 04-05-2011 I mentioned this before but now I've had a bit more of a look at it I can see what the issue may be. Changing Smoke Buoyancy to 2 (or Temp Buoyancy..Fuel Buoyancy seems fine) prints out in the MAXScript listener: $.SmokeBuoyancy = 2 but setting this property via maxscript does not change anything. You can then query the value $.SmokeBuoyancy and it will return what you have set in maxscript but it will not be reflected in the UI, nor in the sim. I have had a look through the subanims and it seems setting $.SmokeBuoyancy is setting $[4][1].Smoke_Buoyancy when it should be setting $[4][3].Smoke_Buoyancy. It seems that $.Smokebuoyancy is not hooked up to $[4][3].Smoke_Buoyancy properly. With Temperature Buoyancy $.TemperatureBuoyancy is hooked up to $[4][1].Temperature_Buoyancy, not $[4][4].Temperature_Buoyancy. The other parameters in the smoke and Temp rollouts seem fine (apart from the vdMultiplier being duplicated so there is no access to the temp vdMultipler). Re: [Bug] Maxscript Access to Smoke and Temprature Buoancy - jrand - 04-06-2011 Hey Jordan, have you tried closing and re-opening the UI to see if the changes are reflected? Re: [Bug] Maxscript Access to Smoke and Temprature Buoancy - Jordan - 04-06-2011 Thats not the issue. Tried it if you run a sim and try $.SmokeBuoyancy = -50 and then $.SmokeBuoyancy = 50 while simming you will see no change. Its not writing its value to the correct paraBlock but the UI is (its just reporting the wrong maxscript property being change)
Re: [Bug] Maxscript Access to Smoke and Temprature Buoancy - jrand - 04-06-2011 aahhh, ok, I see what your saying, and I can confirm it too
Re: [Bug] Maxscript Access to Smoke and Temprature Buoancy - sitnisati - 04-07-2011 Thanks for report - this will be fixed for 2.1c (it's not yet in RC1) Kresimir |