Hi Kelvin !
Thanks for the reply and thanks for providing the information about the different
modes of
InputDevice.
> (2) Another factor is the numerically error build up during the process.
>
> In the first method it seems that the transformation matrix is set
> directly using loookAt(
Hi all,
If anyone is interested in the solution for the strange behavior:
In one case the Transformation of the object is updated depending on the frame rate
because the
difference matrix is multiplied in the behavior and generates a new transformation
every frame.
In the other case the Transf
Hi Fred,
>> ...
>> InputDevice.NON_BLOCKING mode:
>> --
>>
>> A timer thread in Java3D will trigger an event to the
>> InputDeviceScheduler thread every 5ms to read input from device.
>> This sampling rate (default 5ms) can be changed using the
>>
From: "Kelvin Chung" <[EMAIL PROTECTED]>
Sent: Friday, May 04, 2001 1:47 PM
> ...
> InputDevice.NON_BLOCKING mode:
> --
>
> A timer thread in Java3D will trigger an event to the
> InputDeviceScheduler thread every 5ms to read input from device.
> Thi
Hi Paul,
>
>If anyone is interested in the solution for the strange behavior:
>
>In one case the Transformation of the object is updated depending on the frame rate
>because the
>difference matrix is multiplied in the behavior and generates a new transformation
>every frame.
>In the other case
