Re: [Flightgear-devel] jsbsim won't start with w110n40 or w110n30 airports

2005-07-27 Thread Gerard Robin
Le mardi 26 juillet 2005 à 23:13 +0200, Mathias Fröhlich a écrit :
 Hi,
 
 sorry for the late reaction.
 Turns out to be a bad interaction between jsbsims crash detection and my
 past initialization changes.
 The attached patch fixes this by moving crash detection out of the
 initialization phase of jsbsim.
 
 Erik,
 Can you apply that please to flightgears cvs.
 I will care for JSBsim's cvs.
 
 Thanks and sorry
 
Hello Mathias,

I don't understand why do you continu to develop on that wrong crash
detection.
It is a nonsense regarding the JSB undercarriage facilities.
it is a nonsense regarding the other old crash detection process
in
FGLGear.cpp line 507 
 Here's the code: 
 // Crash detection logic (really out-of-bounds detection) 
 if (compressLength  500.0 ||
 vForce.Magnitude()  1.0 ||
 vMoment.Magnitude()  50.0 ||
 SinkRate  1.4666*30)
 {
   PutMessage(Crash Detected: Simulation FREEZE.);
   Exec-Freeze();
 }
The undercarriage definition is very flexible. It gives the facilities
to manage an aircraft customised crash animation with the help of a
nasal script.
If an improvement must be done it could be done on the old existing code
with specifics properties like that one which is coming from a Dave
mail.
crash-detection
  altitude-agl0/altitude-agl
   g-z-max11.0/g-z-max
   g-z-min5.0/g-z-min
   g-x-max20/g-x-max
   g-x-min20/g-x-min
   qbar1089.0/qbar
   pitch-rate3.7/pitch-rate
   yaw-rate3.5/yaw-rate
   mach0.99/mach
 /crash-detection


I fear, the user opinion  is not useful for the development team.
I fear the user opinion is not taken in account.
Please tell me, by that way i will continu to subscribe or not.

Thanks

-- 
Gerard


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] jsbsim won't start with w110n40 or w110n30 airports

2005-07-27 Thread Erik Hofman

Mathias Fröhlich wrote:


Erik,
Can you apply that please to flightgears cvs.
I will care for JSBsim's cvs.


Done.

Erik

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] jsbsim won't start with w110n40 or w110n30 airports

2005-07-26 Thread Harald JOHNSEN

Dave Perry wrote:

This bug showed up about 10 days ago with an update from cvs.  Any 
ideas what is broken?


Regards,
Dave Perry


I have started to investigate that problem but not found anything atm.
I can reproduce the bug in the same situation as you.
FG is *not* freezed. All (?) is working correctly except the screen is 
not refreshed for some strange reason.
The main loop is executed, the render code is executed, you can do a 
clean exit with escape + enter.


Harald.


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] jsbsim won't start with w110n40 or w110n30 airports

2005-07-26 Thread Mathias Fröhlich

Hi,

sorry for the late reaction.
Turns out to be a bad interaction between jsbsims crash detection and my
past initialization changes.
The attached patch fixes this by moving crash detection out of the
initialization phase of jsbsim.

Erik,
Can you apply that please to flightgears cvs.
I will care for JSBsim's cvs.

Thanks and sorry

   Mathias

On Dienstag 26 Juli 2005 03:38, Dave Perry wrote:
 I have posted this issue twice before.  This is with plib, SimGear, fg, 
 and data all from recent cvs.  I have fgfs from cvs up-to-date on my 
 desktop and notebook, both running Linux FC3 and both have this bug 
 after updates from about 10 days ago.
 
 I don't know if there are others that use fgfs from front range 
 locations in Colorado, but I use it to practice instrument approaches in 
 this my home area and my two favorite aircraft for this are the c172p 
 and c310, both jsbsim models.  _The yasim aircraft still work fine with 
 this scenery._  By the way, I downloaded both w110n30.tgz and 
 w110n40.tgz and reinstalled both with no change to this bug.  I have not 
 seen this issue with airports not from these scenery files.
 
 I used --log-level=info to try and figure out what the issue is and here 
 is the beginning and end of that log.
 
  [EMAIL PROTECTED] data]$ ./bin/fgfs 
  --fg-scenery=/usr/local/Scenery-0.9.8 --log-level=info --airport=2V2 
  --aircraft=c172
  Finished command line arguments
  Initializing splash screen
  GeForce FX 5600 Ultra/AGP/SSE/3DNOW!
  Max texture size = 4096
  Depth buffer bits = 24
  Loading Airport Database ...
  Data file version = 715
  [FINISHED LOADING]
  Loading Navaid Databases
  Standardising rwy number from B to 0B
Fixes
  Attempting to set starting position for 2V2:28R
  Failed to find runway 28R at airport 2V2
  Attempting to set starting position from airport code 2V2 heading 270
  runway =  -105.164, 40.1644 length = 1459.99 heading = 122.75
  Position for 2V2 is (-105.156, 40.1609) new heading is 302.75
  Searching for airport code = 2V2
  Position for 2V2 is (-105.164, 40.1638)
  Initializing Time
  Current greenwich mean time = Tue Jul 26 01:12:53 2005
 
  Current local time  = Mon Jul 25 19:12:53 2005
 
  Reading timezone info from: /usr/local/FlightGear/Timezone/zone.tab
  Using zonename = /usr/local/FlightGear/Timezone/America/Denver
First time, doing precise gst
  General Initialization
  === ==
 
 ...
 
  Ltoken = OBJECT_BASE name = 1237121.btg
  token = OBJECT name = CO82.btg
  token = OBJECT name = 7CO3.btg
  token = OBJECT name = K18V.btg
  token = OBJECT name = K18V.btg
  token = OBJECT_SHARED name = Models/Structures/radio-medium.xml pos = 
  -104.604, 40.1208 elevation = 1459 heading = 0
  token = OBJECT_SHARED name = Models/Structures/radio-medium.xml pos = 
  -104.742, 40.0566 elevation = 1488 heading = 0
  token = OBJECT_SHARED name = Models/Structures/radio-medium.xml pos = 
  -104.747, 40.0555 elevation = 1497.8 heading = 0
  prepare_ground_cache(): ac radius = 5.5146, # triangles = 28, # wires 
  = 0, # catapults = 0, ground_radius = 6.37082e+06
  Ltoken = OBJECT_BASE name = 1237129.btg
  token = OBJECT name = 03CO.btg
  token = OBJECT name = 03CO.btg
  prepare_ground_cache(): ac radius = 5.5146, # triangles = 28, # wires 
  = 0, # catapults = 0, ground_radius = 6.37082e+06
  Loading tile /usr/local/Scenery-0.9.8/w110n40/w105n40/1237137
  token = OBJECT_BASE name = 1237137.btg
  token = OBJECT name = K11V.btg
  token = OBJECT name = K11V.btg
  token = OBJECT_SHARED name = Models/Structures/radio-medium.xml pos = 
  -104.706, 40.2614 elevation = 1407.8 heading = 0
  prepare_ground_cache(): ac radius = 5.5146, # triangles = 28, # wires 
  = 0, # catapults = 0, ground_radius = 6.37082e+06
  Loading tile /usr/local/Scenery-0.9.8/w110n40/w105n40/1237145
  token = OBJECT_BASE name = 1237145.btg
  token = OBJECT name = KGXY.btg
  token = OBJECT_SHARED name = Models/Airport/beacon.xml pos = -104.636, 
  40.4291 elevation = 1418 heading = 0
  token = OBJECT name = CO70.btg
  token = OBJECT name = CO70.btg
  token = OBJECT_SHARED name = Models/Structures/radio-medium.xml pos = 
  -104.724, 40.4375 elevation = 1328 heading = 0
  token = OBJECT_SHARED name = Models/Structures/radio-medium.xml pos = 
  -104.724, 40.4378 elevation = 1328.3 heading = 0
  prepare_ground_cache(): ac radius = 5.5146, # triangles = 28, # wires 
  = 0, # catapults = 0, ground_radius = 6.37082e+06
  Loading tile /usr/local/Scenery-0.9.8/w110n40/w105n40/1237153
  token = OBJECT_BASE name = 1237153.btg
  token = OBJECT name = CO48.btg
  token = OBJECT name = CO48.btg
  prepare_ground_cache(): ac radius = 5.5146, # triangles = 28, # wires 
  = 0, # catapults = 0, ground_radius = 6.37082e+06
  prepare_ground_cache(): ac radius = 5.5146, # triangles = 28, # wires 
  = 0, # catapults = 0, ground_radius = 6.37082e+06
  prepare_ground_cache(): ac radius = 5.5146, # triangles = 28, # wires 
  = 0, # catapults = 0, ground_radius = 6.37082e+06
  

Re: [Flightgear-devel] jsbsim won't start with w110n40 or w110n30 airports

2005-07-26 Thread Gerard Robin
Le mardi 26 juillet 2005 à 23:13 +0200, Mathias Fröhlich a écrit :
 Hi,
 
 sorry for the late reaction.
 Turns out to be a bad interaction between jsbsims crash detection and my
 past initialization changes.
 The attached patch fixes this by moving crash detection out of the
 initialization phase of jsbsim.
 
 Erik,
 Can you apply that please to flightgears cvs.
 I will care for JSBsim's cvs.
 
 Thanks and sorry
 
Mathias
 
Or only comment, in order to come back to the good old process.

 // crashed (altitude AGL  0)
   //if (get_Altitude_AGL()  0.0) {
   // crash_message = Attempted to fly under ground.;
   // crash_handler();
   // }
-- 
Gerard


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d