I checked using Flightgear 0.9.8 but could not run it successfully.The few
lines of log data are as follows:

Running Main Loop
======= ==== ====
Updating time
 Current Unix calendar time = 1164188445  warp = 0
 Current GMT = 11/22/2006 9:40:45
 Current Unix calendar time = 1164188445  warp = 0
 Current GMT = 11/22/2006 9:40:45
 Current Julian Date = 2.45406e+006
 COURSE: GMT = 10/22/106 9:40:45
 March 21 noon (GMT) = 1142922600
 Time since 3/21/106 GMT = 246.132
 days = 246  hours = 9.67917  lon = 0  lst = 14.0792
 COURSE: GMT = 10/22/106 9:40:45
 March 21 noon (GMT) = 1142922600
 Time since 3/21/106 GMT = 246.132
 days = 246  hours = 9.67917  lon = 0  lst = 14.0792
 Current lon=0.00 Sidereal Time = 13.7616
 gst => 181.762
 Current LOCAL Sidereal Time = 13.7616 (13.7618) (diff =
Elapsed time interval is = 38000, previous remainder is =
Model iterations needed = 5, new remainder = 1346
Warning: read() not enough bytes.
interpolate(): lookup error, x to small = 0
interpolate(): lookup error, x to small = 0
 Updating Sun position
 Gst = 13.7616
   t->cur_time = 1164188445
   Sun Geodetic lat = -0.351519 Geocentric lat = -0.34935
sun angle relative to current location = 0.639324
 Updating Moon position
   t->cur_time = 1164188445
   Moon Geodetic lat = -0.484999 Geocentric lat = -0.4822
moon angle relative to current location = 0.951894
Updating adjusted fog parameters.
FGTileMgr::update()
State == Running
FGTileMgr::update()
State == Running

interpolate(): lookup error, x to small = 10
Cockpit: code 1 status 0



On 11/21/06, Thomas Biwer <[EMAIL PROTECTED]> wrote:

Umesh,

I am not quite sure but I think I've read something a long time ago that a
guy had the same kind of problem
and got rid of it by switching to another version of flightgear.
I think version 0.9.2 is quite obsolete. Maybe you should try changing to
0.9.10.

Otherwise, it would be nice to have some more detailed information about
the problem flightgear causes: Is it simply dying and closing
or hanging up? You might want to run FG with the --log-level=debug option
and tell us what the last message is you get from that.

Best,
Thomas


>
>Hi,
>I have interfaced external fdm(running separately on other PC) with
Flightgear by sending UDP packets to flightgear.i am currently using
Flightgear version 0.9.2 and 0.9.3 for >that purpose.however I have found
that although the packets reach the destination Pc,flightgear is not
running. I would like to know whether I am correctly forming and sending
>the UDP packets.I am pasting some parts of the code related to UDP
packets
sending.
>
>Code:
><snip>
>
>I am also using correct command to start FGFS with external fdm:
>D:\FlightGear 0.9.3\bin\Win32\FGFS.EXE--native-fdm=socket,in,30,,5500,udp
--fdm=external
>
>Please help......
>Regards,
>Umesh
>


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to