Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

StatustitleParticle Shader  StatustitleFLIP SolverOfficial release

Date – 29 Oct, 2018

Download – Build 3.12.00

 

With Phoenix FD 3.12 we have focused on adding many frequently requested features, improving usability and integration in 3ds Max.


 

Ocean Mesh with Physical Camera and all V-Ray camera types

The ocean mesh in Phoenix is generated in camera space, so it needs to be aware of all the camera options and all camera types. With Phoenix FD 3.12, the Ocean Mesh mode now supports all parameters of the V-Ray Physical Camera and the built-in 3ds Max Physical Camera.

We've also added support for all V-Ray camera types that are available under the V-Ray Render SettingsSpherical, Cylindrical, Box, Fisheye, Warped spherical, Ortho, 360 Virtual Reality Spherical Panorama and Cube 6x1 cameras.

 


 

Instancing and referencing of Phoenix FD Simulators

In versions prior to 3.12, Phoenix FD could only instance Simulators in Mesh render mode. Now you can manually instance Simulators across the scene for preview and rendering in both Volumetric render modes, as well as the Isosurface and Ocean Mesh modes.

Additionally, now you can have Simulators instanced for simulation as well. This means all Simulators will share one cache sequence and the same simulation settings, but each Simulator instance will interact with the obstacles, emitters and forces inside its own grid.

Note that instancing of Simulators using VRayInstancer is currently being implemented in V-Ray and will be available soon.

 


 

Support for Scene and Object XRefs

Adding the ability to instance Simulators in 3ds Max also paves the way for being able to XRef Simulators and Particle Shaders. Caches loaded by the Simulators will be correctly picked in object and scene XRefs by the volumetric shader and Particle Shaders when using explicit cache paths or using the default $(...) Phoenix macros.

Note that if you manually merge the XRefs into a scene where they were XRef-ed into, any $(dir) or $(scene) macros of XRef-ed Simulators will be automatically unrolled to the full directory and scene name of the XRef-ed scene, so Simulators will be able to find their caches from inside the new scene they were merged into.

 


 

Textures support for volumes on V-Ray Next GPU

Now texture mapping the color and opacity of fire and smoke works on V-Ray Next GPU as well. Requires a V-Ray Next nightly build.

 


 

Complete changelog:

 

Status
colourGreen
titleNew
 
Status
titleGPU Volumetrics
 Support for textures for volume rendering with V-Ray Next GPU

Status
colourGreen
titleNew
 
Status
titleOcean Mesher
 Support for all parameters of the V-Ray and 3ds Max Physical Camera types when creating an Ocean Mesh

Status
colourGreen
titleNew
 
Status
titleOcean Mesher
 Support for all V-Ray camera types when creating an Ocean Mesh - Spherical, Cylindrical, Box, Fish eye, Warped spherical, Ortho, Spherical panorama, Cube 6x1

Status
colourGreen
titleNew
 
Status
titleSim Instancing
 Instancing and referencing for rendering and preview of Simulators in non-mesh render modes

Status
colourGreen
titleNew
 
Status
titleSim Instancing
 Instancing and referencing of Simulators during simulation

Status
colourGreen
titleNew
 
Status
title3ds Max Integration
 Support for Simulators and Particle Shaders in Scene and Object XRefs

Status
colourGreen
titleNew
 
Status
titleScripting
 MaxScript interface for getting grid data and loading render presets directly from the Simulator nodes. The new functions are loadRenderPreset, setCoordSys, getVelocity, getRGB, getTemperature, getSmoke, getFuel

Status
colourGreen
titleNew
 
Status
titleScripting
 New MaxScript functions for saving a Simulator render preset to file - <node>.saveRenderPreset <path> and A_SaveRenderPreset <node> <path>

Status
colourGreen
titleNew
 
Status
titleScripting
 New MaxScript functions for saving and loading a Simulator's simulation preset to file - loadSimPreset, saveSimPreset, A_LoadRenderPreset, A_SaveRenderPreset

 

Status
colourYellow
titleImproveD
 
Status
titleFLIP Solver
 WetMap now has different sticky effect against different liquid viscosities

Status
colourYellow
titleImproveD
 
Status
titleVolumetric Shader
 Exposed the hidden grid-based motion blur algorithm from Phoenix FD 3.00.01 for use via the 'mbgrid' script parameter

Status
colourYellow
titleImproveD
 
Status
titleSources
 Discharge Modifiers by Particle Size

Status
colourYellow
titleImproveD
 
Status
titleCache I/O
 Support for the new transformation model of OpenVDB caches from FumeFX 5

Status
colourYellow
titleImproveD
 
Status
titleCache I/O
 New default $(scene_path) macro for simulation cache Output expands to "$(scene)_Phoenix_frames" directory and does not use the node handle in the cache name

Status
colourYellow
titleImproveD
 
Status
titleParticle Nodes
 Converted the Particle Group nodes to a new node type instead of being Simulator instances

Status
colourYellow
titleImproveD
 
