[Flightgear-devel] New Email Address for Dave Perry
I am sending this to all my contacts. My new e-mail address is skida...@gmail.com Please update your contacts if you think you might need to contact me in the future. Thanks, Dave Perry -- LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/22/13. http://pubads.g.doubleclick.net/gampad/clk?id=64545871iu=/4140/ostg.clktrk___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] auto-coordination
Also, the real pa22 Tri-Pacer has a spring rudder interlock with the ailerons so it can be overridden by the pilot when he wants to have cross control as in a cross wind. Dave P. On 03/09/2012 02:45 PM, Adam Dershowitz, Ph.D., P.E. wrote: Few, but at least one: http://en.wikipedia.org/wiki/ERCO_Ercoupe --Adam On Mar 9, 2012, at 12:05 PM, Curtis Olson wrote: The counter argument here is that the existing auto coordination system is nothing more than one line of code that forces some rudder deflection in proportion to aileron deflection -- basically implementing some sort of hard linked manual system. I am sure there are very few (if any?) real life aircraft rigged in such a way. Curt. On Fri, Mar 9, 2012 at 1:57 PM, Renk Thorsten wrote: Ok I haven't entirely given up on the idea of removing the auto-coordination from the code. Why? Wouldn't it be more appropriate to add that rudder control to controls.nas? Nasal runs per graphical frame, FDMs may need to run faster at low framerates. Nasal AP systems tend to become unstable below 15 fps or so (see the F-14b). Then it can be replaced if need be on a per aircraft basis , but not break anything otherwise. You can replace it now on a per aircraft basis at the simple expense of setting a single property to false. If the aircraft is equipped with a better system, then that system can do so. Why is that a problem? And maybe it could be slip/skid-ball driven ... my whole point is NOT to disable it but make it configurable. Yes, them make it configurable on any aircraft you like. But it should not be absent from any aircraft you haven't touched. Cheers, * Thorsten -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net mailto:Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Curtis Olson: http://www.atiak.com http://www.atiak.com/ - http://aem.umn.edu/~uav/ http://aem.umn.edu/%7Euav/ http://www.flightgear.org http://www.flightgear.org/ - http://gallinazo.flightgear.org http://gallinazo.flightgear.org/ -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] a small set of minor aircraft model question...
On 03/05/2012 06:40 PM, Gene Buckle wrote: On Mon, 5 Mar 2012, Gary Neely wrote: Flying means I need to be able to actually read the instrument, so I often prefer larger fonts and bolder lines than perhaps the original had. +1 I'd think that real aircraft engineers would seek to minimize these effects, and that they would manifest significantly in some but not Every single real aircraft instrument I have in my collection has a special anti-glare coating on the glass. They don't reflect enough light to really notice. g. In a month, I will have been flying real light aircraft for 50 years and I agree totally with the above. The use of the reflection affect on the interior of windows and instruments is totally unrealistic and detracting from my enjoyment of flying such models in fgfs. The unrealistic comment is fact and the detracting comment is my opinion. Dave P. -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Link error in fg make install (was git question)
Hi again, Thanks for the pointers (should have checked the wiki.flightgear first). System Description: newly installed hard drive with fresh f16 install (not upgrade or preupgrade) i7 processor with nvidia GF260 XT and proprietary nvidia driver 290.10 fltk and fltk-fluid yum installed this morning new git clones this morning for sg and fg cmake for simgear and flightgear showed no errors and near the end of make install for fg, I get this error: [ 97%] Built target FGAdminUI Linking CXX executable fgadmin CMakeFiles/fgadmin.dir/fgadmin_funcs.cxx.o: In function `FGAdminUI::install_selected()': fgadmin_funcs.cxx:(.text+0x22dc): undefined reference to `Fl_Window::cursor(Fl_Cursor, Fl_Color, Fl_Color)' fgadmin_funcs.cxx:(.text+0x2321): undefined reference to `Fl_Window::cursor(Fl_Cursor, Fl_Color, Fl_Color)' CMakeFiles/fgadmin.dir/fgadmin_funcs.cxx.o: In function `FGAdminUI::remove_selected()': fgadmin_funcs.cxx:(.text+0x256a): undefined reference to `Fl_Window::cursor(Fl_Cursor, Fl_Color, Fl_Color)' fgadmin_funcs.cxx:(.text+0x25c9): undefined reference to `Fl_Window::cursor(Fl_Cursor, Fl_Color, Fl_Color)' collect2: ld returned 1 exit status make[2]: *** [utils/fgadmin/src/fgadmin] Error 1 make[1]: *** [utils/fgadmin/src/CMakeFiles/fgadmin.dir/all] Error 2 make: *** [all] Error 2 I traced from the fgadmin_funcs.cxx includes and it appears all the Fl references are in /usr/include/FL and the terminal output from the cmake command shows it should find the Fl headers. -- Using FLTK_LIBRARIES for fgadmin: /usr/lib64/libfltk_images.so;/usr/lib64/libfltk_forms.so;/usr/lib64/libfltk_gl.so;/usr/lib64/libGL.so;/usr/lib64/libfltk.so;/usr/lib64/libSM.so;/usr/lib64/libICE.so;/usr/lib64/libX11.so;/usr/lib64/libXext.so;/usr/lib64/libm.so;/usr/lib64/libXinerama.so;/usr/lib64/libXft.so -- apr-1-config not found, implement manual search for APR -- /usr/include When I copied sg and fg matching source from a backup made before the change to cmake into a separate folder, I can build both from that folder with no errors. I must be missing something! Any help or suggestions much appreciated. Dave P. -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] New Build Process?
On 02/20/2012 11:45 AM, Martin Spott wrote: castle...@comcast.net wrote: The writeup on the wiki seems a little thin; [...] that's just because CMake is s easy to use ;-)) Cheers, Martin. Thanks to the several people that responded to point me to both git and cmake articles at wiki.flightgear.org. I now have *next sg and fg as well as svn updated fgrun successfully built. I am getting much higher frame rates with most all the shader sliders at their max. When you are gone for months, you see clearly the progress. Dave P. -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] git question
Hi All, I have been gone for almost a year. I want to start new source trees for simgear and flightgear and track on going development. Which git branches should I check out in this new set of directories? And from the e-mails I have read from the developers list, is appears that fgdata still has all the aircraft under development. I plan to rate all the AC I have made significant contributions to via the published rules and push them to the repository. Dave P. -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] git question
On 02/19/2012 02:06 PM, Torsten Dreyer wrote: Am 19.02.2012 21:54, schrieb dave perry: Hi All, I have been gone for almost a year. I want to start new source trees for simgear and flightgear and track on going development. Which git branches should I check out in this new set of directories? And from the e-mails I have read from the developers list, is appears that fgdata still has all the aircraft under development. I plan to rate all the AC I have made significant contributions to via the published rules and push them to the repository. Hi Dave, welcome back! The latest development is in 'next' for SimGear and FlightGear and 'master' for fgdata. Yes, fgdata still holds all aircraft. Some basic instructions are in the wiki: http://wiki.flightgear.org/Git Torsten -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel Thanks Torsten, The wiki link is just what I needed to refresh my memory. I their a similar reference for the change to cmake? Dave P. -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FGData Split Completed - a.k.a. Life after the Split
On 10/18/2011 10:24 AM, Cedric Sodhi wrote: = IMPORTANT NOTICE TO EVERYONE INVOLVED WITH THE DEVELOPMENT OF FGDATA OR AIRPLANES THEREIN = Thanks to the concentrated effort of all people involved, most notably Jorg - who I'd hereby like to thank on behalf of all of us, for spending three successive days and nights branching, cloning, filtering, splitting and verifying data - FGDATA has, by today, successfully been split into individual repositories, comprising the respective planes and FGDATA core data. Again: === !!! === From the present day on, the development version of FGDATA NO LONGER CONTAINS ANY AIRPLANES - You will have to clone a new FGDATA! === - Airplanes migrated - All airplanes, hitherto found in $FGDATA/Aircraft/, have been removed from that place in the development version of FGDATA and can presently be found in their individual repositories at the following URL https://gitorious.org/flightgear-aircraft (Disclaimer: HTML page is rather huge) Please contact either of the following administrators to be given priviledges on one of those repositories: https://gitorious.org/+flightgear-aircraft/memberships - New FGDATA Core - FGDATA is now without any aircraft. The only things which remain in FGDATA's Aircraft directory are general purpose data which are used by a bulk of different airplanes. The respective directories of these data are Generic Instruments Instruments-3d Despite its name, now a historical relict, NO AIRCRAFT SHALL EVER BE PUSHED TO $FGDATA/Aircraft. The new FGDATA can be found in the official repository at the following URL https://gitorious.org/fg/fgdata-new The repository is named fgdata-new for the time being and the old fgdata is kept arround, frozen, to have a fallback if anything should happen. Please contact either of the following administrators to be given priviledges on the new fgdata repository: https://gitorious.org/+flightgear-developers/memberships - Development - All aircraft related development shall henceforth be performed on repositories which are maintained by the respective authors. It is planned that most of the repositories on https://gitorious.org/flightgear-aircraft will be dissolved over time and be taken over by the respective authors. I don't understand the above (up to - Development -). Questions: 1. Are you saying that aircraft developers cannot leave their aircraft in https://gitorious.org/flightgear-aircraft indefinitely? So do we need to set up our own git repository for each ac we maintain? This raises the knowledge/experience bar required for aircraft developers/maintainers. 2. Assuming the answers are no, yes, to #1, will all these repositories be centrally located so one can track new or modified ac of interest? 3. Is there any interest in creating repositories by ac class/type? e.g. historical, military-fighter, military-transport, civilian-light-ac, airliners, etc. By the way, thanks for all the work on this and also for this helpful note of documentation! On a sidenote, some of those repositories are already superflous because development has long been moved somewhere else. These are the first repositories which will be decomissioned. Only repositories for which no author is found will remain stored centrally. Development on the rest of FGDATA will continue in the new FGDATA repository until further notice, possibly until more components are migrated, as it has been brought forward. https://gitorious.org/fg/fgdata-new - Usage - To keep up with the new structure, commit all your local changes on your old FGDATA and move its directory out of the way (for example by renaming it). $ cd fgdata $ git commit -a $ cd .. $ mv fgdata fgdata-OLD Next, clone the new repository of FGDATA $ git clone git://gitorious.org/fg/fgdata-new.git fgdata IF YOU HAD LOCAL CHANGES, you will need to reapply these changes. This could be a little adventurous, because these are actually two separate repositories and you can't just rebase. You'll have to prepare the patches and apply them over. If you need help with this, check on the official IRC channel at irc://irc.flightgear.org/flightgear for help. Now you have the new core FGDATA (possibly with your own changes, if you followed the hint above). In the coming days, we will provide you with scripts which conveniently fetch your personal selection of aircrafts; until then you will have to manually obtain them from the repositories. Here is how: DO NOT PUT THE AIRCRAFTS INTO THE NEW FGDATA! Instead, create a new directory somewhere completely different, say, /usr/local/flightgear/aircrafts and store the aircrafts in there (for example clone them from their repositories). If you specify that directory on the command line to Flightgear, it will find them, altough they are not in the FGDATA directory. E.g.: $ ./fgfs
Re: [Flightgear-devel] Understanding the design of aircraft nasal scripts
On 04/08/2011 10:40 PM, Catherine James wrote: Recently, I've been spending a good bit of time attempting to program all of my most-used aircraft so that I can engage and disengage the autopilot through the joystick. I've been able to get this to work on the Seneca II with a short nasal script in Nasal/SenecaII.nasal that sets the /autopilot/CENTURYIII/controls and /autopilot/CENTURYIII/locks properties appropriately. Silly me, I though it would be a simple matter to port the working code over to the Comanche PA-24-250 (w/ CIII autopilot). Unfortunately, the structure of the nasal scripts of the PA24 bears very little resemblance to that of the Seneca II. Although the relevant autopilot properties are the same for both planes, the flow of control is not. For example, turning on the autopilot roll axis control with the plane on the ground is harmless in the Seneca, but will cause a nasal crash in the (stock, unmodified) Comanche, and turning the autopilot off again will not recover. (The ailerons will be locked permanently at 0 until you restart.) The routine that crashes is action-sim.nas, a file that doesn't even exist in the Seneca. It contains an update_actions() script that is looped repeatedly, updating positions of control surfaces, etc. With the autopilot on, the script attempts to get the appropriate aileron position from the autopilot, but it returns null and then cause a setValue() error when it blindly tries to set the actual aileron position to that null. The same thing happens if I turn on the autopilot in flight by using the joystick to change the /autopilot/CENTURYIII/controls properties through a script. Is there a general file and scripting structure that it is recommended to follow for implementing aircraft? It's very challenging to learn to understand and modify aircraft implementations when the general arrangement of files is so different from one to the next. How are you turning on the roll axis and how are you turning off the autopilot. I just tried to reproduce your failures and did not have the problems you describe. I am the author of the pa24-250. The model assumes that you are using the switches via the picks. The nasal code replicates the behavior described in the Century III Autopilot Flight System Pilot's Operating Handbook. You used to be able to download a PDF of this from Century. This is no longer the case. There are logical relations between the four switches that are included in the model. If you are changing the locks outside the Nasal models, you will most likely create a state that is not possible via the model code and also not accurate according to the referenced manual. -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] c172p scissors interpolations and main rotation interpolations
On 02/14/2011 11:58 AM, Torsten Dreyer wrote: On 02/12/2011 12:59 PM, Torsten Dreyer wrote: By the way. The filtering that will remain in the c172p action-sim.nas for the nav radio could be moved to navradio.cxx. Here again, the needle damping and the needle behavior when tuned to an out-of-range frequency or when the gs is out of range is device dependent. The filtered values are used by Aircraft/Instruments-3d/vor/vor.xml and vor2.xml. I was afraid that modifying navradio.cxx to achieve realistic needle behavior for this vor model might break other vor/gs head or hsi models. We can now easily use the autopilot filters for that, just add a file with the content PropertyList filter nameCDI0 lowpass/name debugfalse/debug typeexponential/type filter-time2.0/filter-time inputinstrumentation/nav[0]/heading-needle-deflection-norm/input outputinstrumentation/nav[0]/filtered-cdiNAV0-deflection/output /filter !-- More filters here -- /PropertyList And add autopilot nameA very descriptive name for this file like Instrument-Filter/name pathAircraft/c172p/path/to/that/file/path /autopilot to c172p-set.xml under /sim/systems No need for coding here, too. Greetings, Torsten I had not tried the kap140 in checking out the changes I submitted today for the c172p. While implementing similar changes to the pa24-250, I noticed that neither the Century IIB not the Century III autopilots work with the above filter method. So I flew the c172p again and sure enough, the kap140 is also broken by the above filter method. Apparently having two autopilots in the same AC ist verboten. Torsten, have you tried two autopilots on an AC in the past? No, it's not verboten at all. I use four(!) autopilot files in the SenecaII (I prefer to call them property-rules because they are much more than just autopilot components). One pitfall is that in preferences.xml there is the generic-autopilot- helper.xml included at /sim/systems/autopilot[1]. If you add a second autopilot (property-rule), this one gets ignored/overwritten. If you rely on the properties handled there (and I assume the 172p does), you need to re-add it manually. Add autopilot nameautopilot helpers/name pathAircraft/Generic/generic-autopilot-helper.xml/path /autopilot together with your new rule and it should work. Torsten Thanks Torsten, I should have looked at the SenecaII set and base files. The answer to my question ... have you tried ... was there. I still would not have thought of the generic helper. Thanks again, Dave P. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] c172p updates (minimize action-sim)
Hi Guys, I have a clean local c172p ready to push that includes: - working nose gear link animation in terms of compression-norm using xml interpolation - working main gear animation in terms of compression-norm using xml interpolation - moved NAV0 and NAV1 needle deflection filters to pseudo-autopilot This leaves only a few lines in action-sim.nas. If there are no objections, I will push this after church. Just got back from church and the send message failed. So I am resending this. Dave P. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] c172p updates (minimize action-sim)
On 02/13/2011 12:43 PM, Stuart Buchanan wrote: On 13 Feb 2011, at 19:26, dave perry wrote: Hi Guys, I have a clean local c172p ready to push that includes: - working nose gear link animation in terms of compression-norm using xml interpolation - working main gear animation in terms of compression-norm using xml interpolation - moved NAV0 and NAV1 needle deflection filters to pseudo-autopilot This leaves only a few lines in action-sim.nas. If there are no objections, I will push this after church. Just got back from church and the send message failed. So I am resending this. No objections from me for removing something from my todo list. Thanks Dave! Done! I moved the remaining lines in action-sim.nas to two other nas files and deleted action-sim.nas. The several listners that associate fgfs tank properties with jsbsim tank properties are now in tank.nas and the lines that use a common property to control both the panel and instrument intensity were added to light.nas. This push also included changes to the pa24-250 landing lights animation. The new landing lights are modeled after the pa22 landing lights. Dave P. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] c172p scissors interpolations and main rotation interpolations
On 02/12/2011 12:59 PM, Torsten Dreyer wrote: By the way. The filtering that will remain in the c172p action-sim.nas for the nav radio could be moved to navradio.cxx. Here again, the needle damping and the needle behavior when tuned to an out-of-range frequency or when the gs is out of range is device dependent. The filtered values are used by Aircraft/Instruments-3d/vor/vor.xml and vor2.xml. I was afraid that modifying navradio.cxx to achieve realistic needle behavior for this vor model might break other vor/gs head or hsi models. We can now easily use the autopilot filters for that, just add a file with the content PropertyList filter nameCDI0 lowpass/name debugfalse/debug typeexponential/type filter-time2.0/filter-time inputinstrumentation/nav[0]/heading-needle-deflection-norm/input outputinstrumentation/nav[0]/filtered-cdiNAV0-deflection/output /filter !-- More filters here -- /PropertyList And add autopilot nameA very descriptive name for this file like Instrument-Filter/name pathAircraft/c172p/path/to/that/file/path /autopilot to c172p-set.xml under /sim/systems No need for coding here, too. Greetings, Torsten I had not tried the kap140 in checking out the changes I submitted today for the c172p. While implementing similar changes to the pa24-250, I noticed that neither the Century IIB not the Century III autopilots work with the above filter method. So I flew the c172p again and sure enough, the kap140 is also broken by the above filter method. Apparently having two autopilots in the same AC ist verboten. Torsten, have you tried two autopilots on an AC in the past? I also tried using PropertyList include=NAVandGSfilters.xml at the top of the actual autopilot xml file so the new filters in NAVandGSfilters.xml should have been as if they were part of the autopilot xml file. This gave no load error but also, the filters were not functioning. If I just copy the filters from NAVandGSfilters.xml into the actual autopilot xml right after the PropertyList tag, everything works including the new filters. This feels like an ugly hack. Should either loading the new filters as a 2nd autopilot of including the pseudo autopilot in the PropertyList tag have worked? Cheers, Dave P. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] c172p scissors interpolations and main rotation interpolations
I am having trouble getting the modified gearscissors.nas to run with
the stand alone nasal.
after adding the three numbers in gedit and saving the file, I get
$ nasal gearscissors.nas GearScissorInterpolation.xml
Runtime error: undefined symbol
at gearscissors.nas, line 1
If I don't edit the file after copying just your template, I get
$ nasal gearscissors.nas GearScissorInterpolation.xml
Parse error: parse error at line 5
which is what I would expect as I have not replaced the text with a number.
If I just add the first two numbers, I get a parse error at line 7 (as
expected), but If I add the 3rd number or even just delete or comment
out that line, I get
$ nasal gearscissors.nas GearScissorInterpolation.xml
Runtime error: undefined symbol
at gearscissors.nas, line 1
Here is the gearscissors.nas after adding in the correct numbers for the
c172p nose strut:
import(math);
var acos = func(x) { math.atan2(math.sqrt(math.abs(1-x*x)), x) }
var R2D = 180.0 / math.pi;
var scissor_dist = 0.240626;
var scissor = 0.194716;
var oleo = 0.1893439;
var theta0 = acos(scissor_dist/2/scissor) * R2D;
print( ?xml version = '1.0' encoding = 'UTF-8' ?\n );
print( PropertyList\n );
for( var i = 0; i 1.05; i += 0.05 ) {
print( entry\n );
var l = (1.0-i) * oleo/2;
l += (scissor_dist-oleo)/2;
print( ind ~ sprintf(%4.3f, i ) ~ /ind\n );
print( dep ~ sprintf(%4.3f, acos( l / scissor ) * R2D - theta0
) ~ /dep\n );
print( /entry\n );
}
print( /PropertyList\n );
The stand-alone nasal compiled fine. Any ideas what is wrong here?
On 02/12/2011 12:59 PM, Torsten Dreyer wrote:
By the way. The filtering that will remain in the c172p action-sim.nas
for the nav radio could be moved to navradio.cxx. Here again, the
needle damping and the needle behavior when tuned to an out-of-range
frequency or when the gs is out of range is device dependent. The
filtered values are used by Aircraft/Instruments-3d/vor/vor.xml and
vor2.xml. I was afraid that modifying navradio.cxx to achieve realistic
needle behavior for this vor model might break other vor/gs head or hsi
models.
We can now easily use the autopilot filters for that, just add a file with the
content
PropertyList
filter
nameCDI0 lowpass/name
debugfalse/debug
typeexponential/type
filter-time2.0/filter-time
inputinstrumentation/nav[0]/heading-needle-deflection-norm/input
outputinstrumentation/nav[0]/filtered-cdiNAV0-deflection/output
/filter
!--
More filters here
--
/PropertyList
And add
autopilot
nameA very descriptive name for this file like Instrument-Filter/name
pathAircraft/c172p/path/to/that/file/path
/autopilot
to c172p-set.xml under /sim/systems
No need for coding here, too.
Greetings, Torsten
--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] c172p scissors interpolations and main rotation interpolations
Hi All,
I also have the interpolation for the nose gear scissors done and working.
The main gear rotation interpolation is also done and working. I have been
busy on other projects today, so have not had time to clean this up for
a git push.
The main gear requires a different script based on the geometry. I
based the script on that section of action-sim.nas.
One issue in generalizing this approach; apparently jsbsim normalizes so
1 ~ 1 ft while yasim normalizes to compression set in the set file.
I can clean this up and push to git tomorrow or I can use Torsten's
autopilot
filter idea to allow the deletion of all of action-sim.nas. Should get that
done tomorrow also.
Main Gear script follows:
import(math);
var acos = func(x) { math.atan2(math.sqrt(math.abs(1-x*x)), x) }
var R2D = 180.0 / math.pi;
var Radius_main = 0.919879;
# Radius_main is the distance from the center of rotation to the tire
contact point
var h0 = 0.63872;
# ho is the vertical height of the center of rotation with no compression
var h_norm = 0.3048;
# h_norm is the height of the center of rotation with compression-norm = 1
var theta0 = acos(h0/Radius_main);
print( ?xml version = '1.0' encoding = 'UTF-8' ?\n );
print( PropertyList\n );
for( var i = 0; i 1.05; i += 0.05 ) {
print( entry\n );
var delta_h = i * h_norm;
print( ind ~ sprintf(%4.3f, i ) ~ /ind\n );
print( dep ~ sprintf(%4.3f, (acos( (h0 -delta_h) / Radius_main
) - theta0 ) * R2D ) ~ /dep\n );
print( /entry\n );
}
print( /PropertyList\n );
Dave P.
On 02/12/2011 04:03 PM, Stuart Buchanan wrote:
Hi Guys,
Thanks very much for looking at this. I had a play with it myself
yesterday, and have XML interpolation code already working for the
nose-gear in my local copy. I used an oleo length of 1ft as
/gear/gear[0]/gear-compression-ft and
/gear/gear[0]/gear-compression-norm seem to be the same by inspection,
which looks fine to my eye. I think that should equate to the oleo
length?
I haven't looked at the main gear yet, and I'd like to get them both
sorted before committing. Using an oleo length equal to twice the main
gear compression should give the correct animation I think.
I've also ported Torstens Nasal code to perl, which I'll add to the
wiki once I've cleaned it up. Like Dave I couldn't get the latest
version of Nasal to compile :)
Dave - sounds like we've been duplicating effort in our enthusiasm to
sort this. If you haven't managed to get the Nasal code working yet, I
suggest I post the perl code and sort out the c172p. Then you should
be able to sort out the pa24 pa28 pretty easily. First one finished
gets to do the pittss1c :)
-Stuart
--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Sinking feeling - c172 on gravel runway
On 02/11/2011 10:28 AM, Stuart Buchanan wrote: On Fri, Feb 11, 2011 at 5:18 PM, Ron Jensen wrote: On Friday 11 February 2011 10:07:11 Geoff McLane wrote: Hi Curt, No probs, now that it seems Ron might have found something, thus the thread is hovering on closing, so chat away... While we argue over how many angles can dance on the head of a pin over on the JSBSim list, here is a simple patch to the c172p fdm that stops the tilting. Thanks Ron, I'll take a look at this over the weekend and get it committed. I've also got on my TODO list replacing the Nasal nose gear animation code with straight XML animations. -Stuart Including the link animations? Getting the correct link angle of rotation requires either an arcos or arcsin approximation. Similar for the main gear strut rotation angles. Dave P. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] list of aircraft that don't load in fgdata
On 01/26/2011 01:31 PM, Anders Gidenstam wrote: On Tue, 25 Jan 2011, dave perry wrote: I have tried to load several AC that did not load with filed to load file name errors. So I did a survey of the entire up-to-date fgdata. I used an up-to-date fgrun and went through all the AC. The following do not load even to the viewer in fgrun: 737-100, 737-300, AG-14, Airwave Xtreme 150, CRJ-200, DC-8-63, Fairchild Metroliner, Fooker50-Denim, Jaguar, Late-29, marchetti, MIG-29 Fulcrum, Mirage F1, North American OV-10A USAFE Bronco, Short Empire, x24b, and Zepphelin NT07 multiplayer copilot. Did you try them in FlightGear too? As far as I know both Short Empire and ZLT-NT-copilot (the latter doesn't have any visible model btw) load fine in FlightGear so if the problems with them occur only in fgrun I'd be inclined to consider it a problem in fgrun's model viewer rather than a problem in the aircraft. Cheers, Anders Hi again, I decided to kill a few hours today chasing down the source of the failure in fgrun for each AC I listed. I can put these failures in 3 classes. These are the first things that fgrun rejects. There are likely others. Class 1: fgfs and fgrun handle recursion of paths differently. Anders, you are correct concerning the failure of fgrun to load both the Short Empire and the ZLT-NT-copilot. These as well as the Jaguar fail to load in fgrun because of differences in the way recursive paths are handled in fgrun and fgfs xml parsers. Class 2: Linux Windows path differences (spaces in dir and file names or case sensitive). 737-300 path is .../Flightdeck/Instruments/STBY/alt.xml but file is ALT.xml AG-14path is .../Instruments/Reloj digital/Reloj digital.xml Fairchild Metroliner path is .../Instruments/Marker/MarkerLights.xml but actual path is .../Instruments/marker/MarkerLights.xml Mirage_F1 path is ../Models/cockpit/Divers/... but actual dir is divers Class 3: File or dir missing 737-100 several redundant models for instruments need to be deleted to match actual directory structure. Example: .../Instruments/aib/ai.xmldir aib doesn't exist CRJ-200 path .../fgdata/Models/Airport/Pushback/warning-light.xml doesn't exist DC-8-63 pathAircraft/dc8-63/Models/cargobox.xml/path doesn't exist Fokker50-Denim path .../Models/fokker50denim.xml doesn't exist Fokker50-KLM path .../Models/fokker50klm.xml doesn't exist Fokker50-VLM path .../Models/fokker50vlm.xml doesn't exist Late-29path .../Effects/wakeG.xml, actual path .../Effects/waves/wakeG.xml Mig-29 path .../Effects/tiptrail.xml, no Effects dir OV-10A USAFE path .../Aircraft/OV10/Effects/smoke.xml, no Effects dir The UIUC models with .mdl files don't load in fgrun viewer and don't seem to work from the command line either. Case 1 needs to be addressed by the maintainers of fgrun. Since this difference in parsing recursive paths only shows up for 3 of 100+ aircraft, it is true that this can be easily avoided by the aircraft maintainers. Case 2 should be addressed by the aircraft maintainers as FlightGear is a cross-platform project. Case 3 should also be addressed by the aircraft maintainers. Some of this is just sloppy xml files with cruft not removed because it is not causing fgfs to crash or abort. Some of this is likely work in progress. Is it possible to add a switch to the fgfs command line so that it aborts when a file or directory request violates the cross-platform goal (names with case not matching the actual dir or file names or names with embedded spaces). Cheers, Dave P. -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] list of aircraft that don't load in fgdata
I have tried to load several AC that did not load with filed to load file name errors. So I did a survey of the entire up-to-date fgdata. I used an up-to-date fgrun and went through all the AC. The following do not load even to the viewer in fgrun: 737-100, 737-300, AG-14, Airwave Xtreme 150, CRJ-200, DC-8-63, Fairchild Metroliner, Fooker50-Denim, Jaguar, Late-29, marchetti, MIG-29 Fulcrum, Mirage F1, North American OV-10A USAFE Bronco, Short Empire, x24b, and Zepphelin NT07 multiplayer copilot. This is on an FC14 Linux machine. Some of these did not load because of folder or file names having spaces in them, so they may load under Windows. Dave P. -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] fgfs crash after about 1 hour 15 min
With yesterday's git for fgfs and simgear, after about 1.25 hours, fgfs froze and I had to use System Monitor to end process fgfs. All seemed normal up to the freeze. OS, up-to-date FC14 on an I7 desktop with nvidia GeForce GTX 260, NVIDIA driver Version: 260.19.29. Command line (from fgrun wizard): /usr/local/bin/fgfs --fg-root=/home/dad/source-osg/fgdata --fg-scenery=/home/dad/source-osg/fgdata/Scenery:/home/dad/source-osg/TerraSync --airport=KLWB --aircraft=pa24-250-CIIB --control=joystick --disable-random-objects --enable-ai-models --enable-real-weather-fetch --prop:/sim/frame-rate-throttle-hz=30 --prop:/sim/menubar/autovisibility/enabled=1 --geometry=1680x1050 --visibility-miles=30 --bpp=32 --fov=65 --texture-filtering=16 --atlas=socket,out,5,localhost,5505,udp --atlas=socket,out,5,localhost,5500,udp --prop:/sim/rendering/shader-effects=true --nav1=109.5 --nav2=114.2 --adf=400 --dme=nav1 I had just passed Casanova VOR (116.3 CSN) on the 72 deg radial (approx. 7 nm out bound). Here is the backtrace: A /home/dad/source-osg/TerraSync/Objects/w080n30/w077n39/kbwi-signature.ac A /home/dad/source-osg/TerraSync/Objects/w080n30/w077n39/rmsjr-two-lane-road.rgb Checked out revision 12725. *** glibc detected *** fgfs: double free or corruption (!prev): 0x15989540 *** === Backtrace: = /lib64/libc.so.6[0x3cd5a78e23] fgfs[0xacf238] fgfs[0xacf3a6] fgfs[0xacf8b9] fgfs[0xacf8e1] fgfs[0xac4da5] fgfs[0xac716a] fgfs[0xac4a4a] fgfs[0xac735b] fgfs[0xac581b] fgfs[0xac5b18] fgfs[0xac6fdf] fgfs[0xac6be9] fgfs[0xac6f3f] fgfs[0xac7510] fgfs[0xac7554] === Memory map: 0040-00e1a000 r-xp 08:06 1180904 /usr/local/bin/fgfs 0101a000-01031000 rw-p 00a1a000 08:06 1180904 /usr/local/bin/fgfs 01031000-0105 rw-p 00:00 0 0116f000-17d3 rw-p 00:00 0 [heap] 4111-41176000 rw-p 00:05 4140 /dev/zero 4133-41332000 r-xs 08:08 3145868 /tmp/glRXG5kL (deleted) 36c820-36c825c000 r-xp 08:06 5637585 /usr/lib64/libGLU.so.1.3.070900 36c825c000-36c845b000 ---p 0005c000 08:06 5637585 /usr/lib64/libGLU.so.1.3.070900 36c845b000-36c845d000 rw-p 0005b000 08:06 5637585 /usr/lib64/libGLU.so.1.3.070900 393360-3933643000 r-xp 08:08 3670062 /lib64/libdbus-1.so.3.5.2 3933643000-3933842000 ---p 00043000 08:08 3670062 /lib64/libdbus-1.so.3.5.2 3933842000-3933843000 r--p 00042000 08:08 3670062 /lib64/libdbus-1.so.3.5.2 3933843000-3933844000 rw-p 00043000 08:08 3670062 /lib64/libdbus-1.so.3.5.2 393600-3936041000 r-xp 08:06 5647016 /usr/lib64/libpulse.so.0.12.2 3936041000-393624 ---p 00041000 08:06 5647016 /usr/lib64/libpulse.so.0.12.2 393624-3936242000 rw-p 0004 08:06 5647016 /usr/lib64/libpulse.so.0.12.2 393640-393644e000 r-xp 08:06 5647015 /usr/lib64/libpulsecommon-0.9.21.so 393644e000-393664d000 ---p 0004e000 08:06 5647015 /usr/lib64/libpulsecommon-0.9.21.so 393664d000-393664f000 rw-p 0004d000 08:06 5647015 /usr/lib64/libpulsecommon-0.9.21.so 3cd560-3cd561 r-xp 08:08 3670043 /lib64/ld-2.12.90.so 3cd561-3cd5611000 --xp 0001 08:08 3670043 /lib64/ld-2.12.90.so 3cd5611000-3cd5621000 r-xp 00011000 08:08 3670043 /lib64/ld-2.12.90.so 3cd582-3cd5821000 r--p 0002 08:08 3670043 /lib64/ld-2.12.90.so 3cd5821000-3cd5822000 rw-p 00021000 08:08 3670043 /lib64/ld-2.12.90.so 3cd5822000-3cd5823000 rw-p 00:00 0 3cd5a0-3cd5b9a000 r-xp 08:08 3670045 /lib64/libc-2.12.90.so 3cd5b9a000-3cd5d99000 ---p 0019a000 08:08 3670045 /lib64/libc-2.12.90.so 3cd5d99000-3cd5d9d000 r--p 00199000 08:08 3670045 /lib64/libc-2.12.90.so 3cd5d9d000-3cd5d9e000 rw-p 0019d000 08:08 3670045 /lib64/libc-2.12.90.so 3cd5d9e000-3cd5da4000 rw-p 00:00 0 3cd5e0-3cd5e84000 r-xp 08:08 3670065 /lib64/libm-2.12.90.so 3cd5e84000-3cd6083000 ---p 00084000 08:08 3670065 /lib64/libm-2.12.90.so 3cd6083000-3cd6084000 r--p 00083000 08:08 3670065 /lib64/libm-2.12.90.so 3cd6084000-3cd6085000 rw-p 00084000 08:08 3670065 /lib64/libm-2.12.90.so 3cd620-3cd6218000 r-xp 08:08 3670147 /lib64/libpthread-2.12.90.so
Re: [Flightgear-devel] git question
On 01/10/2011 02:19 PM, dave perry wrote: I am ready to push some committed fgdata changes from my *master. But I lost my notes. Don't want to mess up. What is the syntax? git push master/origin? Thanks, Dave Never mind. Answer found by git push --help. Sorry, should have done this first. Dave P. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] git question
I am ready to push some committed fgdata changes from my *master. But I lost my notes. Don't want to mess up. What is the syntax? git push master/origin? Thanks, Dave -- Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fgfs configure error
On 01/06/2011 03:01 AM, Jari Häkkinen wrote: find / -name version.h | grep simgear I had already looked at config.log. The check was against simgear/version.h. But since --prefix=$FG_ROOT, the config checks for $FG_ROOT/include/simgear/version.h before it checks for /usr/local/include/simgear/version.h. Using the above find showed the accidentally created version.h in $FG_ROOT. Apparently I had used the config string from a fgfs compile script while compiling simgear 2.0.0 for an atlas build on Dec. 16. All makes sense now. Thanks, Dave -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] fgfs configure error
With today's simgear and flightgear source from git, after compiling and installing simgear, fgfs ./configure CFLAGS=-march=native CXXFLAGS=-march=native --prefix=$FG_ROOT fails with checking simgear/version.h usability... yes checking simgear/version.h presence... yes checking for simgear/version.h... yes checking for SimGear 2.2.0 or newer... [found 2.0.0] ... wrong version configure: error: Install latest SimGear first... make: *** [config.status] Error 1 I assume that it is checking the file /usr/local/include/simgear/version.h that was written by the simgear sudo make install. That file contains #ifndef _SIMGEAR_VERSION_H #define _SIMGEAR_VERSION_H #define SIMGEAR_VERSION 2.2.0 #endif // _SIMGEAR_VERSION_H which should have passed the test. I do have a source folder for SimGear 2.0.0 that contains simgear/version.h that would not pass. But I did a make uninstall in that folder before compiling and installing the git simgear. Suggestions? -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Announce] fog/mist/haze layer now active
Torsten, I just used an fgfs_update script that updates simgear, then fgfs, and then fgdata. The compile of fgfs terminated with the following error: Making install in Environment make[2]: Entering directory `/home/dad/source-osg/flightgear/src/Environment' g++ -DHAVE_CONFIG_H -I. -I../../src/Include -I../.. -I../../src -I/home/dad/source-osg/fgdata/include -I/usr/local/include -march=native -Wall -D_REENTRANT -MT environment_mgr.o -MD -MP -MF .deps/environment_mgr.Tpo -c -o environment_mgr.o environment_mgr.cxx environment_mgr.cxx: In member function ‘double FGEnvironmentMgr::get_cloud_layer_maxalpha(int) const’: environment_mgr.cxx:340:44: error: ‘class SGCloudLayer’ has no member named ‘getMaxAlpha’ environment_mgr.cxx: In member function ‘void FGEnvironmentMgr::set_cloud_layer_maxalpha(int, double)’: environment_mgr.cxx:346:37: error: ‘class SGCloudLayer’ has no member named ‘setMaxAlpha’ environment_mgr.cxx: In member function ‘double FGEnvironmentMgr::get_cloud_layer_maxalpha(int) const’: environment_mgr.cxx:341:1: warning: control reaches end of non-void function make[2]: *** [environment_mgr.o] Error 1 make[2]: Leaving directory `/home/dad/source-osg/flightgear/src/Environment' make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/home/dad/source-osg/flightgear/src' make: *** [install-recursive] Error 1 Did something get missed in your push? Dave P. On 12/15/2010 11:00 AM, Torsten Dreyer wrote: Hi all, i have just pushed some changes to activate a METAR generated cloud layer representing fog, mist and haze if reported. Check it out by selecting the Early morning fog weather scenario in the global weather dialog. It'll get you half a mile visibility and a fog layer of 500' thickness. Once you passed 500ft of altitude you find yourself in a clear sky and above the fog. The transition when passing through the top edge of the layer is not perfect as you might find out by yourself. I'm open to ideas how to improve this. Enjoy - and please report bugs. Torsten -- Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Atlas-devel] problem linking SimGear-2.0.0 for Atlas build
Thanks Brian and Stefan, Adding -ldl in screen Makefile.am did allow SimGear-2.0.0 to compile, but then Atlas compile failed. I actually succeeded compiling Atlas using the current git simgear. There is an issue with current Atlas. If I close Atlas by clicking the X to close the window, it does not kill the Atlas process. And if I relaunch Atlas, a new Atlas process is launched that will not function. It appears that the old process won't let go of the 5500 udp port although I have not confirmed that. The new Atlas process lon. and lat. location is not updating. If I kill both processes, and relaunch Atlas, Atlas again functions correctly. Regards, Dave P. On 12/09/2010 03:51 AM, stefan riemens wrote: See also http://fedoraproject.org/wiki/Features/ChangeInImplicitDSOLinking You might have luck using the fedora provided simgear libraries (install the SimGear-devel package). I know there are a couple of fedora patches applied to simgear, a.o. a patch for the linker. Stefan 2010/12/9 Brian Schackbschack-flightg...@usa.net: Dave == dave perry writes: Dave Hi, I just upgraded to fedora 14. FlightGear builds OK from Dave yesterday's git with current svn osg and current simgear from Dave git. Also fgrun builds OK. But I have not been able to build Dave Atlas from yesterday's Atlas cvs. I get the following link Dave error compiling SimGear-2.0.0 (from a tar) for use with Atlas Dave compile. [...] It seems that Fedora has made ld a lot pickier than other systems. I don't have Fedora so I can't test it, but as a wild guess, try changing the Makefile.am in simgear/screen, adding '-ldl' to the libraries for TextRenderTexture: TestRenderTexture_LDADD = \ libsgscreen.a \ -ldl \ $(top_builddir)/simgear/debug/libsgdebug.a \ $(opengl_LIBS) No guarantees about whether it will work, or whether it constitutes a good solution to the problem. It might be interested to see how SimGear GIT compares to SimGear 2.0.0. Brian -- This SF Dev2Dev email is sponsored by: WikiLeaks The End of the Free Internet http://p.sf.net/sfu/therealnews-com ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- This SF Dev2Dev email is sponsored by: WikiLeaks The End of the Free Internet http://p.sf.net/sfu/therealnews-com ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- This SF Dev2Dev email is sponsored by: WikiLeaks The End of the Free Internet http://p.sf.net/sfu/therealnews-com ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] problem linking SimGear-2.0.0 for Atlas build
Hi, I just upgraded to fedora 14. FlightGear builds OK from yesterday's git with current svn osg and current simgear from git. Also fgrun builds OK. But I have not been able to build Atlas from yesterday's Atlas cvs. I get the following link error compiling SimGear-2.0.0 (from a tar) for use with Atlas compile. Making install in screen make[2]: Entering directory `/home/dad/source-osg/SimGear-2.0.0/simgear/screen' g++ -g -O2 -D_REENTRANT -o TestRenderTexture TestRenderTexture.o libsgscreen.a ../../simgear/debug/libsgdebug.a -lglut -lGLU -lGL -lXmu -lXt -lSM -lICE -lXi -lXext -lX11 -lrt -lm /usr/bin/ld: libsgscreen.a(extensions.o): undefined reference to symbol 'dlsym@@GLIBC_2.2.5' /usr/bin/ld: note: 'dlsym@@GLIBC_2.2.5' is defined in DSO /lib64/libdl.so.2 so try adding it to the linker command line /lib64/libdl.so.2: could not read symbols: Invalid operation collect2: ld returned 1 exit status make[2]: *** [TestRenderTexture] Error 1 make[2]: Leaving directory `/home/dad/source-osg/SimGear-2.0.0/simgear/screen' make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/home/dad/source-osg/SimGear-2.0.0/simgear' make: *** [install-recursive] Error 1 /lib64/libdl.so.2 is a symlink to /lib64/libdl-2.12.90.so Any help appreciated. Regards, D. Perry -- This SF Dev2Dev email is sponsored by: WikiLeaks The End of the Free Internet http://p.sf.net/sfu/therealnews-com ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Aircraft model/cockpit rating
On 12/01/2010 08:14 AM, Gene Buckle wrote: I like the work that Thorsten has done with the rating system, but you guys are getting all tangled up in the details. Why not build a pretty objective score card and then rate the aircraft on that? For example, you can have a list like this: Exterior --- Animated Control Surfaces Animated Landing Gear Livery/texture for 3D model Model is generally representative of depicted type Exterior Lighting Interior --- 2D Cockpit 3D Cockpit Photorealistic Textures/Panel Photorealistic Textures/General interior Panel controls generally representative of depicted type etc. Each one would add a point for a present feature and deduct a point for a feature it should have, but does not. No point would be awarded or deducted for a feature that doesn't apply. An example of this would be Animated Landing Gear - you would score that a zero on a Cessna 172 (if it's not the R model) since the 172 has fixed gear. These things are scorable based on the fact that either a model has this thing or not. It doesn't allow for well it just kinda looks wrong scoring. For the flight model, you can score it against how it compares to data in the POH or pilot's notes. I suspect a flight model evaluation script could be put together in Nasal that would prevent human interaction from ganking the flight test. :) Once the objective score is assembled, you could have another block that was strictly for the reviewers subjective opinon on the aircraft or vehicle being reviewed. Thorsten's made an awesome contribution here - quit flogging it and help refine it! g. Actually, fixed gear can have animations. The C172 gear flexes with gear compression. The wheels spin (when on the ground) and the nose gear links are animated. There are a number of fixed gear aircraft in fgfs that don't have one or more of these animations. I recently added such animation to the Pitts, including reducing the spring and compression in the fdm which improved ground handling. With rudder pedals I can now do takeoffs and landings w/o whacking the lower wing tips on the ground. ; -) I agree with the last comment concerning Thorsten's contribution. Dave P. -- Increase Visibility of Your 3D Game App Earn a Chance To Win $500! Tap into the largest installed PC base get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Strange texture difference on two machines
I made changes to pittss1c/Models/sc1.ac from my desktop (i7 with NV GTX 260) that were part of animating main gear flex and wheel spin. These were pushed and then pulled to my notebook (core duo, NV 9300M). The left main wheel on the notebook is not textured (all white). To make sure the files were the same on both systems, I removed the file s1c.ac from both and then did a git checkout of that file on both systems. This did not change the results on either machine. The left main wheel is textured on the desktop and not textured on the notebook. What are others seeing when they use the pittss1c from today's git? Thanks, Dave P. -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book Blueprint to a Billion shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] pa24 and pitts changes committed
pa24-250 changes The light cone approach to landing lights has not worked for some time. I reverted to my original landing light emulation. Is someone working on light effects? pitts s1c changes 1. fixed typos in sound.xml 2. changes both wing incidence to 1.5 deg. and the horizontal stab incidence to 2 deg per the pitts s1c plan set posted at the Biplane Forum (www.biplaneforum.com). 3. softened both main gear compression and spring to make take-off and landing possible w/o banging the lower wing tips on the ground. The real Pitts is hard to land but not impossible. 4. animated main gear flex to match compression. I missed #1 and #2 in the commit message for the pitts. Dave P. -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] recent environment changes break airport elevation with metar altimeter settings
On 10/07/2010 11:08 AM, Torsten Dreyer wrote: After 18 minutes sitting on the runway with the altimeter setting matching the current METAR, the altimeter is still showing 100 ft too high. Questions: Q1: Since there has not been a METAR change, why is interpolation smoothing necessary at launch. Q2: The rate of interpolation seems excruciatingly slow. Can this be increased? Dave, i have commited some changes to fg and fgdata. Could you please check if these help with your issue? I tested this with commandline fgfs --airport=kord --disable-real-weather-fetch --metar=KORD 042151Z 25010KT 10SM FEW043 SCT200 14/04 A3035 RMK AO2 SLP281 T01390044 --timeofday=noon the result looks good to me. Thanks, Torsten Looks great here also. Thanks, Dave -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] recent environment changes break airport elevation with metar altimeter settings
On 10/04/2010 05:54 PM, Csaba Halász wrote: On Tue, Oct 5, 2010 at 1:28 AM, dave perryskida...@mindspring.com wrote: Before I set the altimeter to 30.35 (i.e. as launched at 29.92), the altimeter reads aprox. 643 and it noticeably drifts down from that acceptable value. If I set the altimeter to 30.35, the altimeter reads approximately 982 not near 653 or 670. It should have drifted down to the proper value if you had waited a little longer. It certainly has stabilized at 643 feet for me. See this picture: http://imagebin.ca/view/LyxG93.html (Note: the needle animation seems a little off) I think this is due to the weather interpolation code, which tries to smooth out the sudden changes that used to occur when you crossed METAR boundaries. After 18 minutes sitting on the runway with the altimeter setting matching the current METAR, the altimeter is still showing 100 ft too high. Questions: Q1: Since there has not been a METAR change, why is interpolation smoothing necessary at launch. Q2: The rate of interpolation seems excruciatingly slow. Can this be increased? -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] GIT and FGDATA
I am not seeing the slowdown. I just ran a simple script that updates simgear, flightgear source, and fgdata. I would estimate that the git pull origin run in fgdata took about 3 minutes. This performance has been typical for me. I ran System Monitor (F12) during the fgdata pull and the data rate was between 96 and 100 KB/s and the memory usage was constant. I connect via Earthlink dsl. Dave P. On 08/06/2010 02:11 AM, Vivian Meazza wrote: Alan Teeder wrote Same here. But the slow-down has been quicker than the increase in data over time. I am to be yet to be convinced that there isn't something else going on besides the increase in the amount of data. I'm beginning to suspect that the whole concept is fundamentally flawed with larger repos. I hope we can devise a work around - and fast. It's taking me longer to push stuff than to write it in the first place. Work has become almost impossible here. Vivian Looking at other reports on the net it may be something to do with the number of changes, not just the size of the repo. I had reached the same conclusion: it does conform to the observed fact that the slow-down has been faster than the increase in data. The splitting of the repo might not overcome the problem if this is indeed the case. Meanwhile, Git-bash works here. No fancy graphics, but I can push/pull. I'm not always sure what I'm pushing, but hey ho, it's still hanging on in there. Vivian -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] git question
On 08/01/2010 01:07 PM, dave perry wrote: Need some help, I did some clean up of the pa24-250 on my desktop which included creating a pa24-250/Nasal folder and moving all the nasal files to that folder. I also created pa24-250-base.xml that contained all the common lines for the set file and now pa24-250-CIIB-set.xml and pa24-250-CIII-set.xml contain the lines unique to the two auto pilots and include the common base file. I did the same for the model files. I used git status to identify what needed to be done before git commit git merge origin/master git push origin master. But when I did a git pull origin from my notebook, I do not see the changes. If I move the pa24-250 folder to trash and do a git pull pa24-250 from the Aircraft folder on my desktop, I get back all the changes. If I do the same on my notebook, I get back the pa24-250 w/o the recent changes. I am confused. Dave P. -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel In the above note replace git pull pa24-250 with git checkout pa24-250 as that is what I typed. -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] git question
Found the problem. Sorry for the noise. On my notebook, the git pull origin aborted and I did not notice this. preferences.xml had been changed in * master (my local branch). I did a git checkout preferences.xml git pull origin and got a lot of updates. Dave P. On 08/01/2010 01:25 PM, dave perry wrote: On 08/01/2010 01:07 PM, dave perry wrote: Need some help, I did some clean up of the pa24-250 on my desktop which included creating a pa24-250/Nasal folder and moving all the nasal files to that folder. I also created pa24-250-base.xml that contained all the common lines for the set file and now pa24-250-CIIB-set.xml and pa24-250-CIII-set.xml contain the lines unique to the two auto pilots and include the common base file. I did the same for the model files. I used git status to identify what needed to be done before git commit git merge origin/master git push origin master. But when I did a git pull origin from my notebook, I do not see the changes. -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] git questions
On 07/03/2010 02:52 AM, Tim Moore wrote: On Fri, Jul 2, 2010 at 10:21 PM, dave perry skida...@mindspring.com mailto:skida...@mindspring.com wrote: Thanks Tim, Here's the result: [...@dave-pc fgdata]$ git push origin master fatal: protocol error: expected sha/ref, got ' -- The git:// protocol is read-only. Please use the push url as listed on the repository page. --' Do I need authorization to be able to push changes to fgdata? Yes, you do. Register on gitorious, upload an ssh key, ping me You won't need to download the whole repo again :) Hi Tim, I am registered on gitorious now and I have entered my ssh public key. What account info do you need to add me to group +flightgear-developers and can I send it to you off list? Dave Perry -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] git questions
Thanks Tim, Here's the result: [...@dave-pc fgdata]$ git push origin master fatal: protocol error: expected sha/ref, got ' -- The git:// protocol is read-only. Please use the push url as listed on the repository page. --' Do I need authorization to be able to push changes to fgdata? On 07/02/2010 11:48 AM, Tim Moore wrote: On Fri, Jul 2, 2010 at 5:43 PM, dave perry skida...@mindspring.com mailto:skida...@mindspring.com wrote: I am having syntax issues trying to push changes to the git fgdata repository. I have made the edits and git add's, git rm's, git submit, and git status shows my local fgdata master branch clean. But I have not been able to push these changes to the repository. I presume you meant git commit instead of git submit. What is the syntax for this? Can I do this from the two local directories that have changes? Assuming you've committed your changes to your local master branch, then git push origin master will do the trick. If your local branch is no longer up-to-date because someone else has committed something to the repo, then you'll need to merge those changes before you can commit your own, either with git pull origin or git fetch origin; git merge origin/master. Tim Thanks in advance, Dave P. -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first http://sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net mailto:Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Issue with default starting scenario
On 04/06/2010 06:05 PM, David Megginson wrote: On Tue, Apr 6, 2010 at 7:34 PM, Peter Brownsmoothwater...@adelphia.net wrote: In terms of simplicity, I would like to offer a suggestion of using one (or more) of the parking positions at airports with (current) parking positions. If the user spawns at an airport without any preset parking positions, a position of :: 90 degrees to the runway and nose at runway edge :: should work for _most_ airports, until that airport is improved and gets a parking position. James suggestion of a multiplier can work, but I would suggest no more then (width*1) from the runway. Too many small airports would drop you in the woods at a greater multiplier. I realize I'm flogging a dead horse (and won't be offended if people tune out), but I just want to mention planes will very rarely be parked close to the runway, to avoid accidents if someone gets blown off the runway, ground-loops, etc. A plane parked near the runway with fuel in its tanks could make a deadly fireball out of what would otherwise be a bit of gear damage, a few broken runway lights, or (at worse) a bent wing. I have seen exceptions, mainly at private and uncertified airports (e.g. farm strips), but normally planes are parked with their noses against a taxiway, not the runway (or otherwise, a safe distance away on a field or apron). Hi Dave, Perhaps those like me that want to go through a normal start up and check list, especially in AC that I fly often and know well, can use Melchior's ac_state.nas to accomplish this goal at airports we often fly from. It should be easy to add to the check for state == 0 and in that case start with the engine running in take-off configuration (meaning all the items in the take off check list are set to nominal safe values). I don't think ac_state.nas is in cvs. I am attaching a tarball copy. This will require changes to the AC files and perhaps addition to ac_state.nas which goes in data/Nasal. I have used ac_state.nas to create pa24-250 files for KLMO (home airport) and KBTL (sisters airport). By renaming state files, fgfs launches with N7764P in a parking area I chose with every switch, mixture, etc. as it was when I parked it and shut it down. Frankly, if you take off from KLMO (Longmont, CO, N7764P home airport) or KEIK (Eire, CO) or much worse from KEGE (Eagle County, CO, elevation) with the mixture full rich, you may not clear obstacles and for sure will use much more of the runway. In fact a guy from Texas crashed his Cardinal, killing his family, departing from KEIK w/o leaning for take off. So it is not possible to achieve safe nominal values that work for all fgfs airports. Regards, Dave P. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] link problem on new 64 bit system
I get the following error compiling fgfs. /usr/bin/ld: cannot find -lopenal But /usr/lib64/libopenal.so.0 = libopenal.so.1 = libopenal.so.1.11.753. My .bashrc has the line export LD_LIBRARY_PATH=/usr/lib:/usr/lib64:/usr/local/lib:/usr/local/lib64:/usr/local/lib/osgPlugins so I don't see why ld is not finding -lopenal? New System: i7 with 6 GB ddr3, nvidia GTX260, Fedora 12 and plib-1.8.5, fresh cvs/svn of osg, SimGear, fgfs, data. Any help would be appreciated :-( Dave P. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] link problem on new 64 bit system
On 04/03/2010 11:34 AM, John Denker wrote: On 04/03/2010 10:21 AM, dave perry wrote: I get the following error compiling fgfs. /usr/bin/ld: cannot find -lopenal But /usr/lib64/libopenal.so.0 = libopenal.so.1 = libopenal.so.1.11.753. Note that libopenal.so (with no suffix) is not listed. My .bashrc has the line export LD_LIBRARY_PATH=/usr/lib:/usr/lib64:/usr/local/lib:/usr/local/lib64:/usr/local/lib/osgPlugins so I don't see why ld is not finding -lopenal? As a test (and, probably, a workaround) try installing a symlink with the name libopenal.so. Thanks John, this worked. This of course leaves two unanswered questions: 1) Why is libopenal.so missing from the out-of-the-box system? 2) Why was its absence not detected during the autoconfigure step? I had another problem that I missed. I copied the cvs source from another machine and configure for fgfs source did not have execute permissions after the copy. I had used an update/compile/install script for SimGear and fgfs and did not notice the permission error for fgfs ./configure. All is running (very fast) now. Dave P. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] material animation still breaks pick highlights
On 01/31/2010 11:16 PM, Tim Moore wrote: On Thu, Jan 21, 2010 at 5:45 PM, dave perry skida...@mindspring.com mailto:skida...@mindspring.com wrote: Hi, I just added a pick object to a material animation so it would be illuminated when cockpit lighting is turned on. This pick object was highlighted as expected via ctrl-C before adding it to the material animation, but now even with the cockpit lighting off, the pick highlight no longer works. This is with yesterday's cvs. Is there an aircraft in CVS that exhibits this problem? Yes, the specific object referenced is the cabin door handle of the pa24-250. there are many objects in the pa24 that have this problem. E.g. all the switches, throttle, carb heat, prop control, and mixture. Thanks, Tim Dave P. -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net mailto:Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Many updates to the pa24-250
On 01/21/2010 01:12 AM, Gijs de Rooy wrote: Dave Perry wrote: I have just submitted the last update from a hit list I started for the pa24 over the holidays. Very nice updates! One small thing seems to be missing though, the payload does not change when baggage is loaded. ;) Yeah, I have not figured out how to change that. -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] material animation still breaks pick highlights
Hi, I just added a pick object to a material animation so it would be illuminated when cockpit lighting is turned on. This pick object was highlighted as expected via ctrl-C before adding it to the material animation, but now even with the cockpit lighting off, the pick highlight no longer works. This is with yesterday's cvs. Dave P. -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Many updates to the pa24-250
On 01/21/2010 06:35 AM, Torsten Dreyer wrote: On 01/21/2010 01:12 AM, Gijs de Rooy wrote: Dave Perry wrote: I have just submitted the last update from a hit list I started for the pa24 over the holidays. Very nice updates! One small thing seems to be missing though, the payload does not change when baggage is loaded. ;) Yeah, I have not figured out how to change that. Just write the weight in lbs to /sim/weight[4]/weight-lb. I wonder, what's in those suitcases... That works! It will be in my next patch. BTW, 122 lbs of pixels. Dave P. -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Many updates to the pa24-250
Hi All, I have just submitted the last update from a hit list I started for the pa24 over the holidays. Updates: * full 3D interior including animated cabin door, animated visors, arm rests. * animated baggage compartment door with baggage loaded and removed by menu. * cabin door and baggage door changes do not distort fuselage contours. * replaced landing gear forks and struts with realistic parts including brakes and brake lines. * replaced nav lights with more realistic parts. * instrument panel moved to proper position in 3D interior. Take it for a hop and play with the improvements. The doors are operated by either picks or by the Comanche menu. Enjoy, Dave P. -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] adding CenturyIIB and CenturyIII to AP list in gui.nas
Hi, Does anyone object to graying out the autopilot menu for tw additional autopilots used by several aircraft? If not, would someone with commit authority please apply the following simple patch? Index: gui.nas === RCS file: /var/cvs/FlightGear-0.9/data/Nasal/gui.nas,v retrieving revision 1.121 diff -u -p -r1.121 gui.nas --- gui.nas16 Nov 2009 20:40:15 -1.121 +++ gui.nas29 Dec 2009 17:43:02 - @@ -103,7 +103,10 @@ _setlistener(/sim/signals/nasal-dir-ini # enable/disable menu entries menuEnable(fuel-and-payload, fdm == yasim or fdm == jsb); -menuEnable(autopilot, props.globals.getNode(/autopilot/KAP140/locks) == nil); +menuEnable(autopilot, props.globals.getNode(/autopilot/KAP140/locks) == nil + and props.globals.getNode(/autopilot/CENTURYIIB/locks) == nil + and props.globals.getNode(/autopilot/CENTURYIII/locks) == nil +); menuEnable(multiplayer, multiplayer.is_active()); menuEnable(tutorial-start, size(props.globals.getNode(/sim/tutorials, 1).getChildren(tutorial))); menuEnable(joystick-info, size(props.globals.getNode(/input/joysticks).getChildren(js))); Thanks, Dave P. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] how to gray out autopilot menu?
Hi, I have searched both the c172p and SenecaII folder for autopilot or gui or just menu and I can not find how these AC gray out the autopilot menu. What's the secret? Dave P. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Glide slope (ILS) range
On 12/18/2009 02:53 PM, John Denker wrote: More generally: Limiting the GS service volume to 10nm or thereabouts is a significant departure (if you'll pardon the expression) from previous FGFS behavior, but it is not wrong. It is a feature, not a bug. Agreed. I often do the ILS rwy 33 approach into KFNL for real for currency maintenance. Often in the procedure turn, the GS flag will activate indicating no usable GS signal. The GS flag may stay until (sometimes after) I start the 45 deg turn to 328 deg inbound on the LOC. This pretty well matches the fgfs GS flag behavior for this approach. Dave P. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Inadvertant change to c172p p_factor
I just noticed that the patch to animate the c172p nose gear strut scissors that I sent to James Turner to commit also picked up a local change I made to decrease the p_factor. RCS file: /var/cvs/FlightGear-0.9/data/Aircraft/c172p/c172p.xml,v retrieving revision 1.24 diff -u -p -r1.24 c172p.xml --- c172p.xml6 Dec 2009 19:12:23 -1.24 +++ c172p.xml9 Dec 2009 03:31:22 - @@ -209,7 +209,7 @@ yaw 0.0 /yaw /orient sense 1 /sense - p_factor 10 /p_factor + p_factor 5 /p_factor /thruster /engine tank type=FUEL !-- Tank number 0 -- Index: initfile.xml === This can be changed back to 10 easily. I have many hours in real c172's and the value of p_factor = 10 feels to me unrealistic. That is why my local copy was changed to p_factor = 5. Regards, Dave P. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] fgfs compile error, today's cvs
I am getting the following error compiling fgfs from cvs today on two different systems. $ make Making all in tests make[1]: Entering directory `/home/dad/source-osg/source-fgfs/tests' make[1]: *** No rule to make target `est-epsilon.c', needed by `est-epsilon.o'. Stop. make[1]: Leaving directory `/home/dad/source-osg/source-fgfs/tests' make: *** [all-recursive] Error 1 $ -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
On 12/01/2009 11:38 AM, John Denker wrote: On 12/01/2009 11:19 AM, Heiko Schulz wrote: To your note: So the c172p has now: -struts animation The reported bug http://www.av8n.com/fly/fgfs/htm/bug-list.htm#bug-x1768 concerns the nutcracker, which as of 1 Dec 2009 looks quite weird because it doesn't fold; it just gets shoved rigidly up into the cowling. I just submitted a patch that animates the c172p nose gear nutcracker so it folds as the strut is compressed. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
On 12/01/2009 12:47 PM, Stuart Buchanan wrote: Hi John, Thanks for the list. A number of the c172p issues are on my to-do list (I've indicated relative priorities - let me know if you think they are wrong), and others should have been fixed recently. I've put some comments inline, along with some specific questions. Of course, if you'd like to submit patches for the c172p, I can get them committed. -Stuart 2 :: c172p basic flight dynamics You suggest two possible explanations. Not having access to a C-172, nor enough flight time to be able to guess which is correct, I'm not sure there's much I can sensibly do without making it worse. If you can suggest which is wrong, I'll see what I can do. My guess would be idle RPM, given your previous comments that the aircraft if over-powered. 4 :: wrong runway, not in airport database I suspect that might be an artifact of the apt.dat file being out of kilter with the scenery you've got. Have you tried TerraSync to see what the latest scenery looks like. 5 :: duplicate livery This is on my todo list. 8 :: c172p and pa24-250 : weird noises For the c172p, would it be worthwhile just replacing the sounds with the c182rg ones? 10 :: c172p interior lighting This should now be fixed - there's a dial to control lighting next to the carb heat. However, it's not connected to the (non-existant!) master switch, or an electrical system in general. 11 :: landing light and taxi light not usable for landing or taxiing This is a general issue that requires a general fix. 12 :: disappearing GS needle Lacking IFR experience, I don't know exactly how to fix this, and in particular the barber-pole behaviour. This was fixed as well as adding realistic GS and Nav flags and smooth transitions to 0 position when out of range or switching to new freq w/o LOC. The c172p, pa24, and pa28 all now use the vor in Aircraft/Instruments-3d. 13 :: no Kollsman window As mentioned by HHS, this should now be fixed. 14 :: c172p rudder pedals On the todo list, but fairly low down. 15 :: c172p parking brake Good point - I'll get this on the todo list. Should be straight-forward to add. For reference, is this pulled on and rotated? Could you describe the movement and the shape of the handle? 16 :: c172p switches On the todo list, but low down. 17 :: c172p voltmeter A side-effect of the lack of an electrical system. 18 :: c172p carb heat, throttle, mixture Now fixed. 19 :: c172p audio panel Requires electrical system. 20 :: c172p carb heat The model for this is improved, but adding the function requires some sort of FDM update, but I'm not quite sure what. 21 :: c182rg sunk in On the todo, but low priority. 22 :: c172p trim indicator Do you have any pictures of this? I've had difficulty finding anything. Also, what's the take-off trim position? 23 :: c172p flap position Now fixed. 24 :: c172p fuel caps Modelling issue - easy to resolve. What colour should they be? 25 :: c172p nutcracker Added to the todo list, low priority. 26 :: see-through 172 Added to TODO list, low priority. 27 :: c172p EGT Added to TODO list, medium priority. 28 :: c172p and SenecaII transponder Added to todo list, medium priority. 29 :: gps Is it realistic to fly without a GPS these days? Well, I manage quite happily ;) Seriously - I think adding a GPS will be quite a lot of work. Do we have any that are plug-and-play? 31 :: check for missing scenery A fine idea. I'll see if I have time. snip 38 :: FGShortRef out of date Very good point. I'll look into what we need to do to regenerate. 39 :: c172p stray structure On the todo list 53 :: c172p electrical system If you have a patch, that would be great. snip -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel
[Flightgear-devel] fgfs sound crystal clear /w pulseaudio in FC12
Hi Erik, For any Fedora users, I recommend preupgrade to FC12. All the fgfs sounds work and are crystal clear, no crackle! This includes ATC, ATIS, vor and loc ident, marker beacons, cockpit sounds (switch clicks, flaps, etc.). I encountered several potential gotchas: 1. If you have an NVIDIA graphics card, before you begin, print the info from the following link: http://linuxsoftwareblog.com/blog/?p=232 2. Clean up /boot before you start preupgrade. Delete all but the most recent kernel files. If you do this, a 200 MB /boot is big enough. 3. Do a sudo yum upgrade before running preupgrade. 4. Be ready with a fedora DVD for a rescue. After preupgrade completes, and the system is rebooted, you may need to edit /etc/inittab to boot into run level 3. 5. The info from the link in #1 should allow you to get nvidia driver support. I use the driver from www.nvidia.com, so only the first item was required to allow the nouveau module to release control so the install could proceed. Hope this helps others. Thanks Erik for staying on this! Regards, Dave P. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fgfs sound crystal clear /w pulseaudio in FC12
On 11/30/2009 09:44 AM, dave perry wrote: Hi Erik, For any Fedora users, I recommend preupgrade to FC12. All the fgfs sounds work and are crystal clear, no crackle! This includes ATC, ATIS, vor and loc ident, marker beacons, cockpit sounds (switch clicks, flaps, etc.). I encountered several potential gotchas: 1. If you have an NVIDIA graphics card, before you begin, print the info from the following link: http://linuxsoftwareblog.com/blog/?p=232 2. Clean up /boot before you start preupgrade. Delete all but the most recent kernel files. If you do this, a 200 MB /boot is big enough. 3. Do a sudo yum upgrade before running preupgrade. Should read 3. Do a sudo yum update before running preupgrade. 4. Be ready with a fedora DVD for a rescue. After preupgrade completes, and the system is rebooted, you may need to edit /etc/inittab to boot into run level 3. 5. The info from the link in #1 should allow you to get nvidia driver support. I use the driver from www.nvidia.com, so only the first item was required to allow the nouveau module to release control so the install could proceed. Hope this helps others. Thanks Erik for staying on this! Regards, Dave P. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FC12 openal and pulseaudio question
Update on symptoms: I went back to osg-2.8.2, updated SimGear, fgfs, and data from cvs. Recall that I upgraded from FC10 to FC12 using preupgrade. Sound is fine in several other applications. My first run of fgfs had no sound and great frame rates (throttled to 30) at KHAF and KSFO. When I used file Quit Exit to try and end fgfs, it locks up completely. If I minimize the window and then maximize the window, it is black. I then used Applications System Tools System Monitor to kill the fgfs process. fgfs process is using 100% of cpu before I kill it. When I restart fgfs, it has very poor frame rate and crackly sound. If I kill the pulseaudio process, and then run fgfs, pulseaudio process is back, I am back to no sound and great frame rates and when I exit fgfs, it locks up again. Anyone successfully using fgfs with sound in FC12? Dave P. Curtis Olson wrote: On Sat, Nov 28, 2009 at 8:31 PM, dave perry wrote: Hi, I used the preupgrade to FC12 from FC10 this Saturday on my ASUS notebook (Intel core2 duo). This installed openal-soft-1.10.622-2 openal-soft-devel-1.10.622-2 and pulseaudio-0.9.21-1 I had to use OpenSceneGraph-2.9.5 as the svn up for osg broke fgfs link. With the above I either get good frame rates (same as in FC10) and no sound or crackly sound with very low frame rates depending on how I launch fgfs. Question: What versions of openal and pulseaudio are others with FC12 using that give good sound and performance? I have a machine here where I did the upgrade from Fedora 10 to Fedora 11 and I see similar symptoms to what you report in your FC10-FC12 upgrade. For the most part, all other audio apps are just fine on this machine. I can play youtube videos, I can play mp3's and audio CD's. I hear the desktop sound effects, etc. But audio for FlightGear has been totally hosed since my upgrade. I have another machine (laptop) which I installed FC11 directly, and audio with respect to FlightGear is better. I generally hear what I should here, but there is quite a bit of static/crackling mixed in, so it is far from perfect. Erik mentioned running openal-info or alcinfo, but neither of these are installed on my machine with my version of openal or alc: $ rpm -aq openal openal-0.0.9-0.17.20060204cvs.fc11.i586 As others have pointed out, pulseaudio (despite it's imperfections) is installed by default on a lot of current distributions. It seems like we should try to find a way to work with it some how. I personally don't want to uninstall pulseaudio from my system and then have to struggle with all my other individual apps to reconfigure their audio and get them back to a working state ... right now, FlightGear seems to be the only app I have that isn't playing nice with pulseaudio. Even my virtual machine (windows XP running inside my Linux host) happily plays all it's sound effects through my linux host system. Regards, Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ http://baron.flightgear.org/%7Ecurt/ -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FC12 openal and pulseaudio question
Problem fixed. Great sound including vor and loc idents. The problem was FC10 rpms that did not get removed. alsa-plugins-pulseaudio were the issue. Sorry for the noise. dave perry wrote: Update on symptoms: I went back to osg-2.8.2, updated SimGear, fgfs, and data from cvs. Recall that I upgraded from FC10 to FC12 using preupgrade. Sound is fine in several other applications. My first run of fgfs had no sound and great frame rates (throttled to 30) at KHAF and KSFO. When I used file Quit Exit to try and end fgfs, it locks up completely. If I minimize the window and then maximize the window, it is black. I then used Applications System Tools System Monitor to kill the fgfs process. fgfs process is using 100% of cpu before I kill it. When I restart fgfs, it has very poor frame rate and crackly sound. If I kill the pulseaudio process, and then run fgfs, pulseaudio process is back, I am back to no sound and great frame rates and when I exit fgfs, it locks up again. Anyone successfully using fgfs with sound in FC12? Dave P. Curtis Olson wrote: On Sat, Nov 28, 2009 at 8:31 PM, dave perry wrote: Hi, I used the preupgrade to FC12 from FC10 this Saturday on my ASUS notebook (Intel core2 duo). This installed openal-soft-1.10.622-2 openal-soft-devel-1.10.622-2 and pulseaudio-0.9.21-1 I had to use OpenSceneGraph-2.9.5 as the svn up for osg broke fgfs link. With the above I either get good frame rates (same as in FC10) and no sound or crackly sound with very low frame rates depending on how I launch fgfs. Question: What versions of openal and pulseaudio are others with FC12 using that give good sound and performance? I have a machine here where I did the upgrade from Fedora 10 to Fedora 11 and I see similar symptoms to what you report in your FC10-FC12 upgrade. For the most part, all other audio apps are just fine on this machine. I can play youtube videos, I can play mp3's and audio CD's. I hear the desktop sound effects, etc. But audio for FlightGear has been totally hosed since my upgrade. I have another machine (laptop) which I installed FC11 directly, and audio with respect to FlightGear is better. I generally hear what I should here, but there is quite a bit of static/crackling mixed in, so it is far from perfect. Erik mentioned running openal-info or alcinfo, but neither of these are installed on my machine with my version of openal or alc: $ rpm -aq openal openal-0.0.9-0.17.20060204cvs.fc11.i586 As others have pointed out, pulseaudio (despite it's imperfections) is installed by default on a lot of current distributions. It seems like we should try to find a way to work with it some how. I personally don't want to uninstall pulseaudio from my system and then have to struggle with all my other individual apps to reconfigure their audio and get them back to a working state ... right now, FlightGear seems to be the only app I have that isn't playing nice with pulseaudio. Even my virtual machine (windows XP running inside my Linux host) happily plays all it's sound effects through my linux host system. Regards, Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ http://baron.flightgear.org/%7Ecurt/ -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july
[Flightgear-devel] FC12 openal and pulseaudio question
Hi, I used the preupgrade to FC12 from FC10 this Saturday on my ASUS notebook (Intel core2 duo). This installed openal-soft-1.10.622-2 openal-soft-devel-1.10.622-2 and pulseaudio-0.9.21-1 I had to use OpenSceneGraph-2.9.5 as the svn up for osg broke fgfs link. With the above I either get good frame rates (same as in FC10) and no sound or crackly sound with very low frame rates depending on how I launch fgfs. Question: What versions of openal and pulseaudio are others with FC12 using that give good sound and performance? Thanks, DaveP. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] more sound problems with Tuesday cvs update
Erik Hofman wrote: dave perry wrote: Before the recent updates, both had normal cockpit sound but no marker beacon or nav ident sounds as well as working Doppler in fly-by view. Just to be sure: did it have proper Doppler (reading the previous line might say just the opposite). If so, could you specify which version of OpenAL you are using by running FlightGear/test/al-info Yes, Doppler was working before the cvs update. [...@dadsoffice bin]$ ./al-info AL_VENDOR = OpenAL Community AL_RENDERER = Software AL_VERSION = 1.1 AL_EXTENSIONS = ALC_EXT_capture AL_EXT_capture AL_EXT_vorbis AL_LOKI_quadriphonic AL_LOKI_play_position AL_LOKI_WAVE_format AL_LOKI_IMA_ADPCM_format AL_LOKI_buffer_data_callback ALC_LOKI_audio_channel ALC_MAJOR_VERSION = 1 ALC_MINOR_VERSION = 0 ALC_EXTENSIONS = ALC_DEFAULT_DEVICE_SPECIFIER = '((sampling-rate 44100) (device '(native)) also [...@dadsoffice bin]$ rpm -q openal openal-0.0.9-0.15.20060204cvs.fc9.i386 -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] more sound problems with Tuesday cvs update
Erik Hofman wrote: dave perry wrote: Yes, Doppler was working before the cvs update. [...@dadsoffice bin]$ ./al-info AL_VENDOR = OpenAL Community AL_RENDERER = Software Alright, the same version as Georg; then it should be fixed in CVS. Erik -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel Yes, sound is working now. I have ATIS sound (at least at KBTL where I checked). Still no ident sounds for NDB, LOC, or VOR stations. Still now marker beacon sound. Thanks for all the effort! Dave P. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] more sound problems with Tuesday cvs update
Hi Erik, I have two systems running fgfs. (1) AMD Athlon XP 3200+ with-up to-date FC10 (pulseaudio-0.9.14-3.fc10.i386) (2) Intel Core 2 duo with-up to-date x86_64 FC10 (pulseaudio-0.9.14-3.fc19.x86_64) Before the recent updates, both had normal cockpit sound but no marker beacon or nav ident sounds as well as working Doppler in fly-by view. How ever, in outside orbit view, the sound pitch depended on the viewers direction from the aircraft. Now, on both systems, the cockpit sound is normal when the aircraft is stationary, but as soon as velocity is non zero , the sound becomes crackly something like the right sound is fighting with a very low pitched sound. Also, Doppler is now very broken with only the very low pitched rumble and a crackle or pop when the closing speed goes from positive to negative. Hope this is helpful, Dave P. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] more sound problems with Tuesday cvs update
Hi Victhor, I tried yum erase pulseaudio which also removed the plugins that depend on pulseaudio, and the sound problems are the same. Victhor Foster wrote: Uninstall PulseAudio. I used to have those problems and they're gone after I removed it. 2009/11/25 Heiko Schulz aeitsch...@yahoo.de: Hi Erik, Hi Erik, I have two systems running fgfs. (1) AMD Athlon XP 3200+ with-up to-date FC10 (pulseaudio-0.9.14-3.fc10.i386) (2) Intel Core 2 duo with-up to-date x86_64 FC10 (pulseaudio-0.9.14-3.fc19.x86_64) Before the recent updates, both had normal cockpit sound but no marker beacon or nav ident sounds as well as working Doppler in fly-by view. How ever, in outside orbit view, the sound pitch depended on the viewers direction from the aircraft. Now, on both systems, the cockpit sound is normal when the aircraft is stationary, but as soon as velocity is non zero , the sound becomes crackly something like the right sound is fighting with a very low pitched sound. Also, Doppler is now very broken with only the very low pitched rumble and a crackle or pop when the closing speed goes from positive to negative. Hope this is helpful, Dave P. I have to add that Sound volume is broken too now,(but Mute is working), and mk-viii as well. Can't hear them anymore Kind Regards HHS __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] more sound problems with Tuesday cvs update
Thanks Stefan, I plan to after Thanksgiving and before Christmas. I need both the 32bit and 64 bit DVDs, so two long downloads. Dave P. stefan riemens wrote: Alternatively, upgrade to something newer. I have found PulseAudio has much improved since f10. (I'm a long-time fedora user myself as well). F10 is going to be end of life (no more updates) within a month time anyway. F12 has been great for me... 2009/11/25, Victhor Foster victhor.fos...@gmail.com: Uninstall PulseAudio. I used to have those problems and they're gone after I removed it. 2009/11/25 Heiko Schulz aeitsch...@yahoo.de: Hi Erik, Hi Erik, I have two systems running fgfs. (1) AMD Athlon XP 3200+ with-up to-date FC10 (pulseaudio-0.9.14-3.fc10.i386) (2) Intel Core 2 duo with-up to-date x86_64 FC10 (pulseaudio-0.9.14-3.fc19.x86_64) Before the recent updates, both had normal cockpit sound but no marker beacon or nav ident sounds as well as working Doppler in fly-by view. How ever, in outside orbit view, the sound pitch depended on the viewers direction from the aircraft. Now, on both systems, the cockpit sound is normal when the aircraft is stationary, but as soon as velocity is non zero , the sound becomes crackly something like the right sound is fighting with a very low pitched sound. Also, Doppler is now very broken with only the very low pitched rumble and a crackle or pop when the closing speed goes from positive to negative. Hope this is helpful, Dave P. I have to add that Sound volume is broken too now,(but Mute is working), and mk-viii as well. Can't hear them anymore Kind Regards HHS __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: data/Aircraft/c172p/Nasal action-sim.nas, 1.1, 1.2
Ron Jensen wrote:
The relationship between feet and meters is exactly 0.3048 feet per
meter. Your conversion value of 12/39.4 is approximately 0.30456... It
would be better to do:
# constants
...
var radTOdeg = 57.295779;
var ftTOmeter = 0.3048;
...
# Right main
var delta_h = dhR_ft.getValue()*ftTOmeter;
var right_alpha_deg = ( math.acos( (h0 - delta_h)/R_m ) - theta0_rad
)*radTOdeg;
# Left main
var delta_h = dhL_ft.getValue()*ftTOmeter;
var left_alpha_deg = ( math.acos( (h0 - delta_h)/R_m ) - theta0_rad
)*radTOdeg;
This is more exact and also avoids two divisions per frame.
Thanks Ron,
All but the exact ftTOmeter value is already in cvs. I used ooCalc to
compute 1/.0254 and did not format the cell. Good catch. Would someone
with commit privilege apply this patch?
? Nasal.diff
Index: action-sim.nas
===
RCS file: /var/cvs/FlightGear-0.9/data/Aircraft/c172p/Nasal/action-sim.nas,v
retrieving revision 1.4
diff -u -p -r1.4 action-sim.nas
--- action-sim.nas 24 Nov 2009 16:51:47 - 1.4
+++ action-sim.nas 24 Nov 2009 17:20:30 -
@@ -56,7 +56,7 @@ var update_actions = func {
var h0 = 0.63872;
var theta0_rad = 0.803068;
var radTOdeg = 57.295779;
- var ftTOm = 0.304569;
+ var ftTOm = 0.3048;
# Right main
var delta_h = dhR_ft.getValue()*ftTOm;
Dave P.
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: data/Aircraft/c172p
Heiko Schulz wrote: Hello. First thanks for comitting the changes to the c172p. For all, I don't see me as main author, just as another one beside the already known, just made a new 3d-model and 3d-panel. So thanks for Dave Perry as another contributer for the instruments-lights! I see still issues and this regards still to the alignement of the 3d-modell. It looks o.k. in the air, but on the ground it is not o.k. Martin is right, when he says that the real aircraft is tilted standing on the ground at exactly 5 degrees to the back. A c172N POH found on the web, say this too, as my drawings I got as well. Manual: http://www.redskyventures.org/doc/cessna-poh/C172N-1978-POH-S1to7-scanned.pdf Page 5 for the drawing. So the prop is also tilted 5 degrees to the back. The mistake is that I modelled the aircraft standing on the ground, instead in cruising level. So the maingear struts has to be compressed when the aircraft is one the ground, which is actually not the case- the mainstruts doesn't compress yet. Problem: just changing the pitch in Models/c172p.xml doesnt't made this right. You can easily see that, when you compare the locations of the gears in the fdm with the one in Blender. The most right answer would be to change the orientation of the model in Blender, but this means also to edit the animations and the positions of the instrumentsA lot of work, but then it would be right ( and the ambient colors could be corrected as well) I would begin with the work today, but may need help with the mainstruts compression, as this means maybe a bit math... Anything against, or maybe even someone who wants to do the whole job? ;-) Kind Regards Heiko Hello Heiko, I have another patch ready to submit with xml indents and tabs fixed and consolidation of redundant sections as well as alignment of the propeller spin axis with the spinner axis. I believe that the position on the ground should be totally determined by the gear compression forces and the mass and cg. I.e. it will correct itself once we implement correct gear compressions. So don't mess with rotating the 3d model. At least let me try to get it right with gear compressions. One other issue I see with the 3d model and the textures. The way the cuts in the textures is done, one has nearly vertical surfaces on each side near the bottom edge of the windshield. This results in severe stretching of the textures on each side below the windshield. This is fairly obvious and needs to be corrected. This again involves a lot of work. Does the team think we need to fix this for the liveries before the next release as this is the default ac? Regards, Dave P. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] boost library version
Geoff McLane wrote:
On Thu, 2009-11-19 at 00:18 +1100, George Patterson wrote:
2009/11/17 Diego Fernando Rodríguez Varón diegorodrigu...@gmail.com:
Hello everyone.
I was experiencing the segmentation fault reported by Nicolas before so I
just tried updating and compiling. But I get the following error:
checking for boostlib = 1.37.0... configure: error: We could not detect
the boost libraries (version 1.37 or higher). If you have a staged boost
library (still not installed) please specify $BOOST_ROOT in your
environment and do not give a PATH to --with-boost option. If you are sure
you have boost installed, then check your version number looking in
boost/version.hpp. See http://randspringer.de/boost for more
documentation.
I'm using Ubuntu 8.04 and the boostlib supported is 1.34.
So I had change the configure.ac file
AX_BOOST_BASE([1.34.0]
Is flightgear stopping support for Hardy Heron? :( Hopefully not.
Do I really need 1.37?
Hi Diego,
You might be able to get the source package for libboost1.37 for
Intrepid and try compiling it under Hardy. I will try and run up a VM
to test this idea. Howevere it might take me a bit as I am away over
the weekend.
Regards
George
Tim Moore wrote:
[...] The critical feature from 1.37 is unordered_map; does
Debian stable have std::tr1::unordered_map (i.e., /usr/include/c
++//unordered_map)?
In Ubuntu 8.04 LTS - the latest boost suite available via
the update manager is 1.34...
~$ dpkg -l | grep boost
ii boost-build 2.0-m11-2 Build system
ii libboost-date-time-dev1.34.1-4ubuntu3 set of date-time libraries
based on generic
ii libboost-date-time1.34.1 1.34.1-4ubuntu3 set of date-time libraries
based on generic
ii libboost-dev 1.34.1-4ubuntu3 Boost C++ Libraries
development files
... etc, etc, etc ...
~$ find /usr/include/ -name unordered_map\*|xargs ls -l
-rw-r--r-- 1 root root 6143 2009-02-20 13:37 /usr/include/c
++/4.2/tr1/unordered_map
Does that mean I will _NOT_ be able to compile SG/FG in my
current Ubuntu?
Ok, did CVS update, and bingo, during configure, in SG -
checking for boostlib = 1.37.0... configure: error: etc, etc as
listed above...
SOOO, do I have to manually 'install' boost? Like boost_1_40_0.tar.gz
say, and deal with, as written on the boost web page -
'Boost.CMake is now distributed separately. The
cmake build for boost is BROKEN in the tarballs above. See the
Boost.CMake wiki page for pointers to working versions.'
Tried -
~$ sudo aptitude install libboost-all-dev
[snip]
Couldn't find any package whose name or description matched
libboost-all-dev
No packages will be installed, upgraded, or removed.
[snip]
And
~$ sudo apt-get install libboost-all-dev
[snip]
E: Couldn't find package libboost-all-dev
So those did NOTHING! And as stated the Synaptic Package
Manager only list 1.34, so also does not help...
Do I, and others like me, have to now get into downloading
the later source of boost, and 'fight' to compile/install it?
Working with the BROKEN CMake as listed above???
Ok, I downloaded boost_1_40_0.tar.gz 39,253,625, unpacked
just the 'boost' folder! I am in my $HOME/fg/fg7, which I
shall call root here. In this 'root' I have an 'install'
directory, where I 'install' PLIB, OSG, simgear, etc...
so I can work with later versions of these than in the
distro...
So I unpacked the boost directory into -
root/install/boost/include
producing
root/install/boost/include/boost
Then by removing the SG configure.ac line -
AX_BOOST_BASE([1.37.0])
and adding -
# specify the boost location
AC_ARG_WITH(boost, [ --with-boost=PREFIX Specify the prefix path to
boost])
if test x$with_boost != x ; then
echo boost prefix is $with_boost
EXTRA_DIRS=${EXTRA_DIRS} $with_boost
fi
I suppose I could have ALSO added some 'code' to check
the boost version in boost/version.hpp, but that
can come later...
And then doing an appropriate -
./configure --with-boost=$HOME/install/boost ...etc...
I could get SG compiled. As I understand at present
SG/FG only requires the boost headers, and none
of the compiled boost libraries...
This got SG compiled OK... but then I must do
the SAME thing in fgfs/source/configure.ac,
and maybe I can get it ALL COMPILED!!!
But am I wasting my time? Is there an EASIER
way than this? ;=()
As John Denker wrote:
Introducing additional dependencies into FGFS makes
extra work for a lot of people.
I am sorry, but here here to that ;=))
Heads up! No, tail down ;=))
Geoff.
PS: Who do I need to contact about getting
a later 'boost' into the Ubuntu distribution?
Do I contact the 'boost' or the 'Ubuntu'
developers? Or both? That is, who is normally
responsible for 'updating' a distribution?
The distro developers, or the package
developers?
And that would be a similar question concerning
updating the flightgear,
Re: [Flightgear-devel] BUG - Evening, Rain, Propeller
Heiko Schulz wrote: The Model-Author of the c172p has this on his list, but did not find any time to change this... Hi Heiko (and anyone who is maintaining the c172P), Several questions: First, who is the Model-Author for the c172p? A search of the c172 folder only yields David Megginson who has not been active with fgfs for some time. The current 3d model was don by someone else; perhaps you. Second, I have edited my local copy for cvs so that the nav-light switch also controls instrument/pannel lights so the c172p can be flown at night. I also point the vors to the recent changed Instruments-3d/vor folder which you can try out using either the cvs pa24 or cvs pa28. with these changes to Instruments-3d/vor, the GS flag now works and the needles smoothly transition to 0.0 when out-of-range or when tuned to a non-gs vor/loc. Does anyone object to committing these changes? Regards, Dave P. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] BUG - Evening, Rain, Propeller
Heiko Schulz wrote: Hello Dave, I did the the 3d-model incl. the 3d-panel, but there was still a lot of issues. All other things (fdm, wrapping xml's, 2d-panels etc) I left untouched. Hi Heiko (and anyone who is maintaining the c172P), Several questions: First, who is the Model-Author for the c172p? A search of the c172 folder only yields David Megginson who has not been active with fgfs for some time. The current 3d model was don by someone else; perhaps you. Second, I have edited my local copy for cvs so that the nav-light switch also controls instrument/pannel lights so the c172p can be flown at night. I also point the vors to the recent changed Instruments-3d/vor folder which you can try out using either the cvs pa24 or cvs pa28. with these changes to Instruments-3d/vor, the GS flag now works and the needles smoothly transition to 0.0 when out-of-range or when tuned to a non-gs vor/loc. Does anyone object to committing these changes? That sounds great, and I'm agree with this changes. Kind Regards Heiko Thanks Heiko, I will submit a patch with the above update. Dave P. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] proposed small change to navradio.cxx
Hi All,
Presently, the gs deflection retains it's final value when the nav
frequency is changed to a station that has no glide slope or when the gs
goes out of range. I had been using the select animation to overcome
this, but that does not allow using a nasal filter to smoothly park the
gs needle. The attached small patch overcomes this. I wanted to have
other ac developers comments before I ask James Turner to commit this
small change.
Dave P.
? navradio.diff
Index: navradio.cxx
===
RCS file: /var/cvs/FlightGear-0.9/source/src/Instrumentation/navradio.cxx,v
retrieving revision 1.57
diff -u -p -r1.57 navradio.cxx
--- navradio.cxx24 Oct 2009 08:31:39 -1.57
+++ navradio.cxx10 Nov 2009 20:31:01 -
@@ -580,6 +580,8 @@ void FGNavRadio::updateGlideSlope(double
if (!_gs || !inrange_node-getBoolValue()) {
gs_dist_node-setDoubleValue( 0.0 );
gs_inrange_node-setBoolValue(false);
+_gsNeedleDeflection = 0.0;
+_gsNeedleDeflectionNorm = 0.0;
return;
}
@@ -589,6 +591,8 @@ void FGNavRadio::updateGlideSlope(double
gs_inrange_node-setBoolValue(gsInRange);
if (!gsInRange) {
+_gsNeedleDeflection = 0.0;
+_gsNeedleDeflectionNorm = 0.0;
return;
}
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] New Sound system committed
Erik Hofman wrote: Scott Hamilton wrote: On Thu, 2009-10-29 at 13:57 +0100, Erik Hofman wrote: Hi ya Erik, I just tried out the test3, no sound what so ever... I've committed the current state of my local code to see if it fixes anything. Erik Hi Erik, Updated both my core2 duo (64 bit FC10) and my Athlon XP 3200+ (32 bit FC10) both running FC10 openal and freealut distribution rpms. ATC and aircraft sounds are now working on both systems. Neither had aircraft sounds before this update. Thanks for all your work! Dave P. -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Altimeter setting does not produce correct field altitude
Tim Moore wrote: On 10/27/2009 01:49 PM, dave perry wrote: Tim Moore wrote: On 10/17/2009 07:42 PM, Ron Jensen wrote: On Sat, 2009-10-17 at 11:24 -0600, dave perry wrote: With current cvs update on my notebook, I am not getting the correct field elevation when I set the altimeter to match the real weather altimeter setting. It is off by 160 feet today at KLMO (field elevation 5052). With my desktop which was last updated from cvs about 10/3, it is very nearly correct even with radically high or low pressures. I've seen this problem going back into the middle of September: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23719.html It would be nice if someone figured out how to fix this... With Ron's help I've committed a fix for this. Please check it out and report any further problems. Thanks, Tim Hi Tim, With the altimeter set to the ALT (in hg) in the weather conditions table from the Environment gui, the field elevations I checked were correct. But the number in this table no longer matches the real weather scenario metar number. I believe Torsten made significant changes to the real weather code. I just did a test with real-weather-fetch at KSLC. When I set the altimeter using the QNH in the metar -- 29.76 -- the altitude is right on, as far as I can see. It's true that this pressure doesn't match the pressure shown in the Environment Conditions gui, 29.814, but that is to be expected; that pressure is now the true pressure at sea level, not the altimeter pressure. Does this jibe with what you're seeing? Tim Hi Tim, Yes. After an update of fgfs and simgear this morning, I started at KEGE (Eagle County RGNL with a field elevation and TDZE both equal to 6540 ft using real weather. The QNH was 29.37 from metar. When I set the altimeter to this, it indicated 6528. Since I was at the threshold, not the TZE, that is close enough and much closer that with the altimeter set to the ALT (in hg) from the gui weather conditions. ALT (in hg) from the gui weather conditions used to be the QNH and one could reset it in the gui while flying so that the pressure altitude and the indicated altitude with the altimeter set to the QNH were not the same. In that case, one could do an approach and the minimums were realistic. It seems that we can no longer do this when using the manual input as the metar source. Why does the sim pilot need to know the sealevel pressure? In the above manual scenario, the sim pilot does need to know the QNH. Regards, Dave P. -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Altimeter setting does not produce correct field altitude
Tim Moore wrote: On 10/17/2009 07:42 PM, Ron Jensen wrote: On Sat, 2009-10-17 at 11:24 -0600, dave perry wrote: With current cvs update on my notebook, I am not getting the correct field elevation when I set the altimeter to match the real weather altimeter setting. It is off by 160 feet today at KLMO (field elevation 5052). With my desktop which was last updated from cvs about 10/3, it is very nearly correct even with radically high or low pressures. I've seen this problem going back into the middle of September: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23719.html It would be nice if someone figured out how to fix this... With Ron's help I've committed a fix for this. Please check it out and report any further problems. Thanks, Tim Hi Tim, With the altimeter set to the ALT (in hg) in the weather conditions table from the Environment gui, the field elevations I checked were correct. But the number in this table no longer matches the real weather scenario metar number. I believe Torsten made significant changes to the real weather code. Thanks, Dave P. -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] New Sound system committed
Well, after an update this morning, I am back to only atc sounds on my Athlon 32 bit machine independent of the gui time selection. As noted in an earlier post, I had the aircraft sounds start once after I used the gui debug reload of the autopilot config file. openal-0.0.9-0.15.20060204cvs.fc9.i386 freealut-1.1.0-6.fc9.i386 FC10 up to date Alan Teeder wrote: I had no sound yesterday evening – but this was an aircraft that I am working on (JSBSim) and didn’t investigate why this should be suddenly so. As with Dave Perry I have an Athlon 32 bit machine. *From:* Scott Hamilton [mailto:scott.hamil...@popplanet.biz] *Sent:* 27 October 2009 11:14 *To:* FlightGear developers discussions *Subject:* Re: [Flightgear-devel] New Sound system committed On Tue, 2009-10-27 at 09:03 +0100, Erik Hofman wrote: dave perry wrote: I have been away on a trip for the last 5 days. Today, I did a make clean for both SimGear and fgfs before the compiles. I launched fgfs on the 32bit Athlon and at first, only ATC and no wind or aircraft sounds. It was night, so I used the gui to change the time to afternoon and what do you know, I have all the sounds. If I change back to clock time, only atc sound. This is repeatable. Anyone else who sees this? I tried it locally (with the latest CVS sources for SimGear and FlightGear) and I always get sound. Actually for some aircraft I've lost all sounds, changing time (to one of the presets or clock time) during flight made no difference; dhc8: engine - none flaps transit - none gear transit - none marker morse - none ATC - yes A380: engine - none wind - none tarmac rumble - none flaps transit - yes gear transit - none seat belt chime - yes marker morse - yes ATC - yes c172r engine - none wind - none flaps transit - none marker morse - none ATC - yes The command line args are; bin/fgfs --log-level=warn --enable-hud --enable-sound --airport=YSSY --runway=34L --aircraft=c172r --enable-real-weather-fetch --timeofday=morning --prop:/sim/sound/enabled=true I also noticed that if I change the main volume in the sound dialog, it also reduces the ATC volume, I think the UI assumes they are separate volume controls? Scott. Erik -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] New Sound system committed
Erik Hofman wrote: It would be nice to know who of you who have problems run on 64-bit and if any one with these problems (sounds not playing) actually runs in 32-bit. Erik -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel I have a 64bit Intel core2 duo notebook FC10 that the sound mostly works (no dopler). I have a 32bit Athlon XP 3200+ FC10 that has no sound other than ATC. -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] New Sound system committed
dave perry wrote: Erik Hofman wrote: It would be nice to know who of you who have problems run on 64-bit and if any one with these problems (sounds not playing) actually runs in 32-bit. Erik -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel I have a 64bit Intel core2 duo notebook FC10 that the sound mostly works (no dopler). I have a 32bit Athlon XP 3200+ FC10 that has no sound other than ATC. Hi Erik, I have been away on a trip for the last 5 days. Today, I did a make clean for both SimGear and fgfs before the compiles. I launched fgfs on the 32bit Athlon and at first, only ATC and no wind or aircraft sounds. It was night, so I used the gui to change the time to afternoon and what do you know, I have all the sounds. If I change back to clock time, only atc sound. This is repeatable. Dave P. -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] New Sound system committed
Erik Hofman wrote: dave perry wrote: dave perry wrote: With an update this morning from cvs, I still only hear ATC and that with frequency distortion. Did I miss a required library change? I have openal-0.0.9-0.15.20060204cvs.fc9.i386 and freealut-1.1.0-6.fc9.i386 with fc10. The above is on my desktop (Athlon XP 3200+, current FC10, AC'97 Chip ALC650. I also have a notebook with an Intel core2 duo running FC10 64 bit. On this system I get all the AC sounds but still distorted ATC. I am using the following update script on both systems. Sorry I have been busy fixing technical bugs lately. Functional bugs are for a later date. So it's not your setup thats the problem. Erik Hi Erik, I was tweaking an autopilot config file today on my desktop (which has not had any aircraft sounds). After about an hour of flight reloading the autopilot config many times after edits, suddenly I have aircraft sounds after one of the autopilot reloads. It remained on until I reloaded fgfs. Last update from cvs yesterday evening. Dave P. -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] New Sound system committed
James Sleeman wrote: On 20/10/09 00:07, James Sleeman wrote: On 19/10/09 23:42, Erik Hofman wrote: Ok I think I've ironed out most of the bugs. I hope also the one that James reported but I don't hold my breath for it just yet. So far so good, compiles and runs, and produces sound. Will try a short flight and see if any problems crop up. Seems to be working ok, a bit, umm, stuttery, sort of, particularly background wind, seemed to switch left-right a bit, but those problems might just be me, maybe even just an illusion. With an update this morning from cvs, I still only hear ATC and that with frequency distortion. Did I miss a required library change? I have openal-0.0.9-0.15.20060204cvs.fc9.i386 and freealut-1.1.0-6.fc9.i386 with fc10. -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] New Sound system committed
dave perry wrote: With an update this morning from cvs, I still only hear ATC and that with frequency distortion. Did I miss a required library change? I have openal-0.0.9-0.15.20060204cvs.fc9.i386 and freealut-1.1.0-6.fc9.i386 with fc10. The above is on my desktop (Athlon XP 3200+, current FC10, AC'97 Chip ALC650. I also have a notebook with an Intel core2 duo running FC10 64 bit. On this system I get all the AC sounds but still distorted ATC. I am using the following update script on both systems. echo This script will update source from cvs and then compile and install echo (1) the SimGear library, echo (2) FlightGear source files, and echo (3) finally just update the FlightGear/data folder. echo echo Updating the SimGear library source cd ~ cd source-osg/SimGear cvs up -dP sh autogen.sh ./configure CFLAGS=-march=native CXXFLAGS=-march=native --with-jpeg-factory echo echo Compiling SimGear ** make echo echo Installing the SimGear library * sudo make install echo echo Updating FlightGear source * cd ../source-fgfs cvs up -dP sh autogen.sh ./configure CFLAGS=-march=native CXXFLAGS=-march=native --prefix=$FG_ROOT echo echo Compiling FlightGear *** make echo echo Installing FilghtGear executables ** sudo make install echo echo Updating the Base package data * cd $FG_ROOT cvs up -dP echo cd ~ echo Update COMPLETE! Regards, Dave P. -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] SimGear compile error
syd adams wrote: This works for me ... ./configure CFLAGS= -march=athlon CXXFLAGS=-march=athlon --with-jpeg-factory ... once I remembered to do a make clean before make :) Thanks Syd, The make clean turned out to be the problem. This works for me ... ./configure CFLAGS=-march=native CXXFLAGS=-march=native --with-jpeg-factory using gcc-4.3.2-7.i386. -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] SimGear compile error
Anders Gidenstam wrote: On Sat, 10 Oct 2009, dave perry wrote: I have --build=i686 as a switch to configure. Where do I supply -march=? You set CXXFLAGS and CFLAGS (but the latter might not be needed). My configure line starts with: configure CFLAGS=-O2 -g -march=core2 -mfpmath=sse -Wall CXXFLAGS=-O2 -g -pipe -march=core2 -mfpmath=sse -Wall Thanks for the reply. I tried -march=i686 (in place of core2) as follows: ./configure CFLAGS=-O2 -g -march=athalon -mfpmath=sse -Wall CXXFLAGS=-O2 -g -pipe -march=athalon -mfpmath=sse -Wall --with-jpeg-factory and I still get the same compile errors. I have an AMD Athalon XP 3200+ cpu. Using athalon in place of i686 will cause the configure to abort. Is the change to SGAtomic.cxx that causes this break really necessary? Dave P. -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Altimeter setting does not produce correct field altitude
With current cvs update on my notebook, I am not getting the correct field elevation when I set the altimeter to match the real weather altimeter setting. It is off by 160 feet today at KLMO (field elevation 5052). With my desktop which was last updated from cvs about 10/3, it is very nearly correct even with radically high or low pressures. -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] SimGear compile error
With today's SimGear CVS, I am getting the following compile error Making all in props make[3]: Entering directory `/home/dad/source-osg/SimGear/simgear/props' g++ -g -O2 -D_REENTRANT -lOpenThreads -o props_test props_test.o libsgprops.a ../../simgear/xml/libsgxml.a ../../simgear/misc/libsgmisc.a ../../simgear/debug/libsgdebug.a ../../simgear/structure/libsgstructure.a props_test.o: In function `SGAtomic::operator--()': /home/dad/source-osg/SimGear/simgear/props/../../simgear/structure/SGAtomic.hxx:60: undefined reference to `__sync_sub_and_fetch_4' I am running Fedora 10 with gcc-4.3.2-7.i386. Regards, Dave P. -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] nontrivial external situations
James Turner wrote: On 15 Sep 2009, at 22:59, Thomas Betka wrote: But each LOC on an airfield has it's own frequency This is where the problems start: http://www.nats-uk.ead-it.com/aip/current/ad/EGPH/EG_AD_2_EGPH_2-1_en.pdf IVG and ITH share the same frequency - 108.9Mhz, and there's some circuit/switch/etc in the tower to activate one DME/LOC/GS trio or the other. Aside from that, I think everything you said was correct - as ever, I am not a pilot. The good news is, I think I've come up with a more consistent heuristic (to make Curt happy!) than the current one. This is not that uncommon. I flew IFR into Evensville, Indiana. There I-EVV (109.9) serving RWY 22 has the same frequency as I-DSO (109.9) serving RWY 4. -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Sport-model nav-radio (was Re: GS sensitivity)
James Turner wrote: It adds false LOC and GS signals, a better GS deviation computation, and LOC sensitivity based on the runway dimensions. The last part I'm not totally sure about - it makes localizers *very* sensitive - maybe I've adapted the code incorrectly, but this doc: http://www.allstar.fiu.edu/aerojava/ILS.htm indicates that at 10nm, the beam should be approx 1m (statue or nautical, I don't know) wide (with some variation for the runway aspect formula) - and it feels much, much narrower than that to me, though I haven't tested this rigourously. Comments awaited with interest :) As a sanity check, I used the rule of thumb of 0.5 deg per dot = CDI pegs at 2.5 deg each side and x/10 = sin(2.5 deg) . So LOC full width at 10 nm from LOC antenna = 20*sin(2.5 deg) = 0.872 . Since this is approximate (i.e. from the rule of thumb), the statement in the link /The width of the navigational beam may/ be varied from approximately 3º to 6º, with 5º being normal. It is adjusted to provide a track signal approximately 700 ft wide at the runway threshold. The width of the beam increases so that at 10 NM from the transmitter, the beam is approximately one mile wide. passes this sanity check. I have not flown the patch yet. In this patch, does the region of reliable signal satisfy Figure 1-1-6 on page 503 of the 2008 AIM? That figure shows valid signals for two over lapped archs. Arch 1: +\-35 deg out to 10 nm. Arch 2: +\- 10 deg out to 18 nm. In real IFR flying, you are always looking for two events as you are intercepting the LOC. #1: the needle to come live with a valid morris code for the LOC, and #2 the needle to break away from the case (i.e.un-peg). #1 occurs well before #2 and relates to the AIM figure 1-1-6. #2 relates to the beam width. It would be great to have both well modelled. Dave P -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] GS sensitivity - especially for aircraft / panel developers
James Turner wrote: On 9 Sep 2009, at 03:01, dave perry wrote: Sorry, I misunderstood you concerning the animation edits. I will be glad to help with the xml edits and testing. Getting rid of the spurious 5x for the glide scope and adding the clamps is a good idea and adding the normalized CDI and GS could make the animators job easier. I will start by changing the vor.xml and vor2.xml in Instruments-3D that are used in the pa24 and pa28 and perhaps several other AC. I've already changed various aircraft locally, for testing: - the generic 2D and 3D instruments - the Seneca, B1900d, 747-400, C172P and Aerostar - the Primus-1000 suite I don't claim to have done this 100% correctly yet - especially, I need to convince myself the that GS-ARM modes of the various autopilots (eg, the KAP-140 in the default C172) are behaving correctly, since this is generally implemented as Nasal scripts testing the GS needle deflection. One area I do need help with is the autopilot PID laws: eg, here's the relevant chunk for the B1900d: pid-controller nameGlideslop Hold/name input propinstrumentation/nav/gs-needle-deflection-norm/prop /input reference value0/value /reference output propautopilot/settings/target-pitch-deg/prop /output config Kp-1.5/Kp beta1.0/beta alpha0.1/alpha gamma0.0/gamma Ti10.0/Ti Td0.0/Td u_min value-10/value /u_min u_max value5/value /u_max /config /pid-controller Since I've switched the input to be the normalised prop, we've gone from a unclamped input (swinging from sometimes -60 to 60!) to one which is much 'smaller' in magnitude and clamped to [-1 .. 1]. I *guess* the fix will be to increase the gain on the PID, otherwise GS hold will tend to lag, but that's about the total of my knowledge of tweaking the PIDs. I have updated and tested the vor.xml, vor2.xml in Instruments-3D/vor as well as the century3.nas in Aircraft/Generic and the corresponding PID controllers. I will do the same for the AltimaticIIIC used in the SenecaII as I wrote the CenturyIII and AltimaticIIIC nasal and PID's which are very similar to the CenturyIII. I think we will have to change all the nasal GS arm entries. I also am familiar with the kap140 nasal, so I will update that also. I have found that the parameters in the PID controllers need to be optimised for each aircraft as the plant changes with a change in flight model optimisation. I am not using the normalized property. This made increasing the proportional gain kp by 5x a very good starting point for re-optimization. I will re-optimize the Cessna 172 PID file. None of the above has been committed to CVS. Shall I send the diffs to you James for committing. Dave P -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] GS sensitivity - especially for aircraft / panel developers
James Turner wrote: - secondly, I'm changing (or will) the glideslope deviation to be 'correct' degrees: [-0.7 .. 0.7], i.e removing the spurious 5x scalar that has somehow crept in, and fixing many clients which assumed the range was [-10 .. 10], or something else again. This is in keeping with your flight instructor, I believe. I just looked at the latest navradio.cxx in CVS. You added the normalised _gsNeedleDeflectionNorm but did not remove the 5x from _gsNeedleDeflection. This is to avoid breaking the clients that have not been updated, right? Am I safe to assume that once most of the client updates are done, the 5x will be removed. That is, is it OK to do the nas and xml updates and optimisation using degrees and not the normalized values. Dave P -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] GS sensitivity - especially for aircraft / panel developers
Hi James, Your note below caused me to ask if the LOC needle deflection is scaled differently than the VOR needle deflection in navradio.cxx. It is and the comment that it is 4x more sensitive is correct according to notes from Instrument Ground School. From a pilot point of view, what we need to achieve is 2 deg per dot for VOR and 1/2 deg per dot for the LOC and that should remain the responsibility of the AC and instrument modeler doing the animation. Also, the same ground school instructor indicated that the actual instrument deflection range might vary as long as the deg per dot target was achieved. The vor.xml and the vor2.xml in Instruments-3D already are correct to the above description assuming degrees for units and the 4X LOC scaling now in navradio.cxx. I don't think it is a good idea to go to a normalized value in a blanket edit of other's instruments as the needle deflection in the animation SHOULD be scaled to achieve the 2 deg per dot for VOR and the 1/2 degree per dot for the LOC. If the navradio.cxx maintains the 4x factor and clamps the heading-needle-deflection to +/- 10 deg, the modeler can use the same scalar for both the VOR and LOC. This scalar will likely vary from instrument to instrument to get the propper dot performance. +/- 0.7 is correct for the glide slope and again the scaling in the instrument will vary depending on the display. Dave P James Turner wrote: As part of cleaning-up the nav-radio code, I need to make a painful change: fixing the confusion over GS maximum needle deflection. I'm aware that there's problems with the radio reception model, but I'm not going to attempt to address that at all - what I need to fix in the short term is a much 'simpler' problem - the confusion over the range of /instrumentation/nav/gs-needle-deflection. Some aircraft (eg, the default C172, and the Primus 1000 suite) are assuming the range is -10 to +10 degrees (matching the CDI deflection) - others assume 3.5 degrees (1), or other things again. The Connie is scaling the property by 1.4, and clamping to +/- 6, for example - which just about makes sense given the actual range, but no sense at all if the range is +/-10. Hence, this is not about 'fixing' the code in navradio, more picking a single definition and then fixing panels to follow that definition. Here is what I'm going to do: - change gs-needle-deflection to report the GS deviation *in degrees* - add a gs-needle-deflection-norm property, reporting the deflection as the range +/- 1.0 (I'll probably do that for the CDI as well). 1.0 will be on the peg, 0.0 will be centred - no surprises here, I hope. - clamp the GS deviation to +/- 0.7 degrees in the nav-radio code (as we clamp the CDI deflection to +/-10 degrees). This is significant, because many panels currently work due to the value *not* being clamped to any range. I.e there will be a peg at the sim level, not just a a peg defined at the animation / panel level. - update ALL the references to the property in the data directory (that's 273 references, according to 'grep'!) to be consistent with this. For most cases, I'll probably switch to using the normalised property, to avoid any future confusion (I hope) - and to avoid many scalars in XML files based upon the 0.7-degree limit. The major benefit of all this, apart from increased sanity in the code, will be much more precise GS reporting in many aircraft, I hope. This may lead to end- users reporting that flying glide-slopes has become 'harder' in some aircraft (such as the C172) since the sensitivity will have increased by a factor of three. If anyone has a major objection to this, please let me know. If anyone wants to help with fixing up panels, then *definitely* let me know. Regards, James (1) - 3.5 degrees is the value you'd arrive at by examining the source code - there is the 'magic 5' multiplier that scales the actual deviation, +/- 0.7 degrees, by 5, in the nav radio code. As far as I know (and based on comments in the code), no one is really sure why the multiplier is present. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on
Re: [Flightgear-devel] GS sensitivity - especially for aircraft / panel developers
James Turner wrote: - fourthly, and most importantly, I'm not doing a blanket edit - I wish I could! I'm going to have to go through each aircraft, make the changes, and then test that aircraft. I'm sure I'l miss some things, but I still believe it's worth it to kill off the dreaded 5x multiplier, and fix all the aircraft who've been assuming the range is [-10..10] - or anything else. Hopefully that's clearer. James Sorry, I misunderstood you concerning the animation edits. I will be glad to help with the xml edits and testing. Getting rid of the spurious 5x for the glide scope and adding the clamps is a good idea and adding the normalized CDI and GS could make the animators job easier. I will start by changing the vor.xml and vor2.xml in Instruments-3D that are used in the pa24 and pa28 and perhaps several other AC. Dave P -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navradio
James Turner wrote: On 6 Sep 2009, at 22:50, dave perry wrote: The height is correct. It looks like every other call of FGNavRadio::updateWithPower gets the wrong value for nav_elev. Hope this helps find the bug. I was wrong about the height being correct. Thought it might be a scope problem for nav_elev so I tried moving the declaration back to navradio.hxx and moving the assignment of a value back into the search. The search is never called??? I'll also keep looking at this and let you know if I find the problem. Thanks Dave, this is almost certainly my fault - and indeed all the airports I tested at are very close to sea level elevation. Very odd that it's alternating from a valid value to zero, I'll dig into the code today. Thanks again, James -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] navradio
I updated SimGear, fgfs source and data yesterday for both my desktop and notebook. The glide slope is now broken. The angle seems correct but it now acts as if the ILS is always from 0 ft MSL. I tried the rw 23 ILS at KBTL with field elevation of 952 ft, rw 23 at KBJC with field elevation of 5670 ft and rw 28 at KSFO with field elevation near 0. At KSFO, all seems correct. At KBTL, I flew outbound at 1250 ft MSL and the GS crossed center at the OM. That was 950 ft too low, or about the field elevation. Rockey Mountain Metro is too high to make the same check. I put cout nav_elev = nav_elev endl; after line 361 and un commented cout dist = x height = y endl; after line 594 in navradio.cxx. This produced at KBTL and the pa24-250 the following in the log window: creating 3D noise texture... DONE KI266 dme indicator #0 initialized Nasal Electrical System Initialized power up nav_elev = 0 nav_elev = 930 nav_elev = 0 nav_elev = 930 nav_elev = 0 nav_elev = 930 nav_elev = 0 nav_elev = 930 nav_elev = 0 nav_elev = 930 nav_elev = 0 dist = 553.906 height = 281.795 nav_elev = 930 nav_elev = 0 dist = 553.906 height = 281.795 nav_elev = 930 nav_elev = 0 dist = 553.906 height = 281.795 nav_elev = 930 nav_elev = 0 The height is correct. It looks like every other call of FGNavRadio::updateWithPower gets the wrong value for nav_elev. Hope this helps find the bug. Dave P -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Major oil leak in real N7764P
Hi all, One of the two co-owners with me of the real N7764P (pa24-250) had the connector of one of the oil cooler hoses break just before entering the pattern at KLMO, where we hangar. We check the oil in preflight to 9 quarts and he had just under 6 quarts at shut down. The left side and belly were covered with dripping oil. He was returning from a camping trip in Yellowstone National Park. If the leak had occurred any time earlier on this leg, he would have been over the mountains. The mechanic that replaced the oil cooler said, 5 more minutes of flight would have exhausted the oil. We had a major overhaul done at Firewall Forward (Fort Collins KFNL) in December and January and they are paying for the repair under warranty. They and the mechanic that replaced the oil cooler agreed that the connector was not installed correctly as the hose put a lot of side load on the connector and vibration caused the fitting to crack and fail. Firewall Forward has implemented retraining of their mechanics to avoid similar problems on future overhauls. The AC is again flyable after replacing the oil cooler, this time with proper fittings and hose attachments. Regards, Dave P. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Till Busch's terrain shaders
Erik Hofman wrote: I wrote: Ahh, that line should read: float n=0.06 + dot(nvL, a); instead of: float n=0.06 + dot(nvL[0], a); Which brings the frame rate back to what it was :-/ Maybe it might be a good idea to specify which of the effects you want to turn on or not? Chances are I could care less about the landmass effect and would rather see the water effects active. I just turned on the effects and noted that we now see snow above about 8,000 MSL. That would be real for winter but not summer. Where is this set? Can the snow lever be set by the season or date? Exciting improvements already! Dave P. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] startup.nas
Torsten Dreyer wrote: Just commited a hack for envrionment_ctrl.cxx. It now waits for the first METAR to arrive before proceeding with the initialization sequence. This prevents the nasal-dir-initialized signal being fired before a METAR has arrived. I more and more like the idea of removing startup.nas and implenting the automatic runway selection depending on METAR wind directly in the METAR-subsystem, probably enabled by a property. I didn't mark the hack as temporary because temporary solutions usually last longest ;-) For now, the message from startup.nas should have disappeared and automatic runway selection based on METAR wind should work again. Torsten Hi Torsten, I still get the message from startup.nas at some airports. Here is an example at KLMO, home base for the real N7764P. [...@dadsoffice data]$ ./bin/fgfs --airport=KLMO --aircraft=pa24-250 --fg-scenery=/home/dad/scenery --enable-real-weather-fetch FGMultiplayMgr - No receiver port, Multiplayermode disabled Nasal runtime error: nil used in numeric context at /usr/local/games/FlightGear/data/Nasal/startup.nas, line 12 called from: /usr/local/games/FlightGear/data/Nasal/startup.nas, line 29 KI266 dme indicator #0 initialized Nasal Electrical System Initialized fgfs and SimGear updated from cvs yesterday. Regards, Dave P. -- ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] osg devel and Tims changes
Tim Moore wrote: dave perry wrote: I am getting segmentation fault after updating osg trunk from svn, SimGear from cvs, and fgfs source from cvs. I also tried compiling against osg-2.8.2-rc4. I still get a segmentation fault right after loading aircraft completes. Can you send me a backtrace? Thanks, Tim Problem solved. I had not successfully updated $FG_ROOT and did not notice this failure since my update script appeared to end successfully. A fresh check out of data fixed the problem. Thanks. Dave P. -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] osg devel and Tims changes
Tim Moore wrote: Mathias Fröhlich wrote: Hi, With yesterdays checkin from Tim we need a more or less recent osg version to build flightgear. Tim promised to provide come conditional code to work around that. But I would suggest to just have a somehow recent osg version as a requirement for current simgear/flightgear development. Can we agree on that or shall we still require sg/fg built on osg-2.8? Tim, what is the actual osg development release we need to have? I just checked in changes that re-enable us to compile using osg 2.8. I tested against 2.8.2-rc4, but it should work with 2.8.0 and above. Soon there may be features that require a more recent OSG to work, but I agree that it would be nice to be able to run with 2.8. Tim -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel I am getting segmentation fault after updating osg trunk from svn, SimGear from cvs, and fgfs source from cvs. I also tried compiling against osg-2.8.2-rc4. I still get a segmentation fault right after loading aircraft completes. Dave P. -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] YASim EGT doesn't change?
Victhor wrote: I've noticed that EGT on YASim piston engines won't change. How can I set the mixture that way? :) At least the engine could respond to a mixture change, like losing power, but they don't. I remember they would respond to mixture changes, did some YASim update break it? I googled YASim but I couldn't find any site related to it. -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/blackberry ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel Try either the pa24-250 or the pa28-161. For both of these ac I used nasal to model a number of aircraft specific realism factors. You can examine the file action-sim.nas for both to see how this was done. These models target a realistic response to the mixture setting which does eventually drop the rpm and fuel flow. I used the POH to target the peak temp and peak fuel flow in these models. YASim supplies the rpm and the fuel flow used in these models. The new egt value is low-pass filtered and then set to the new property: setprop(/engines/engine[0]/egt-degf-fix, egt_lowpass.filter(egt)); I ignore the YASim value for egt. Regards, Dave Perry -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/blackberry ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] pa24 and seneca II autopilots broken
Torsten Dreyer wrote: I just updated SimGear, fgfs source, and data from cvs on my FC10 notebook. The Century IIB, Century III, and Altimatic autopilot hot spots don't show with ctrl-C and they don't work. I checked to see if any of their files in Aircraft/Instruments-3D/ had been changed. They had not. So I am assuming some other recent change has broken them. The digital OAT in the pa24 is also broken. What all these share is panel xml files that are relative to a model that is then loaded in another model xml. I could fix the autopilot animations by switching to pick hot spots. Fixing the OAT is not that simple as the OAT panel uses layers to write the digital temps. Any recent changes come to mind that might be the cause? I can confirm this bug for the SenecaII. Nothing has changed for the model for a while, and I'd expect it to work as before - which is doesn't. I'm short on spare time right now but will look into it before weekend. Torsten BTW. The panel hotspots should have been replaced by picks anyway - sorry for my lazyness... Hi Torsten, To avoid duplication of effort, I plan today to change the Century IIB, the Century III, and the Altimatic to use picks. I will send you the patches so you can check them out before committing them to cvs. Regards, Dave P. -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] pa24 and seneca II autopilots broken
I just updated SimGear, fgfs source, and data from cvs on my FC10 notebook. The Century IIB, Century III, and Altimatic autopilot hot spots don't show with ctrl-C and they don't work. I checked to see if any of their files in Aircraft/Instruments-3D/ had been changed. They had not. So I am assuming some other recent change has broken them. The digital OAT in the pa24 is also broken. What all these share is panel xml files that are relative to a model that is then loaded in another model xml. I could fix the autopilot animations by switching to pick hot spots. Fixing the OAT is not that simple as the OAT panel uses layers to write the digital temps. Any recent changes come to mind that might be the cause? Regards, Dave P. -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Progress report on the infamous error in TriangleIntersect NAN Problem
Heiko Schulz wrote: I think the pa24-250 is another user of this. Does this aircrafts also cause this NaN-errors? Hi Heiko, The pa24-250 uses Aircraft/Instruments-3d/comp/comp.xml. Regards, Dave P. -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] SimGear --build= options?
I am trying to build cvs fgfs on a new notebook running Fedora10 x86_64. I am getting a configure error w/o --build specified. What should I specifiy for --build=?. The processors - Intel(R) Core(tm)2 Duo processor T5800. - Dave P. -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] SimGear --build= options?
dave perry wrote: I am trying to build cvs fgfs on a new notebook running Fedora10 x86_64. I am getting a configure error w/o --build specified. What should I specifiy for --build=?. The processors - Intel(R) Core(tm)2 Duo processor T5800. - Dave P. -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel Sorry, I did not say in the body of the note that the configure error occurs when building SimGear. -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] SimGear --build= options?
Csaba Halász wrote: On Tue, Jan 27, 2009 at 7:10 PM, dave perry skida...@mindspring.com wrote: Sorry, I did not say in the body of the note that the configure error occurs when building SimGear. configure should be able to figure out --build by itself. Look into config.log and the configure script itself to check why it fails. Also, the verbatim error message would help. I had copied the SimGear from a non 64 bit machine. A clean SimGear cvs co solved the issue. Thanks, Dave -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
