TrackIR change in 1.2.6

[Flagrum]

Sorry but I can't help with FFB as I don't have stick with it.

So nobody else who is now so enthusiastic about the fix of their TIR problem uses FFB? Tbh, I'd rather live with some stutters than with no FFB.

 

Just in case you missed my feedback about the fix you posted: http://forums.eagle.ru/showpost.php?p=1924889&postcount=240

Perhaps the ED guys already have an idea when they see this.

 

Thanks! :o)

 

edit: sniped! :o)

Then if you never had the problem (it wasn't a problem for me either) then just don't use this code?

Actually, that is what I do. But I still wanted to raise attention to it because fixes for one problem must not break other features. I just don't want to end without FFB when ED incorporates the fix into the next release ......

Edited November 9, 2013 by Flagrum

[Kuky]

I've noted your comments about FFB not working with this code... wait and see if they can/will do something more about it.

[Flagrum]

I've noted your comments about FFB not working with this code... wait and see if they can/will do something more about it.

Thanks, much appreciated! :o)

[Lange_666]

I suspect everybody had it, it's just that not everybody noticed it due to already flying with less then optimal FPS.

+1 on this (which is logical).

[blackbelter]

I'm not Kuky :) but assuming yes, you can delete it :thumbup:

 

Thanks mate!

[c0ff]

I copy&pasted the code into my autoexec.cfg but then the force feedback on my G940 wasn't working anymore. :cry: I could narrow it down to the IF line:

if not input then input = {} end

Without it, FFB is working again.

 

If the assignment

input.use_read_thread = false

remedies the original issue, I can't say (or rather: tell the difference) ... I've never had that problem in the first place. :music_whistling:

 

Yes, setting input.use_read_thread=false disables FFB in 1.2.6. The bug is fixed in the internal version.

 

input.use_read_thread=true is the default value in 1.2.6, and does not solve the original issues for those who have it.

 

Changes were made to the input processing in the attempt to fix FPS loss with MS FFB2 joysticks.

Looks like in its current state the code creates more problems than it solves and needs more testing and experiments.

1.2.7 will revert these things back to 1.2.5 level until we have a better solution.

[71st_Mastiff]

this has helped with the Track ir now I have another issue, the scenery and terrain seem to stutter now..:joystick:

[Huckle]

I've noted your comments about FFB not working with this code... wait and see if they can/will do something more about it.

 

Please do, the FFB is important for helicopter.

[howie87]

I can also confirm the fix works (I don't have a FFB stick anyway).

 

Thankyou for fixing this ED and thanks for your help Kuky!