TP 3 + Krakatoa 1.1

the good news:



Feb 15 version of Krakatoa renders TP 3.0 particles with motion blur.





bad news:


  1. Krak doesn’t see the TP color


  2. Krak “Density” exponent has no effect – TP particles are always rendered with the same density.





    this is Max 9 32-bit in WinXP 32-bit – I’m requesting a new license for our 64-bit machines…



    thanks


the good news:



Feb 15 version of Krakatoa

renders TP 3.0 particles with

motion blur.





Thanks for the good news!







bad news:


  1. Krak doesn’t see the TP

    color


  2. Krak “Density” exponent has

    no effect – TP particles are

    always rendered with the same

    density.





    Thanks for the bad news, too!

    We know about the color - there is currently no way to get to the color information that we know about, and we asked Cebas about a solution, too. In general, TP stores data in the mesh of the particle and there appears to be neither a color channel we could access, nor a way to get to the mesh of a particle and extract anything useful from there.

    At least the color override/material override in Krakatoa should affect them. Does that work for you?



    As for the Exponent, now this is surprising. We should definitely figure out what is going on with that. We have TP 2.5 on Max 8 and we will try to run Krakatoa 1.1 with it to see if it shows the same problem…

cool, cool





yes, the Material Override works as well as Custom Color, although I’ll test a gradient and Particle Age to see if those change the TP particle color over time…



would you like me to ask Cebas about the color channel stuff or are you in contact with them?



the density exponent is indeed strange… I don’t think that was working in Krak 1.0 either.



more soon…


We are looking into using the data channels to set color for the particles. This way you can apply arbitrary colors using the Particle Data operator.



In regards to the density problems, have you tried setting the exponent to -30? I would expect the particles to disappear completely.



Darcy

Hi Darcy,



Data Channel control for particle color would be great. In fact, any data needed from TP can easily be put in a Data Channel if that would help.



I was wrong about the density thing. Below 0 it scales down accordingly (and -10 to -30 is pretty much too small to see).



Exponent values at zero and above, however, yield the same results. 0 appears the same as 30! Weird, no?


Hi Darcy,



Data Channel control for

particle color would be great.

In fact, any data needed from

TP can easily be put in a Data

Channel if that would help.



I was wrong about the density

thing. Below 0 it scales down

accordingly (and -10 to -30 is

pretty much too small to see).



Exponent values at zero and

above, however, yield the same

results. 0 appears the same

as 30! Weird, no?





Not necessarily.



When a particle system does not have its own Density channel, Krakatoa assumes a density of 1.0. An exponent of 0 means 1.0 (10^0 = 1), so if you enter 1.0E0, you will get a density of 1.0. If you increase the exponent to 1,2,3 etc., you will get a density of 10,100,1000 etc, but a density of 1.0 already means opaque alpha, so having your particles even more opaque than they are already is rather difficult ;o)



High values would make sense only if the original particle system had a density channel containing very low values like 0.001 or something and you wanted to bump that up. But TP does not have such a channel (YET! :o) so we start with a default density of 1.0 here…



Going down with the exponent gives you more decimal positions, so -1,-2,-3 give you 0.1,0.01,0.001 and this results in an alpha channel that is a lot less than 1.0. Thus, when many particles occupy the same pixels, you get more opacity and single particles tend to get invisible.

thanks for the explanation! I had thought the Density would affect the “size” of the rendered dot and not just the opacity. Good to know, thanks.