Command line output

[Otuama]

Does the command line have to print the 'Summery Information' each frame?

It may be useful to be printed at the start of the command line process (or even needed) but not each frame. The summary info list gets quite big if you have a lot of nodes in the scene.

However, it's a nice thing having updated particle counts for hybrido and standard emitters.

Could only the important (changing) nodes be displayed each frame? For example, any nodes which create hybrido or standard particles. For example:

>10:27:46: ================ Frame 30 finished ================

..
Summary information
-------------------

Circle01: Liquid [2,201 particles] d=1000.0 p=1.000 v=3.000
HY_Domain01: [43 x 23 x 43 = 289152752 cells] [8,092 particles [0.300000 cell size]
HY_Splash01: Dumb [15,698 particles]

Timing information
-------------------
Elapsed time: 00:00:11
Remaining time (estimated): 00:00:57
Average time (frame): 00:00:00

>10:27:46: ================ Frame 31 started ================

>10:27:46: ================ Frame 31 finished ================

..
Summary information
-------------------

Circle01: Liquid [2,294 particles] d=1000.0 p=1.000 v=3.000
HY_Domain01: [44 x 23 x 44 = 287488176 cells] [8,320 particles [0.300000 cell size]
HY_Splash01: Dumb [16,015 particles]

Timing information
-------------------
Elapsed time: 00:00:11
Remaining time (estimated): 00:00:55
Average time (frame): 00:00:00

>10:27:46: ================ Frame 32 started ================

--------------------------------------------
--------------------------------------------

[FlorianK]

I think it is very good having this information each frame, so one can see if something's going wrong while in CL mode. Anyway, being able to turn it off or switching between different verbosity modes was useful.

[Otuama]

Maybe so but how can one determine whether something is going wrong with a sim by simply being shown a list of nodes?

The sim may be going wrong but the CL won't tell you that dynamic objects, for example, aren't falling the way they should or that nodes have been left inactive etc.

It's the users role to sort that first.

[FlorianK]

I can tell what's going wrong by watching the amount of ptcls and the time it took to calculate. E.g. if a sim breaks after a couple of frames. Object collisions etc. I susally check before doing a CL sim.

[Otuama]

Yeah, that's what I meant in my original post.

It's a great idea having the particles being shown. That's why I asked for only the 'changing' nodes being shown and gave a CL example showing only particle nodes.

What I don't think the CL needs to display is daemons, objects, maybe even Realwave's because none of those nodes show beneficial information in the CL.