Closed GoogleCodeExporter closed 9 years ago
Hello Giovanni,
thank you for the report... I've checked the changes, but between those two
versions nothing changed in the parts of code responsible for tracking.
I'd ask you for some clarification - you say the X,Y,Z are NaN; how about the
angles (pitch, roll, yaw)? Do they work?
The logfile messages are normal - the verbose TrackIR search is there to help
resolving some spurious TrackIR problems and the nonexistent key messages are
OK too; in the past, there was only one symetrical limit for each axis
(Pitch-limits,...), while now there are two (Pitch-left-limit,
Pitch-right-limit).
As for the preferences, there are two places; the main one is the .linuxtrack
directory in your home, namely linuxtrack.conf file. The other one is used only
to store window positions, so they should pose no problems whatsoever.
Having said that, looking at your preferences, there doesn't seem to be any
problem with them; I also tend to provide some "backwards compatibility", so
the new version either understands the old format, or if it is not possible, it
will provide a safe default.
At the moment, I'd ask you to conduct the following tests:
- does this happen consistently? Meaning, every time you start the ltr_gui? (no need to restart the Wii server)
- open the terminal and try the following commands:
{{{
> export LINUXTRACK_DBG=t
> cd "/Users/Giovanni/Desktop/X-Plane 10 Demo/ltr_gui.app/Contents/MacOS"
> ./ltr_gui
}}}
It should start linuxtrack GUI in the mode that logs the values from the
"driver".
It should give me some pointers to where do those NaNs get there...
Just start the tracking, and when you see those NaNs, stop it again.
When done, please send me the logfile contents to take a look...
- try starting ltr_gui, go to the Misc tab and check the "Use legacy pose computation method" button and then start the tracking - does it change anything?
- what happens when you press Recenter button while the NaN is reported?
Kind regards,
Michal
Original comment by f.jo...@email.cz
on 15 Mar 2012 at 7:26
Thanks for the quick reply. When I'll come back from work, i'll try the
commands you provided, and send you the log file. As for now, i remember that
when I start the wii camera, Pitch Roll and Yaw angles are ok; are properly
displayed in the "edit sensitivities" window, with values that appear to be
consistent.
X Y Z translation return NaN during all the recording of the camera. When i
recenter the window (in the 3D model), it continues to show a blue screen
(maybe the 3D model is loaded properly, but the X Y Z position are out of the
Field of View).
Thanks
Giovanni
Original comment by antares...@gmail.com
on 15 Mar 2012 at 7:54
Thank you for the update Giovanni...
I'll be waiting for the log.
Thank you for your help,
Michal
Original comment by f.jo...@email.cz
on 15 Mar 2012 at 9:11
>At the moment, I'd ask you to conduct the following tests:
>
>- does this happen consistently? Meaning, every time you start the ltr_gui?
(no need to restart the Wii server)
Yes, it happens every time I start the ltr_gui.
I tried both with the "Use legacy pose computation method" option activated and
de-activated, but returns me always NaN in the sensitivities window for X, Y,
and Z translation.
I attach the logs obtained with the LINUXTRACK_DBG=True option.
"Log" is the first attempt (at the end I tried to press the "Recenter" button
but nothing happens (in the 3D visualization).
"LogWithLegacy" is the second attempt (with the "Use Legacy Pose Computation
Method" option activated.
Finally I attach the X-PLANE error picture I sent you via mail
"Errorxplane.png".
I'm running on OSX 10.7, have Xcode installed, maybe I can compile ltr (quite a
newbie in that).
Do you think the problem is the WiiRemote as camera or the OS version I'm
currently running?
Thanks a lot for the help! Let me know if I can do/test something else.
Giovanni
Original comment by antares...@gmail.com
on 15 Mar 2012 at 5:36
Attachments:
Hello Giovanni,
I can reproduce the problem, which should simplify the debugging...
I'll keep you posted,
Michal
Original comment by f.jo...@email.cz
on 15 Mar 2012 at 7:24
Hello Giovanni,
here is the fix - so far it seems to cure the problem for me...
The zip file contains libltr.dylib.0
Ctrl-click on the ltr_gui, select the show package contents; go to Contents,
Frameworks and replace the library with the new one.
Let me know how it works...
Kind regards,
Michal
Original comment by f.jo...@email.cz
on 15 Mar 2012 at 9:07
Attachments:
Thank you so much,
fantastic job, the custom library fixes everything!!!!!The ltr_gui is working
properly, the 3D model is back again and so are the X, Y, Z translations.
The X-PLANE plugin now launches properly, but I noticed that it is not 6DOF (it
has Pitch and Yaw, but misses roll, maybe is an issue of X-PLANE 10), another
thing that i noticed, is that in the ltr_gui the movements are smooth and very
natural; in X-PLANE the view wobbles and bounces so much. What is the
difference between the x-plane plugin and ltr_gui? (i've PilotView Plugin
installed too)
Thank you!
Giovanni
Original comment by antares...@gmail.com
on 15 Mar 2012 at 10:56
Hello Giovanni,
thank you for the good news...
The 6DOF plugin for XPlane on Mac is yet to be released; right now I'm
implementing facetracking and when this is released, 6DOF will be included.
Bouncing view might be caused by several things - Pilotview is adding movements
according to the G forces, also there used to be thing called Cinema Verite,
which does something similar (it was option in the XPlane). Other than that,
I'm not sure what could be the cause of this.
Let me know, if you find something...
Kind regards,
Michal
Original comment by f.jo...@email.cz
on 15 Mar 2012 at 11:23
Sorry to tell you that in the new release the issue is not fixed, i even tried
to replace the library with the one you gave me, but x-plane plug-in is still
corrupt and the 3D model window of ltr_gui does not load the 3D cockpit.
Original comment by antares...@gmail.com
on 26 Mar 2012 at 5:13
Thank for the report - I'm sorry I missed it; there is just too much going on
right now... Hopefully the newest release would fix this problem too.
Kind regards,
Michal
Original comment by f.jo...@email.cz
on 28 Mar 2012 at 5:22
Hello,
I'm closing this issue, as Beta 7 seems to cure the problem (as you reported in
issue 19). Feel free to reopen it, should the problem show up again...
Kind regards,
Michal
Original comment by f.jo...@email.cz
on 5 Apr 2012 at 5:24
Original issue reported on code.google.com by
antares...@gmail.com
on 14 Mar 2012 at 11:19