Status
titleTools
 Cache Converter now requires source and destination files and is verbose by default

Status
colourYellow
titleImproveD
 
Status
titleUser Interface
 Particle Shaders created by enabling Foam or Splash, or by Quick Setup presets, are now named after the simulator with 'Foam/Splash/Mist Shader' appended

Status
colourYellow
titleImproveD
 
Status
titleUser Interface
 Renamed the Foam and Splash 'Outside Life' option to 'Max Outside Age'

Status
colourYellow
titleImproveD
 
Status
titleUser Interface
 Renamed 'Sticky Effect' and 'Sticky' to 'Sticky Liquid' and 'Sticky Foam' respectively

Status
colourYellow
titleImproveD
 
Status
titleUser Interface
 Renamed 'Boundary conditions' to 'Container Walls'

Status
colourYellow
titleImproveD
 
Status
titleSDK
 Exposed a new function - getVolRendSamplerFromNode() which takes a node as an argument in order to support Simulator instances

Status
colourYellow
titleImproveD
 
Status
titleInstaller
 Show a warning when installing Phoenix for V-Ray 3 together with V-Ray Next and vice versa

 

Status
colourRed
titlefixed
 
Status
titleFLIP Solver
 Liquid particles got deleted on contact with deforming geometries, Alembic and Point Caches

Status
colourRed
titlefixed
 
Status
titleFLIP Solver
 Liquid sources emitted in pulses when adaptive grid resizes, since Phoenix FD 3.11

Status
colourRed
titlefixed
 
Status
titleFLIP Solver
: Could not emit liquid from particle systems, since Phoenix FD 3.11

Status
colourRed
titlefixed
 
Status
titleFLIP Solver
 If the Liquid Simulator's cache Output path could not be written to, no error was shown and the simulation continued, since Phoenix FD 3.11

Status
colourRed
titlefixed
 
Status
titleFLIP Solver
 Surface Tension Droplet Breakup caused liquid drops in zero gravity to take diamond shapes

Status
colourRed
titlefixed
 
Status
titleFLIP Solver
 Confine Geometries used by Liquid Simulators were not internally set to Solid like Fire/Smoke Simulators do

Status
colourRed
titlefixed
 
Status
titleFLIP Solver
 Solid geometry without Clear Inside did not create liquid voxels under the Fillup for Ocean level

Status
colourRed
titlefixed
 
Status
titleFLIP Solver
 Liquid was created in voxels covered by Confine Geometry when Fillup for Ocean was used

Status
colourRed
titlefixed
 
Status
titleFLIP Solver
 Significant difference in the simulation between Sticky Liquid set to 0.001 and 0.002

Status
colourRed
titlefixed
 
Status
titlegrid Solver
 Crash when Resimulating with Adaptive Grid with Preallocation and the result grid was over 2.1 billion voxels

Status
colourRed
titlefixed
 
Status
titleVolumetric Shader
 Missing buckets with moving Simulator in Volumetric Geometry mode and Motion Blur

Status
colourRed
titlefixed
 
Status
titleGPU Volumetrics
 Wrong cache file was rendered with V-Ray Next GPU when Resimulation was enabled, Play Speed was not 1.0 and Use Time Bend Controls was On

Status
colourRed
titlefixed
 
Status
titleGPU Volumetrics
 Warning about Emit light not supported on V-Ray Next GPU was shown when rendering in Mesh mode

Status
colourRed
titlefixed
 
Status
titleGPU Volumetrics
 Volumes didn't render in V-Ray Next GPU in scenes where Particle Shaders referenced missing caches

Status
colourRed
titlefixed
 
Status
titleGPU Volumetrics
 Incorrect light intensity with Approximate Scattering using V-Ray Next GPU

Status
colourRed
titlefixed
 
Status
titleParticle Shader
 The Size Multiplier of a Particle Shader animated by Particle Age did not work correctly for particles born on negative frames

Status
colourRed
titlefixed
 
Status
titleParticle Shader
 Rare infinite loop when rendering particles in Bubble mode with V-Ray Next

Status
colourRed
titlefixed
 
Status
titleParticle Shader
 Point Mode and Fog Mode did not render when Render as Geometry was enabled

Status
colourRed
titlefixed
 
Status
titleParticle Shader
 Rendering in Bubbles Mode, then rendering in Fog Mode, and then again rendering in Bubbles Mode still rendered the fog when Render as Geometry was enabled

Status
colourRed
titlefixed
 
Status
titleParticle Shader
 Crash with Particle Shader in Geometry Mode and geometry with VRayMtl with V-Ray Edges Tex rounded edges bump since Phoenix FD 3.10

Status
colourRed
titlefixed
 
Status
titleIsosurface Rendering
 Render Cutter in Isosurface mode of a Simulator with VRayMtl with Affect Shadows blocked GI rays for geometry inside the Cutter with V-Ray Next

Status
colourRed
titlefixed
 
