Gone for a week & TP 2.5 testing scenes

Deprecated Krakatoa 1.0 Beta Discussion
1

hi,



I’m gone on vacation this week and return on Sunday.



Attached are some sample scenes for TP 2.5 using Max 8:


  1. “simple krakatoa TP 25.max”



    A simple scene using Matterwaves to emit particles at high speed. Used to test Krakatoa motion blur. Shutter is at 720 with 8 samples, but as of build 17 sp2 there was no moblur.




  2. “simple krakatoa TP 25 - NOSEED.max”



    Sample scene as above but NOSEED inserted into the TP dynamic set (DynSet), so the expected effect would be NO randomization… e.g. multiple partitions will yield the exact same result.




  3. “simple krakatoa TP 25 - save to BIN - missing gap.max”



    Simple scene that saves 4 partitions to a .bin sequence. But there is a problem if you view that .bin sequence in Realflow (or maybe a particle loader, or PFlow) – there are gaps in the particle stream around frames 44 and 79 (I think those are the exact frames). Anyway, there shouldn’t be a gap.





    The moblur and gap bugs were reported. Just thought I’d post some scenes in case anyone could test if a new build arrives this week. Else see you next week…



    -joe


2

hi,



I’m gone on vacation this week

and return on Sunday.



Attached are some sample

scenes for TP 2.5 using Max 8:


  1. “simple krakatoa TP

    25.max”



    A simple scene using

    Matterwaves to emit particles

    at high speed. Used to test

    Krakatoa motion blur. Shutter

    is at 720 with 8 samples, but

    as of build 17 sp2 there was

    no moblur.





    Turns out Cebas implemented the velocity value in the particle interface different from all other particle systems - it was units per tick instead of per frame. We fixed this today so motion blur now works as expected. We fixed another related bug in the process…
3

w00t - good to hear!


4

2) "simple krakatoa TP 25 -
NOSEED.max"

Sample scene as above but
NOSEED inserted into the TP
dynamic set (DynSet), so the
expected effect would be NO
randomization... e.g. multiple
partitions will yield the
exact same result.

Have not tested your scene yet (VERY busy here), bit all my tests with my own TP 2.5 setups in Max 8 show that NOSEED works as expected when entered into the DynSet's comment. Did you have the opposite experience? Was this an error report, or just a demo scene to simplify our work?

We will look into that BIN file problem next.
5

it was a demo scene to test…



look forward to the velocity update… (why did cebas use a different method? was it non-standard?)

6

it was a demo scene to test…



look forward to the velocity

update… (why did cebas use a

different method? was it

non-standard?)





TP exposes some values like positions and velocities through a standard 3ds Max interface which was introduced when PFlow was implemented. It allows ANY new particle system to be accessed using the same set of methods (that’s why we have the Other Systems option in the Krakatoa GUI - right now, there are no such systems, but if some new particle system would support that interface in the future, we would already be able to read some data from it ;o)

The velocity value was just supplied in a different time scale. It is not a big deal, we intend to use the TP SDK methods later to get more data than just position and velocity, but for the current temp. solution it was necessary to add a special case handling.

7

I see - thanks for the explanation! Hope the SDK helps Krak access all possible options in TP… thanks!