I notice that 0.9.9 scenery is available from several mirrors. Is there
an rsync capable site for Scenery-0.9.9?
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Since a
cvs update -dP
and recompile of cvs plib, cvs SimGear, cvs fgfs, and data, I am getting
the following error in the Log Window when I run fgfs from fgrun.
fgfs:freeglut_window.c:300:fgOpenWindow:Assertion
'window-Window.VisualInfo != ((void*)0)' failed
I am running Fedora Core 3 that
Curt Olson wrote:
One dumb thing to check if you run nvidia hardware. If you upgraded
your kernel or other libs with up2date you might have overwritten parts
of your opengl driver installation (at least with the nvidia drivers
this can happen.) It might be worth verifying that you can run
After noting Sid Boyce note concerning freeglut on the users list where
~/.fgfsrc was the issue, I renamed that file and fgfs worked. Then I
checked which option in fgrun would cause the freeglut abort. The only
problem option I found is
--enable-clouds3d
Same result from the command line.
. In the Render menu, it looks like the 3D Clouds is grayed
out.
Is this now a hard wired default in CVS?
... Dave Perry
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
.
This will go on until I stop it with the start-up window shoing the text
loading scenery objects.
This bug showed up about 10 days ago with an update from cvs. Any ideas
what is broken?
Regards,
Dave Perry
___
Flightgear-devel mailing list
Flightgear
I did some more experimenting with two different Linux installs updated
to yesterday's CVS (plib, SimGear,fgfs, and $FG_ROOT). All the jsbsim
aircraft that I tried cause fgfs to hang at the same place when starting
from airports from w110n40.tgz. None of the yasim aircraft I tried have
this
This bug showed up when I updated from CVS last weekend. Description
follows:
(1) With the default c172, fgfs hangs with the loading scenery
objects is displayed if --airport= (any airport from w110n40) It does
not hang for the j3cub or the pa28-161.
(2) With (atleast som) airports outside
of the wind shear and strong head winds on
the approaches, all the power setting I normally use at different points
in the approaches were different. My commercial rating is now worth
something again.
Thanks to the entire FlightGear team for a great simulator with real
world applicability!
Dave
For the last several days I have been getting the following error when
compiling fgrun from cvs.
main.o(.text+0x18e): In function `main':
/usr/local/source/fgrun/src/main.cxx:87: undefined reference to `Fl::lock()'
So I removed all the files and do a clean co from cvs. I still get the
same
I updated fgfs and SimGear from cvs last evening and now fgrun aborts.
I compiled fgrun from the 0.4.5 tarball. This is under FC2 linux.
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
version=1.0 encoding=UTF-8?
!-- Maintainer: Dave Perry --
PropertyList
nameCH PRODUCTS CH FLIGHT SIM YOKE USB /name
nameCH FLIGHT SIM YOKE USB /name
axis n=0
descAileron/desc
binding
commandproperty-scale/command
property/controls/flight/aileron/property
power2.0/power
/binding
/axis
I just updated plib, SimGear, fgfs from cvs and it ran fine with last
weeks base package. Then I updated the base package and I get a segfault.
I will try to get more info with log level debug set.
Dave P
___
Flightgear-devel mailing list
[EMAIL
mine, then using
name ... /name, we could have two different files that
have the right propeller and mixture axis for both.
Also, I am attaching the edited pro-yoke-usb.xml file. It would be an
improvement for both linux and windows users if this were added to cvs.
Regards,
Dave Perry
?xml
P4 notebook with up2date Fedora Core2 and
Friday cvs.
Anyone else having this problem?
Thanks for any help,
Dave Perry
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
in 9.5a.
By the way, I really liked the paint on the A-10's, f16, and many other
improvements in the ac inventory!
Thanks to the entire team!
Dave Perry
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear
I just updated plib, SimGear, fgfs, and the base package from cvs. Both
js_demo and fgfs dont identify my CH Flight Sim Yoke and my Pro Pedals,
both USB. js_demo shows just for the name of both. jstest
identifies both correctly. I tried and old js_demo and it worked as
usual. Does anyone
David Megginson wrote:
Thanks for the feedback. I have a book deadline looming, so I don't have
any big chunks of time free until after the 9th, but if you feel like
tweaking the J3 Cub and DC-3 files until you like the handling better, I'll
be happy to commit the changes. Ideally, we want
Jim Wilson wrote:
Run with --log-level=debug to see which SubSystem that occurs in. Could be an
xml bug.
I did. Here is where it aborts:
Finally initializing fdm
Start common FDM init
...initializing position...
...initializing ground elevation to -2.67116ft...
...initializing sea-level
Vivian Meazza wrote;
/Have you tried the Spitfire yet?
//
//I would be grateful for any comments you might have.
//
//
//
/I had flown it for the first time last night, but mostly at altitude.
Very maneuverable and feels like a high performance ac wrt aileron -
rudder coordination.
Since
David Megginson wrote:
This problem has little effect on normal flight, but it matters a lot for
the landing and takeoff rolls of taildraggers -- without it, they have an
unrealistic tendency to nose over.
I have been tied up with an upgrade to SuSe 9.1 and wanted to comment on
the tail
fgfs aborted with the dc3.
[EMAIL PROTECTED]:/usr/local/FlightGear ./bin/fgfs --aircraft=dc3
Object TrimElevation not found
Initializing OpenAL sound manager
Oops AL error in sample set_volume()! -0.2 for
/usr/local/FlightGear/Aircraft/dc3/Sounds/engine_running.wav
Oops AL error in sample
I am attaching an edit of this file that should work with either Windows
or Linux. As of a few days ago, the CVS file did not work at all.
Would a Windows person with this joystick try it and then it could be
included in the release.
Dave P.
!--
Joystick binding definitions for Saitek Cyborg
Help!
Since my CH Yoke and Pedals don't work with the new joydev driver in
Suse 9.1, I need to use my Saitek Cyborg Evo joystick. Both js_demo and
jstest show all it's axes and buttons working but ony the non DEFANGED
functions work in FlightGear (that is aileron, elevator and rudder ...
no
Perhaps this has been discussed before, but I just updated my SuSe Linux
to 9.1 pro and the various autogen scripts are not working right. The
following errors occurred after updating plib from cvs and runing autogen:
cvs update -dP
dadsoffice:/usr/local/source/plib # sh autogen.sh
Running
I just tried to practice the ILS RWY 30 approach into KLBF (Lee Bird
Field at North Platte, Nebraska) since I plan to be there this week.
When I tune nav1 to 111.5, no response. So I gunzip nav.dat.gz, and
search on ILBF and sure enough the LLZ record is there with the right
frequency and
David Megginson wrote:
William Earnest wrote:
/ Another small feather for FlightGear's rather large hat. Today I
// passed my instrument rating checkride, significantly helped by the
// program in forming a decent scan and control by panel. It certainly
// reduced the number of lessons and
Curt Olson wrote:
It could be that some glide slope elevations are off in the new nav
data. Check that nav.dat file and compare the elevation of the GS vs.
the field elevation and see if there is any major discrepancy ...
As I indicated in my other post, I checked the elevations in
I posted the following near the end of May.
At least some of the glide slopes are now not working that were before
this change.
The glideslope at KSFO is working.
The glideslope at Greeley, CO (I-DCI, 110.3) never comes off pegged at
the bottom (saying you are high).
Same comment for the
Curt Olson wrote:
The last two days I've been hammering on the nav database code. My
first goal is to directly support Robin's native nav database file
format. In his latest data release, he separates out dme, gs, loc, and
marker beacon transmitters rather than lumping them all into a single
a better derivation?
Not complaining, just trying to help.
Dave Perry
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
several other AC and did hear a change with the throttle for the
hunter, but still get the ame repeating error.
Is anyoune else seeing similar errors?
Dave Perry
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman
with this update.
Dave Perry
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
),
there is a fairly large drop off or shear in the scenery. This area for
real is very flat.
Hope these examples help.
Dave Perry
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
in the current scenery just west of
Des Moines.
Not complaining,
Dave Perry
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
directory `/usr/local/source/source/src/Main'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/usr/local/source/source/src'
make: *** [install-recursive] Error 1
I have tried using --with-jpeg-factory in the SimGear configure, but
still get a similar error.
Any ideas?
Dave Perry
United captian as my instructor.
It is clear to me that fgfs made this much easier.
Thanks,
Dave Perry
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
delete queue
fgfs: ssg.h:288: void ssgBase::deadBeefCheck(): Assertion `type != (int)
0xDeadBeef' failed.
Aborted
Regards,
Dave Perry
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Jim Wilson said:
I'm going to take a stab in the dark and say this probably won't happen if you
do not activate glide slope hold.
I just reflew this flight from Battle Creek to Kalamazoo, MI including
the precision approach to RW 35 at KAZO with out terrasync or atlas.
No abort this time. At
I updated from cvs last night and noticed that both the j3cub and the
dc3 no longer converge in yasim. I checked several other yasim
aircraft, and their models all converged. (an225, a10, p51d, and
c172). Has anything changed in yasim?
Dave Perry
I updated plib, SimGear, FlightGear, and the base package from cvs
Thursday evening. Now the 3d model for the default c172 is very
angular. I don't see this on the other models.
Regards,
Dave
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
I have posted this observation before. but since the topic came up
again, I will post this again.
I have the hat switch configured so it allows smooth changes in vies
as if I am moving my head (hen inside the plane) or moving my view point
and view direction in an outside view.
When in an
the pull-down frequencies,
but the radio panel display is still wrong.
Is this just a temporary artifact of the binding change over to Nasal?
Merry Christmas and happy holidays to all!
Dave Perry
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http
Paul Surgeon wrote:
Can someone recommend a nVidia based card that works flawlessly with FG?
I'm on a tight budget so I'm looking at the low end cards.
Does FG run well on a FX 5200?
Paul,
I have experience with the original GF3, the GF4 MX440, the FX 5200, the
FX 5600, and the FX 5600 Ultra
-line
Windows users a lot.
Dave Perry
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
The recent changes from default.apt.gz to basic.dat.gz and
runways.dat.gz breaks the use of Atlas. Even the CVS Atlas is still
looking for default.apt.gz. Will we try to update Atlas before the
FG9.3 release?
Dave
___
Flightgear-devel mailing list
This is really a question.
I live near Jeffco (KBJC) half way between Denver and Boulder, CO and
often shoot practice ILS approaches in fgfs in this area. The new
scenery, etc., make Jeffco much more realistic from the air. There used
to be a huge hump in the middle of 29R (the main ILS
Matevz Jekovec wrote:
Do you have libjpeg installed and did you run SimGear ./configure
--with-jpeg-factory ?
Thanks,
That solved the problem. When did this become required?
Back in the air,
Dave Perry
___
Flightgear-devel mailing list
[EMAIL
Updated plib, SimGear, FlightGear (source) from cvs. Got the following
error compiling FlightGear.
make[2]: Entering directory `/usr/local/source/FlightGear/src/Main'
g++ -DPKGLIBDIR=\/usr/local/FlightGear/lib/FlightGear\ -g -O2 -D_REENTRANT
-L/usr/X11R6/lib -o fgfs bootstrap.o
up on the mains early in the acceleration roll like the real ac does.
Was there a reason for the changes to hstab an vstab that I am missing?
A big dc3 fan,
Dave Perry
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman
is to address wash out? If
so, who should I give feedback to as I think the twist does not wash out
both wings.
Thanks,
Dave Perry
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Dave Perry wrote (but never attached the file):
David Megginson writes:
Monday evening I updated SimGear, the source, and data from cvs. The
dc3.xml file in Aicraft-yasim was changed for the worse (IMHO).
I'll be happy to put it back to what it was, but it might be better if
you could spend
David Meggison wrote:
I also find the DC-3 a little
harder to control on takeoff, and am considering increasing the rudder
effectivity a bit, but as far as I know, *all* taildraggers are
naturally unstable on the ground when the tailwheel pops up (i.e. any
turn automatically increases unless
Sunday, June 22, I put fgfs from cvs on my Dell Latitude
2.2 GHz P4 with 512 MB, on board nvidia GF4, and RH9.0 Linux.
HW Browser shows 82801CA/CAM AC'97 Audio with i810_audio driver
dmesg shows the driver can support 6 channels but then defaults to 2
channel mode.
lsmod shows that soundcore,
David Megginson wrote:
Are you modifying /controls/aileron-trim or /controls/flight/aileron-trim?
David,
The c172p-3d only has one place in the
/file/browse properties/controls/flight/aileron-trim[0]
drop down menu and with the updated base cvs, that option works. But
the c310u3a-3d gives
Jim Wilson wrote
The markings are almost readible on the trim wheel in this photo:
http://www.kiwiaircraftimages.com/pages/01mstg17.html
The words, neutral and elevator trim are clear enough, but I'm just
not sure about the four letters that mark the directions. It looks like
TN and NN.
The boost was missed in the pro-yoke-usb.xml update to the new
/controls/engines/engine[.]/boost
format. I made the obvious edits, tested the change with the dc3 which
is hard to fly in the Denver area w/o boost. That is why I noticed
this. Could some one commit this to the base cvs?
The
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
I updated plib and simgear from cvs yesterday and compiled both. This
evening updated FlightGear source from cvs and compiled. Then updated
the base package from cvs and then tried to launch the p51d. Got the
following error:
$ ./bin/fgfs --aircraft=p51d
Cannot open file:
Jim,
I had tried changing the version also. I copied in the config file you
posted and got further. But now it did not find the merlinV-1650 which
dod not come in with the cvs update to the base package.
Thanks,
Dave
Jim Wilson wrote
Dave,
After editing the the config file and putting 1.60
David Megginson wrote:
I've added support for wing twist to YASim. The twist allows you to
model washout during a stall, so that every stall doesn't result in a
violent spin. YASim also has an undocumented incidence property for
wings (in non-aerobatic planes, wings are not usually perfectly
David,
I flew the j3cub again and I take back my assesment of the climb and
glide. It appears that it starts with significant nose down trim.
I was also having trouble keeping it straight on the runway, but when I
gave it a lot of up trim, the tail came up and I could keep it straight
with
I updated SimGear, FlightGear, and the base from cvs and recompiled
today. Since then, all the c172 panels (both 2d and 3d) have two bugs.
1. The airspeed indicator does not work, and
2. The tachometer pointer looks like it is part of a dial. It does
rotate, just the wrong graphic.
Regards,
I just updated SimGear, FlightGear source, and base package from cvs.
Now when I try to change frequencies, the numbers to the right of the
decimal change mod 1, but the 1's, 10's and 100's didgits don't change.
I know there were changes made in this area. Did I miss updating
something?
Thanks to Norman Vine and Curt!
I did not find any stray copies of either SimGear of plib. the only
thing I did different in this update was to remove fgfs from
FlightGear/bin before I did make and make install. The cvs update of
all (plib, SimGear) was done last night and I updated
I updated plib, simgear, and FlightGear source from cvs this evening and
compiled plib and simgear with no problems. I get the following error
compiling FlightGear (at the compile of ground.cxx).
source='ground.cxx' object='ground.o' libtool=no \
depfile='.deps/ground.Po'
Erik wrote:
William Earnest wrote:
/ Dave Perry wrote:
/
/ Again, an old copy of the the base with bin/fgfs (compiled early in
// December) runs fine.
// Regards,
// Dave
/
I've sent a patch to Curtis which fixes a possible core dump when
/sim/systems/electrical/path has not been defined
Norman Vine Wrote:
Dave Perry writes;
/ Bill Earnest wrote:
// Norman Vine wrote:
// / Dave Perry
// //
// //Here is the last few lines before the segmentation fault.
// //
// //Loading tile /usr/local/FlightGear/Scenery/w010n00/w001n00/2938503 //
// // Did you update the fgBase files from
Norman Vine Wrote:
/ Can you post a backtrace from the debugger so we can see where
// it's crashing?
//
/
Dave Perry writes:
Here is the gdb text after the model is complete to the segfault:
JSBSim startup complete
VIEW
0.6839 0.2052 0.7001 0.
-0.5326 0.7962 0.2870 0.
Norman Vine wrote:
please enter 'backtrace full' in the gdb window immediately after
gdb reports the Segmentation fault and post the results
Dave Perry writes:
Here is the bactrace.
Tile not found (Ok if initializing)
scheduling needed tiles for -122.358 37.6117
load() base = /usr/local
Bill Earnest wrote:
Norman Vine wrote:
/ Dave Perry
//
//
//Here is the last few lines before the segmentation fault.
//
//
//Panel visible = 0
//Playing audio after 0 sec: rumble
//Playing audio after 0 sec: squeal
//Tile not found (Ok if initializing)
//scheduling needed tiles for -122.358
Here is the last few lines before the segmentation fault.
Panel visible = 0
Playing audio after 0 sec: rumble
Playing audio after 0 sec: squeal
Tile not found (Ok if initializing)
scheduling needed tiles for -122.358 37.6117
load() base = /usr/local/FlightGear/Scenery
Loading tile
I updated SimGear, FlightGear, and fgfsbase Friday the 13th in the
evening. I also updated the nvidia driver to 1.0-4191 using source
RPMS. After compiling the fgfs stuf and installing the new nvidia
drivers, I get a segfault trying to load the first tiles. I went back
to a version of
I like the c172p-3d 3d model and 3d cockpit a lot.
Three comments/concerns for the recent changes to the flight model:
1. The nose pitch-up when adding flaps seems extreem. If I don't
change the elevator trim a lot, the plane actually stalls. If I recall
correctly, the Piper Tri-Pacer
I updated SimGear, FlightGear, and the base from CVS yesterday. Since
then, I can't start the right engine and the throttle, prop speed, and
mixture have no affect (the pannel animations still move the levers, but
the RPM and manifold pressure stay at idel on engine[0] and pegged at
zero on
For the last 2 or 3 CVS updates (or for the last 2 weeks) I have been
getting regular
Segmentation faults right at touchdown with the dc3. The last few lines
of the
terminal output follow. Is anyone else seeing this?
Updating light parameters.
Sun angle = 59.873
ambient = 0.35 diffuse =
David Megginson wrote:
No, it was a bug-fix to model.cxx. I'll look at it when I get a
chance, but if someone else (Jim?) wants to fix it first, I don't plan
on complaining.
I used intuition from the new main gear rotation animations. I made the
following change to the four offset-deg
I updated Plib, SimGear, FlightGear, and the base from cvs tonight. The
dc3 main gear is not positioned properly by the animation in the latest
cvs. When you retract it, it goes to the proper gear down angle. When
it is extended the gear, it rotates even further.
I compared the dc3-dpm.xml
The lights look great!
The rear facing white light on the rudder is switched on with
the red and green wing tip lights as the nav lights. Is there a
RearNavLightOn and RearNav LightOFF object name?
- Dave P
___
Flightgear-devel mailing list
[EMAIL
I updated plib, simgear, and FlightGear sources, and well as fgfsbase
from cvs Sunday and
recompiled all source. I noticed that the dc3 pannel is black at night
except for the radio
lcds. I just updated via cvs both fgfsbase and FlightGear source and
recompiled
and the dc3 pannel is still
The c172-yasim pannel is lit at night, so this seems to be a change to
the dc3 only.
- Dave
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
I posted the following note to the Nvidia linux forum. The issue seems
to be an interaction between fgfs and the Nvidia driver.
NVIDIA linux foum post:
I am a FlightGear enthusiast. Over the past year I have run various
kernels with all the released nvidia linux drivers and various versions
I just installed the current development CVS for both SimGear and fgfs with
./config --with-threads and make and make install ok.
Also installed development CVS fgfsbase.
I did not update Plib from recent CVS. Still using plib-0.1.6.
Kernel is 2.4.18-10 RH7.3 and graphic card driver is
I installed the latest development plib tar file and recompiled fgfs.
No change.
The last 2 lines before the freeze:
Cannot open file: /usr/local/FlightGear/Scenery/Objects.txt
Initializing splash screen
The splash screen displays and remains the active window.
But the systme is frozen.
FWIW with the switch --disable-splash-screen, fgfs loads and runs ok.
Even with this switch, the splash screen displays, but no lock up.
-Dave
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
I have continued to work with the dc3.xml for yasim and some of the
numbers in the original file seem inconsistent with the 3D model. Here
are my questions:
1. Shouldn't the z value for the wing be -0.95 as the z for the wing is
for the root mid cord. This is a low wing. This matches the
Vikki,
I normally use a CH Product Flight Sim Yoke, but do have the Cyborg 3D
Gold USB. So I removed the yoke and plugged in the Saitek. I got
values from -0.8 to +0.2 or +0.3 on all four axies running js_demo
(usually in ../FlightGear/bin. Then I ran jscal /dev/js4 -c to do a
calibration
Vikki,
Concerning joysticks.xml for your Saitek.
I decided to go ahead and make a joysticks.xml file for this joystick
and try it out. This file is set up for 1 or 2 engines and it includes
buttons for flaps, propeller pitch, mixture, elevator trim, external
view cycle, and the hat is set up
Andy,
I put the main gear back at x=-6.02 and added a ballast under the
cockpit at 700 lbs and it handles very well. I even did some x-wind
take offs and landings. Here the locking tail wheel helps in the
initial acceleration. For strong x-winds, I think one uses differential
power (and
Didn't attach the xml.
Dave
airplane mass=16865
approach speed=58 aoa=13
control-setting axis=/controls/throttle[0] value=0.4/
control-setting axis=/controls/throttle[1] value=0.4/
control-setting axis=/controls/mixture[0] value=1.0/
control-setting axis=/controls/mixture[1] value=1.0/
Attched find an xml file dc3.xml that includes edits that allow
accelleration on the main gear and relativly easy wheel landings. With
these changes, I can leave the tail wheel unlocked for take-off and
landings.
Changes:
1. Relaxed the stall width for both the wing and the hstab. A dc3
I have been using FlightGear since 7.7 and have only recently begun to
follow the CVS snapshot. I worked my way through college and a flight
Instructor and have about 1500 hours in real ac. I also have flown many
tail-draggers. I agree with your view of the tail-dragger ac and pilots.
I
I added an effectiveness=nnn to both the htab and vtab. I was not
able to get good control once the tail was up w/o the change to vtab
also. I played arround with various values between 2 and 3.
I was able to get good control (vtab effectiveness) and early tail up
(htab effectiveness) with
93 matches
Mail list logo
