Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: FlightGear/src/GUI new_gui.cxx, 1.51, 1.52
Melchior Franz wrote: Update of /var/cvs/FlightGear-0.9/FlightGear/src/GUI In directory baron:/tmp/cvs-serv25323 Modified Files: new_gui.cxx Log Message: add signal on GUI reinit; needed for reloading Nasal loaded XML dialogs Unfortunately this fails on FreeBSD with current OSGG CVS: gmake[2]: Entering directory `/usr/local/src/FlightGear/src/Model' [...] g++ -g -O3 -march=pentiumpro -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/opt/gnu/include -I/usr/local/include -I/opt/FlightGear/include -I/opt/OSG/include -I/usr/X11R6/include -g -O2 -I/opt/FlightGear -D_REENTRANT -c -o model_panel.o model_panel.cxx model_panel.cxx: In function `osg::Node* load_panel(SGPropertyNode*)': model_panel.cxx:28: error: cannot allocate an object of type `FGPanelNode' model_panel.cxx:28: error: because the following virtual functions are abstract: /opt/OSG/include/osg/Drawable:425: error: virtual void osg::Drawable::drawImplementation(osg::RenderInfo) const gmake[2]: *** [model_panel.o] Fehler 1 Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- - 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] [Flightgear-cvslogs] CVS: FlightGear/src/GUI
Martin Spott wrote: Melchior Franz wrote: Update of /var/cvs/FlightGear-0.9/FlightGear/src/GUI In directory baron:/tmp/cvs-serv25323 Modified Files: new_gui.cxx Log Message: add signal on GUI reinit; needed for reloading Nasal loaded XML dialogs Unfortunately this fails on FreeBSD with current OSGG CVS: Ah, wait, I might have mixed up different things - I simply don't know why. Compiling definitely worked after reverting your change but this effect didn't prove to be reproducable ?!?? Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- - 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] Generic aar.nas/AI properties
Hello all! First off, when linking the B-2(yasim) to the generic aar.nas I experienced a constant switching of the engines/out-of-fuel property which unsurprisingly results in low thrust. Could this be related to the broken fuel-consumed-lbs property (of yasim?) that is jumping around close to zero? Secondly, is live manipulating of AI model properties possible at the moment? In the flightgear property browser I found orientation/true-heading-deg and some radar properties but I think it would come in handy to be able to manipulate speed, altitude and waypoints (and maybe more Wink) for an AI model. So it would be possible to spawn an AI tanker at a desired location or be able to launch testbeds or rockets from a plane and direct it to a desired location. I am using an end feb build of osg/fg. Maybe I missed something, thanks in advance, markus - 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] Generic aar.nas/AI properties
* Markus Zojer -- Thursday 29 March 2007: First off, when linking the B-2(yasim) to the generic aar.nas I experienced a constant switching of the engines/out-of-fuel property which unsurprisingly results in low thrust. Fixed. This was a bug in aar.nas, that was triggered by the B-2 occasionally not consuming *any* fuel between two loop runs, which seems to be a bug elsewhere ... 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
[Flightgear-devel] nasal development news
I have today added/finished two simple features that are
interesting for development of Nasal code.
(A) Help-Nasal Console
This dialog supports now several tabs, of which each can hold
separate Nasal code snippets, all of which are saved on exit
and reloaded next time. This is useful for little tests, or for
executing code for which writing a key binding is just too much
work, such as props.dump(props.globals). It's easy to add more
tabs (= radio buttons). One just needs to add more code nodes
to autosave.xml.
(B) (re)loading Nasal modules at runtime
There's a new function debug.load_xml_nasal(), which loads an XML
file with embedded Nasal into a nasal namespace. For syntax
coloring reasons one may want to use a *.nas extension for this file.
Example:
$ cat $FG_ROOT/Aircraft/foo/test.nas
PropertyListscript![CDATA[
# --
print(hi!);
var hello = func { print(I'm the test.hello() function) }
# --
]]/script/PropertyList
$
One can now edit this file and import the code into fgfs with
this line in a key binding or typed into the Nasal Console dialog:
debug.load_xml_nasal(Aircraft/foo/test.nas);
This will load the Nasal code from Aircraft/foo/test.nas
into namespace test and execute it, so you'll see the message
hi! on the terminal, and have function test.hello() immediately
available. You can at runtime change the Nasal file, and import
again, etc. And once you are happy with the code, just remove the
two XML lines and load the file via classical method.
The namespace, to which the code is loaded, is determined from the
file name. foo.nas or foo.xml will be added to namespace foo.
The namespace gets created if it didn't exist. Alternatively, one
can define a namespace in the file by addind a module name:
PropertyListmodulewhatever/modulescript![CDATA[
...
]]/script/PropertyList
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] Generic aar.nas/AI properties
Markus Zojer Hello all! First off, when linking the B-2(yasim) to the generic aar.nas I experienced a constant switching of the engines/out-of-fuel property which unsurprisingly results in low thrust. Could this be related to the broken fuel-consumed-lbs property (of yasim?) that is jumping around close to zero? Secondly, is live manipulating of AI model properties possible at the moment? In the flightgear property browser I found orientation/true-heading-deg and some radar properties but I think it would come in handy to be able to manipulate speed, altitude and waypoints (and maybe more Wink) for an AI model. So it would be possible to spawn an AI tanker at a desired location or be able to launch testbeds or rockets from a plane and direct it to a desired location. Several AI tankers are already available - you can use any of these: --ai-scenario=refueling_demo (KC135-E) --ai-scenario=refueling_demo_1(KC135-E} --ai-scenario=refueling_demo_2(KA6-D) If these don't suit - then modify them to your taste. We only have Ballistic objects atm, but you can use this to simulate unguided rockets. I have in mind to do something about guided weapons in the future. Vivian - 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] Generic aar.nas/AI properties
Hi!
Looking at aar.nas I noticed some seemingly unnecessary elsif usage,
wonder if they are there for a reason:
if (size(selected_tanks) == 0) {
} elsif (consumed = 0) {
} elsif (consumed 0) { === HERE
}
... and ...
if (capacity - lbs = fuel_per_tank) {
} elsif (capacity - lbs fuel_per_tank) { === HERE
}
Also, I think there might be a bug here: fuel_per_tank is a negative number!
Thus the first condition will always be true. As we are in the
refuelling branch, I think it would make the code more readable if a
positive fuel_per_tank was used.
Another minor problem: during refuelling if one of the tanks fills up
in the current iteration, the extra fuel will not be distributed among
the other tanks. As this function is called often and thus processes
small amounts of fuel at a time, this does not really make a
difference. (Plus the tanks will usually fill up at the same time.)
Might be completely wrong, don't hesitate to kick me :)
Greets,
Csaba
-
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] Generic aar.nas/AI properties
* Csaba Halász -- Thursday 29 March 2007:
if (size(selected_tanks) == 0) {
} elsif (consumed = 0) {
} elsif (consumed 0) { === HERE
Yeah, that's now redundant. It wasn't until a few hours ago. Didn't
look at that.
if (capacity - lbs = fuel_per_tank) {
} elsif (capacity - lbs fuel_per_tank) { === HERE
True. No idea where this comes from.
Also, I think there might be a bug here: fuel_per_tank is a negative number!
Sheesh. Will check. This file was converted from an older version,
and apparently I added a few extra bugs. Thanks for reporting.
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
[Flightgear-devel] New Nasal in CVS
A big heads up. I just updated the Nasal interpreter to sync it with Nasal CVS: Sync with Nasal CVS (soon to become Nasal 1.1). Notable new features: Nasal now supports calls to subcontexts and errors can be thrown across them, leading to complete stack traces when call() is used, instead of the truncated ones we now see. Vectors can now be concatenated using the ~ operator that used to work only for strings. Better runtime error messages in general due to a fancier naRuntimeError() implementation A big data size shrink on 64 bit systems; the size of a naRef dropped by a factor of two. Braceless code blocks have been added to the parser, so you can write expressions like if(a) b(); just like in C. Note that there's still a parser bug in there that fails when you nest a braced block within a braceless one. Character constants that appear in Nasal source code can now be literal multibyte UTF8 characters (this was always supported for string literals, but character constants were forced to be a single byte). New modules: bits, thread, utf8 and (gulp...) io. The bits library might be useful to FlightGear, the utf8 one probably not as Plib does not support wide character text rendering. The thread library will work fine for spawning threads to do Nasal stuff, but obviously contact with the rest of FlightGear must be hand-synchronized as FlightGear isn't threadsafe. The io library is no doubt the most useful, as it exposes all the basic stdio.h facilities; it's also frighteningly dangerous when combined with networked code... This almost certainly broke something, somewhere. Please be on the lookout for anything that looks like it might be an interpreter bug or new behavior. Likewise, let me know if any platform builds broke -- at the very least, MSVC project files are going to need to be updated for the new files. Andy - 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] encoder/altimeter kap140.nas
On Wed, 2007-03-28 at 21:57 -0600, Ron Jensen wrote: Dave, I've been running John's code for a while now and have not noticed any problems with it. I compiled with your patch this morning but have not had a chance to fly it yet. One change I would like see from a neatness point of view: Is it possible to rename atmo.?xx as atmosphere.?xx? Thanks for the patch, Ron Ron, Thanks for the testing and feedback. I have been running a version of John's models similar to this patch for several weeks with no issues. I will do a replace of atmo with atmosphere. This is in the direction of clear naming of files that Melchior has often suggested. Thanks, - 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