Status
titleRender Elements
 Buckets in VRayLightSelect render element when rendering the Simulator in Volumetric Geometry mode with Phoenix Light Cache enabled

Status
colourRed
titlefixed
 
Status
titleRender Elements
 The Simulator's Shadow, Raw Shadow, GI, and Raw GI render elements didn't render correctly in Volumetric Geometry mode with Phoenix Light Cache enabled

Status
colourRed
titlefixed
 
Status
titleRender Elements
 The Simulator's Shadow, Raw Shadow, GI, and Raw GI render elements didn't render correctly with enabled Phoenix Light Cache

Status
colourRed
titlefixed
 
Status
titleRender Elements
 Random crash when rendering a Simulator in Volumetric Geometry mode with V-Ray Velocity Render element

Status
colourRed
titlefixed
 
Status
titleOcean Mesher
 The Simulator surface appeared rougher than the Ocean extension in the distance at a low angle with low Ocean Subdivs and low Horizon Roughness

Status
colourRed
titlefixed
 
Status
titleOcean Mesher
 Incorrect mesh velocity when rendering a moving Ocean or Cap mode Simulator with Motion Blur

Status
colourRed
titlefixed
 
Status
titleOcean Mesher
 The Underwater Goggles option did not account for the Off-Screen Margin option

Status
colourRed
titlefixed
 
Status
titleOcean Mesher
 Artifacts on the grid border when rendering in Ocean Mesh mode with Mesh Smoothing and Use Liquid Particles

Status
colourRed
titlefixed
 
Status
titleOcean Mesher
 Black artifacts near the horizon in Ocean Mode with Horizon Roughness and the camera was far from the Simulator origin

Status
colourRed
titlefixed
 
Status
titleOcean Mesher
 Noisy Phoenix Mesh displacement using an Ocean Texture when looking at tall waves from the side since Phoenix FD 3.03

Status
colourRed
titlefixed
 
Status
titleOcean Mesher
 Missing mesh polygons on the container border when rendering in Ocean Mesh mode with Mesh Smoothness above 0

Status
colourRed
titlefixed
 
Status
titleOcean Mesher
 Using Mesh Smoothing in Ocean Mesh or Cap Mesh render mode shrunk the mesh

Status
colourRed
titlefixed
 
Status
titleOcean Texture
 Artifacts when rendering Ocean with high Ocean Subdivs and high Ocean Texture Level of Detail

Status
colourRed
titlefixed
 
Status
titleGrid Texture
 Crash if using a Grid Texture sampling a 'Rendering ...' channel that used the same Grid Texture as Based On or Modulate texture

Status
colourRed
titlefixed
 
Status
titleGrid Texture
 Crash or a different render when re-rendering the same frame that used a Grid Texture

Status
colourRed
titlefixed
 
Status
titleGrid Texture
 Random crash after selecting a new Simulator in a Grid Texture

Status
colourRed
titlefixed
 
Status
titleGrid Texture
 Grid Texture did not update during sequence render if it was plugged into an Output map

Status
colourRed
titlefixed
 
Status
titleGrid Texture
 Grid Texture did not read the Rendering Color or Opacity channels from a Simulator in Mesh or Isosurface Mode

Status
colourRed
titlefixed
 
Status
titlePreview
 Incorrect preview when the Simulator's Pivot Point was Offset

Status
colourRed
titlefixed
 
Status
titlePreview
 The range for velocity preview was wrong then there was no velocity channel and auto-range was enabled

Status
colourRed
titlefixed
 
Status
titleCache I/O
 Caches containing digits after the # format could not be loaded

Status
colourRed
titlefixed
 
Status
titleCache I/O
 Caches containing a minus/dash sign before the # format could not be loaded

Status
colourRed
titlefixed
 
Status
titleParticle Nodes
 Crash after deleting a Simulator and one or more of its hidden PG nodes together

Status
colourRed
titlefixed
 
Status
titleStoke
 Phoenix Simulators could not be used as a Velocity Field Source in Stoke MX since Phoenix FD 3.05

Status
colourRed
titlefixed
 
Status
titleStoke
 Crash when simulating with Stoke MX using a Simulator with a Grid Texture in its material as a Velocity Field Source

Status
colourRed
titlefixed
 
Status
titleParticle Flow
 Emitting from Particle Flow systems where some events have no particles produces emission at coordinates 0,0,0

Status
colourRed
titlefixed
 
Status
titlePRT I/O
 PRT Export in the interval from frame 0 to frame 0 exported the entire timeline range

Status
colourRed
titlefixed
 
Status
titlePRT I/O
 After exporting once, the PRT Export dialogue became non-modal and another one could be opened, which could lead to crashes

Status
colourRed
titlefixed
 
Status
titletools
 Cache Converter required a missing aurloader.dll

Status
colourRed
titlefixed
 
Status
titlepresets
 Simulation or render presets had a different number of keyframes every time they were saved

Status
colourRed
titlefixed
 
Status
title3ds max integration
 Crash while running a simulation if selecting 'New scene'