[vrjuggler-info] Porting drivers from 2.0-alpha3 to 2.0-alpha4... pending VFX3D item

[Sinisa P. <sin...@es...>]

Hi all,

I'm working on WinXP, using VR Juggler 2.0-alpha4, and trying to port my
VFX3D HMD drivers, vfx3d definition file and one standalone configuration
file (using vfx3d element) from 2.0-alpha3.

I modified standalone and gadgeteer drivers for VFX3D HMD to compile with
2.0-alpha4 (and tested them).  Standalone driver is written by using the
original driver provided with VFX3D.  I created a definition file
VFX3D.jdef, and used it in my configuration file Full_Vfx3d.jconf.

I am trying to use Full_Vfx3d.jconf in osgNav application to control the
orientation of the viewpoint, but when the application is started the
viewpoint orientation does not change when moving the HMD.

By increasing the notification level I found out that vfx3d element does not
get handled by any of the jccl::ConfigElementHandlers, and in particular not
by gadget::InputManager.  At notify levels 4 through 7 I repeatedly get the
messages:

[0003020/000] DBG:  class gadget::InputManager::configProcessPending:
Entering: 1 items pending.
[0003020/000] DBG:   Item: name:MyVfx3d type:vfx3d
                      Pending item: MyVfx3d type: vfx3d --> Not handled by
this handler.


Vfx3d_drv_d.dll seems to be loaded ok, from the messages:

[0003020/000] DBG:  Item: name:Input Manager type:input_manager
[0003020/000] gadgetINP:   Input Manager: Adding pending config element.
[0003020/000] gadgetINP:    Handling input_manager element:
[0003020/000] gadgetINP:     [gadget::InputManager::configAdd()] Appending
default search path
'C:\VRJuggler\V2.0-alpha4-FromSource\lib\gadgeteer\drivers'
[0003020/000] gadgetINP:     [gadget::InputManager::configAdd()] Loading
driver DSO 'VFX3D_drv'
[0003020/000] DBG:     vpr::LibraryLoader::findAndInitDSO(): Looking for
'C:\VRJuggler\V2.0-alpha4-FromSource\lib\gadgeteer\drivers\VFX3D_drv_d.dll'
[0003020/000] DBG:     Loading library:
C:\VRJuggler\V2.0-alpha4-FromSource\lib\gadgeteer\drivers\VFX3D_drv_d.dll
[0003020/000] DBG:     Loaded DSO successfully.
[ OK ]
[0003020/000] DBG:     Got pointer to DSO initialization function.


Last output of report of the InputManager status (with 3 items pending,
later only MyVfx3d remains pending) looks like this:

========== InputManager Status ==========
Devices:
AppDigitalControls:  name:            AppDigitalControls  type:class
gadget::SimDigital
SystemDigitalControls:  name:         SystemDigitalControls  type:class
gadget::SimDigital

Proxies:
HeadProxy   Proxies:None (internal dummy)
MainWindowEventProxy   Proxies:None (internal dummy)
VJAppExitProxy   Proxies:SystemDigitalControls
VJSystemStopKernelProxy   Proxies:SystemDigitalControls

Alias List:
    VJAppExit  proxy: VJAppExitProxy
    VJHead  proxy: HeadProxy
    VJKeyboard  proxy: MainWindowEventProxy
    VJSystemStopKernel  proxy: VJSystemStopKernelProxy
========== InputManager Status ==========

In my application I am accessing the VFX3D tracker through VJHead alias for
HeadProxy, and HeadProxy in configuration file Full_Vfx3d.jconf 'points to'
MyVfx3d element.


I appreciate any pointers on what I might have missed during configuration.
I'll continue stepping through the code in the morning, focusing on
gadget::InputManager::configProcessPending().  Please, point out if I'm
looking in all the wrong places (hopefully, with suggestions of better 
places).

Thanks, best regards, Sinisa