Hi,
I have placed a copy of the diff file for the latest multiplayer update at:
http://members.optusnet.com.au/d.mcc/
I think the diff that I last posted to the devel mail list may have been
generated incorrectly.
Duncan McCreanor
___
On Tue 25. March 2003 19:20, you wrote:
On Tuesday 25 March 2003 6:41 am, Richard Bytheway wrote:
As a pay-by-the-minute modem user, I would prefer not to have 200MB of
data dumped into the base package CVS if possible. The cheapest my
connection gets is £0.48 per hour. 200MB is about 20
Duncan McCreanor wrote:
Hi,
I have placed a copy of the diff file for the latest multiplayer update at:
http://members.optusnet.com.au/d.mcc/
I think the diff that I last posted to the devel mail list may have been
generated incorrectly.
Okay I'll take a look at it.
Erik
Martin Dressler [EMAIL PROTECTED] said:
No, The most of layers are textures or gradients. One final layer in in
instrument is composed of 3 to 20 and more source layers. The xcf also
include source photos transformed and shifted for use. And I have 3 xcf per
one instrument in different
Duncan McCreanor wrote:
Hi,
I have placed a copy of the diff file for the latest multiplayer update at:
http://members.optusnet.com.au/d.mcc/
I think the diff that I last posted to the devel mail list may have been
generated incorrectly.
Excellent. They are in CVS now.
Thanks!
Erik
The P-51D accelerometer has what appears to be E UNITS printed on the face
in several not quite detailed enough photos I have. I thought perhaps it was
G UNITS, but it doesn't really look like a G in any of the photos.
Does anyone have a take on this?
Thanks,
Jim
Hi
guys!Finally I made landing light support in flightgear!It uses coolest
per-pixel attenuated spotlightBut it cost additionally 2 textures one of
them is 3d texture and othercubemapand it uses register combiners and
vertex programsI test it on geforce3 and it works well on linux.Here is
* Roman Grigoriev -- Wednesday 26 March 2003 17:05:
I test it on geforce3 and it works well on linux.
Does is work with other cards than nVidia, too?
m.
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
Hello all,
I downloaded the cvs source tree for the first time
yesterday and all the compiling went okay, but it
won't link. Here is the output:
[EMAIL PROTECTED] Main]$ make
g++ -DPKGLIBDIR=\/usr/local/lib/FlightGear\ -g -O2
-L/usr/X11R6/lib -o fgfs
main.o fg_commands.o fg_init.o fg_io.o
* [EMAIL PROTECTED] (Roman Grigoriev) [2003.03.26 10:09]:
Finally I made landing light support in flightgear!
Awesome!
Here is screenshots
http://fgfs.narod.ru/fgfs-screen-001.jpg
http://fgfs.narod.ru/fgfs-screen-002.jpg
http://fgfs.narod.ru/fgfs-screen-003.jpg
I too maintain my own, and if you read a little way
back in the achives I mentioned you have to also
update FG/src/include/config.h, which arrives as
config.h-msvc6, with something like -
#ifndef GLUT_H // per MSVS install directory
#define GLUT_H GL\glut.h
#endif // #ifndef GLUT_H
Roman Grigoriev writes:
Finally I made landing light support in flightgear! It uses coolest
per-pixel attenuated spotlight But it cost additionally 2 textures
one of them is 3d texture and other cubemap and it uses register
combiners and vertex programs I test it on geforce3 and it works
I noticed that all of the YASim models tended to nose down with
neutral elevator. I assumed that it was a WB problem and tried
shifting weight all over the place in the J3 cub (and even moved the
wings around), but nothing fixed the problem.
In the end, I figured out that the YASim solver simply
David Megginson wrote:
I noticed that all of the YASim models tended to nose down with
neutral elevator. I assumed that it was a WB problem and tried
shifting weight all over the place in the J3 cub (and even moved the
wings around), but nothing fixed the problem.
Right. The solver just
Andy Ross writes:
This came up a while back. Apparently I didn't put it in the docs. A
slightly terser explanation is this:
YASim trims the aircraft (with tail incidence, not control input) so
that the elevator value is exactly zero in the specified cruise
configuration. It
David Megginson wrote:
That was not happening, however; instead, with 0 elevator and 0
elevator trim, all aircraft would continue pitching downwards and
accelerating past Vne. Setting the elevator property solved the
problem. I don't know why it wasn't trimming for 0
elevator/elevator trim.
Hi,
How come whenever I release an aircraft for JSBSim, a few weeks later I
see an anouncement on avsim.org that this type of aircraft will be
available to MSFS with a realistic flight model?
It happened with the F-16, it happened with the F-104 and it will happen
with the F-15 also!
Oh
Andy Ross writes:
And it *was* trimming for zero /controls/elevator{-trim}. That's the
whole point: It's not a bug in the solver. The pitching moment* at
the specified cruise conditions is very near zero; that's what the
solver does. The problem is that a real aircraft under those
Erik Hofman writes:
How come whenever I release an aircraft for JSBSim, a few weeks later I
see an anouncement on avsim.org that this type of aircraft will be
available to MSFS with a realistic flight model?
It happened with the F-16, it happened with the F-104 and it will happen
David Megginson wrote:
Erik Hofman writes:
How come whenever I release an aircraft for JSBSim, a few weeks later I
see an anouncement on avsim.org that this type of aircraft will be
available to MSFS with a realistic flight model?
It happened with the F-16, it happened with the F-104
Here are some screen shots of the last couple of night's progress:
http://www.spiderbark.com/fgfs/p51dshot9.png
http://www.spiderbark.com/fgfs/p51dshot10.png
Does anyone know anything about how the radio compass (ADF), upper left
instrument should work? I'm not sure yet where the radio
Erik Hofman writes:
I wouldn't have a problem with that either if they respect the GPL,
which in most cases they don't. Further more it take a considerable
amount of time gathering all the data, and just taking the data for
your own good is, so to say, not nice.
Is our data GPL'd, or
On Wed, 2003-03-26 at 15:16, David Megginson wrote:
Erik Hofman writes:
I wouldn't have a problem with that either if they respect the GPL,
which in most cases they don't. Further more it take a considerable
amount of time gathering all the data, and just taking the data for
your
On 26 Mar 2003, Tony Peden wrote:
Probably true, but credit (if it's due) is not terribly much to ask for.
This is a recurring theme in the Windows world. Almost noone who
develops train models for MSTS and Trainz wants to part with their 3d
models, because of the abundance of unscrupulous
Here are expanded versions of controls.hxx and controls.cxx
http://home.attbi.com/~davidculp2/controls.hxx
http://home.attbi.com/~davidculp2/controls.cxx
I've integrated it into FlightGear/JSBSim, but haven't tested it yet with
other FDM's or with the autopilot. If anyone's interested I'll
- Original Message -
From: David Megginson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, March 26, 2003 8:50 PM
Subject: re: [Flightgear-devel] Landing Spotlight in Flightgear (I made
it!!)
Roman Grigoriev writes:
Finally I made landing light support in flightgear! It
Bert Driehuis writes:
This is a recurring theme in the Windows world. Almost noone who
develops train models for MSTS and Trainz wants to part with their 3d
models, because of the abundance of unscrupulous folks who then market
the stuff they got for free. One developer I know even went
* [EMAIL PROTECTED] (Michael Selig) [2003.03.25 16:53]:
I have just added R/C transmitter support to the FlightGear base
package. To make it all work, one must have a supported radio and purchase
an RCJOY USB box ($90) as well as a cable (~$12) from
http://www.leweng.com. This USB box
This morning, before leaving for work, I tried the normal short field
technique in the c172p-3d (full flaps, just above stall, behind the
power curve decent, with the touch down immediately after pulling the
power.) This was my first attempt in fgfs. I think I can easilly beat
this with a
* [EMAIL PROTECTED] (Jim Wilson) [2003.03.26 17:05]:
Does anyone know anything about how the radio compass (ADF), upper left
instrument should work? I'm not sure yet where the radio controls are (the
radio actually sits behind the pilot seat).
My biggest problem is not knowing what the
Does anyone know anything about how the radio compass (ADF), upper left
instrument should work? I'm not sure yet where the radio controls are (the
radio actually sits behind the pilot seat).
My biggest problem is not knowing what the second arrow is (the one with two
white lines
Hi! I'm having a few teething problems installing Flightgear. Right
now I'm puzzled because I don't have glut.h on my system. Shouldn't it
come with glut3.7-8. thanks!
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
What is your system? If you have Windows then you will need to build
GLUT on your own. GLUT should come with MESA (or the OpenGL drivers of
your video card) under Linux (at least that's how I get it).
Jonathan Polley
On Wednesday, March 26, 2003, at 11:02 PM, Howell Caton wrote:
Hi! I'm
I don't mean to scare anybody, but this has to do with the upcoming
Panther release (10.3). With the release of Panther, I will be dumping
my 10.1 partition and won't be building FlightGear for MacOS X 10.1,
although I don't keep it current right now, in favor of maintaining
10.2 and 10.3
* [EMAIL PROTECTED] (Howell Caton) [2003.03.26 23:14]:
Hi! I'm having a few teething problems installing Flightgear. Right
now I'm puzzled because I don't have glut.h on my system. Shouldn't it
come with glut3.7-8. thanks!
You didn't mention what OS/Distro you are using, but make sure
At 3/26/03, Cameron Moore wrote:
* [EMAIL PROTECTED] (Michael Selig) [2003.03.25 16:53]:
I have just added R/C transmitter support to the FlightGear base
package. To make it all work, one must have a supported radio and
purchase
an RCJOY USB box ($90) as well as a cable (~$12) from
36 matches
Mail list logo
