Re: [Flightgear-devel] Compiling CVS version with cygwin/gcc3.2-2....
David Megginson wrote: Patrick Staehlin writes: To compile the development CVS version of FlightGear(0.9.0) i had to apply some small changes to SimGear and FlightGear. The changes need probably some additional ifdefs for other platforms but since my linux-hd crashed i can't verify that. These are in CVS now. It needs one small adjustment: --- /home/erik/src/CVS/fgfs/SimGear/simgear/sky/clouds3d/SkyContext.hpp Sun Nov 17 10:18:47 2002 +++ SimGear/simgear/sky/clouds3d/SkyContext.hpp Sun Nov 17 10:29:46 2002 @@ -29,11 +29,10 @@ // warning for truncation of template name for browse info // #pragma warning( disable : 4786) #include SkySingleton.hpp -#include compiler.h +#include simgear/compiler.h #include list #include map #include algorithm -#include compiler.h #ifdef WIN32 # include extgl.h #else Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
re: [Flightgear-devel] dc3 main gear animation broken
Dave Perry writes: I compared the dc3-dpm.xml file with that in the 8.0 source, and it is the same. Have any of the recent changes (yasim?) broken this? No, it was a bug-fix to model.cxx. I'll look at it when I get a chance, but if someone else (Jim?) wants to fix it first, I don't plan on complaining. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Compiling CVS version with cygwin/gcc3.2-2....
Erik Hofman writes: It needs one small adjustment: Thanks -- it's in CVS now. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Engine models: start-up and commonality betweenFDMs
David Megginson wrote: Julian Foad writes: Ah, glad you're there. If you're interested and have time to look, my current attempt is at http://www.btinternet.com/~julianfoad/fgfs/JSB_piston_engine.diff http://www.btinternet.com/~julianfoad/fgfs/engine_sound.diff What's the current status of these? Are the people who work with sound in general agreement that they're a good thing? I've looked at the sound stuff, but without a proper explanation I see no need to apply it. Even worse, it doesn't seem to work without some code changes. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] dc3 main gear animation fix
David Megginson wrote: No, it was a bug-fix to model.cxx. I'll look at it when I get a chance, but if someone else (Jim?) wants to fix it first, I don't plan on complaining. I used intuition from the new main gear rotation animations. I made the following change to the four offset-deg referencing the main gear (wheel and strut). offset-deg+34/offset-deg This makes the two positions of the main gear correct and the motion seems OK. This was my first guess. - Dave P. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] MSVC6 WIN98 Update - Nov. 2002
Success at last!
Added one more fix in plib -
In ssgContext.cxx, added the line
ssgContext::ssgContext () {
...
ovCullface = FALSE ;
ovState = NULL ;
and re-built plib (Debug and Release)
And i was up and flying. Well not quite. Running the Debug
version under the default fdm (w/ panel) is folly in my little system,
it had 'crashed' before any good scene graph was shown, or 'user
inputs' read, so i added my - quiet - system.fgfsrc, of -
file
# 2002 Nov 17
--aircraft=ufo
--altitude=2500
--disable-panel
--fog-disable
--disable-clouds
--enable-hud
/file
and, of course into hud.cxx, i dropped my usual line after -
HUD_TextList.add( fgText(40, 10, gmt_str, 0) );
#include hud-fr.inl
which contains -
#ifndef HUD_IN_XML
{
char buf[32];
sprintf(buf, %d, (int)get_frame_rate() );
HUD_TextList.add( fgText(540, 10, buf, 0) );
}
#endif // !HUD_IN_XML
and there i was, as 2500 feet, in a 'beautiful' ac - ufo.
The new joysticks.xml arrangement is great, in that
to accomodate my system i only need to add the line -
js n=1 include=Input/Joysticks/Default/joystick.xml/
and my MS Sidewinder js worked fine ...
WOW, the new 'scenery' with 'building', and the runway
lights, make flying the ufo truely magic ...
If i maintained direction, and a steady speed saw frame rates
as high as 34, running Release version, in a CONSOLE
where all stdout and stderr are redirected to a file - my own
exec32.exe.
It is fantastic what has been achieved. Congratulations.
Hope some of my 'fixes' help ...
Regards,
Geoff.
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] dc3 main gear animation fix
Dave Perry [EMAIL PROTECTED] said: I used intuition from the new main gear rotation animations. I made the following change to the four offset-deg referencing the main gear (wheel and strut). offset-deg+34/offset-deg This makes the two positions of the main gear correct and the motion seems OK. This was my first guess. - Dave P. Dave, All that David M. changed was the order of the math, previously the offset value was incorrectly applied directly to the unfactored input values. The new code implies that the factor must convert to degrees (which make sense since thats how the 3D rotations work and was the original intention). It was: (input + offset) * factor. Now it is: input * factor + offset-deg. So the change to the xml returning animation behavior to what it was before the fix is very simple. On existing models: thenew-offset-deg = factor * theold-offset-deg. The dc3 fix is in cvs now. I'm thinking this finally fixes all the models in cvs, but there may be some others or folks might have their own local customizations. Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] dc3 main gear animation fix
Jim Wilson writes: The dc3 fix is in cvs now. I'm thinking this finally fixes all the models in cvs, but there may be some others or folks might have their own local customizations. Many thanks. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Flying Tutorial
Hello, I've started to write a FlightGear Training. Sometime hopefully it will be a full comprehensive manual for users. It starts right at the end of Michael and Martin's 'Getting Started' and will explain all (say most) aspects of aviation and FlightGear. You will find the very first idea of the document under: http://home.t-online.de/home/carsten.hoefer/docs.html As You will see it's only the structure of the tutorial, but it should give You the idea behind it. I would like You to read it and tell me Your opinion. Did I miss something? Is there a better order? Is anyone out there to write one of the sections? Carsten ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Code
Jon Berndt wrote: Is there a way to determine which methods/attributes in a class are unused by anybody? I'm thinking maybe there's a utility out there somewhere or a link directive. This would assist in code streamlining/cleanup. Other than grep :-) You can browse through lists of references, looking for empty lists, in a source browser like the ones in MS Visual C++ and Source Navigator (formerly by Red Hat, now a SourceForge project). In MSVC you can only browse, as far as I know, but Source Navigator is open-source and uses Perl or Python scripts to do much of its user interface, so it's probably not hard to get it to output the list of unreferenced symbols. Others IDEs like KDevelop list definitions and declarations but not references. Getting the linker to tell you is an interesting idea that I haven't looked into. Perhaps you could do this manually by listing the public symbols in each library first, and then in the linked application, and comparing the two lists. Or perhaps you can make one list of all the exported symbols from the application and its libraries, and another list of all the imported symbols, and compare those. The unix utilities nm and objdump can list symbols in object files and libraries. I haven't come across a utility specifically for doing this, but I'd be interested. - Julian ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Engine models: start-up and commonality betweenFDMs
David Megginson wrote: Julian Foad writes: Ah, glad you're there. If you're interested and have time to look, my current attempt is at http://www.btinternet.com/~julianfoad/fgfs/JSB_piston_engine.diff http://www.btinternet.com/~julianfoad/fgfs/engine_sound.diff What's the current status of these? They're only ideas in progress, and are not right. Please don't put them in CVS as they are. - Julian ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Code
Julian Foad writes: Jon Berndt wrote: Is there a way to determine which methods/attributes in a class are unused by anybody? I'm thinking maybe there's a utility out there somewhere or a link directive. This would assist in code streamlining/cleanup. Getting the linker to tell you is an interesting idea that I haven't looked into. Perhaps you could do this manually by listing the public symbols in each library first, and then in the linked application, and comparing the two lists. Or perhaps you can make one list of all the exported symbols from the application and its libraries, and another list of all the imported symbols, and compare those. The unix utilities nm and objdump can list symbols in object files and libraries. I haven't come across a utility specifically for doing this, but I'd be interested. This one got me thinking to :-) I am not familiar enough with the internals of the ld to know how todo this but this is EXACTLY the kind of thing that libbfd is for % info bfd ld can create a cross reference file that may be a good starting point for doing this by hand. The resulting cxref file lists all the functions sorted alphabetically and all of the object files that they are referenced from FGFCS::GetComponentName(int) ../../src/FDM/JSBSim/libJSBSim.a(FGFCS.o) FGFCS::GetComponentOutput(int) ../../src/FDM/JSBSim/libJSBSim.a(FGFCS.o) FGFCS::GetComponentStrings() ../../src/FDM/JSBSim/libJSBSim.a(FGFCS.o) ../../src/FDM/JSBSim/libJSBSim.a(FGOutput.o) FGFCS::GetComponentValues() ../../src/FDM/JSBSim/libJSBSim.a(FGFCS.o) ../../src/FDM/JSBSim/libJSBSim.a(FGOutput.o) FGFCS::GetDaCmd() const ../../src/FDM/JSBSim/libJSBSim.a(FGFCS.o) add -Wl,--cref to $LDFLAGS in the src/Main/Makefile if you want to experiment be warned this results in a large cxref file ~5 meg Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
re: [Flightgear-devel] Flying Tutorial
Carsten Höfer writes: As You will see it's only the structure of the tutorial, but it should give You the idea behind it. I would like You to read it and tell me Your opinion. Did I miss something? Is there a better order? Is anyone out there to write one of the sections? It looks interesting -- I'll try to find time to read it in more detail. In the meantime, you asked for checklists. Fortunately, I'm a fast typist, so here are the checklists for normal procedures in the 1981 C172P, straight out of the POH (forgive any typos): PREFLIGHT INSPECTION (1) Cabin 1. Pilot's Operating Handbook -- AVAILABLE IN THE AIRPLANE. 2. Control Wheel Lock -- REMOVE. 3. Ignition Switch -- OFF. 4. Avionics Power Switch -- OFF. 5. Master Switch -- ON. 6. Fuel Quantity Indicators -- CHECK QUANTITY. 7. Avionics Cooling Fan -- CHECK AUDIBLY FOR OPERATION. 8. Master Switch -- OFF. 9. Static Pressure Alternate Source Value (if installed) -- OFF. 10. Baggage Door -- CHECK, lock with key if child's seat is to be occupied. (2) Empennage 1. Rudder Gust Lock -- REMOVE. 2. Tail Tie-Down -- DISCONNECT. 3. Control Surfaces -- CHECK freedom of movement and security. (3) Right Wing Trailing Edge 1. Aileron -- CHECK freedom of movement and security. (4) Right Wing 1. Wing Tie-Down -- DISCONNECT. 2. Main Wheel tire -- CHECK for proper inflation. 3. Before the first flight of the day and after each refueling, use sampler cup and drain small quantity of fuel from fuel tank sump quick-drain valve to check for water, sediment, and proper fuel grade. 4. Fuel Quantity -- CHECK VISUALLY for desired level. 5. Fuel Filler Cap -- SECURE. (5) Nose 1. Engine Oil Level -- CHECK, do not operate with less than five quarts. Fill to seven quarts for extended flight. 2. Before first flight of the day, and after each refueling, pull out strainer drain knob for about four seconds to clear fuel strainer of possible water and sediment. Check strainer drain closed. If water is observed, the fuel system may contain additional water, and further draining of the system at the strainer, fuel tank sumps, and fuel selector value drain plug will be necessary. 3. Propeller and Spinner -- CHECK for nicks and security. 4. Landing Light(s) -- CHECK for condition and cleanliness. 5. Carburetor Air Filter -- CHECK for restrictions by dust or other foreign matter. 6. Nose Wheel Strut and Tire -- CHECK for proper inflation. 7. Nose Tie-Down -- DISCONNECT. 8. Static Source Opening (left side of fuselage) -- CHECK for stoppage. (6) Left Wing 1. Main Wheel Tire -- CHECK for proper inflation. 2. Before first flight of the day and after each refueling, use sampler cup and drain small quantity of fuel from fuel tank sump quick-drain value to check for water, sediment, and proper fuel grade. 3. Fuel Quantity -- CHECK VISUALLY for desired level. 4. Fuel Filler Cap -- SECURE. (7) Left Wing Leading Edge 1. Pitot Tue Cover -- REMOVE and check opening for stoppage. 2. Fuel Tank Vent Opening -- CHECK for stoppage. 3. Stall Warning Opening -- CHECK for stoppage. To check the system, place a clean handkerchief over the vent opening and apply suction: a sound from the warning horn will confirm system operation. 4. Wing Tie-Down -- DISCONNECT. (8) Left Wing Trailing Edge 1. Aileron -- CHECK for freedom of movement and security. BEFORE STARTING ENGINE 1. Preflight Inspection -- COMPLETE. 2. Seats, Seat Belts, Shoulder Harnesses -- ADJUST and LOCK. 3. Fuel Selector Value -- BOTH. 4. Avionics Power Switch, Autopilot (if installed), Electrical Equipment -- OFF. 5. Brakes -- TEST and SET. 6. Circuit Breakers -- CHECK IN. STARTING ENGINE 1. Mixture -- RICH. 2. Carburetor Heat -- COLD. 3. Master Switch -- ON. 4. Prime -- AS REQUIRED (2 to 6 strokes; none if engine is warm). 5. Throttle -- OPEN 1/8 INCH. 6. Propeller Area -- CLEAR. 7. Ignition Switch -- START (release when engine starts). 8. Oil Pressure -- CHECK. 9. Flashing Beacon and Navigation Lights -- ON as required. 10. Avionics Power Switch -- ON. 11. Radios -- ON. BEFORE TAKEOFF 1. Parking Brake -- SET. 2. Cabin Doors and Window(s) -- CLOSED and LOCKED. 3. Flight Controls -- FREE and CORRECT. 4. Flight Instruments -- SET. 5. Fuel Selector Value -- BOTH. 6. Mixture -- RICH (below 3000 feet). 7. Elevator Trim and Rudder Trim (if installed) -- TAKEOFF. 8. Throttle -- 1700 RPM. a. Magnetos -- CHECK (RPM drop should not exceed 125 RPM on either magneto or 50 RPM differential between magnetos). b. Carburetor Heat -- CHECK (for RPM drop). c. Engine Instruments and Ammeter -- CHECK. d. Suction Gage -- CHECK. 9. Throttle -- 1000 RPM or LESS. 10. Radios -- SET. 11. Autopilot (if installed) -- OFF. 12. Air Conditioner (if installed) -- OFF. 13. Strobe Lights -- AS DESIRED. 14. Throttle Friction Lock -- ADJUST. 15. Brakes -- RELEASE. TAKEOFF Normal Takeoff 1. Wing Flaps -- 0 deg - 10 deg. 2. Carburetor Heat -- COLD. 3. Throttle --
