Re: [Flightgear-devel] ? cockpit lighting ?
Jim Wilson wrote:
A while back I added material animation for changing OpenGL emissive material
properties
on the fly, so that a dimmer could be added to the P51D Cockpit.
Subsequently it was rewritten by Melchior IIRC.
Most of the aircraft doesn't actually have this configured, but if you are
interested you
could study the P51D configuration and perhaps add similar support to the
cessnas. The
property names won't have effect except for the aircraft that have been
configured to
modify emissive properties on certain cockpit objects depending on that
property-name's
value.
See also this attached file. It's for the ch53e, but I don't think it's
in CVS yet.
Josh
# The point of this file is to create a bunch of properties to drive the
emission
# of various objects in the cockpit by the material animation. It takes the norm
# values for the three light switches and mixes them with each other and (if
# defined) RGB values for those lights. These should be put in:
# controls/lighting/dome/color/red
# ...
# controls/lighting/instruments/color/blue
#
# The are affected by all three lights, the panel by the panel and dome
# lights, and the dome lights by nothing else. There are weighted values
defining how much
# one light switch affects each group of objects.
#
# Values are output to:
# controls/lighting/dome/emission/red
# ...
# controls/lighting/instruments/emission/blue
#
# copyright 2006 Josh Babcock jbabcock (at) atlantech (dot) net
#
# TODO
# Implement a night vision mode system like in the ch53e
# Make a system with a materials.showdialog() to make it easier to play with
colors.
# TODO, get this from a property
shadowFactor = 0.7;
# Light color settings (input)
panelRed = '';
panelGreen = '';
panelBlue = '';
panelNorm = '';
instrumentsRed = '';
instrumentsGreen = '';
instrumentsBlue = '';
instrumentsNorm = '';
domeRed = '';
domeGreen = '';
domeBlue = '';
domeNorm = '';
# Actual emissive values for these models (output)
panelEmisRed = '';
panelEmisGreen = '';
panelEmisBlue = '';
instrumentsEmisRed = '';
instrumentsEmisGreen = '';
instrumentsEmisBlue = '';
domeEmisRed = '';
domeEmisGreen = '';
domeEmisBlue = '';
# Utility functions
maxChannel = func (r, g, b) {
if ( r g ) {
max = r;
} else {
max = g;
}
if ( max b ) {
return(max);
} else {
return(b);
}
}
# Functions to figure out what the light will actually look like after all
three sources are mixed.
# The colors get averaged, the norm values get added with weights then clipped
to 1.
adjustDomeColor = func {
# Only the dome light shines on this stuff
var red = domeRed.getValue();
var green = domeGreen.getValue();
var blue = domeBlue.getValue();
var norm = domeNorm.getValue();
domeEmisRed.setDoubleValue(red * norm);
domeEmisGreen.setDoubleValue(green * norm);
domeEmisBlue.setDoubleValue(blue * norm);
}
adjustPanelColor = func {
# Mix multiple light sources
var red = ((
(panelRed.getValue() * panelNorm.getValue())
+ (domeRed.getValue() * domeNorm.getValue() )
)/2);
var green = ((
(panelGreen.getValue() * panelNorm.getValue())
+ (domeGreen.getValue() * domeNorm.getValue() )
)/2);
var blue = ((
(panelBlue.getValue() * panelNorm.getValue())
+ (domeBlue.getValue() * domeNorm.getValue() )
)/2);
# Normalize the color down if it is greater than one
maxColor = maxChannel(red, green, blue);
if (maxColor 1) {
red = red / maxColor;
green = green / maxColor;
blue = blue / maxColor;
}
panelEmisRed.setDoubleValue(red);
panelEmisGreen.setDoubleValue(green);
panelEmisBlue.setDoubleValue(blue);
}
adjustInstrumentColor = func {
# This time, we bias the instruments
var red = ((
(panelRed.getValue() * panelNorm.getValue() *
shadowFactor)
+ (domeRed.getValue()* domeNorm.getValue() *
shadowFactor)
+ (instrumentsRed.getValue() * instrumentsNorm.getValue()
)
)/3);
var green = ((
(panelGreen.getValue() * panelNorm.getValue() *
shadowFactor)
+ (domeGreen.getValue()* domeNorm.getValue() *
shadowFactor)
+ (instrumentsGreen.getValue() * instrumentsNorm.getValue()
)
)/3);
var blue = ((
(panelBlue.getValue() * panelNorm.getValue() *
shadowFactor)
+ (domeBlue.getValue()* domeNorm.getValue() *
shadowFactor)
+ (instrumentsBlue.getValue() * instrumentsNorm.getValue()
)
[Flightgear-devel] Yasim property tree for helicopter interfacing
Hi I need to record the control and the environmental (position, velocity, etc.) data for a helicopter for some research that I am busy with. I am very new ot FG, but it seems like I will be able to use the --generic option to grab the data from FG while flying it. The problem is that I cannot find the property tree entry for collective pitch and lateral and longitudinal cyclic pitch. I guess the tail rotor is defined in terms of the rudder. Can anyone help? Regarding the --generic option, the README.IO file states the following: Generic Communction: --generic=params With this option it is possible to output a pre-configured ASCII string using a predefined seperator. The configuration is defined in an XML file located in the Protocol directiory of the base package. params can be: serial port communication:serial,dir,hz,device,baud,protocol socket communication: socket,dir,hz,machine,port,style,protocol output to a file: file,dir,hz,filename,protocol But what is the name of the XML file? As I see it the filename option in the list file,dir,hz,filename,protocol refers to the output file and not the XML file containing the options. Francois - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] autopilot broken by recent osg branch fgfs update
On Tue 23 January 2007 03:27, Dave Perry wrote: I updated both SimGear, fgfs source, and data for the osg branch yesterday. After the compiles and installs with no errors, none of the autopilots are working. This includes the default autopilot from the gui as well as the kap140 (I am testing the new version from Roy Vegard Oveson). All were working before the cvs update. The kap140 files are from before the update. I tried the pa28-161 with the default autopilot and the symptoms were the same as with the kap140. With the PRE_OSG_Plib branch fgfs and the /data from the osg branch test, everything still works as expected. The altitude capture still works but the HDG, APR, and NAV do nothing except wing level. Turning the HI heading bug has no affect. The locks are updating in the property list. Are others seeing this behavior? Regards, Hello, Dave Yes i did noticed it , and said that bug on that mailing-list, but could not explain it http://sourceforge.net/mailarchive/message.php?msg_id=37840820 follow the thread Regards -- Gérard - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Yasim property tree for helicopter interfacing
--- Francois du Plessis wrote: Hi I need to record the control and the environmental (position, velocity, etc.) data for a helicopter for some research that I am busy with. I am very new ot FG, but it seems like I will be able to use the --generic option to grab the data from FG while flying it. The problem is that I cannot find the property tree entry for collective pitch and lateral and longitudinal cyclic pitch. I guess the tail rotor is defined in terms of the rudder. Can anyone help? Regarding the --generic option, the README.IO file states the following: Generic Communction: --generic=params With this option it is possible to output a pre-configured ASCII string using a predefined seperator. The configuration is defined in an XML file located in the Protocol directiory of the base package. params can be: serial port communication:serial,dir,hz,device,baud,protocol socket communication: socket,dir,hz,machine,port,style,protocol output to a file: file,dir,hz,filename,protocol But what is the name of the XML file? As I see it the filename option in the list file,dir,hz,filename,protocol refers to the output file and not the XML file containing the options. protocol is the name of the .xml file that contains your definitions in the $FG_ROOT/Protocol/ directory, without the .xml suffix. So --generic=file,out,10,flight.csv,helidata would output to the file flight.csv using the protocol definition in $FG_ROOT/Protocol/helidata.xml Hope this helps. -Stuart Francois - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel ___ The all-new Yahoo! Mail goes wherever you go - free your email address from your Internet provider. http://uk.docs.yahoo.com/nowyoucan.html - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] segfault in listener +- location-in-air
* John Denker -- Wednesday 17 January 2007:
On 01/17/2007 02:31 PM, Melchior FRANZ wrote:
The documentation doesn't say that. It says exactly:
Note that a listener can not remove itself, neither directly
nor indirectly.
Sorry, I missed that.
No, problem. And sorry for my rants. :-) On the official
doucmentation page under http://plausible.org/nasal/ listeners
aren't mentioned at all. But I always update the Nasal page
when I change some listener or signal thing:
http://wiki.flightgear.org/flightgear_wiki/index.php?title=Nasal_scripting_language
I have now also implemented what you suggested: self-removable
listeners:
var L = setlistener(/foo, func {
print(Hi. I'm a one-shot listener function!);
removelistener(L);
});
It turned out that I need some of them, too. No way to further
delay that. :-)
m.
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] autopilot broken by recent osg branch fgfsupdate
On Tuesday 23 January 2007 16:00, gh.robin wrote: On Tue 23 January 2007 03:27, Dave Perry wrote: I updated both SimGear, fgfs source, and data for the osg branch yesterday. After the compiles and installs with no errors, none of the autopilots are working. This includes the default autopilot from the gui as well as the kap140 (I am testing the new version from Roy Vegard Oveson). All were working before the cvs update. The kap140 files are from before the update. I tried the pa28-161 with the default autopilot and the symptoms were the same as with the kap140. With the PRE_OSG_Plib branch fgfs and the /data from the osg branch test, everything still works as expected. The altitude capture still works but the HDG, APR, and NAV do nothing except wing level. Turning the HI heading bug has no affect. The locks are updating in the property list. Are others seeing this behavior? Regards, Hello, Dave Yes i did noticed it , and said that bug on that mailing-list, but could not explain it http://sourceforge.net/mailarchive/message.php?msg_id=37840820 follow the thread Regards Just updated from CVS (HEAD (OSG)), and it seems to me that the autopilots are working. I tried the KAP140, and the generic in the pa28-161. Both worked fine in heading mode, and the followed the bug on the HSI. Gérard, are you still heaving trouble with the autopilot? If you are could you please tell us excactly what isn't working. Are the controllers not activated at all? Are they using non-existent input properties? Have you tried to activate the debugging of the controllers (writes debugging info to the console)? -- Roy Vegard Ovesen - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Yasim property tree for helicopter interfacing
Hi Francois, the parameters you are searching for are not in the property tree. But the control axes, which are linear to these: /controls/flight/rudder /controls/engines/engine[0]/throttle /controls/flight/elevator /controls/flight/aileron (additional some trim values are also added, but if you don't use them...) Maik Francois du Plessis schrieb am 23.01.2007 15:48: Hi I need to record the control and the environmental (position, velocity, etc.) data for a helicopter for some research that I am busy with. I am very new ot FG, but it seems like I will be able to use the --generic option to grab the data from FG while flying it. The problem is that I cannot find the property tree entry for collective pitch and lateral and longitudinal cyclic pitch. I guess the tail rotor is defined in terms of the rudder. Can anyone help? Regarding the --generic option, the README.IO file states the following: Generic Communction: --generic=params With this option it is possible to output a pre-configured ASCII string using a predefined seperator. The configuration is defined in an XML file located in the Protocol directiory of the base package. params can be: serial port communication:serial,dir,hz,device,baud,protocol socket communication: socket,dir,hz,machine,port,style,protocol output to a file: file,dir,hz,filename,protocol But what is the name of the XML file? As I see it the filename option in the list file,dir,hz,filename,protocol refers to the output file and not the XML file containing the options. Francois - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Yasim property tree for helicopterinterfacing
Maik OK, so the ones I am looking for is mapped to the ones you mention below? That makes sense in keeping the system generic. From what I read in the forums, it seems like the current helicopter model is not very accurate nor very realistic. I am busy developing an autotuning autopilot for a large RC helicopter. For this reason I need to fly the heli, capture the data and then train my controller on the data. FlightGear seemed like the obvious choice, but maybe it is not at the moment. Could you maybe advise me on the best option to follow for now that would result in the least effort to get what I want. It seems like either X-plane or MSFS is the way to go. Please advise if you can. On another point - one of my students is possibly going to do a FG implementation of the RC helicopter model developed by Gavrilets at MIT. If anyone already have part of that model implemented, it would be very helpful. Francois -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Maik Justus Sent: 23 January 2007 09:17 PM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] Yasim property tree for helicopterinterfacing Hi Francois, the parameters you are searching for are not in the property tree. But the control axes, which are linear to these: /controls/flight/rudder /controls/engines/engine[0]/throttle /controls/flight/elevator /controls/flight/aileron (additional some trim values are also added, but if you don't use them...) Maik Francois du Plessis schrieb am 23.01.2007 15:48: Hi I need to record the control and the environmental (position, velocity, etc.) data for a helicopter for some research that I am busy with. I am very new ot FG, but it seems like I will be able to use the --generic option to grab the data from FG while flying it. The problem is that I cannot find the property tree entry for collective pitch and lateral and longitudinal cyclic pitch. I guess the tail rotor is defined in terms of the rudder. Can anyone help? Regarding the --generic option, the README.IO file states the following: Generic Communction: --generic=params With this option it is possible to output a pre-configured ASCII string using a predefined seperator. The configuration is defined in an XML file located in the Protocol directiory of the base package. params can be: serial port communication:serial,dir,hz,device,baud,protocol socket communication: socket,dir,hz,machine,port,style,protocol output to a file: file,dir,hz,filename,protocol But what is the name of the XML file? As I see it the filename option in the list file,dir,hz,filename,protocol refers to the output file and not the XML file containing the options. Francois -- -- -- --- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEV DEV -- -- ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Yasim property tree for helicopterinterfacing
Hi Francois, Francois du Plessis schrieb am 23.01.2007 20:33: From what I read in the forums, it seems like the current helicopter model is not very accurate nor very realistic. Oh? Who said that? Probably he/they was/were writing about V0.9.10, but not about the actual cvs build (larger improvement last year). The bo105 should be highly realistic, the parameters of the other helicopters still need some tuning. Maik - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] VC8 OSG Build problems
Hi Stuart, I didn't compile fg-osg since a few weeks. Today i updated cvs (flightgear and simgear) and it compiles without error. Maik Stuart Buchanan schrieb am 22.01.2007 23:00: Hi All, I'm having problems building CVS on Visual C++.net 2005 (again). This was working quite happily a couple of weeks ago. I've been following the instructions here: http://www.oflebbe.de/oflebbe/FlightGear/index.html Specifically using the pre-built libraries: - 3rdparty-2006-11-25.zip - osg_ot_md.zip I'm now getting the following link errors: LINK : fatal error LNK1181: cannot open input file 'osgParticle.lib' Is this because the pre-built libraries are missing some part of OSG that the latest FG uses? Presumably I should move to OSG CVS, but my enthusiasm for another CVS dependency is minimal. Any suggestions, or should I stop being such a wus and get building? -Stuart ___ All New Yahoo! Mail – Tired of unwanted email come-ons? Let our SpamGuard protect you. http://uk.docs.yahoo.com/nowyoucan.html - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Yasim property tree for helicopterinterfacing
Well, good then. I will get these and give it a try. Do you build on Windows or on Linux? Can I use the bleeding edge tarball on the main FlightGear site to get these latest updates? Francois -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Maik Justus Sent: 23 January 2007 09:42 PM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] Yasim property tree for helicopterinterfacing Hi Francois, Francois du Plessis schrieb am 23.01.2007 20:33: From what I read in the forums, it seems like the current helicopter model is not very accurate nor very realistic. Oh? Who said that? Probably he/they was/were writing about V0.9.10, but not about the actual cvs build (larger improvement last year). The bo105 should be highly realistic, the parameters of the other helicopters still need some tuning. Maik - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Yasim property tree for helicopterinterfacing
Hi Francois, I am using Windows and compile it with mscv-express. But flightgear can be compiled under many different OS. Info about how to compile can be found in the wiki and in the documentation on www.flightgear.org. Maik Francois du Plessis schrieb am 23.01.2007 20:51: Well, good then. I will get these and give it a try. Do you build on Windows or on Linux? Can I use the bleeding edge tarball on the main FlightGear site to get these latest updates? Francois -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Maik Justus Sent: 23 January 2007 09:42 PM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] Yasim property tree for helicopterinterfacing Hi Francois, Francois du Plessis schrieb am 23.01.2007 20:33: From what I read in the forums, it seems like the current helicopter model is not very accurate nor very realistic. Oh? Who said that? Probably he/they was/were writing about V0.9.10, but not about the actual cvs build (larger improvement last year). The bo105 should be highly realistic, the parameters of the other helicopters still need some tuning. Maik - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Yasim property tree for helicopterinterfacing
I will then follow the Cygwin route of least resistance for the moment. Thanks for the guidance. Francois -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Maik Justus Sent: 23 January 2007 10:05 PM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] Yasim property tree for helicopterinterfacing Hi Francois, I am using Windows and compile it with mscv-express. But flightgear can be compiled under many different OS. Info about how to compile can be found in the wiki and in the documentation on www.flightgear.org. Maik Francois du Plessis schrieb am 23.01.2007 20:51: Well, good then. I will get these and give it a try. Do you build on Windows or on Linux? Can I use the bleeding edge tarball on the main FlightGear site to get these latest updates? Francois -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Maik Justus Sent: 23 January 2007 09:42 PM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] Yasim property tree for helicopterinterfacing Hi Francois, Francois du Plessis schrieb am 23.01.2007 20:33: From what I read in the forums, it seems like the current helicopter model is not very accurate nor very realistic. Oh? Who said that? Probably he/they was/were writing about V0.9.10, but not about the actual cvs build (larger improvement last year). The bo105 should be highly realistic, the parameters of the other helicopters still need some tuning. Maik -- --- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEV DEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- --- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEV DEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Yasim property tree for helicopterinterfacing
Better use msvc-express (Olaf Flebbe's Howto is linked in the wiki). Maik Francois du Plessis schrieb am 23.01.2007 21:13: I will then follow the Cygwin route of least resistance for the moment. Thanks for the guidance. Francois -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Maik Justus Sent: 23 January 2007 10:05 PM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] Yasim property tree for helicopterinterfacing Hi Francois, I am using Windows and compile it with mscv-express. But flightgear can be compiled under many different OS. Info about how to compile can be found in the wiki and in the documentation on www.flightgear.org. Maik Francois du Plessis schrieb am 23.01.2007 20:51: Well, good then. I will get these and give it a try. Do you build on Windows or on Linux? Can I use the bleeding edge tarball on the main FlightGear site to get these latest updates? Francois -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Maik Justus Sent: 23 January 2007 09:42 PM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] Yasim property tree for helicopterinterfacing Hi Francois, Francois du Plessis schrieb am 23.01.2007 20:33: From what I read in the forums, it seems like the current helicopter model is not very accurate nor very realistic. Oh? Who said that? Probably he/they was/were writing about V0.9.10, but not about the actual cvs build (larger improvement last year). The bo105 should be highly realistic, the parameters of the other helicopters still need some tuning. Maik -- --- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEV DEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- --- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEV DEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Development Docs
Hi all. I'm new in FGS. Does anybody know where can I find a good documentation about FG development. Thanks in advance Thiago Drechsel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] autopilot broken by recent osg branch fgfsupdate
On Tue 23 January 2007 18:48, Roy Vegard Ovesen wrote:
On Tuesday 23 January 2007 16:00, gh.robin wrote:
On Tue 23 January 2007 03:27, Dave Perry wrote:
I updated both SimGear, fgfs source, and data for the osg branch
yesterday. After the compiles and installs with no errors, none of the
autopilots are working. This includes the default autopilot from the
gui as well as the kap140 (I am testing the new version from Roy Vegard
Oveson). All were working before the cvs update. The kap140 files are
from before the update.
I tried the pa28-161 with the default autopilot and the symptoms were
the same as with the kap140.
With the PRE_OSG_Plib branch fgfs and the /data from the osg branch
test, everything still works as expected.
The altitude capture still works but the HDG, APR, and NAV do nothing
except wing level. Turning the HI heading bug has no affect. The
locks are updating in the property list.
Are others seeing this behavior?
Regards,
Just updated from CVS (HEAD (OSG)), and it seems to me that the autopilots
are working. I tried the KAP140, and the generic in the pa28-161. Both
worked fine in heading mode, and the followed the bug on the HSI.
Gérard, are you still heaving trouble with the autopilot? If you are could
you please tell us excactly what isn't working. Are the controllers not
activated at all? Are they using non-existent input properties? Have you
tried to activate the debugging of the controllers (writes debugging info
to the console)?
Hello Roy,
I just updated from that CVS (HEAD (OSG)), and i confirm getting the same
trouble than Dave , (which is a positive progress to mebecause i have
again the autopilot Altitude working).
I had a talk before with with Dave regarding ---kap140 bug+fix--- topics
where i explained
--- When the hdg bug is moved the AC seems to obey to that order but the AC
is not auto corrected for the right heading and start to turn permanently
---
The properties are set with the right values on the /autopilot . Heading and
lock are right
the heading-bug-error-deg is updated in real time
But the auto correction is not done.
The most representative test for that bug is when i try to use the WP
function i get the right value on the properties, but the aircraft never goes
toward the right heading.
I don't know how to activate debugging of the controllers, and
Debugging Options: --log-level={bulk,debug,info,warn,alert
are useless
Regards
--
Gérard
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Fw:nbsp;Developmentnb sp;Docs
wiki.flightgear.org -- -- From:Thiago Drechsel [EMAIL PROTECTED] Date:2007-01-24 07:30:14 To:FlightGear developers discussions Cc:(无) Subject:[Flightgear-devel] Development Docs Hi all. I'm new in FGS. Does anybody know where can I find a good documentation about FG development. Thanks in advance Thiago Drechsel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] autopilot broken by recent osg branch fgfsupdate
On Tue, 2007-01-23 at 18:48 +0100, Roy Vegard Ovesen wrote:
Just updated from CVS (HEAD (OSG)), and it seems to me that the
autopilots are
working. I tried the KAP140, and the generic in the pa28-161. Both
worked
fine in heading mode, and the followed the bug on the HSI.
I just did a cvs update -dP for both simgear and the fgfs source (osg
branch) and the new version kap140 works with the one quirk; to get
the heading bug to work requires going to the debug gui and reloading
the autopilot config.
Here is the version with the differential approximation for altFt. I
think this is exactly what you asked for in
What I'm asking for is an equation to convert from pressure altitude
to ASL
altitude. Something like
ASL_alt = f(pressure_alt, ref_pressure)
1) Add the partial derivative function before altAlert:
hPartial = func {
p0 = arg[1];# Units of p0 must match units of delta p
p = arg[0]; # Units of p must match units of delta p
t0 = 288.15;# [K]
LR = -0.0065;# [K/m]
g = -9.80665;# [m/s²]
Rd = 287.05307; # [J/kg K]
gamma = (Rd*LR)/g;
z = -(t0/LR)*gamma*pow((p/p0),gamma)/p0;
return z;
}
2) Replace the computation of altFt in altAlert with
pressureAltitude = getprop(encoder, pressure-alt-ft);
hPartBaro = hPartial(baroSettingInhg, 29.92) / 0.3048006;
# print(hPartBaro = ,hPartBaro);
altFt = pressureAltitude + hPartBaro * (baroSettingInhg - 29.92);
Notice:
1) altFt = f(pressure_alt, baro_setting)
2) requires only one call of pow (i.e. exp and ln)
I will send you the working kap140.nas with these changes off-list. It
is working well here.
Regards,
--
Dave Perry
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
