![]() Phoenix always converts internally the units to a common world-size length, so the only important thing is how big the container is according to the Grid or Simulation rollouts. Note that it doesn't matter if this is two meters or two thousand millimeters - the way you view the units is irrelevant. If you are simulating a camp fire, your container should be at most a couple of meters wide. You can check the dimensions of the container in the Grid rollout, and also you can check the dimensions of an already simulated cache in the Simulation rollout. Instead, it overrides the existing files, because it does not change the channels used as source.īoth the Liquid and the Fire/Smoke simulators work best when the scale of the container matches the real-world size of the simulated effect. Liquid resimulation does not use separate path. This topic is regarding fire/smoke resimulation. These are all possible, you just need to have velocity in the base cache and an existing path to it. Of course, you may use more complicated setups where you resimulate over an already resimulated cache file, or you may Load an existing base cache file as the initial state of the re-simulation. ![]() ![]() The reason may be that either the files in the Resimulation's Input Path do not exist at all, or they do not have Velocity exported when you have simulated them beforehand. "Cannot start the Re-Simulation! Please make sure the simulation was run with the 'Velocity' channel checked under the 'Output' rollout, and that the cache files in the Resimulation Input path exist." The following error message may appear when you start a Resimulation: Also, beware that if the Resimulation Output Path coincides with the Resimulation Input Path, Phoenix will not prevent you from overwriting your existing cache files - it's valid to do so if you need a more complicated setup. Otherwise, if you enter your paths manually, please make sure that the Resimulation Input resolves to an existing cache sequence with exported Velocity channel (you can check the channels present in a cache file form the Simulation rollout). When resimulation is enabled, the preview and rendering will read from the Resimulation Output Path instead of the render Input.īy default, Phoenix reads the files in the $(same_as_output) path, which are already simulated by the regular simulation process, and then saves new *.aur caches in the $(scene_path) path with " _resim" appended at the end of the file name. Resimulation takes as input a sequence of *.aur, *.f3d, or *.vdb cache files, and processes them in order to improve the grid detail, change the time-scale of the animation, or run a particle simulation again without changing the grid content.ĭuring resimulation, Phoenix reads cache files in the Resimulation Input path, performs some of the above operations, and then saves a new cache sequence in the Resimulation Output path. Here is the basic flow:Ĭhanging the Default Phoenix Paths for Resimulation You may also manually change the render input path to a series of cache files that you have stored somewhere else previously, or to the cache files of a different simulator in the same scene, or even to a series of *.f3d or *.vdb files exported from other simulation software. So even if you change the output manually, the render will keep reading from the new location. By default, Phoenix looks for render/preview input files in the $(same_as_output) path, which is the path in the Output Rollout. The default paths and file names above are generated using the $(scene_path) macro as an output path, and there are other macros you can use as well, or just manually enter the path you need.Īfter Phoenix has created the *.aur frame cache files, you can preview them in the viewport and render them using V-Ray or the Scanline renderer of 3ds max. You can manually change the output path from the Output rollout. For example, a simulator named "PhoenixFD001" outputs these cache files: Inside the cache folder, the default names use the simulator's name. ![]() By default, the cache files are put in a folder next to the *.max scene with the same name as the scene and with "_Phoenix FD_frames" appended: Phoenix saves each simulated frame in a cache file with an *.aur extension, numbered using the frame index. This page provides tips on a variety of topics to help you get the most out of Phoenix. This page provides information on how to get the most out of Chaos Phoenix for 3ds Max.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |