Hi!
I had a little trouble getting my joystick recognized.
First, js_demo didn't show the name, because
FG_PLIB_JOYSTICK_GETNAME disappeared in configure.ac 1.20.
The first patch fixes js_demo.cxx.
Then I noticed a spelling error in the joystick name in
sidewinder-precision-pro.xml which is
Curtis L. Olson [EMAIL PROTECTED] wrote:
I am just commiting an additional command line option to specify a
starting time of day in the sense of:
Did you probabliy mix up other options ? I usually run FlightGear with
--start-date-lat=2002:04:11:11:11:11 and enjoy a nice morning. After
the
Paulo Henrique S. de Santana wrote:
Hi, I am listening the list for a time (about six months) until a have a
(time) chance to join and try to collaborate with the project.
I have some ideias that need to be cleaned and discussed and a lot of
areas in the Flightgear development that i want to learn
Thomas Arendsen Hein wrote:
Hi!
I had a little trouble getting my joystick recognized.
First, js_demo didn't show the name, because
FG_PLIB_JOYSTICK_GETNAME disappeared in configure.ac 1.20.
The first patch fixes js_demo.cxx.
Then I noticed a spelling error in the joystick name in
Erik Hofman [EMAIL PROTECTED] wrote:
Update of /var/cvs/FlightGear-0.9/data/Aircraft/T38
In directory baron:/tmp/cvs-serv23354
Modified Files:
T38.xml
I'd vote for a modification of the 3D model. The cones behind the
engines don't look _that_ realistic when sitting idle on the runway:
Martin Spott wrote:
Erik Hofman wrote:
Update of /var/cvs/FlightGear-0.9/data/Aircraft/T38
In directory baron:/tmp/cvs-serv23354
Modified Files:
T38.xml
I'd vote for a modification of the 3D model. The cones behind the
engines don't look _that_ realistic when sitting idle on
Frederic BOUVIER [EMAIL PROTECTED] wrote:
Martin Spott wrote:
Erik Hofman wrote:
Update of /var/cvs/FlightGear-0.9/data/Aircraft/T38
In directory baron:/tmp/cvs-serv23354
Modified Files:
T38.xml
I'd vote for a modification of the 3D model. The cones behind the
engines don't
Martin Spott wrote:
and _if_ they appear the probably should be sort of yellow/orange,
not white,
Not really, the T-38 doesn't have an afterburner.
It's meant to be the heath buildup that disturbs the airflow and hence
influences the visibility in the specific area.
Erik
Erik Hofman [EMAIL PROTECTED] wrote:
Update of /var/cvs/FlightGear-0.9/FlightGear/src/Cockpit
In directory baron:/tmp/cvs-serv26208
Modified Files:
panel.cxx
Although this improves the altimeter display in the default aircraft,
the c310u3a-3d looks a bit strange now at my end:
Erik Hofman [EMAIL PROTECTED] wrote:
It's meant to be the heath buildup that disturbs the airflow and hence
influences the visibility in the specific area.
Personally I consider the cones a bit dominant for this purpose,
Martin.
--
Unix _IS_ user friendly - it's just selective about who
Erik's right. The cones are supposed to represent a mirage effect from
heat, which actually exists but isn't cone shaped. The real effect looks
like a tube for a very short distance then becomes turbulent and blends in to
the atmosphere (and is carried downwind). In the daytime the plume
On Mon, 15 Sep 2003 19:06:10 +0200
Arnt Karlsen [EMAIL PROTECTED] wrote:
Are we still interested in migration to LibSDL? (cause I am ;))
..shoot! Whoever codes it gets the credit for it. ;-)
I've got an version sort of working using SDL_mixer. Unfortunately neither
SDL nor SDL_mixer have
David Megginson [EMAIL PROTECTED] wrote:
Norm is right that the only robust solution is to build a big, central
database-driven GIS repository, where we can check out individual
polygons, lines, and elevation points, edit them, and then check them
back in again (preferably in a distributed
Martin Spott writes:
I wonder how long it takes until someone imports the world's SRTM data
into GRASS (with a networked database backend like PostGIS).
AFAIK lots of people are doing this
I assume
quite a few people not related to FlightGear already have data that
could be merged.
Norman Vine [EMAIL PROTECTED] wrote:
Martin Spott writes:
I wonder how long it takes until someone imports the world's SRTM data
into GRASS (with a networked database backend like PostGIS).
AFAIK lots of people are doing this
Do you suggest we should do so too ? Why don't people share
Nick [EMAIL PROTECTED] said:
Good evening,
Just as a matter of professional technique, the pilot's opinion is the =
last place to go for verification. Do every possible thing you can to =
He he...an airliner pilot that designs flight dynamics models in his spare
time may not totally agree
Jim Wilson wrote:
Erik Hofman said:
Martin Spott wrote:
Although this improves the altimeter display in the default aircraft,
the c310u3a-3d looks a bit strange now at my end:
http://document.ihg.uni-duisburg.de/bitmap/FGFS/Panel_04.png
I don't get it. Is this OpenGL implementation dependent or
Jim,
Maybe so, but the Boeing test pilots I worked with
were OK with it. They realize that they are uncalibrated and adaptive
(with few notable exceptions).
Nickolas HeinMorgantown WV
- Original Message -
From:
Jim Wilson
To: FlightGear developers
discussions
Erik Hofman [EMAIL PROTECTED] wrote:
Martin Spott wrote:
Although this improves the altimeter display in the default aircraft,
the c310u3a-3d looks a bit strange now at my end:
http://document.ihg.uni-duisburg.de/bitmap/FGFS/Panel_04.png
What depth buffer do you have? I tested it with my
Erik Hofman [EMAIL PROTECTED] wrote:
Update of /var/cvs/FlightGear-0.9/FlightGear/src/Cockpit
In directory baron:/tmp/cvs-serv3773
Modified Files:
panel.cxx
Log Message:
Try to prevent z-buffer problems for video cards with a 16-bit depth buffer
_Slight_ improvement on a 24 bpp
The 3D model is not that far yet. I'm not very good when it comes to
modelling. Its completely made in blender (2.27).
No movable parts yet. I realized that the ac-export python script does
not use the names for the meshes that are given in blender.
Is anyone else using only blender to create
Bernie Bright wrote:
On Mon, 15 Sep 2003 19:06:10 +0200
Arnt Karlsen [EMAIL PROTECTED] wrote:
Are we still interested in migration to LibSDL? (cause I am ;))
..shoot! Whoever codes it gets the credit for it. ;-)
I've got an version sort of
Martin Spott wrote:
Erik Hofman [EMAIL PROTECTED] wrote:
Update of /var/cvs/FlightGear-0.9/FlightGear/src/Cockpit
In directory baron:/tmp/cvs-serv3773
Modified Files:
panel.cxx
Log Message:
Try to prevent z-buffer problems for video cards with a 16-bit depth buffer
_Slight_ improvement on a
Nick [EMAIL PROTECTED] said:
Jim,
Maybe so, but the Boeing test pilots I worked with were OK with it.
They realize that they are uncalibrated and adaptive (with few notable
exceptions).
Nickolas Hein
Morgantown WV
True. I think the problem (in my experience) is often the lack of
Erik Hofman [EMAIL PROTECTED] wrote:
Update of /var/cvs/FlightGear-0.9/FlightGear/src/Cockpit
In directory baron:/tmp/cvs-serv8404
Modified Files:
panel.cxx
Log Message:
Don't just disable depth buffer writes but instead disable the depth test all
together
By accident my message
Hallo!
When trying to start fgfs --airport=KEMT I get:
WARNING: ssgLoadAC: Failed to open
'/fg_root/Aircraft/c172/Models/c172-dpm.ac/Aircraft/c172/Models/c172-dpm.ac'
for reading
with current SimGear/FlightGear CVS.
The attached patch fixes the problem, since sgLoad3DModel expects
fg_root as
Jim,
Make your best effort to find the data before you have a pilot take a look at it. If
you'd like I can try some of my sources at Boeing - I think they might still talk to
me.
Nick
From: Jim Wilson [EMAIL PROTECTED]
Date: 2003/09/16 Tue AM 11:16:33 CDT
To: FlightGear developers
Martin Spott writes:
Curtis L. Olson [EMAIL PROTECTED] wrote:
I am just commiting an additional command line option to specify a
starting time of day in the sense of:
Did you probabliy mix up other options ? I usually run FlightGear with
--start-date-lat=2002:04:11:11:11:11 and enjoy a
On 16 Sep 2003 08:39:26 GMT,
Martin Spott [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]:
Erik Hofman [EMAIL PROTECTED] wrote:
Update of /var/cvs/FlightGear-0.9/data/Aircraft/T38
In directory baron:/tmp/cvs-serv23354
Modified Files:
T38.xml
I'd vote for a modification
On Tue, Sep 16, 2003 at 05:08:15PM +0200, Matevz Jekovec wrote:
The 3D model is not that far yet. I'm not very good when it comes to
modelling. Its completely made in blender (2.27).
No movable parts yet. I realized that the ac-export python script does
not use the names for the meshes that
On Mon, Sep 15, 2003 at 10:19:45PM -0500, David Culp wrote:
I'd like to hear what you think. (esp. concerning the flightmodel)
Very nice! I took it around the pattern once, and it flies well.
I'll fly it some more later. Off hand I'd say it needs a little more drag
when fully
On Mon, Sep 15, 2003 at 11:33:44PM -0400, Nick wrote:
Good evening,
Just as a matter of professional technique, the pilot's opinion is the last place to
go for verification. Do every possible thing you can to check your results
objectively. Then tell the pilot you've done every possible
Manuel,
If you find errors in the MSFS let me know. I
have a friend who is a developer there, on CFS but he talks to the MSFS guys
too. Just for information he is a fully-trained (Kansas Univ.) engineer
who used to do aero model development for Boeing. Also a great guy.
I used to go to
Manuel Bessler writes:
Sure, if a model flies 'by the numbers' is a good start, but there
are other properties that need to be simulated well for a good
model, esp. outside of cruise (cruise is probably the simplest
part).
It's all numbers, of course: it's just that the numbers for the
Curtis L. Olson [EMAIL PROTECTED] said:
Did you probabliy mix up other options ? I usually run FlightGear with
--start-date-lat=2002:04:11:11:11:11 and enjoy a nice morning. After
I just checked in some changes that may or may not help your
situation.
Hi Curt,
Starting with
35 matches
Mail list logo
