Closed GoogleCodeExporter closed 8 years ago
Hello,
the preferences are supposed to be in ~/.config/linuxtrack/linuxtrack1.conf
file.
From the log, it seems that there are changes in the default config, and it
seems to be read allright. I'd recommend you to set other than JPEG format
(RGB3 or BGR3 should be OK). Also the webcam doesn't seem to report any usable
framerates at all (and my code seems to use uninitialized values, which is a
bug that I'm going to take a look at).
And if I'm correct, the problem you have is that webcam setup is not
remembered, right? I think I know where the problem is - the name reported by
webcam starts with a space, that is stripped when the prefs are read in and
then it wouldn't match...
I'll take a look at it too, hopefully today or tomorrow I should be able to
commit the fix...
In the meantime, if you have access any other webcam, try it instead...
Thank you for giving it a shot and for reporting the problem.
Kind regards,
Michal
Original comment by f.jo...@email.cz
on 11 May 2013 at 11:20
Hello Michal,
I've tried the software right now with another webcam and it works awesome on
FlightGear. I've still to configure it better, but now i can't do it because i
am so excited to fly on 3d enviorment! ;)
I send you the 2 preferences files that ltr_gui creates for the New Webcam (the
one that is working) and the Old Webcam (the one that it is still not working).
Any more files you need just tell me and i'll send you as soon as possible.
I've set the option Pixel-format = YU12 in both webcams and i can see the 3D
Model working great.
I've also like to know if there is a way to reconfigure the webcam settings at
the sametime that FlightGear is running. And also if is there any command to
disable it for a while and enable it agein? (Maybe if i need to go to the
toilette i would like to not get my view crazy!)
Thanks a lot for your work!
Oriol
Original comment by Oriol.Al...@gmail.com
on 12 May 2013 at 7:14
Attachments:
Hello Oriol,
I'm glad that you made it work at last...
As for flightgear bindings, they are a work of Alexander, but I might be able
to help a bit... I assume you are using the ltr_pipe to get the data to the
sim. There is a possibility to send it (ltr_pipe) signals for recenter (HUP)
and pause/unpause(SIG1) - see README.ltr_pipe in share/doc/linuxtrack. However
I don't think it is very convenient.
I'm going to take a look at the Flightgear bindings soon, to make them more
user friendly; in the meantime, you can still use the ltr_gui to control the
tracking - just start ltr_gui (and start tracking), then start ltr_pipe and
flightgear. Then you can control the tracking from ltr_gui. And to save a bit
of CPU, you can disable the 3D preview in the fourth pane and enable it only
when you need it for setting things up.
Kind regards,
Michal
Original comment by f.jo...@email.cz
on 12 May 2013 at 10:53
I just committed a fix for the bug you encountered. Could you try to compile
it, run it using the previous webcam and let me know if it works?
Kind regards,
Michal
Original comment by f.jo...@email.cz
on 12 May 2013 at 1:07
Hi Michal,
I've tried the previous webcam and it works great! Thank you very much!
And also thanks a lot for the previous message you sended, with that now i can
recenter the webcam anytime i need it with just calling a simple script.
Kind regards,
Oriol
Original comment by Oriol.Al...@gmail.com
on 15 May 2013 at 12:44
Hello Oriol,
I'm glad it works for you and thank you for the report!
If all goes well, a new linuxtrack universal package should appear in about a
week (provided I don't encounter any major problems), so you won't have to
compile it...
I'm going to close the issue; should the problem reappear, feel free to reopen
it or open a new one...
Kind regards,
Michal
Original comment by f.jo...@email.cz
on 15 May 2013 at 6:17
Original issue reported on code.google.com by
Oriol.Al...@gmail.com
on 11 May 2013 at 5:56Attachments: