FYI
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Craig Bruce
Sent: Tuesday, September 23, 2003 1:39 AM
To: [EMAIL PROTECTED]
Subject: [wms-dev] CWXML-BXML library release
For anyone who may be interested, CubeWerx has made a public beta release
Me too, except I get it every time (well three out of three).
Cygwin, W2K, recent CVS.
I get a normal startup as far as the first set of morse beeps, then the error that
David sees, and back to a prompt.
Different aircraft and airports make no noticable difference.
Richard
-Original
Richard Bytheway wrote:
Me too, except I get it every time (well three out of three).
Cygwin, W2K, recent CVS.
I get a normal startup as far as the first set of morse beeps, then the error that David sees, and back to a prompt.
Different aircraft and airports make no noticable difference.
From:
On 9/23/03 at 10:32 AM Erik Hofman wrote:
I think it is fixed now. Thanks for the report, it looks like that made
it easier to track the problem down.
It turned out to be a combination of the reorganization, un-initialized
variables and the wrong function call order in the update() function.
On Mon, 2003-09-22 at 23:00, Norman Vine wrote:
FYI
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Craig Bruce
Sent: Tuesday, September 23, 2003 1:39 AM
To: [EMAIL PROTECTED]
Subject: [wms-dev] CWXML-BXML library release
For anyone who
I think I would like to start prepairing for the 0.9.3 release of
FlightGear. Lot's of stuff has changed, and the latest scenery works
slightly better with the current cvs code.
Thanks,
Curt.
--
Curtis Olson HumanFIRST Program FlightGear Project
Twin Citiescurt 'at'
Curtis L. Olson wrote:
I think I would like to start prepairing for the 0.9.3 release of
FlightGear. Lot's of stuff has changed, and the latest scenery works
slightly better with the current cvs code.
What is the timeline you have in mind?
I am working on a reorganization of the subsystem-, and
I think I would like to start prepairing for the 0.9.3 release of
FlightGear.
Two new key bindings are needed for the JSBSim turbine engine, and since key
bindings can be a bit contentious I thought I'd open it up for debate. I
personally don't care what keys are used. Both bindings will
David Culp wrote:
I think I would like to start prepairing for the 0.9.3 release of
FlightGear.
Two new key bindings are needed for the JSBSim turbine engine, and since key
bindings can be a bit contentious I thought I'd open it up for debate. I
personally don't care what keys are used.
I'm seeing runway/taxiway misalignment at two airports in the base scenery,
latest CVS Simgear/Flightgear/data. The offenders are KPAO and KSQL, KSQL
being particularly bad. Is anyone else seeing this, or just me?
Cheers - Dave
___
Flightgear-devel
For the starter you could use the default keys, but slightly modified in
the -set.xml file for JSBSim turbine driven aircraft.
I tried that once, but ran into a catch. I can override values that are
already defined, and I can define new values, but I couldn't figure out how
to erase
David Culp wrote:
For the starter you could use the default keys, but slightly modified in
the -set.xml file for JSBSim turbine driven aircraft.
I tried that once, but ran into a catch. I can override values that are
already defined, and I can define new values, but I couldn't figure out how
to
Curtis L. Olson [EMAIL PROTECTED] wrote:
I think I would like to start prepairing for the 0.9.3 release of
FlightGear. Lot's of stuff has changed, and the latest scenery works
slightly better with the current cvs code.
Nice to hear - I hope I'll get the manual up to date in time. There are
a
3.) fix several aircrafts: For example thos who are supposed to have a
speed brake should really have a working one.
Yeah, my J-22 has speed brakes (modeled and animated correctly), but
shift+b doesn't do anything? This should really be fixed...
- Matevz
Yeah, my J-22 has speed brakes (modeled and animated correctly), but
shift+b doesn't do anything? This should really be fixed...
Try Ctrl-B. Does your keyboard have that?
Dave
--
David Culp
[EMAIL PROTECTED]
Matevz Jekovec [EMAIL PROTECTED] wrote:
3.) fix several aircrafts: For example thos who are supposed to have a
speed brake should really have a working one.
Yeah, my J-22 has speed brakes (modeled and animated correctly), but
shift+b doesn't do anything? This should really be fixed...
Martin Spott [EMAIL PROTECTED] said:
Matevz Jekovec [EMAIL PROTECTED] wrote:
3.) fix several aircrafts: For example thos who are supposed to have a
speed brake should really have a working one.
Yeah, my J-22 has speed brakes (modeled and animated correctly), but
shift+b
Am Dienstag, 23. September 2003 19:51 schrieb Martin Spott:
Curtis L. Olson [EMAIL PROTECTED] wrote:
I think I would like to start prepairing for the 0.9.3 release of
FlightGear. Lot's of stuff has changed, and the latest scenery works
slightly better with the current cvs code.
Nice to
On Tuesday 23 September 2003 20:05, Jim Wilson wrote:
Martin Spott [EMAIL PROTECTED] said:
Matevz Jekovec [EMAIL PROTECTED] wrote:
3.) fix several aircrafts: For example thos who are supposed to have a
speed brake should really have a working one.
Yeah, my J-22 has speed
Jim Wilson [EMAIL PROTECTED] wrote:
We may find that we'll need to have certain keys reserved for per aircraft
definitions, rather than modifying (overriding) global key input properties,
at least for the time being.
I'd say everything is welcome that is backed by some structure that
On Tuesday 23 September 2003 11:40 am, Curtis L. Olson wrote:
I think I would like to start prepairing for the 0.9.3 release of
FlightGear. Lot's of stuff has changed, and the latest scenery works
slightly better with the current cvs code.
Thanks,
Curt.
Standing by
Lee Elliott wrote:
Has anyone made up a list of all the controls that need er... controling?
I'm inclined to think that we need to clearly identify all the requirements
before planning the schemes.
FlightGear/docs-mini/README.properties
Pick your favorite...
Erik
Martin Spott wrote:
Shift-b _schould_ toggle the parking brake and it does so on _most_
aircrafts - some by LeeE have additional very nice gimmicks. Someone
posted Ctrl-b for the speed brake but none of the aircraft that I tried
has a working one.
The F-16 and Fokker 100 have a working
On 9/23/03 at 5:22 PM David Luff wrote:
I'm seeing runway/taxiway misalignment at two airports in the base
scenery,
latest CVS Simgear/Flightgear/data. The offenders are KPAO and KSQL, KSQL
being particularly bad. Is anyone else seeing this, or just me?
Hmm, comparing the old default.apt
David Luff writes:
Hmm, comparing the old default.apt with the new runways.dat for KSQL, it
appears that the runway orientation has been altered to be correct now (and
presumably the position also) but that the taxiways have been left as they
were. I can redo the taxiway positions and
On 9/23/03 at 6:15 PM Curtis L. Olson wrote:
The best thing to do would be to submit runway/taxiway data reports
(and fixes if possible) to Robin Peel. He runs the master data
repository and that's where the data ultimately needs to be fixed.
I agree, and I'll definately send in revised
On Tuesday 23 September 2003 22:17, Erik Hofman wrote:
Lee Elliott wrote:
Has anyone made up a list of all the controls that need er... controling?
I'm inclined to think that we need to clearly identify all the
requirements
before planning the schemes.
So far I've just removed some duplication and a binding that doesn't seem to
be used anywhere (see log).
If someone has the TeX utils (and tex4ht) setup on their system, the
FGShortRef.* could use an update. Attached below is a list of changes that
need to be made.
If noone steps up to update
Jim Wilson writes:
Also F8 (Cycle fog type) and F9 (toggle textures) no longer work. Should thes
bindings be removed?
F8 seems to work on my machines
Sigh It looks like F9 needs to get fixed again.
This is a *very* useful essential debugging feature
for anyone interested in seeing what
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
On Wednesday 24 September 2003 02:13, Dave Perry wrote:
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
I noticed this
31 matches
Mail list logo
