[Flightgear-devel] Segmentation fault using --native option

2007-03-20 Thread Sébastien MARQUE
Hi,

I got a segmentation fault using
--native=file,in,10,test --fdm=external
where the file test is 12MB big

Then I tried with a smaller file (1.2MB) and it worked fine.

I'm using FG OSG CVS, compiled yesterday and this is the first time I 
use this option.
The test files are created using --native=file,out,10,test

here is the result (last lines) of --log-level=debug with the 12MB size 
file:

Running Main Loop
===  
Updating time
   Current Unix calendar time = 1174401951  warp = 0
   Current GMT = 3/20/2007 14:45:51
   Current Unix calendar time = 1174401951  warp = 0
   Current GMT = 3/20/2007 14:45:51
   Current Julian Date = 2.45418e+06
   COURSE: GMT = 2/20/107 14:45:51
   March 21 noon (GMT) = 1174478400
   Time since 3/21/107 GMT = -0.884826
   days = 0  hours = 14.7642  lon = 0  lst = 2.76417
   COURSE: GMT = 2/20/107 14:45:51
   March 21 noon (GMT) = 1174478400
   Time since 3/21/107 GMT = -0.884826
   days = 0  hours = 14.7642  lon = 122.357  lst = 18.607
   Current lon=0.00 Sidereal Time = 2.61449
   gst = 194.614
   Current LOCAL Sidereal Time = 18.4573 (18.4573) (diff = -0.149675)
Elapsed time interval is = 716961, previous remainder is = 1083
-- Frame rate is = 7
Model iterations needed = 86, new remainder = 1378
Finally initializing fdm
Start common FDM init
...initializing position...
Checking for lon = -122.357deg, lat = 37.6135deg, alt = -ft
prepare_ground_cache(): ac radius = 10, # triangles = 0, # wires = 0, # 
catapults = 0, ground_radius = 0
prepare_ground_cache(): trying to build cache without any scenery below 
the aircraft
prepare_ground_cache(): ac radius = 10, # triangles = 0, # wires = 0, # 
catapults = 0, ground_radius = 6.37021e+06
...initializing ground elevation to -1.512ft...
...initializing sea-level radius...
  lat = 37.6135 alt = -1.412
...initializing velocities...
...initializing Euler angles...
End common FDM init
Attempt to set archive flag for non-existant property 
/position/ground-elev-ft
Attempt to set archive flag for non-existant property 
/position/ground-elev-m
Attempt to set archive flag for non-existant property 
/position/sea-level-radius-ft
** FDM initialized **
lon = -2.13554 lat_geod = 0.65648 lat_geoc = 0.653236 alt = -1.412 
sl_radius = 2.08996e+07 Equator = 2.09256e+07
prepare_ground_cache(): ac radius = 10, # triangles = 27, # wires = 0, # 
catapults = 0, ground_radius = 6.37021e+06
Success reading data.
Erreur de segmentation

Best regards.

Seb

-
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.phpp=sourceforgeCID=DEVDEV
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] tutorial news

2007-03-20 Thread AJ MacLeod
On Tuesday 20 March 2007 00:35, Melchior FRANZ wrote:
 I've started to overhaul Stuart's (excellent!) tutorial system.
 See the Lightning's startup tutorial for a marker example.
 It draws a nice blinking, magenta colored marker circle around
 the switch that the user is supposed to press.  :-)
Thanks for working on this - I don't know how many people have found and/or 
used the existing Lightning engine start tutorial (or indeed any of the 
existing tutorials), but the marker in particular is a huge improvement 
(particularly for those who have poor English.)

 More tutorial changes to expect ...
I'm looking forward in particular to the lookat thingy, that should be a very 
nice touch...

For other aircraft authors (or even those who aren't, but would like to 
contribute their knowledge of various flight procedures etc), I'd encourage 
people to have a look at adding more tutorials.  The process is really not 
very difficult (reading the existing examples should be quite sufficient 
documentation) and as usual help can be had from here or the IRC channel.

These tutorials can be a big help to people just starting out with FG, and are 
so much better than a dry description of processes.  I'm also certain that 
with a little imagination our (amazingly flexible) tutorial system can be 
abused a bit to add all sorts of other interesting functions and scenarios 
into FG ;-)

Cheers,

AJ

-
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.phpp=sourceforgeCID=DEVDEV
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] tutorial news

