3/1/2024 0 Comments Fluidsim examplesVertical movement is green: 0% up, 50% standing, 100% down. Horizontal movement is described by shades of red: a value of 50% means we are standing, 100% is full speed right, 0% is full speed left. Imagine that we are moving on a two-dimensional plane and our moving direction and speed (together called velocity) are described by colors. Creating a Simple Texture Sampling Emitter Unlike classic baked VFX, our systems could respond to physics. Instead of overwriting intrinsic velocity, we are pushing particles to sim defined directions while allowing collisions with scene geometry. Maybe the most spectacular example is using velocity data from a fluid simulation to accelerate particles. The point is that we are altering particle behaviour and not determining. Unlike geometry texturing, "particle texturing" should not be a one-to-one topological mapping between the texture space and the particle-space: fluid data could (1) provide initial conditions for a dynamic simulation, (2) drive abstract parameters or (3) used additively. We could drive masses of GPU particles with fluid data. Niagara provides an alternative use case: utilizing the Sample Texture Data Interface, we could directly sample fluid data with Niagara modules (no materials are needed) and interpret the texture-stored values as float / vector / color type variables to drive arbitrary particle parameters.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |