* Csaba Halász -- Tuesday 10 July 2007:
I have split my modifications into smaller changes so that they can
be reviewed and applied individually, but nobody cared [...]
Nobody cared? You presented it on the list, but never asked for
it being committed. Or have I missed something?! What you did
Hi all,
First of all, I'd like to thank and congratulate everyone on FlightGear, an
already excellent effort with still so much potential. I'm very excited by
what you are all doing.
I'd currently lack the skills, but I'd like to work towards being in a
position where I can contribute to
Hi Peter,
yes, you can do meaningful development on Flightgear in Windows. (e. g.
I am developing on windows with msvc-express).
On this page Olaf Flebbe described, how to build Flightgear with
msvc-express:
http://www.oflebbe.de/FlightGear/index.html
Do you have any idea, where you would like
Hi Maik,
Thanks for your prompt reply and the link. I'll try it out.
I have no idea where I'd like to work on yet but I guess I'll help out where
I'm needed and where I am able to - ie complex 3d modeling and flight
physics are beyond my ability and experience I'm afraid (but maybe anything
is
On Tuesday 10 July 2007 10:48, Peter Roehlen wrote:
Maybe I could work on the user interface initially? Eventually, it would
be nice to enhance the product with some simple/optional guided experiences
- much like the missions and tutorials in FS9/FSX.
You mean something like what we have
Oops, it seems that I have a lot to learn about the FlightGear program too
:-) I just tried the take-off one - it works very well. (I had six
deviations so I'm not sure what that says about my virtual piloting
ability).
I like your suggestion for starting off with mission building. I'd need
On Tuesday 10 July 2007 11:26, Peter Roehlen wrote:
Oops, it seems that I have a lot to learn about the FlightGear program too
:-)
Join the club :-) The thing about FG is that it covers a very wide range of
interests, and people mostly tend to investigate only the bits they're
particularly
Okay, thanks AJ. Armed with the link from Maik and the below information I
have plenty to go ahead with.
Cheers - Peter.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of AJ
MacLeod
Sent: Tuesday, 10 July 2007 8:41 PM
To: FlightGear developers
On 7/10/07, Melchior FRANZ [EMAIL PROTECTED] wrote:
* Csaba Halász -- Tuesday 10 July 2007:
I have split my modifications into smaller changes so that they can
be reviewed and applied individually, but nobody cared [...]
Nobody cared? You presented it on the list, but never asked for
it
Hi, I'm trying to make a multiple display with
:--native-fdm=socket,out,24,x.x.x.x,5505,udp for the
master--native-fdm=socket,in,10,,5505,udp --fdm=external for the slaveand
everything runs fine. But when i want to add
:--native-ctrls=socket,out,10,152.81.40.31,5506,tcp to the master
I believe this was an unfortunate bug that snuck into v0.9.10. I'm pretty
sure it's fixed in the development tree.
Regards,
Curt.
On 7/10/07, jean louis huynen wrote:
Hi,
I'm trying to make a multiple display with :
--native-fdm=socket,out,24,x.x.x.x,5505,udp for the master
Hello all!
As promised a preview version of the bone for cvs.
Can be downloaded here:
http://homepage.univie.ac.at/markus.zojer/fgfs/B-1B.tar.gz
start with --aircraft=B-1B
Some feedback about the FDM would be nice, since I never flew the bone :-)
Fly on,
Markus
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I made some more patches for bad gear on multiplayer.
http://rage.kuonet.org/~anmaster/flightgear/beaufighter.patch
http://rage.kuonet.org/~anmaster/flightgear/c310u3a.patch
http://rage.kuonet.org/~anmaster/flightgear/mosquito.patch
Expect even
You mentioned outputing data to a socket. Can you give me an outline of how
to set that up? Doing everything is JSBSim is fine for now. I think I just
need aircraft orientation and g-forces on the pilot.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jon
* Markus Zojer -- Tuesday 10 July 2007:
http://homepage.univie.ac.at/markus.zojer/fgfs/B-1B.tar.gz
start with --aircraft=B-1B
Thanks, committed. I changed the line endings in one file from
DOS to UNIX, made absolute paths in the animation file relative,
and I had to crop the thumbnail.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I'm sorry to spam this list ;) but here are some more patches:
http://rage.kuonet.org/~anmaster/flightgear/ju52.patch
http://rage.kuonet.org/~anmaster/flightgear/flash2a.patch
http://rage.kuonet.org/~anmaster/flightgear/bf109.patch
On 07/10/2007 02:21 PM, Hans Fugal wrote:
Will someone please apply this patch, or provide feedback? Thanks!
Feedback: Looks sensible. Works fine chez moi (Debian etch, OSG).
Committed to the _Sport Model_.
http://www.av8n.com/fly/fgfs/README.sport.model
Hi Markus,
thanks for the new aircraft.
I found a small problem in b-1b-sound.xml.
There was a bug in the directional sound in Flightgear, which made the
directional sound not work. Due to this, nobody recognized some mistakes
in the README.xmlsound. (It's all fixed now). The direction need not
Hi,
sorry, I forgot, the coordinate system definition was wrong in the
README.xmlsound, too.
Maik
Maik Justus schrieb am 10.07.2007 21:16:
Hi Markus,
thanks for the new aircraft.
I found a small problem in b-1b-sound.xml.
There was a bug in the directional sound in Flightgear, which made
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Using fg/plib I get this:
WARNING: ssgSGIHeader::: Failed to open
/home/anmaster/src/flightgear/data/Aircraft/B-1B/Models/Instruments-3d/knob.rgb'
for reading.
Failed to load submodel: Failed to open file
at
Hi John,
John Denker schrieb am 10.07.2007 21:05:
Committed to the _Sport Model_.
???
as as I read the cvslogs, it was already committed to cvs. Don't you
think, that mixing your patches partially with patches already in cvs
would make it harder to port any of your patches back to cvs?
--- Maik Justus wrote:
Hi AnMaster,
AnMaster schrieb am 10.07.2007 20:58:
I'm sorry to spam this list ;) but here are some more patches:
http://rage.kuonet.org/~anmaster/flightgear/ju52.patch
http://rage.kuonet.org/~anmaster/flightgear/flash2a.patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
http://rage.kuonet.org/~anmaster/flightgear/Aerostar-700.patch
http://rage.kuonet.org/~anmaster/flightgear/f104.patch (but this plane is not
flyable anyway, I wonder why such a broken plane is in CVS...)
I also uploaded a new version of
On 07/10/2007 03:24 PM, Maik Justus wrote:
John Denker schrieb am 10.07.2007 21:05:
Committed to the _Sport Model_.
???
as as I read the cvslogs, it was already committed to cvs.
The two commits happened within a few minutes of each other.
Such things are bound to happen from time to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I'm terribly sorry I hit reply on the wrong thread.
AnMaster wrote:
I checked the other patches I made for bad properties outside the main xml
file and have as a result of that updated some patches:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Apart from that I wrote to the wrong thread...
I checked the other patches I made for bad properties outside the main xml
file and have as a result of that updated some patches:
http://rage.kuonet.org/~anmaster/flightgear/mosquito.patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Some more property path patches:
http://rage.kuonet.org/~anmaster/flightgear/747-400.patch
http://rage.kuonet.org/~anmaster/flightgear/ogel.patch
http://rage.kuonet.org/~anmaster/flightgear/E3B.patch
After update of simgear, source, and data using
cvs up -Pd -rPRE_OSG_PLIB_20061029
for each update, I am getting the error when I run fgfs:
Unknown top level section: wxradar
Fatal error: Detected an internal inconsistency in the instrumentation
system specification file. See earlier errors for
On Tue 10 July 2007 23:04, AnMaster wrote:
Apart from that I wrote to the wrong thread...
I checked the other patches I made for bad properties outside the main
xml file and have as a result of that updated some patches:
http://rage.kuonet.org/~anmaster/flightgear/mosquito.patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
gh.robin wrote:
On Tue 10 July 2007 23:04, AnMaster wrote:
Apart from that I wrote to the wrong thread...
I checked the other patches I made for bad properties outside the main
xml file and have as a result of that updated some patches:
On 7/11/07, Dave Perry [EMAIL PROTECTED] wrote:
After update of simgear, source, and data using
cvs up -Pd -rPRE_OSG_PLIB_20061029
for each update, I am getting the error when I run fgfs:
Unknown top level section: wxradar
Fatal error: Detected an internal inconsistency in the
On Wed 11 July 2007 01:12, AnMaster wrote:
gh.robin wrote:
On Tue 10 July 2007 23:04, AnMaster wrote:
Apart from that I wrote to the wrong thread...
I checked the other patches I made for bad properties outside the main
xml file and have as a result of that updated some patches:
On Tue, 10 Jul 2007 22:17:42 +0200
AnMaster [EMAIL PROTECTED] wrote:
http://rage.kuonet.org/~anmaster/flightgear/Aerostar-700.patch
Hi AnMaster, thanks for fixing all the aircraft . Now maybe those annoying
messages will go away :).
Just a note though , it wasn't neccesary to fix the Aerostar
On Wed, 2007-07-11 at 01:26 +0200, Csaba Halász wrote:
On 7/11/07, Dave Perry [EMAIL PROTECTED] wrote:
After update of simgear, source, and data using
cvs up -Pd -rPRE_OSG_PLIB_20061029
for each update, I am getting the error when I run fgfs:
Unknown top level section: wxradar
Fatal
On 7/11/07, Dave Perry [EMAIL PROTECTED] wrote:
On Wed, 2007-07-11 at 01:26 +0200, Csaba Halász wrote:
On 7/11/07, Dave Perry [EMAIL PROTECTED] wrote:
After update of simgear, source, and data using
cvs up -Pd -rPRE_OSG_PLIB_20061029
for each update, I am getting the error when I run
I meant to reply to this yesterday...
On Mon, 9 Jul 2007, JOSHUA WILSON wrote:
I have made some more changes to the 787 model.
Your timing is excellent, as Boeing rolled out the 787 Sunday (7/8/'7):
http://seattletimes.nwsource.com/html/businesstechnology/2003780379_787main09.html
On Tue, 2007-07-10 at 22:17 +0200, AnMaster wrote:
http://rage.kuonet.org/~anmaster/flightgear/f104.patch (but this plane is not
flyable anyway, I wonder why such a broken plane is in CVS...)
Assuming you mean the way the airplane jumps around at startup, the
attached patch will make it behave.
I've added a mixture test to the YASim jet engine , so that it can be shut down
by setting mixture to 0; Same as out of fuel condition , without having to
empty a tank and change aircraft weight to disable an engine.
Could someone commit the patch if it passes inspection , and Andy's approval ,
Hi Csaba,
On Tue, Jul 10, 2007 at 07:40:46PM +0200, Csaba Halász wrote:
Hi Holger!
Maybe try the sed hack with a shorter prefix, such as replacing
_ZNSt6vector with _ZNSt6vectorX. Note that it is a pretty brutal thing
to do for the whole binary, and might break it in a million ways. Or,
39 matches
Mail list logo
