Hey Bob, another TERRIFIC TTT, cheers. A quik Q: when you inserted the change range node to interpret the particle speed data, is there a reason you didn't you use the 'Vector Change range' node instead? Since it comes after a Vector User Data node and a Vector Length node? Just curious about your thought process. Thanks in advance.
These Redshift/Xparticle tutorials are great! Keep them coming!
Please provide more updates on the usage of Redshift, which is very practical. Cycles are really inconvenient
Fab - many thanks for sharing!
Nice ! Very cool tutorial. I needed to know this for so long now. Thanks :)
Can Anyone share how long did it took to cache this 1000F Scene? For Benchmarks..
My System is MacBook Pro M3 Max and it took 5m 24s to cache.
Great Tutorial!!!! Does anyone know how to take the nxColor information and use it in Octane?
Ah Redshift!!!!! Finaly!
Hey Bob, another TERRIFIC TTT, cheers. A quik Q: when you inserted the change range node to interpret the particle speed data, is there a reason you didn't you use the 'Vector Change range' node instead? Since it comes after a Vector User Data node and a Vector Length node? Just curious about your thought process. Thanks in advance.
A Vector Change Range node changes the range for the individual x, y, z. We want to change the speed, which is a scalar - the vector length.
@@INSYDIUMLTD thanks for the reply and for being so clear about it, this is helpful. Cheers
😊
Great as always !!!
Love it!