WTF is PSL, you ask? It's our other scripting language,
besides Nasal (PSL ... "plib's scripting language"). But
it was only ever used once in CVS (for a keybinding that
output lat/lon IIRC), we'll sooner or later abandon plib
altogether, and PSL is a joke compared with Nasal.
Objections? Any user
* Stuart Buchanan -- Tuesday 22 January 2008:
> If not, I wonder whether I should just move them to somewhere
> less prominent in the wiki with a disclaimer, as they are
> currently more prominent than they deserve to be, IMHO.
Good idea. I see all the same problems that you do. And I find it
qui
Now that HEAD is for fg/osg only, some aircraft and other stuff
will soon start to work badly or not at all with v1.0 and fg/plib.
No problem for exclusive fg/osg users, but some people still like
volumetric shadows and 3D clouds and will therefore also use
fg/plib for a while. (Helicopters in outs
With Curt's OK I have now created a PLIB branch for the data
directory. For developers this means:
- work on HEAD can go on as usual -- there's no need to care
about the PLIB branch at all
- HEAD does no longer have to be compatible with fg/plib and
fgfs v1.0
- only changes that should be co
Hi,
you have to know that FlightGear has never had a common coding
style (at least not since I'm contributor, that is 2001/3).
The rule was always that who starts writing a file decides for
a style, and everyone adding to that file later respects this
style. (There are exceptions, such as when a f
* [EMAIL PROTECTED] -- Saturday 19 January 2008:
> and i am starting to do general clean-ups and optimizations
> (e.g. replacing serveral if - else if - else if... with switch)
Don't do that! Switch *may* sometimes be the better solution,
and very often it isn't. When I used if/else-if somewhere,
* Chris Metzler -- Tuesday 08 January 2008:
> "fgfs --aircraft=ufo" is enough to give me the same
>
> } Nasal runtime error: props.setDoubleValue() with non-number
> } at /home/cmetzler/Projects/FlightGear-0.9/data//Nasal/props.nas, line 26
Can't reproduce that here, neither with fg/plib nor fg
* Stuart Buchanan -- Friday 18 January 2008:
> Of course, if we're not planning to make any further plib releases,
> then there is no need for a PLIB data branch :) .
A plan is (only) a plan. We should keep the possibility to
release a version 1.1 with the most annoying bugs of 1.0 fixed.
Aircraft
We should now really think about making a plib branch for
the data -- just named PLIB (no pointless date!). The old
and unused plib branch (PRE_OSG_PLIB_20061029) could be
removed. It doesn't contain anything useful. I guess it's
safe to assume that no more plib based release will be made
(except m
* Stefan Seifert -- Thursday 17 January 2008:
> find . -name \*.xml | xargs grep vsi-3d
I didn't use this because this puts all file paths into the
command line buffer, and it depends on the buffer size whether
it works or not (unlike with "while read"). I remember cases
where it didn't work, but
* Syd&Sandy -- Thursday 17 January 2008:
> Charming , as always :)
:-P
Note that it didn't disturb me at all that you broke something --
that happens to everyone. The more you do, the more you break
occasionally. So the rate of breakage is really a good sign, not
a bad one. :-)
Only the explana
* Syd&Sandy -- Wednesday 16 January 2008:
> I rarely get time to check other's work , so I never know who
> else is using the gauges ...
Sorry, but that's absurd. It takes almost no time to check ...
$ find $FG_ROOT/Aircraft -name \*.xml|while read i; do grep -l vsi-3d.xml $i;
done
/usr/loc
First of all, sorry for my -- once again -- harsh posting. I was just
a bit overwhelmed by an "AARGH" feeling. ;-)
* On Dec 27, 2007 12:42 PM, Syd&Sandy <[EMAIL PROTECTED]> wrote:
> The reason behind this was a new monitor , now I have to set FOV to 70 for
> a decent view...
And that's exactl
* Barry Fawthrop -- 12/24/2007 2:04 AM:
> For Those Interested I have completed the xml file for the
> Saitek Pro Flight Yoke System with std Throttle Quadrant
I'm happy about new drivers and improvements to existing ones.
But there's one big problem with this driver: you are using almost
no contr
* Stuart Buchanan -- 12/28/2007 5:57 PM:
> I've uploaded my own one to
> http://www.nanjika.co.uk/flightgear/fighterstick-usb.xml
There are some problems that one would probably not realize
immediately, but will cause unwanted behavior in some cases:
* you aren't stopping the trigger with contro
* Syd Adams -- 12/27/2007 4:27 AM:
> Log Message:
> Added field-of-view to the save file of my aircraft
> Updated the radar to a 2d screen , still not working 100%
Bad idea. I saw it coming that fgfs would kind-of go down the
drain if nobody cares about consistency (which I recently gave
up for k
* gerard robin -- Saturday 22 December 2007:
> Yet, we have such information out of YAsim, from AI ? (like said Csaba )
> fgfs --aircraft=WhichFly --carrier=WichFloat --parkpos=cat1
> FG place the WhichFly at the right place on the cat
Yes, but that's something else -- that's defined in th
* gerard robin -- Saturday 22 December 2007:
> It is the best way, to have in property the coordinates of the points which
> are defined in the AI model (may be, the precision would a problem)
The properties are the smaller problem, whether they are inserted
via Nasal or automatically. The vect
* Melchior FRANZ -- Saturday 22 December 2007:
> One could certainly get the values out, but that would be a
> lot more work.
Oh, and the manual way has the advantage that you can easily add
arbitrary stuff, such as other (non-cat) vertex offsets, or offsets
for places where no vertex is an
* Csaba Halász -- Saturday 22 December 2007:
> Well, the FGAICarrier code already finds catapult and wire nodes,
> maybe we can just add them to the property tree there?
But it does so as an OSG node visitor with intersection testing
done by OSG, or something. One could certainly get the values ou
* gerard robin -- Saturday 22 December 2007:
> The problem here is we don't have a generic solution this must
> be calculated for each carrier or any AI object [...]
Ah, you want to avoid the calculation per object. Frankly, I don't
think that's such a generic problem. Most carrier capable aircra
* gerard robin -- Saturday 22 December 2007:
> The problem here is we don't have a generic solution this must
> be calculated for each carrier or any AI object according to the
> .xml file definition , one calculation for Nimitz one for Foch one
> for ... and so on.
That's not the problem.
* gerard robin -- Saturday 22 December 2007:
> I would like to know (to calculate) the diff of position between the
> position of the aircraft and the position of a specific point on an
> AI object in my case the catapult and the wires on the carrier.
> Is their any way (nasal ??) to get it out of
* Curtis Olson -- Saturday 22 December 2007:
> silent rejection == not enough time to think about it. :-)
Well, exactly one year and two days.
> when I get back maybe send me a reminder.
OK. :-)
m.
-
This SF.net email i
Could we, please, have ATOM/RSS support for the fgfs forum? There
are complete solutions for the forum software phpBB available, and
reportedly installed within minutes. For example:
http://phpbb.potomactavern.org/smartfeed/
Advantage: one can see new contributions in a newsreader and
quickly o
* gerard robin -- Saturday 22 December 2007:
> To me, these property are not declared twice, [...]
The problem isn't that they are "declared" twice, but that there
are two code parts that try to tie it, or the same code is run
twice. And this is certainly not a bug in your aircraft config.
m.
--
* gerard robin -- Saturday 22 December 2007:
> Failed to tie property /controls/gear/float-down to a pointer
The error message is generated in JBSim/input_ouput/FGPropertyManager.cpp
when SGPropertyNode::tie returned false. And this can only be the case
if something tries to tie a property that is
> -
> This SF.net email is sponsored by: Microsoft
And can we, please, change our mail provider? :-}
m.
-
This SF.net email is sponsored by: Microsoft
The problem was acknowleged by nVidia for the beta 169.04!
WTF didn't they fix it for the release?! (Ok, ok, some say
that about our bugs ... :-)
http://www.nvnews.net/vbulletin/showthread.php?t=104363
(And no, removing ~/.nvidia-settings-rc doesn't help.)
m.
-
* Melchior FRANZ -- Thursday 20 December 2007:
> psychedelic sky, bo105 all black.
And it looks like this:
http://members.aon.at/mfranz/lsd.jpg [20.4 kB]
m. :-)
-
This SF.net email is sponsored by: Microsoft
Defy
* Melchior FRANZ -- Thursday 20 December 2007:
> But the FlightGear splash screens are now broken! All of them!
> Only colorful pattern. And the HUD font.
And the "classic" GUI style font (which is a texture font).
And the vasi/papi lights! Looks like this is something that need
* Melchior FRANZ -- Thursday 20 December 2007:
> Often this isn't something that's worth announcing, but this time
> the list of changes sounds interesting:
>
> http://www.nvidia.com/object/linux_display_ia32_169.07.html
[...]
> Not that I've tried yet ...
And no
* Georg Vollnhals -- Wednesday 19 December 2007:
> You asked on the FG forum for driving cars. I made an example a long
> time ago with a driving truck on the EDDW airport.
BTW: the ufo does since a while export flightplans. You just
select an arbitrary object, set a trace with it, and press
the '
* Pavel T -- Wednesday 19 December 2007:
> I was thinking of this idea and I thought you might like it.
> You might have guessed already by the subject of the e-mail. I was thinking
> of maybe someone could make different versions of trees and make someking of
> a tool that puts a number a number o
* gerard robin -- Wednesday 19 December 2007:
> I don't agree, :)
>
> in reality the Osprey lands on Carrier, and is 'driven' to the hangar
> (elevator).
OK, so far you *agree* ... :-)
> Within FG when you have land it on the Carrier you can manage to taxis it(
> admit not easy) with
Much better now. :-)
But the v22 on the elevator is cheating (and thus violating
my personal diktator policies). You can't realistically land
it there, and there's no way to move a v22 to the elevator
once landed. Cheated "screenshots" have annoyed me since
years ... almost decades. Pretty photo-
* Shad Young -- Wednesday 19 December 2007:
> I wanted to keep it cross-platform, but now that there is mention of an
> HTML interface, I am going to suggest to my client that a PHP/web
> interface might be a good way to go. But then again, this might require
> an embedded server to provide "out
* Chris Metzler -- Wednesday 19 December 2007:
> "Lightning-KSFO-06"-- why does the page visitor need to know
Well, the whole screenshot isn't something that a visitor should know. ;-)
The lightning is quite small in the middle in a rather not-so-interesting
position.
> Oh, and I'd keep trying
Many of the shots are quite good. But some are ... umm ...
http://www.flightgear.org/Gallery-v1.0/Link/787fujiuy6.html
Dark bump-mapped cloud soup on the bottom, an almost perfect
presentation of our white-mountain/blue-sky bug, and lots of
aliasing steps. Not exactly a teaser.
This is techni
* Melchior FRANZ -- Tuesday 18 December 2007:
[bell206/as350]
> I've moved them to the Attic/ in CVS, but I assume they need to be
> removed manually from the download page.
Ah, I see that's already done. :-)
BTW:
* Maik Justus -- Monday 17 December 2007:
> Melchior: Whats
* Maik Justus -- Monday 17 December 2007:
> could you please delete the as350 and the bell206 from the download
> page? Both have no 3D-model and a very poor FDM.
I've moved them to the Attic/ in CVS, but I assume they need to be
removed manually from the download page.
Once someone comes along
* Stewart Andreason -- Monday 17 December 2007:
> Nasal runtime error: non-scalar in numeric context
> at /usr/local/FlightGear/data/Nasal/aircraft.nas, line 601
Whoops, indeed. Thanks for reporting, committed. (No problem for
the release, as it was apparently not used. :-)
m.
* Heiko Schulz -- Monday 17 December 2007:
> Sorry,
No problem. Thanks for the submission.
> it is updated now!
... and committed. That makes two thumbnails: ASK21 and Saab35
Hmm ... which next? Most missing ones are for aircraft by people
who have commit rights, so should I bother? Scratchin
* Heiko Schulz -- Monday 17 December 2007:
> can someone commit this to the ASK 21?
>
> www.hoerbird.net/thumbnail.jpg
Can you submit it in the standard size 171x128 for fgfs thumbnails?
$ identify thumbnail.jpg
thumbnail.jpg JPEG 171x118 171x118+0+0 DirectClass 8-bit 3.41406kb
m.
* Melchior FRANZ -- Monday 17 December 2007:
> it's clearly a job for Maik's winch/anchor feature.
Looks like this doesn't work. As far as I've understood,
it only offers: pulled or pulling aircraft via MP, getting
pulled by an AI aircraft, or a static winch. I haven't
* Georg Vollnhals -- Monday 17 December 2007:
> Just now (!!!) remembering Torsten's Dragonfly banner-trick (!!!) which
> is pretty similar:
Yes, it's clearly a job for Maik's winch/anchor feature. He has
already lifted me via MP: I was in a sgs233, and Maik lifted me
with a bo105. There's just n
* Syd&Sandy -- Monday 17 December 2007:
> #0 0xb7b49b25 in __cxa_throw () from /usr/lib/libstdc++.so.6
> #1 0x084a5126 in FGTileLoader::add (this=0xadde67c, tile=0x117c4878)
> at FGTileLoader.cxx:98
OK, that's this code:
tile_path = globals->get_fg_scenery();
if (!tile_path.
* Syd&Sandy -- Sunday 16 December 2007:
> fgfd --Aircraft=Bravo --log-level=debug
Works here. No segfault. (Just dead slow. :-)
> Uncaught Exception: you should see a meaningful error message
Try this:
$ gdb --args fgfs --aircraft=Bravo --log-level=debug
(gdb) break main
(gdb) run
(g
* Syd&Sandy -- Sunday 16 December 2007:
> [...] the Bravo also loads a bunch of models from the
> Instruments-3d/primus folder , so I might have pushed it to the limit
PLIB doesn't have problems with lots of vertices/faces etc., but
only with too many per object, so this could only be trigge
* Melchior FRANZ -- Sunday 16 December 2007:
> No segfaults here. But PLIB has some hard-coded limits:
Yeah, yeah ... "hard coded limits". Of course, it's only badly
chosen data types, which are now kept for compatibility reasons.
(And because Steve says that ought to be
* Syd&Sandy -- Sunday 16 December 2007:
> Just a note to say I'm getting a lot of segfaults in the last few days ...
> Maybe the Bravo is getting to big
No segfaults here. But PLIB has some hard-coded limits: number
of vertices per object, number of triangles, etc. (2^15 for each,
IIRC). Some air
* Chris Metzler -- Sunday 16 December 2007:
> Maybe I'm missing something here [...] the reason for the new
> scenery was that the old scenery was inconsistent with the
> current apt.dat [...]
Well, you missed the fact that it was the same person who had
*caused* the inconsistency by committing ne
* AnMaster -- Saturday 15 December 2007:
> Yes but tar ball have been made [...]
But they aren't released. Can still be fixed.
I'd revert the last changes to the dhc2F that broke it.
The manual seems to have changed after the packaging, too,
and there certainly was a reason for the changes.
Let'
* AnMaster -- Saturday 15 December 2007:
> IIRC the Beaver was included. But as I mentioned before
> ("[Flightgear-devel] Missing file in cvs for dhc2F") it is
> broken. My mail seems to have been ignored.
That's bad, indeed. The whole aircraft should get thrown out.
There's a file in the seahawk
* AnMaster -- Saturday 15 December 2007:
> Well I wanted to show the runway lights or aircraft lights in some
> of my screenshots. Hard to do that at noon. :P
True. But night lighting is one of our weakest areas, so it's probably
better to hide that away.
m.
-
- dark screenshots should be avoided, as they likely look bad
on cheap and/or badly adjusted/adjustable monitors. I have that
problem with mine, and that wouldn't be a good reason, but I
also know that others have them. If you don't have anything to
hide, use daylight! :-}
---
For a new release, especially one with version number 1.0, we
should provide some new screenshots for the website. Normally,
Curt would ask for that, but as he is/was away for a few days,
I start with this reminder. Screenshots should ...
- use maximum quality (antialiasing!)
- disable gui parts (
* Hans Fugal -- Thursday 13 December 2007:
> There's a green HUD bug in pre2 on OS X. No lines are shown. It's been
> this way for a while I think.
If this is a Mac-only bug, then I'd say Tat should disable the
HUD transparency in preferences.xml for the Mac package. Unless
people want the old opa
* Cédric Lucantis -- Thursday 13 December 2007:
> I'd like to know if the 'repeatable' flag in the key bindings is
> supposed to work ?
Yes, but only with SDL. It does (AFAIK) not yet work with osgViewer,
and it will probably never work with glut.
> So maybe there are better solutions [...]
Y
> Modified Files:
> apt.dat.gz
> Log Message:
[...]
> Move/rotate Half Moon Bay (KHAF) taxiways to fit the realigned runway.
Sorry, but that doesn't cut it. I've seen *many* runways where the
visuals and the runway data aren't aligned. This "fix" is only
KHAF-tutorial cosmetics.
There are
* Stuart Buchanan -- Wednesday 12 December 2007:
> attempting to start at Half-Moon Bay (KHAF) will place you off one
> side of the runway in the grass
This version mismatch also very likely breaks ILS approaches
to lots of runways. (And more importantly: it breaks the glide
slope tunnel visualiz
* gerard robin -- Wednesday 12 December 2007:
> And, what, about the Bleriot FDM done by David and Lee ?
Oh, I don't want to diktate about this either. But I think with
the current FDM it would put us into a glasshouse, from which
throwing stones at the MSFS scenery viewer would be unwise.
m.
--
* Durk Talsma -- Saturday 08 December 2007:
> Based on all the input sofar, I'd like to propose the following
> list of aircraft for inclusion in the next release:
BTW: one of these lacks a texture file. I just don't want to
diktate that it be added ...
m. :-}
--
* Heiko Schulz -- Sunday 09 December 2007:
> http://www.hoerbird.net/737-300.v12.09.2007.tar.gz
I would have liked to commit that, but I have no idea whether there's
a maintainer still around. The lack of responses implies that there
isn't, in which case it would be OK to commit. (?)
m.
---
* gerard robin -- Tuesday 11 December 2007:
> [...] with YASim, i try to give an init value within the
> Aircraft-set.xml file
>
>
>
>
> 0
> 1
> After startup the throttle value is set to Zero instead of the required
* Durk Talsma -- Tuesday 11 December 2007:
> As it looks right now, either tonight, or Thursday evening will
> be my two windows of opportunity this week.
I would rather go for Thursday, then. It's only known for a short
time which aircraft are planned to go in, and even today and yesterday
there
* Tatsuhiro Nishioka -- Monday 10 December 2007:
> this patch can be and should be applied to CVS/head too
Done, thanks.
m.
-
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place t
* Melchior FRANZ -- Sunday 09 December 2007:
> * Melchior FRANZ -- Sunday 09 December 2007:
> > BTW: in my tests yesterday I noticed that the part was
> > never called, and so the loop is never stopped.
>
> Just for the record: yes, that's not done ATM. Will fix tomorr
* Melchior FRANZ -- Sunday 09 December 2007:
> BTW: in my tests yesterday I noticed that the part was
> never called, and so the loop is never stopped.
Just for the record: yes, that's not done ATM. Will fix t
* Melchior FRANZ -- Sunday 09 December 2007:
> glut in fg/plib or fg/osg?
Disregard. I see from the diff that it's fg/osg. In that
case the patch shouldn't be applied. Tim, can you check if
your last change to the glut interface has caused that. We'll
drop glut anyway, so there&
* Roy Vegard Ovesen -- Sunday 09 December 2007:
> glut.
glut in fg/plib or fg/osg?
I'm asking because I fixed the problem for SDL and osgViewer,
and Mathias fixed it for glut. There was a recent change in
the glut bindings for fg/osg. Maybe this has to do with it.
I'd just like to know *what* we
* Roy Vegard Ovesen -- Sunday 09 December 2007:
> I noticed that when I use "sync to VBlank" to restrain the
> framerate to the monitor's update rate, large jumps happen quite
> often when the mouse cursor is warped to the center.
Not here. Is this with glut or sdl? Does anyone else see that?
I th
* Csaba Halász -- Sunday 09 December 2007:
> Any ideas? Should we put in a comma-separated list of symbolic names?
Not comma, but yes, I think that's the best thing. There should IMHO
already be a name/number list in AIBase.hxx. Then the property could
do what we do with logging classes:
/sim/l
* Curtis Olson -- Sunday 09 December 2007:
> a change to a common object breaks your aircraft. Newer aircraft
> may not work with older versions of FlightGear that don't have the
> shared pieces you expect.
Newer aircraft usually don't work with older releases, anyway. There's
too much changing.
* Csaba Halász -- Sunday 09 December 2007:
* > On Dec 9, 2007 11:02 AM, Melchior FRANZ <[EMAIL PROTECTED]> wrote:
> > The aircraft types aren't bits,
> I have turned them into bits :)
Yes, I admit that I didn't spend more time for the review than
you spent for the ex
* Tatsuhiro Nishioka -- Sunday 09 December 2007:
> For downloadable add-on aircraft, 3D instruments should be stored
> inside each downloadable aircraft package even these can be duplicated.
NO! $FG_ROOT/Aircraft/{Generic,Instruments,Instruments-3d} are to
be shipped with the release. They are mea
* Csaba Halász -- Wednesday 05 December 2007:
> First patch fixes a bug caused by the uninitialized _range_nm member.
> If it happens to contain nan, this will never get overwritten.
> Second patch adds support for filtering what should be displayed.
Do the patches apply to both branches?
How's t
* Maik Justus -- Sunday 09 December 2007:
> With this trick I should be able to transfer the wing-fold
> and engine-tilt animation of the v22 over the MP-protocol.
Yeah, that's a typical case for properties where standardization
wouldn't make much sense, and generic ones are therefore preferable
* Tatsuhiro Nishioka -- Saturday 08 December 2007:
> Durk, could you apply my patch to CVS?
Too late! Already committed. Thanks. :-)
m.
-
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the
* Anders Gidenstam -- Saturday 08 December 2007:
> Though my dual control version of the c172p already uses more
> than 10 extra float properties.. :)
I have no problem with adding more, now that I know that they
have no effect if they aren't used. And if you are using some
others, anyway, then we
* gerard robin -- Saturday 08 December 2007:
> but don't forget that we can within JSBSim avoid most of the Nasal code
> everything done in the FDM.
Again: this doesn't even *work* for what you fear it could be (ab)used.
The bit of Nasal code in bo105.xml is simply ignored if you fly the
bo105. I
* Durk Talsma -- Saturday 08 December 2007:
> Based on all the input sofar, I'd like to propose the following list of
> aircraft for inclusion in the next release:
Looks good. Not trying to say anything particular -- just FYI:
20M 787
20M A-10
26M bf109
3.2Mbo105*
84K
* Melchior FRANZ -- Saturday 08 December 2007:
> $FG_ROOT/Aircraft/Models/bo105.xml
Bah ... $FG_ROOT/Aircraft/bo105/Models/bo105.xml
m.
-
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
I
* Melchior FRANZ -- Saturday 08 December 2007:
> it was time to add some generic properties for "internal communication".
It's probably also time to remind people again of the possibility to
add Nasal code to model (animation) XML files. This is then only
run when the model is u
* gerard robin -- Saturday 08 December 2007:
> I worry that way /sim/multiplay/generic/.. because i thought
> that the best way, regarding every surface position was to
> include it into the "/surface-positions/foo" property
You miss the point, as maybe some others do as well. The generic
pr
* AnMaster -- Saturday 08 December 2007:
> Yes, I already made a patch (see "[Flightgear-devel] Patch for
> Harrier: making it's thrust vector work over mp") for the harrier
> that makes use of this :)
Yes, you are quick. This will have to be reviewed and OK'ed by the
harrier model maintainer.
After Maik has clued me up about multiplayer properties -- that
only those are transmitted, which actually exist at init time
(which is why they need to be defined in the *-set.xml file),
it was time to add some generic properties for "internal communication".
That is: properties which aren't dedic
* AnMaster -- Saturday 08 December 2007:
> Melchior FRANZ wrote:
> > "aircraft" minus "model"? :-}
> Well what do you suggest for storing /sim/aircraft in otherwise?
Err, looks like you didn't get the hint. A '-' in programming
context is a minus,
* AnMaster -- Saturday 08 December 2007:
> Indeed that was what I did, as a way to do aircraft specific mappings. Now I
> renamed the variable to aircraft-model.
"aircraft" minus "model"? :-}
m.
-
SF.Net email is sponsored
* AnMaster -- Saturday 08 December 2007:
> Melchior FRANZ wrote:
> > You probably defined a variable named "aircraft" somewhere else
> > in the joystick driver file, and this overwrote the "aircraft"
> > namespace
> Ah, should call it aircraft-model
* AnMaster -- Friday 07 December 2007:
> aircraft.HUD.cycle_color()
[...]
> Yet I get this for button:
> Nasal runtime error: No such member: HUD
> at /input/joysticks/js/button[3]/binding, line 1
You probably defined a variable named "aircraft" somewhere else
in the joystick driver file, and th
* Tatsuhiro Nishioka -- Friday 07 December 2007:
> 1. DList stack overflow
I've seen them on other occasions in fg/plib. Haven't tried with
Shift-Esc, but I think that's a plib problem. Don't think that's
something we can fix before the release. It's definitely not one
of bugs that people usually
* gerard robin -- Friday 07 December 2007:
> http://pagesperso-orange.fr/GRTux/StampeSV4.jpg
Wow, that's a nice one!
> Unfortunately it will not be available before FG stable will
> be released :(
We can postpone the release for it. ;-)
m.
-
* Stuart Buchanan -- Friday 07 December 2007:
> j3cub -> dhc2W -> pittss1c/p51d/bf109/
BTW: the p51d wasn't considered very realistic in IRC discussions,
so I'm not even sure if it should be in the default collection.
Being a well known and remarkable aircraft in real life isn't enough.
But th
* Melchior FRANZ -- Friday 07 December 2007:
> - avoiding really difficult to fly aircraft in the default aircraft
>collection doesn't make fgfs a toy, and
Oh, and to take some pressure from the bf109, I declare now the
"pittss1c" the official victim that I'l
* dave perry -- Friday 07 December 2007:
> What is proposed is to make the default turbulence = 0.0 at start-up,
> not turning off turbulence modeling. You can still use the weather menu
> to set the desired turbulence or you can [...]
OK, before even more people answer who didn't get what I wa
* Laurence Vanek -- Friday 07 December 2007:
> Although I like realistic flight my ILS approaches we very unstable with
> the turb values given in the Preferences.xml file [...]
But, but ... some have just told us that we shouldn't make it too
easy, or fgfs will be perceived as a toy. So I'd rath
* gerard robin -- Thursday 06 December 2007:
> I have red that the choice in between a model A and an other
> model B is to choose the easier to fly.
>
> Do you mean that FlightGear is a game (versus some other FS
> non free). I am feeling that we are loosing the base of the
> values we had when
* Georg Vollnhals -- Thursday 06 December 2007:
> 2. Add an entry to the aircraft help how to get back to the 2D panel
> once lost (ie. if an unexperienced user looks to the side with the
> mouse. I am pretty sure, someone starting with FG is lost!)
Maybe turn the 2D panel into a 2.5D panel. (That
* Melchior FRANZ -- Wednesday 05 December 2007:
> Given that we will/should drop both glut and sdl support, I wouldn't
> waste time for sdl.
On fg/osg, that is. Of course sdl is the way to go on fg/plib.
m.
-
S
601 - 700 of 1910 matches
Mail list logo
