Curt...
I believe I'm just inputting control surface positions, however but I did
have the remote plugged in, I'll make sure to unplug it on my next try.
On Sun, Aug 7, 2011 at 11:10 AM, Curtis Olson <curtol...@gmail.com> wrote:
> Inputs: what inputs are you sending? Are they getting overwritten by
> internal processing? If you are inputting position and orientation (for
> instance) you need to turn off the internal flight dynamics engine
> (--fdm=null) If you are inputting control surface positions, you probably
> don't want a joystick plugged in, etc.
>
>
> On Sun, Aug 7, 2011 at 6:12 AM, Arnt Karlsen <a...@c2i.net> wrote:
>
>> On Sat, 6 Aug 2011 23:09:44 -0400, Derrick wrote in message
>> <CAF74wjbov8xiA26W3_n2EA6HX04B2_8+U6mPn=9votkv8hu...@mail.gmail.com>:
>>
>> > OK so I found a solution, I think, I changed the COM port number to
>> > COM3. That seems to work but now FLIGHTGEAR will not accept inputs
>> > for some reason, when I set as shown below, FG just sits there and
>> > spins its wheels. If I set it up for output that works just fine. In
>> > addition to that I can't setup two generic protocols one for input
>> > and one for output, when I do that I just get an error can not open
>> > com port. I'm beginning to think that communication through the
>> > serial port doesn't work at all.
>> >
>> > C:\Program Files\FlightGear\bin\Win32\fgfs.exe
>> > --fg-root=C:\Program Files\FlightGear\data
>> > --fg-scenery=C:\Program Files\FlightGear\data\Scenery;C:\Program
>> > Files\FlightGear\scenery;C:\Program Files\FlightGear\terrasync
>> > --aircraft=f-14b
>> > --control=joystick
>> > --enable-random-objects
>> > --enable-ai-models
>> > --enable-clouds3d
>> > --fog-disable
>> > --geometry=1280x1024
>> > --bpp=32
>> > --texture-filtering=16
>> > --timeofday=noon
>> > --atlas=socket,out,5,localhost,5500,udp
>> > --generic=serial,in,3,COM3,115200,FlightGear_GPI
>>
>> ..tried --generic="serial,in,3,\\.\COM3,115200,FlightGear_GPI"?
>>
>>
>> --
>> ..med vennlig hilsen = with Kind Regards from Arnt Karlsen
>> ...with a number of polar bear hunters in his ancestry...
>> Scenarios always come in sets of three:
>> best case, worst case, and just in case.
>>
>>
>> ------------------------------------------------------------------------------
>> BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
>> The must-attend event for mobile developers. Connect with experts.
>> Get tools for creating Super Apps. See the latest technologies.
>> Sessions, hands-on labs, demos & much more. Register early & save!
>> http://p.sf.net/sfu/rim-blackberry-1
>> _______________________________________________
>> Flightgear-devel mailing list
>> Flightgear-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>>
>
>
>
> --
> Curtis Olson:
> http://www.atiak.com - http://aem.umn.edu/~uav/
> http://www.flightgear.org - http://gallinazo.flightgear.org
>
>
>
> ------------------------------------------------------------------------------
> BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
> The must-attend event for mobile developers. Connect with experts.
> Get tools for creating Super Apps. See the latest technologies.
> Sessions, hands-on labs, demos & much more. Register early & save!
> http://p.sf.net/sfu/rim-blackberry-1
> _______________________________________________
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
>
------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
The must-attend event for mobile developers. Connect with experts.
Get tools for creating Super Apps. See the latest technologies.
Sessions, hands-on labs, demos & much more. Register early & save!
http://p.sf.net/sfu/rim-blackberry-1
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