2007-03-20 Thread Stuart Buchanan
--- AJ MacLeod wrote:
 On Tuesday 20 March 2007 00:35, Melchior FRANZ wrote:
  I've started to overhaul Stuart's (excellent!) tutorial system.
  See the Lightning's startup tutorial for a marker example.
  It draws a nice blinking, magenta colored marker circle around
  the switch that the user is supposed to press.  :-)

snip

 These tutorials can be a big help to people just starting out with FG,
 and are 
 so much better than a dry description of processes.  I'm also certain
 that 
 with a little imagination our (amazingly flexible) tutorial system can
 be 
 abused a bit to add all sorts of other interesting functions and
 scenarios 
 into FG ;-)

One scenario I thought might be quite fun to put together would be a
helicopter Search and Rescue. This led me to think of new features that
would make writing such a tutorial easier.

1) A distance-to function, that would evaluate to true when the user was
within a given distance to a point (expressed in lat/long). This would be
more useful than the current work-around that forces the tutorial writer
to define a box with given long/lat sides. 

2) The ability to define objects in the scenery within a tutorial, e.g.
adding a downed aircraft/missing walker

3)The ability to trigger select animations on objects. This is possible
indirectly by writing to a property, but isn't ideal.

Of course, this is all stuff I should be adding myself, but I'm sure
Melchior could put together a much more elegant solution before I got as
far as recompiling FG with the latest CVS :)

-Stuart



___ 
What kind of emailer are you? Find out today - get a free analysis of your 
email personality. Take the quiz at the Yahoo! Mail Championship. 
http://uk.rd.yahoo.com/evt=44106/*http://mail.yahoo.net/uk 

-
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.phpp=sourceforgeCID=DEVDEV
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] tutorial news

2007-03-20 Thread Melchior FRANZ
I just committed some changes. Among other things, one can now also
open the tutorial marker adjustment dialog by typing tutorial.dialog()
in the Help-Nasal-Console, so people don't have to bother defining
key bindings. It's not such an often used feature.



* Stuart Buchanan -- Tuesday 20 March 2007:
 One scenario I thought might be quite fun to put together would be a
 helicopter Search and Rescue.

Yes, I thought of that, too. Missions where the copilot directs one
to the car accident etc. (Follow the street ... Ten miles ... Ohh ...
that doesn't look good ...  :-)
 


 1) A distance-to function, [...]

Should be easy. The Nasal code for that is already in ufo.nas. Just
need to factor that out in a separate library.



 2) The ability to define objects in the scenery within a tutorial, e.g.
 adding a downed aircraft/missing walker

That's already possible. I implemented that for the ufo scenery object
editor. And the bo105 placed Memorial Cows at crash locations, but
this service wasn't well received ...   ;-)  Just need to add a small
function.



 3)The ability to trigger select animations on objects. This is possible
 indirectly by writing to a property, but isn't ideal.

Well, properties are really the only way to communicate with animations,
and that's not a bad thing. You can now embed Nasal in tutorials, so
there's nothing stopping you from launching an interpolate() etc.



 before I got as far as recompiling FG with the latest CVS :)

There were no changes in C++. You just need to update data/cvs (which
works for both branches -- with the sad exception of some traffic
stuff, which we should really migrate. There's really no point in
having two branches with this being the only difference.

m.

-
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.phpp=sourceforgeCID=DEVDEV
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] tutorial news

2007-03-20 Thread Melchior FRANZ
* Stuart Buchanan -- Tuesday 20 March 2007:
 1) A distance-to function, that would evaluate to true when the user was
 within a given distance to a point (expressed in lat/long). This would be
 more useful than the current work-around that forces the tutorial writer
 to define a box with given long/lat sides.

Implemented. One can define one or more targets:

  targets
  target
  longitude-deg-122.37931/longitude-deg
  latitude-deg37.626/latitude-deg
  /target

  target
  longitude-deg-123.456/longitude-deg
  latitude-deg34.567/latitude-deg
  /target
  /targets


... and the tutorial logic will offer distance and direction of the
aircraft to each of them as

  /sim/tutorial/targets/target[0]/direction-deg
  /sim/tutorial/targets/target[0]/distance-m

  /sim/tutorial/targets/target[1]/direction-deg
  /sim/tutorial/targets/target[1]/distance-m

A direction of 0 means that the target is straight ahead, 90 means
it's on the right, -90 on the left, -180 or -179. in the back.
This can then be used in conditions.


Another improvement is, that one can now define more than one
message or audio, in which case one is chosen at random. See
the cvs log message for an example.  :-)

m.

-
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.phpp=sourceforgeCID=DEVDEV
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel