Author Topic: t16000m fcs on xbox - massive deadzones  (Read 10820 times)

dblaze025

  • Newbie
  • *
  • Posts: 7
t16000m fcs on xbox - massive deadzones
« on: May 10, 2020, 06:55:18 AM »
so i got the s1 to use with a t16000m fcs on my xbox one, i got everything set up and it works great, with the exception of the massive deadzone on on the joystick. it feels like its turned up to like 90%, and i only get a response from the last 10%. I have it set up throught the app on my phone and all the buttons and triggers are fine, and the joystick itself actually controls the craft correctly, but its just impossible to make small adjustments to your aim when you have to jerk the stick all over the place. please help!

ironically, this is what i was trying to avoid by going the reasnow route instead of the hori ace combat stick or the tflight hotas one.

richard

  • Global Moderator
  • *****
  • Posts: 4833
Re: t16000m fcs on xbox - massive deadzones
« Reply #1 on: May 11, 2020, 05:21:41 PM »
hi, please enable "I/O monitor" in "Settings" in our APP, and then return to "HOME" to troubleshooting.
you will see all the input and output of S1,
shall found something in it.

Any more support in need, please provide more details of yours.

dblaze025

  • Newbie
  • *
  • Posts: 7
Re: t16000m fcs on xbox - massive deadzones
« Reply #2 on: May 17, 2020, 10:08:24 AM »
hi, please enable "I/O monitor" in "Settings" in our APP, and then return to "HOME" to troubleshooting.
you will see all the input and output of S1,
shall found something in it.

Any more support in need, please provide more details of yours.


I used the i/o mode to map the controller in the first place. it turns out the issue is not deadzone, but input lag, and its very bad, like 2-3 seconds worth. you can see a video of this here: https://www.reddit.com/r/StarWarsBattlefront/comments/ghxo19/this_makes_starfighter_assault_like_a_brand_new/

console - xbox one x
controller - thrustmaster t16000 fcs
game - battlefront 2 and ace combat 7

richard

  • Global Moderator
  • *****
  • Posts: 4833
Re: t16000m fcs on xbox - massive deadzones
« Reply #3 on: May 17, 2020, 07:19:30 PM »
sorry, the video is inaccessible for us.
can you upload it to youtube or some other file sharing server,
and post the link here?

dblaze025

  • Newbie
  • *
  • Posts: 7
Re: t16000m fcs on xbox - massive deadzones
« Reply #4 on: May 18, 2020, 12:05:57 AM »
sorry, the video is inaccessible for us.
can you upload it to youtube or some other file sharing server,
and post the link here?

How about this https://imgur.com/gallery/wYLNpgj

richard

  • Global Moderator
  • *****
  • Posts: 4833
Re: t16000m fcs on xbox - massive deadzones
« Reply #5 on: May 18, 2020, 11:30:16 AM »
just checked your video,
1. we think the lag you feel in the "I/O monitor" is the delay of bluetooth transmission,
which is designed to work as low-priority process.
it is not the real delay of the flight stick.
2. and please reduce Third-party controller's "Deadzone" to 5 or others in our APP,
and try it again. it might improve your control.
3. btw, the config you activated in S1 shall be "Controllers and Joysticks",
   do not use other configs.

dblaze025

  • Newbie
  • *
  • Posts: 7
Re: t16000m fcs on xbox - massive deadzones
« Reply #6 on: May 19, 2020, 01:08:08 AM »
just checked your video,
1. we think the lag you feel in the "I/O monitor" is the delay of bluetooth transmission,
which is designed to work as low-priority process.
it is not the real delay of the flight stick.
2. and please reduce Third-party controller's "Deadzone" to 5 or others in our APP,
and try it again. it might improve your control.
3. btw, the config you activated in S1 shall be "Controllers and Joysticks",
   do not use other configs.

1. The lag is not in the app, it is happening when I try to actually use the stick in games. In the video you can clearly see when I move the stick it takes several seconds for the movement to be replicated on screen. The stick is plugged into the adapter which is plugged into the Xbox, what does Bluetooth have to do with anything?

2.i have tried several different deadzone settings, all the way down to zero and it doesn’t have an impact

3. That is the config I’m using

richard

  • Global Moderator
  • *****
  • Posts: 4833
Re: t16000m fcs on xbox - massive deadzones
« Reply #7 on: May 19, 2020, 11:09:35 AM »
will look into that and get back to you later.

BTW, if a controller is used to play these games(battlefront 2 and ace combat 7) for controlling aircrafts,
do not use S1,
will you face the same lag?

dblaze025

  • Newbie
  • *
  • Posts: 7
Re: t16000m fcs on xbox - massive deadzones
« Reply #8 on: May 19, 2020, 01:14:11 PM »
Do you mean just using a regular Xbox controller without the S1? There is no lag when I do that.

richard

  • Global Moderator
  • *****
  • Posts: 4833
Re: t16000m fcs on xbox - massive deadzones
« Reply #9 on: May 21, 2020, 10:15:46 AM »
got it.

richard

  • Global Moderator
  • *****
  • Posts: 4833
Re: t16000m fcs on xbox - massive deadzones
« Reply #10 on: May 21, 2020, 11:17:59 AM »
one more question, does the delay issue go with buttons of your flightstick too?

dblaze025

  • Newbie
  • *
  • Posts: 7
Re: t16000m fcs on xbox - massive deadzones
« Reply #11 on: May 21, 2020, 12:52:22 PM »
no, its only the throttle control and the stick itself, and the rudder paddles on the throttles. the triggers and all the buttons do not have noticeable lag.

the xbox controls for throttle in battlefront 2 are controlled by left stick up/down and in ace combat its left trigger/right trigger. both lag when mapped to the main throttle control on the flight stick "Z+/-" however it is most noticeable on ace combat. on battlefront 2 it seems the roll lags the more than the other flight controls. 

dblaze025

  • Newbie
  • *
  • Posts: 7
Re: t16000m fcs on xbox - massive deadzones
« Reply #12 on: May 21, 2020, 01:15:57 PM »
Here is are two more videos, if you slow them down you can see there’s maybe 1-2 frames between pressing the button and the missiles firing on screen, not terrible. But the throttle takes several seconds to react.

https://imgur.com/gallery/lb5gsrM