Is it normal if my volumetric cube keep animating even I haven't added any time manipulation to it yet?
(Ignore this. It's because of the noise).
dean
Sept. 10th, 2020
This is incredible, I wonder if it's possible to create a procedural node based explosion without requiring baking.
Huân Lê-Vương
Sept. 10th, 2020
*@dean* He uploaded an explosion example in Chapter 4-4
Simon Thommes
Sept. 10th, 2020
*@Huân Lê-Vương* That example was to show baked simulations, it's not just a procedural shader!
Technically you could do something similar with nodes, but it would be much more difficult than this simple fire and would probably never look as good as actual simulation.
But if you want something more stylized then it might be a valid option.
Huân Lê-Vương
Sept. 10th, 2020
*@Simon Thommes* oh sorry!
Aron
Oct. 22nd, 2020
How power stretch vector space? add,substract and scale is intuitive how vector sapce manipulate.
(0~1,0) + (1,0)= (0~2,0) is just move (0~1,0) x (4,0) =(0~4,0)is just scale but 0~1 to power of 2 , 1 is 1 and 0,x is less then 1. I can't associate it to stretch the vector
what difference between scale the vector and stretch the vector?
I'm not good at eng but i hope this question delivered well :)
Huân Lê-Vương
Oct. 23rd, 2020
*@Aron* scale is "linear". power isn't linear. when scaling, the vector remain the same "shape" of it, just "bigger"/"smaller". power is we multiply the value to itself multiple time, imagine each coordinate will be scaled in a different way than the others may result in stretching the vector.
Aron
Oct. 23rd, 2020
*@Huân Lê-Vương* oh thanks for answer my question. 0~0.1 to power of 2 is 0~0.01 so 0~0.1 value range get shorter but 0.9~1 to power of 2 is 0.81~1 so 0.9~1 value range get longer , generally 0~1 value range is stretched lengthen. so top of fire animation is fatster then bottom
is it correct?
Huân Lê-Vương
Oct. 24th, 2020
*@Aron* for example, we create a plane. we take X value of the Generated. on the graph, the function of X is y=x with the limit from 0 to 1.
We power the value of X with the exponent of 2. now the function is y=x^2. limit from 0^2 to 1^2. the value still goes from 0 to 1 but look at the graph, it's stretched.
to see how it's stretched, just separate the y=x^2 into 10 steps of 0.1 using a snap operation (add a math node, change to snap, increment 0.1)
in the graph, as you mention above, at the first step of 0.1, y=0.1^2=0.01. so when x goes from 0 to 0.1, y only goes from 0 to 0.01.
At the last step 0.9 to 1, you see from 0.9^2 to 1^2 is 0.19. so the y goes 19 time faster than it does at the first step.
Aron
Oct. 24th, 2020
*@Huân Lê-Vương* great! thank you to solve my question!
Joel V Favela
July 28th, 2023
Hello! I have a problem in my file, I did the steps of the course but when I run the animation, it runs slower than the course and the reference file. I looked in the general settings and the animation setting (I changed the playback from "play every frame" to "Frame Dropping" but it didn't work), I couldn't find where the problem could be. Can you help me?
Simon Thommes
July 31st, 2023
@Joel V Favela That can have different reasons. If the example file works fine for you I assume it's not a hardware issue. Make sure that the framerate is set to the same value. The time mapping in the nodes itself could also be different, make sure the same values are used for the math in there.
When you render out a video in the example file and your file, are they the same speed then?
Join to comment publicly.
13 comments
Awesome!
Is it normal if my volumetric cube keep animating even I haven't added any time manipulation to it yet?
(Ignore this. It's because of the noise).
This is incredible, I wonder if it's possible to create a procedural node based explosion without requiring baking.
*@dean* He uploaded an explosion example in Chapter 4-4
*@Huân Lê-Vương* That example was to show baked simulations, it's not just a procedural shader!
Technically you could do something similar with nodes, but it would be much more difficult than this simple fire and would probably never look as good as actual simulation.
But if you want something more stylized then it might be a valid option.
*@Simon Thommes* oh sorry!
How power stretch vector space? add,substract and scale is intuitive how vector sapce manipulate.
(0~1,0) + (1,0)= (0~2,0) is just move (0~1,0) x (4,0) =(0~4,0)is just scale but 0~1 to power of 2 , 1 is 1 and 0,x is less then 1. I can't associate it to stretch the vector
what difference between scale the vector and stretch the vector?
I'm not good at eng but i hope this question delivered well :)
*@Aron* scale is "linear". power isn't linear. when scaling, the vector remain the same "shape" of it, just "bigger"/"smaller". power is we multiply the value to itself multiple time, imagine each coordinate will be scaled in a different way than the others may result in stretching the vector.
*@Huân Lê-Vương* oh thanks for answer my question. 0~0.1 to power of 2 is 0~0.01 so 0~0.1 value range get shorter but 0.9~1 to power of 2 is 0.81~1 so 0.9~1 value range get longer , generally 0~1 value range is stretched lengthen. so top of fire animation is fatster then bottom is it correct?
*@Aron* for example, we create a plane. we take X value of the Generated. on the graph, the function of X is y=x with the limit from 0 to 1.
We power the value of X with the exponent of 2. now the function is y=x^2. limit from 0^2 to 1^2. the value still goes from 0 to 1 but look at the graph, it's stretched.
to see how it's stretched, just separate the y=x^2 into 10 steps of 0.1 using a snap operation (add a math node, change to snap, increment 0.1)
in the graph, as you mention above, at the first step of 0.1, y=0.1^2=0.01. so when x goes from 0 to 0.1, y only goes from 0 to 0.01.
At the last step 0.9 to 1, you see from 0.9^2 to 1^2 is 0.19. so the y goes 19 time faster than it does at the first step.
*@Huân Lê-Vương* great! thank you to solve my question!
Hello! I have a problem in my file, I did the steps of the course but when I run the animation, it runs slower than the course and the reference file. I looked in the general settings and the animation setting (I changed the playback from "play every frame" to "Frame Dropping" but it didn't work), I couldn't find where the problem could be. Can you help me?
@Joel V Favela That can have different reasons. If the example file works fine for you I assume it's not a hardware issue. Make sure that the framerate is set to the same value. The time mapping in the nodes itself could also be different, make sure the same values are used for the math in there.
When you render out a video in the example file and your file, are they the same speed then?