Board index FlightGear Support Hardware

Killing the deadspot

Joysticks, pedals, monitors.

Killing the deadspot

Postby StuartC » Sun Jul 22, 2018 6:44 pm

I am trying to kill a deadspot ( its only present in FG ). I have used the anti deadspot code in the XML, but it doesn't appear to have any effect.


<axis>
<dead-band type="double">0</dead-band>
<desc type="string">Aileron</desc>
<binding>
<command type="string">property-scale</command>
<property type="string">/controls/flight/aileron</property>
<factor type="double">1.0</factor>
<offset type="double">0</offset>
</binding>
</axis>

I have used it on all the axes, and the deadspot still exists.
Am I using that code wrong, or it is just not functional any more ?
StuartC
 
Posts: 2686
Joined: Fri Jun 18, 2010 8:18 pm
Location: Arse end of the Universe
Callsign: WF01
Version: 2018.3.2
OS: W10 64 bit

Re: Killing the deadspot

Postby sim » Sun Jul 22, 2018 10:10 pm

<axis n="0">
<desc>Aileron</desc>
<dead-band type="double">0.15</dead-band> <tolerance type="double">0.02</tolerance> <binding>
<command>property-scale</command>
<property>/controls/flight/aileron</property>
<offset type="double">0.0</offset>
<squared type="bool">true</squared>
</binding>
</axis>


This is from my AV8R stick, not much difference. Hope it works for you Stuart. Yours has dead band value as zero, try a higher value.
My Aileron has no factor value code although elevator and rudder do have it.
Last edited by sim on Sun Jul 22, 2018 10:31 pm, edited 4 times in total.
User avatar
sim
 
Posts: 1420
Joined: Tue Jun 30, 2009 2:13 pm
Location: Shropshire England
Callsign: Fly4Fun
Version: 0.9.10 up
OS: 64 Win 10 HD6450

Re: Killing the deadspot

Postby wkitty42 » Sun Jul 22, 2018 10:15 pm

StuartC wrote in Sun Jul 22, 2018 6:44 pm:<dead-band type="double">0</dead-band>

umm... a double should have a decimal point in it... try "0.0" instead of "0"...
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 5225
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: Killing the deadspot

Postby StuartC » Mon Jul 23, 2018 8:10 am

Tried both ways, nether make any difference to the dead zone at all.
StuartC
 
Posts: 2686
Joined: Fri Jun 18, 2010 8:18 pm
Location: Arse end of the Universe
Callsign: WF01
Version: 2018.3.2
OS: W10 64 bit

Re: Killing the deadspot

Postby wkitty42 » Mon Jul 23, 2018 6:27 pm

you're absolutely sure that FG is using the file that you are editing? we've seen that bite a few times ;)
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 5225
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: Killing the deadspot

Postby StuartC » Mon Jul 23, 2018 6:57 pm

Yes it is cos if I change anything in the joystick config screen it overwrites the changes I make in the xml.
StuartC
 
Posts: 2686
Joined: Fri Jun 18, 2010 8:18 pm
Location: Arse end of the Universe
Callsign: WF01
Version: 2018.3.2
OS: W10 64 bit

Re: Killing the deadspot

Postby wkitty42 » Mon Jul 23, 2018 8:18 pm

ha! ok... that's one way to test it :lol:

i don't have any other ideas... oh, but wait...

here's the only places that "dead-band" shows up in the FG src directory...
Code: Select all
~/flightgear-dev/next/flightgear/src$ egrep -Hinr -e "dead-band" *

Input/FGEventInput.cxx:152:  deadband = node->getDoubleValue("dead-band", 0.0);
Input/FGJoystickInput.cxx:273:      js->setDeadBand(n_axis, axis_node->getDoubleValue("dead-band", 0.0));
Input/fgjs.cxx:158:                axis->setDoubleValue("dead-band", jss->getJoystick(jsi->getInputJoystick())


which reminds me that at least the joystick code has been copied from plib so it can still be used even though plib is in the process of being eliminated... you might want to inquire on the dev list since that may have been affected by this work...
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 5225
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: Killing the deadspot

Postby StuartC » Mon Jul 23, 2018 8:24 pm

Its for my Heli kit, which isn't exactly supported correctly at the moment, although it does work.
StuartC
 
Posts: 2686
Joined: Fri Jun 18, 2010 8:18 pm
Location: Arse end of the Universe
Callsign: WF01
Version: 2018.3.2
OS: W10 64 bit

Re: Killing the deadspot

Postby wkitty42 » Mon Jul 23, 2018 8:29 pm

ahhh, yes... do you have something else with a dead area in it that you can dead-band out and see if dead-band is actually still working? i don't have anything here with a dead area to test with...
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 5225
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: Killing the deadspot

Postby StuartC » Mon Jul 23, 2018 8:31 pm

Nope my other controller is an RC box which has no dead spot. The Helikit is only seeing a Deadspot in FG, not in other sims.
StuartC
 
Posts: 2686
Joined: Fri Jun 18, 2010 8:18 pm
Location: Arse end of the Universe
Callsign: WF01
Version: 2018.3.2
OS: W10 64 bit


Return to Hardware

Who is online

Users browsing this forum: No registered users and 0 guests