Linuxtrack works great, only once per install...

[KarlLeclerc]

Installed Linuxtrack 0.99.18 from downloaded MacOS .dmg archive on MacOS 10.12.5 for use with X-Plane 11.02r2. Installation instructions were good. The setup for "face-tracking" using the iSight camera built into the Mac worked great, all day. Never had so much fun flying X-Plane. Unfortunately, after a shutdown of the Mac computer, upon launching X-Plane again, I get a message from the Linuxtrack plug-in telling me that "Linuxtrack has been moved and that I need to run the setup again". Tried that, did not work. Same message. The X-Plane Log.txt file indicates that the Linuxtrack plug-in gets loaded, but no error message. The only way I can get Linuxtrack to work again is to erase all tracks of the installation and to re-install completely from the .dmg It will then run perfectly... once. Thanks for a great piece of software Michal. My support donation is on its way. I just need a bit of help with this disappearing act here... :)

Karl

[KarlLeclerc]

Michal, I have not played with Unix systems for over 30 years but while poking around the files on my Mac using a "Terminal", I also found that:

• each time I configure using ltd_gui, it does create a new config file in the .config/linuxtrack directory of the user
• a zero-byte ltr_server.lock file keeps getting created in the same directory after each run (even after I remove it) I don't know if that helps you or not...

[uglyDwarf]

Hello, I saw something like that before - the new MacOS versions when run certain apps will run them in a sort of sandbox with randomly generated directory name, and the name changes each time you run it... Please try the following: open the .dmg and drag the ltr_gui and ltr_pipe to a desktop. Open this, ltr_gui, click save prefs button and close it... Now try to run the ltr_pipe and see if it runs (the camera should light up and you should see a "waterfall" of numbers in a window)... In that case, you should be able to run the X-Plane just fine... If it doesn't work (either the ltr_gui, or the X-Plane), please open the ltr_gui, go to the Misc. pane and paste here the first few lines of the Log (there should be a View log button)... Kind regards, Michal

[KarlLeclerc]

Thanks for the quick reply Michal. Yes, it worked. I just realized that ltd_gui.app is not a file but a directory. I guess that the combination of your code and the MacOS require that it sits on, and runs from the Desktop. You are also quite correct about the random generation. When I ran the ltr_gui setup from the desktop, the "Prefix" statements in the .config/linuxtrack/linuxtrack1.conf file were all pointing to the ltd_gui.app directory with the fixed user desktop pathname. When I previously ran the ltd_gui setup from a different directory (other than the desktop), these "Prefix" statements were pointing to randomly generated pathnames. Quite unexpected, but like I said, before yesterday, I had not opened a Unix filesystem in over 30 years (I kinda like the Mac GUI :). I guess I have to keep the ltd_gui.app directory and its associated files on the desktop for now. I should be able to get rid of the ltd_pipe from the desktop, correct? Thanks again. Karl

[uglyDwarf]

Hello Karl, actually it seems to be a feature of the gatekeeper introduced around MacOS 10.12 - there seems to be kind of heuristics that puts certain processes to this random "jail"; you can try to put the ltr_gui anywhere else (Applications, ...), just make sure to run it after the move and save prefs, so the clients can find the necessary stuff (via the prefix)... As for the ltr_gui being a directory - that is so called application bundle; it is a self-contained package containing the binary, and all the libraries, resources and other stuff the application needs. It is very common on MacOS X - most applications are created in this way. It allows to install an application just by dragging (copying) it from the .dmg archive and also uninstalling becomes just dragging the app to the trash bin. It does have its flaws, but it is very user friendly and convenient... As for the ltr_pipe, you can definitely get rid of it - it is just much quicker way to test if the tracking works... Kind regards, Michal

[KarlLeclerc]

Learning something new everyday… thanks for the information, and for helping me out of trouble.

Keep up the good work Michal.

Karl

On Jul 14, 2017, at 7:00 PM, uglyDwarf [email protected] wrote:

Hello Karl, actually it seems to be a feature of the gatekeeper introduced around MacOS 10.12 - there seems to be kind of heuristics that puts certain processes to this random "jail"; you can try to put the ltr_gui anywhere else (Applications, ...), just make sure to run it after the move and save prefs, so the clients can find the necessary stuff (via the prefix)... As for the ltr_gui being a directory - that is so called application bundle; it is a self-contained package containing the binary, and all the libraries, resources and other stuff the application needs. It is very common on MacOS X - most applications are created in this way. It allows to install an application just by dragging (copying) it from the .dmg archive and also uninstalling becomes just dragging the app to the trash bin. It does have its flaws, but it is very user friendly and convenient... As for the ltr_pipe, you can definitely get rid of it - it is just much quicker way to test if the tracking works... Kind regards, Michal

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/uglyDwarf/linuxtrack/issues/138#issuecomment-315487215, or mute the thread https://github.com/notifications/unsubscribe-auth/AcxQoz5xAUjczQ3L6vFwMiq53-Pfbqhiks5sN_MJgaJpZM4OXzOF.