If you plan to do any formation flight, then you need all the resolution you
can get from engine controls.
Anyway, I would try to dimension the resolution on the minimum amount of play
that can be obtained on the controls.
Just build one sensor and edit the input file so that you can map it to a
different channel every time, then check the FGFS property it is mapped to and
see if you can hold it to a set value and move it smoothly between the extremes.
Alessandro
> Date: Wed, 7 Mar 2012 20:59:18 +0100
> From: rob...@gmx.net
> To: flightgear-devel@lists.sourceforge.net
> Subject: Re: [Flightgear-devel] Double Input Resolution?
>
> > Think of it this way, determine the angular travel of your control
> > stick; for 8bits divide by 256; for 12 bits divide by 4096. That defines
> > the resoluion., i.e. degrees per bit. So then you have to decide how
> > good is your sensor in defining the control stick location. If you can't
> > sense 4096 discrete positions your wasting time and money using 12 bits.
>
> Well, I'll choose the proper sensor depending on the expected resolution
> (but not only!), no doubt about that. The method used to measure this
> value has its role too.
>
> I've read a good deal about hall sensors for high res sensors (I already
> started investigating those one too).
>
> You see I try and choose considering various factors here; FGFS needs
> are a part of this decision process. There's costs, easy of usage, and
> reliability also.
>
> I'd like to know what FGFS developers think it has to be expected from a
> decent input device, the other aspects are up to me.
>
> Torsten's right when it says the Parking Brake needs only 1bit
> resolution. He's got a valid point: it's his point of view :-)
>
> I'm not using a joystick since I installed Windows7 so I can't see
> what's the default input res used by FGFS with a Joystick. Could someone
> help me there?
> That's the res people using FGFS are generally expecting for basic
> elevator/aileron/rudder actions. And I guess it's enough for them. I
> wonder if more is needed.
>
> Then again, engine controls may work flawless with an 8bit res input.
> Anybody thinks a 10bit res is needed here?
>
> I'm not talking about what people are currently doing (I'd go with 24bit
> on everything ... joking!), I'm asking about reasons (technical aspects,
> facts) that can help me decide for high-res against low-res.
> That would help me a lot in making good choices with respect to what
> FGFS is expecting from an input device.
>
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
