#8 Use realtime compute.

[G.A. Cignoni]

WinDriver must use the realtime compute.

[G.A. Cignoni]

Logged In: YES
user_id=1311864

The driver must idle when compute requires less time and
must warn when compute require more time.

[G.A. Cignoni]

Logged In: YES
user_id=1311864

WinDriver must show:
- actual elapsed time (system time);
- simulation elapsed time (as returned by the dll);
- performed cycles (as returned by the dll).

In realtime ACT and SET must be almost equal.
In batch ACT is a performance indicator.

SET is always the sum of used dt's.
In batch dt's are all equal as they are set by the interface.
In realtime dt's are calculated by the dll using the system
clock, the set dt is used to drive the simulation, in general
actually used dt are > of set dt.

[G.A. Cignoni]

Logged In: YES
user_id=1311864

When the realtime compute will be implemented, the current
realtime way of executing the simulation has to be
maintained as "Continuous". That is there will be three
modes: batch, continuous and realtime.

The continuous mode has also a slider to set a factor to
delay or speed-up the simulation. The dt is used by the sim
and dt * factor is used to set the WinDriver timer.

[G.A. Cignoni]

Logged In: YES
user_id=1311864

More about continuous and realtime modes.

The interface timer is limiting the interface update time at
about 20 millisec. This is also a practical lower bound for
the realtime dT. This limitation has to be avoided.

It should be possible to update the interface only every n
cycles so that the actual dt in not tied to the interface
limitations: interface is updated every 100 millisec, but
in the 100 millisec frame it is executed a batch of n cycles.

Can also be used in the continuous mode to further speed up
the simulation.

For realtime it needs a specifica realtime compute.