Friday, May 21, 2010

FumeFX 2.0 for Autodesk 3ds Max is Here!!



One of the most successful plug-ins is back with a new release.



Here are just some of the exciting new features in FumeFX 2.0:

  • Wavelet Turbulence mode: Allows users to add extra detail to low resolution simulations without losing their original motion or timing.

  • Post processing: Gives users the ability to tighten (shrink) the FumeFX grid as much as possible around smoke and fire to limit memory consumption.

  • Retiming: Lets users slow down and speed up their FumeFX simulation caches.

  • Fuel-specific weight parameter: This parameter allows you to increase weight of the fuel causing it to be directly affected by the gravity.

  • New FumeFX_Burn WSM: Allows you to affect your mesh's vertex color based on FumeFX values.

  • New FumeFX Source: You can now use one FumeFX source as the source for another FumeFX simulation.

  • New Void Source: This helper will erase all the fields inside or outside of it (depending on the settings).

  • Temperature can now control where fire creates smoke. When temperature is above a set threshold, smoke will be added to the grid.

  • Turbulence and Forces are now visible inside the viewport even if grid is not simulated.

  • The FumeFX Object Source helper now can handle multiple objects in a single helper.

  • The FumeFX Particle Source helper now uses AfterBurn style controls.

  • Auto Synchronize Paths option now added to Global FumeFX Preferences so that when you change the Delault Output path, any Wavelet Turbulence, Retiming and Preview Window paths will be changed automatically as well.

  • In the Preferences dialog, you can now change Presets folder.

  • The FumeFX Preview Window will now update if you rotate the active viewport.

  • You can now change the Preview path from within the FumeFX UI

  • The Velocity channel has been added to the list of FusionWorks Render Elements.

  • Additional MAXScript commands have been added for superior scripted controls of the entire FumeFX 2.0 process.

No comments:

Post a Comment