![]() ![]() Note that compressing the cache also requires processing time which will slow down the simulation. If you are using very high resolution grids and disk space becomes an issue, you can enable compression. In order to run a simulation on a locked cache, you have to uncheck this box first. If checked the current cache directory is locked against accidental overwrite. TFD will use the alternative base path if the main base path cannot be found or accessed. Since the paths will differ between the operating systems. This is useful for render farms that use a mix of MacOS and Windows. You can specify an alternative cache base path in the Alt. If you start a simulation without specifying a base directory or cache, the default base directory from the TurbulenceFD preference tab will be used and a new cache will be created automatically. Select the cache in the list that will be used for simulation and rendering.Įach cache is saved to a sub-directory of the base directory. In the list below, you can use the add/rename/remove buttons to manage the caches in the base directory. Specifies a base directory for all simulation caches of this TurbulenceFD object. While all frames are written to disk, TurbulenceFD will only keep a small number of frames in working memory and dynamically load frames from disk as necessary for rendering and in-editor previewing. The filenames contain the frame number, so you can easily identify every single frame, for example to continue the simulation from that frame at a later time (see General parameters above). bcf file contains all active channels (see Simulation parameters) and the velocity, if you enable it (see Cache Velocity below). ![]() Every additional channel uses another 8MB per frame.Įach frame is written to a separate. That's 2MegaVoxel x 4byte x 3 = 24MB for each frame - only for the velocity. The velocity channel is actually a vector channel, so it uses 3 times as much space. A 128x128x128 grid (2 MegaVoxel) basically corresponds to 128 bitmap images with 128x128 32bit (=4byte) pixels for each channel we cache. Moreso than rendering however, detailed voxel grids require a lot of memory. Just like high-quality rendering, fluid simulation is a computationally very intensive task. If the available memory is exceeded, the machine will most likely become unresponsive and you may have to reboot your system. When running simulations un-supervised, it's a good idea to make sure the container dimensions and simulation settings are chosen such that the avilable memory is sufficient. You can ignore the warning if you know that your simulation will stay small enough or if you're keeping an eye on the simulation progress, so you can abort the simulation if necessary. When starting the simulation, TurbulenceFD will warn you if the available memory would not suffice would the simulation take up the whole container. The last section shows the maximum size a single cache frame would have on disk without compression for a normal simulation and an Up-Res pass. The middle section shows the amount of memory the simulation will at most require when run on the CPU, the GPU or in Up-Res mode. The first section shows the maximum dimensions of the container in voxels and the total number of MegaVoxels or Million Voxels (MV). ![]() How much the simulation will actually need depends on how the simulation grows over time.ģ86圆49x395 99.0MV - CPU 7.9GB GPU 3.7GB UpRes 62.4GB - Cache/F: 1.9GB UpRes 14.9GB This field shows the maximum resolution (in voxels) that the container can use as well as the amounts of memory that it would use in this case. The fluid will stay in place or be clipped at the new container boundaries. If you're moving the container using the Grid Offset parameter, only the container will move. Moving the container as an object will move the container and the fluid in it. You can move the container object like any other object in the scene or you can this Grid Offset parameter. There are two ways of moving the fluid container in space during simulation. The info field Max Memory Usage shows the memory that the simulation would use if the simulation used all the space in this container. See the Clip Below parameters of the fluid channel tabs for more details. In most cases, the simulation will clip even more than that, trying to minimize the box that acutually needs to be simulated. The simulation will clip everything outside of this box. Specifies the size of the fluid container. When changing this value, the resolution will change accordingly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |