Whenever I change the sensitivity it never saves it and always reverts to the default settings ?

[GoogleCodeExporter]

What steps will reproduce the problem?
1.open linuxtrack GUI
2.change the sensitivity settings to your preference and press save
3.open xplane 10 and the settings you have just made revert back to default.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
the very latest version on mac lion os 

Please provide any additional information below.

Original issue reported on code.google.com by strutt...@gmail.com on 19 May 2012 at 10:20

[GoogleCodeExporter]

Hello,
there are several things, that might cause this behavior...

First of all, when you do some change, save it, quit linuxtrack gui and start 
the gui again - do you see the change there?

The other thing is, are you changing the default profile? XPlane plugin at the 
moment uses the default profile...
Kind regards,

Michal

PS. When running the XPlane, do you leave the linuxtrack gui running?

Original comment by f.jo...@email.cz on 20 May 2012 at 5:17

[GoogleCodeExporter]

I have started xplane with the GUI running and without it running. If I start 
it without running the GUI then it just uses the default profile which is too 
sensitive and also erratic with some strange behaviour.....when the GUI is 
still running the sensitivity issue seems to slow down but the game is 
unplayable due to the views I get......turn my head left and a see the cockpit 
roof..... Turn my head right and I leave the cockpit and end up outside......

Original comment by strutt...@gmail.com on 20 May 2012 at 11:33

[GoogleCodeExporter]

This is quite strange...
First of all - the switched rotations would suggest that in the model section, 
you have Track Clip selected, instead of Track Clip Pro...
Also check that you didn't change the camera orientation (first tab).

What I'd suggest is to set up the sensitivities using the linuxtrack GUI 3D 
model first, and then do the tweaking...

One more question - did you used (or tried) linuxtrack before?
Kind regards,

Michal

PS. Could you paste me the start of linuxtrack log? It contain the preferences 
and it might answer several questions... (last tab, I think, there is a button 
for that)

Original comment by f.jo...@email.cz on 20 May 2012 at 3:00

[GoogleCodeExporter]

If you still experience this issue, feel free to reopen the ticket, or open a 
new one...
Kind regards,

Michal

Original comment by f.jo...@email.cz on 28 Feb 2013 at 1:40

• Changed state: WontFix

[GoogleCodeExporter]

hi i gave up in the end but have decided after all this time to give it another 
shot and still the same behaviour remains...i dont know how to send you the log 
file ?

Original comment by strutt...@gmail.com on 21 Apr 2013 at 5:10

[GoogleCodeExporter]

i think this is the log file 

Original comment by strutt...@gmail.com on 21 Apr 2013 at 5:52

Attachments:

• [log file txt.rtf](https://storage.googleapis.com/google-code-attachments/linux-track/issue-22/comment-6/log file txt.rtf)

[GoogleCodeExporter]

Hello,
first of all, thank you for giving it another shot...
From the log, there doesn't seem to be any problem.
There are two possibilities now; one of them is, that ltr_gui crashes before it 
have a chance to write prefs (however I didn't receive any other report of this 
behavior so far). The other possibility is, that there is a permissions problem 
with the preferences and it can't save them (I had several reports of this 
problem, however it seems to be somewhat related to the system, not ltr_gui 
itself)...

I'd like to ask you to try this: open the ltr_gui, go to the tracking tab, 
change one of the sensitivities, press the Save button and quit ltr_gui. Now, 
when you open the ltr_gui again, do you see the change?

If you do, then try to save the changes regularly to avoid losing them when 
just quitting ltr_gui. In this case, I'd be interested to see the crashlogs 
(start Applications/Utilities - Console and you should find there ltr_gui.app 
crashlogs).

However, if you don't see the change, I'd suspect the permission problem. To 
salvage it, I'd recommend you to run the following command in terminal:

mv ~/.linuxtrack ~/linuxtrack_bck

It will move the current prefs, so the new ones will be created and now 
hopefully with correct permissions... Should the command output any error 
message, let me know and I'll help you to sort it out. 

By the way, there is a brand new MacOS version in works, that will hopefully be 
released in few next days (MacOS have several subtle differences in behavior 
when compared to linux and I happened to use one of them, so I'm trying to work 
around the problem right now).

Kind regards,

Michal

Original comment by f.jo...@email.cz on 21 Apr 2013 at 6:35

• Changed state: New

[GoogleCodeExporter]

Firstly Thankyou for your quick response and for being so helpful :) ....this 
is the real problem ..
1- I load up the GUI 
2- then the model to see how my movements look
3- if I look to the right everything is fine apart from it being really 
sensitive
4- I look to the left and it jerks and looks upward briefly before carrying on 
to the left...and the same when I'm returning back to face the front.
5- if I change the sensitivities or any other setting it becomes so unstable 
and erratic it is unusable.

Again thanks for all your help

Mick

Original comment by strutt...@gmail.com on 22 Apr 2013 at 8:03

[GoogleCodeExporter]

Hi,
the symptoms you describe suggest one of the two problems:

1) Do you have the correct model selected? Looking to the log, there is a NP 
TrackClip Pro selected - that is the one with LEDs... As you changed this, I 
assume you really have it, so that should not be the problem.

2) Most probably you have there a light source interfering; go to the Tracking 
window and select the camera view. Ideally, you should see there three "blobs", 
where the camera sees the LEDs of your model. Each of those three blobs should 
have a white cross inside all the time, throughout the whole range of usable 
motion.

Now, should you see more than three blobs, you need to find where the unwanted 
ones come from - may it be a daylight reflection, lightbulb or alike and get 
rid of them.
For example I had a problem with a lightbulb - I just adjusted the TrackIR to 
get it out of its field of view...

Should the crosses disappear, then you'd need to change the min and max blob 
settings; however I don't think that should be a problem as I use those values 
without any problems...
Kind regards,

Michal

Original comment by f.jo...@email.cz on 22 Apr 2013 at 8:56

[GoogleCodeExporter]

Hi again and with a big sigh of relief I think I've cracked it with your 
help....... It seems that it was picking up a reflection from my headphones on 
which the clip is attached so all I had to do was adjust the clip upward 
slightly and now everything is fine .... And Thankyou again for being so 
helpful.. It was driving me insane having a track IR and not being able to use 
it but thanks to you I can now experience my flight simulator as it should be 
so thanks a million

Mick

Original comment by strutt...@gmail.com on 22 Apr 2013 at 3:52

[GoogleCodeExporter]

Hi,
I'm glad you managed to sort it out...

I know the feeling - it was what made me to start this project in the first 
place.
I'm going to close this ticket now, should you encounter any more problems, 
don't hesitate to reopen it or file a new one.
Kind regards,

Michal

Original comment by f.jo...@email.cz on 23 Apr 2013 at 4:44

• Changed state: Done