TDC Vertical Slew Stops Working With Any Saturation Change

[arriflex]

I have my TDC set to my WH throttle slew, its obviously crazy sensitive so I dial in curve+saturation. Horizontal works fine but vertical stops working altogether when I add any saturation. This is in 2.0.

 

Thoughts?

[PiedDroit]

I have my TDC set to my WH throttle slew, its obviously crazy sensitive so I dial in curve+saturation. Horizontal works fine but vertical stops working altogether when I add any saturation. This is in 2.0.

 

Thoughts?

TDC is bugged, it has a hardcoded threshold. It only starts moving at 50.

Try custom curve 50 to 100

[Frederf]

It's currently binary control. 0-50% no move, 51-100% move. There are only two speeds, stop and go.

[chrisrucksack]

Since (~ march 2016) you can use the TDC on axis, it's known.

http://forums.eagle.ru/showthread.php?t=162433

http://forums.eagle.ru/showthread.php?t=162428

http://forums.eagle.ru/showthread.php?t=165643

 

I think, it's programmed like a button. You need to press the button 100% to get a reaction.

 

I hope, to add user saturation changes is on RAZBAM fix/add list.

[arriflex]

It's strange because horizontal works with a saturation adjustment, only vertical doesn't.

[iLOVEwindmills]

It's strange because horizontal works with a saturation adjustment, only vertical doesn't.

 

Yeah this, it seems like there's just a bit of code missing from the vertical axis, considering you can adjust the horizontal one all you want.

[Pineapple Pete]

Well this clears up my questions. I am having the same problems. Exactly

Edited August 5, 2016 by Pineapple Pete

[Pineapple Pete]

Is this a universal problem or just occurring randomly? My slew controls work properly in the F-15 btw.

[Dino Might]

Only M2000 problem, as far as I know. The radar is all sorts of messed up in today's (8/6) patch. STT cannot lose lock anymore (opposite of what used to happen with it losing lock if you breathed wrong), but the TDC slew is totally borked and you can't adjust saturation. Hoping they hotfix this over the weekend. Otherwise, M2000 is not usable right now for me in Blue Flag.

[Whisper]

Only M2000 problem, as far as I know. The radar is all sorts of messed up in today's (8/6) patch. STT cannot lose lock anymore (opposite of what used to happen with it losing lock if you breathed wrong), but the TDC slew is totally borked and you can't adjust saturation. Hoping they hotfix this over the weekend. Otherwise, M2000 is not usable right now for me in Blue Flag.

They cannot hotfix it. ED pushed the wrong binaries apparently, and we'll have to wait for the next update

 

Envoyé de mon SM-T810 en utilisant Tapatalk

[Panthir]

Same issue here. It's very sad that when they fix something in the same time the break something else.

 

In the previous update it was the trim issue for users with a secondary FFB device connected.

In this update they fixed it but they broke the M-2000C horizontal TDC.

[hollowman8904]

Same issue here. It's very sad that when they fix something in the same time the break something else.

 

In the previous update it was the trim issue for users with a secondary FFB device connected.

In this update they fixed it but they broke the M-2000C horizontal TDC.

 

 

 

Perhaps RAZBAM should look into testing their code. It seems like some feature gets broken with every release.

 

 

Sent from my iPhone using Tapatalk

[Sarge55]

Pffft.... another expert on his iPhone.

[arriflex]

Pffft.... another expert on his iPhone.

 

Thanks for the productive response!

[Sarge55]

Thanks for the productive response!

 

You're welcome... :music_whistling:

[Boxin]

I'm not sure if this will help everyone but I want to share just incase.

 

The Y and X axis move at different speeds so both axis will not look identical by the time you're done.

 

In my case my Y axis would move in small increments / was very slow at 51 and my X Axis was still pretty quick. I adjusted the Y axis accordingly until it closely resembled the speed of my X axis.

As stated by someone in this thread earlier, input starts at 51.

 

It isn't perfect, but it helps.

 

I use a Warthog...

 

What I did is...

 

1) Chose User Curve

2) Moved all the sliders up to 100

3) Moved Saturation Y Down to 51 and worked up from there.

4) I then raised the Saturation Y slider up by 20 then lowered all sliders to 80 except the last 3 which I left at 100. This allows me to have a higher speed when moving the mini stick to it;s threshold.

 

I hope this helps someone. You now get this jist of it and can find your own preference with this base idea.

 

It is a variation of the user curve trick many use on the KA-50

 

Cheers

Edited August 8, 2016 by Boxin