TrackIR change in 1.2.6

[Lange_666]

Suck it up Howie, be patienced... :D

 

By the looks of it, test builds of 1.2.7 have it also. Time to do something else but flying, maybe a bit of CA...?

[Rhinox]

...Time to do something else but flying, maybe a bit of CA...?

If I wanted to play tank-commander, I'd start "World of Tanks". I did not buy DCS for that...

[Lange_666]

Can't you command some AA missiles instead?

[Kuky]

Can you guys try this code in Autoexec.cfg:

 

if not input then input = {} end

 

input.use_read_thread = false

 

does it help anyone?

[_Dredd]

Can you guys try this code in Autoexec.cfg:

 

 

 

does it help anyone?

 

I can test tmrw night.

[Lange_666]

Can you guys try this code in Autoexec.cfg:

 

does it help anyone?

 

Kuky dude, you're da man. I tested on various FPS rates with VSync on and off, ie 30 FPS 1/2 adaptive VSync, 60 FPS VSync and no VSync (around 115-120 FPS) every time with and without the autoexec.cfg present.

With this into the autoexec.cfg, it works out nicely...:thumbup:

 

This means i'm back in bussiness...:joystick: :pilotfly:

[_Dredd]

OMG ? It's fixed ?! I'll definitely test tonite.

 

:thumbup::pilotfly:

 

Bring on 1.2.7!

[repsol]

Hello Kuky...

 

A BIG thank you for your suggestions ! Things are working again :thumbup:

 

I'm back in the sky... blowing things up... and it feels great :pilotfly:

[71st_Mastiff]

i just upgrade to a evga gtx780 and the new r331 drivers and now having this issue.

how do i fix this?

[Lange_666]

how do i fix this?

http://forums.eagle.ru/showpost.php?p=1923833&postcount=231

[Golo]

I can confirm that it works. I no longer have this problem with Kukys solution, all is smooth again.

Did clean instal of latest 1.2.6 version + latest DCS A-10C module.

 

Now I have to ask, where the **** was the problem, and what was it (for future) between 1.2.5 and 1.2.6 why some ppl had this problem and some did not?

[TZeer]

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

[Flagrum]

Can you guys try this code in Autoexec.cfg:

 

 

 

does it help anyone?

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:

[71st_Mastiff]

http://forums.eagle.ru/showpost.php?p=1923833&postcount=231

 

I know but where is that config at?

[repsol]

I know but where is that config at?

 

 

- startmenu...top selection (user name)

- saved games

- DCS

- There you'll find 'Config' at the top

- create a new file with notepad++ called "autoexec.cfg" and type in thoose two lines and save it to the config folder...Thats it

[Fifi]

Have to admit there is a good improvment with your latest fix in autoexec.cfg :thumbup:

 

Even if i couldn't really noticed this micro stuttering before, things are for sure smoother now :music_whistling:

[Kuky]

FYI, this is not MY fix... it's ED's so again don't thank me, thank ED :D

 

And FYI #2, the bug seems to have been introduced in 1.2.6 when input code of the sim got its own thread, so things got messed up there... that's all I can tell you. I will provide your positive feedback to ED... and thanks for the feedback.

[Flagrum]

FYI, this is not MY fix... it's ED's so again don't thank me, thank ED :D

 

And FYI #2, the bug seems to have been introduced in 1.2.6 when input code of the sim got its own thread, so things got messed up there... that's all I can tell you. I will provide your positive feedback to ED... and thanks for the feedback.

erm, what about the FFB issue I had?

[blackbelter]

Hi Kuky,

 

Do I need to delete the line

input.read_rate = 120

before I add the new lines, which are

if not input then input = {} end

 

input.use_read_thread = false

?

And is the blank line in between them important?

 

Thank you!

 

Cheers

[Fifi]

Hi Kuky,

 

Do I need to delete the line

input.read_rate = 120

 

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

[Wolf Rider]

I've noticed with the latest release nVidia driver a bit (very slight) of the jittery problem was introduced (more noticeable when zoomed in onto the flight panel, rather than panning out over terrain but wasn't a game stopper in any sense)... the second of the two fixes you passed on from ED sorted that out Kuky.

 

Thanks

 

I was also reading that Windows 8 has changed the way it handles USB drivers, which may figure in somewhere as well

[_Dredd]

Whoop!

Thanks Kuky for addressing the bug to ED. Thanks ED for helping us fix this!!

 

Back in action, and it's better then ever. Thank you

 

:thumbup::thumbup:

 

:pilotfly:

[Kuky]

Hi Kuky,

 

Do I need to delete the line

input.read_rate = 120

before I add the new lines, which are

if not input then input = {} end

 

input.use_read_thread = false

?

And is the blank line in between them important?

 

Thank you!

 

Cheers

 

Answers to 2 questions are YES and NO

[Kuky]

erm, what about the FFB issue I had?

 

Sorry but I can't help with FFB as I don't have stick with it. My guess would be that as FFB is part of input code, it's somehow related to this... so changing code would affect both... I don't really know, maybe you can make new thread explaining exactly what's happening on your end and some tester with FFB can help out.

Edited November 9, 2013 by Kuky

[Kuky]

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:

 

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