[Flightgear-devel] Detailed Simulation of Wing Forces
Hi, We're working on a project to feed back information about airflow on a wing to the pilots skin (tactile feedback). Our project web page is here-- http://www.d.umn.edu/~cprince/PubRes/FbF/ Right now, we're pretty early in progress and working with simulated wings. I've started using XPlane to provide a simulation of wing airflow sensors-- by tapping into its simulation of lifting forces on the aircraft wing. Can Flight Gear do something similar? Can I get an array of data on lifting forces over the wing back from the simulator, in real time? (I've looked through the flight gear manual some, and through the flight model docs some and can't see what I'm looking for). Thanks! Chris. -- ___ 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. Yep - me, too for KLMO. I'll look into soon. Torsten -- ___ 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
