Jim Wilson wrote:
What happens on a kill/int/segfault? Can it be changed to something like a
single pixel or some other unobtrusive thing instead?
That should work also because it is changed to the normal cursor in the
atexit() function (but I haven't tested it because it doesn't happen for
me,
Erik Hofman wrote:
Curtis L. Olson wrote:
What specific changes are you refering to?
Fixes for the Scenery Loading dialog that now loads much faster on low
end hardware because it is frame rate independent (thanks to Frederic).
Lots of small fixes (joystick configurations, Nasal fuel handling
Erik Hofman wrote:
Update of /var/cvs/FlightGear-0.9/FlightGear/src/Main
In directory baron:/tmp/cvs-serv21379
Modified Files:
metar_main.cxx
Log Message:
Some code cleanups, and add a number of command line options.
In this context an idea comes to my mind: Would'nt it be useful
Melchior FRANZ wrote:
Here's another problem: $ fgfs --aircraft=c172-610x-jsbsim makes fgfs
abort, because this redirects to ../c172r/c172r-jsbsim-base.xml, which
tries to include c172r-base.xml. But this file is searched in c172/, not
in c172r (where it could be found).
This is fixed in CVS
Erik Hofman wrote:
Erik Hofman wrote:
Curtis L. Olson wrote:
What specific changes are you refering to?
Fixes for the Scenery Loading dialog that now loads much faster on low
end hardware because it is frame rate independent (thanks to Frederic).
Lots of small fixes
* Martin Spott -- Tuesday 17 August 2004 11:09:
In this context an idea comes to my mind: Would'nt it be useful to let
'metar' honour the respective parameters in a ~/.fgfsrc file (proxy
settings for example) in the same the way, 'fgfs' does !?
Useful?yes
Feasible? hmm
This would involve
Melchior FRANZ wrote:
* Martin Spott -- Tuesday 17 August 2004 11:09:
In this context an idea comes to my mind: Would'nt it be useful to let
'metar' honour the respective parameters in a ~/.fgfsrc file (proxy
settings for example) in the same the way, 'fgfs' does !?
Useful?yes
* Martin Spott -- Tuesday 17 August 2004 12:24:
I thought one might encapsulate the respective FG functions into a lib
and link 'metar' against it Just a quick idea - please
disregard.
I've done the environment thing. Works well and doesn't require to mess with
the libs. Also, it's more
Melchior FRANZ wrote:
As far as I've learnt meteo stuff (I have my theoretical test wednesday
morning :-/ CAVOC translates into visibility 10 km (~ 7 miles) or
greater and no clouds below 5000 ft GND. I thought, clear skies is
being abbreviated by SKC,
Sure. Don't be so picky! ;-)
Erik Hofman wrote:
Kalle Valo wrote:
Erik Hofman [EMAIL PROTECTED] writes:
I was wondering, do others feel that the changes in the last week or
so justify a new release (0.9.5-1)?
If you are going to make a new release, just don't name it 0.9.5-1,
please. That would create lots of confusion for
Frederic Bouvier wrote:
Are you sure js changes are fixes ? I saw problem reports recently.
They seem to have been fixed. But I wouldn't know, I don't have a joystick.
I don't update plib for ages and I am not keen to do it after what I read.
Moreover, we rely on plib released versions, not CVS,
There were already few discussions about this a couple of months ago
when terrasync was launched.
My question is when I run terrasync and fgfs and fly where there's no
terrain available yet, do I need to restart fgfs session for the new
terrain to take effect, or are fgfs and terrasync already
Matevz Jekovec wrote:
Why not simply name it 0.9.5.1 (latest kernel is 2.6.8.1 as well as they
found a tiny bug in 2.6.8 version). Letters behind a version could mess
with things like a for Alpha, b for Beta, RC for Release Candidate and
so on. I think 0.9.5.1 is the only logical explenation to
Matevz Jekovec wrote:
There were already few discussions about this a couple of months ago
when terrasync was launched.
My question is when I run terrasync and fgfs and fly where there's no
terrain available yet, do I need to restart fgfs session for the new
terrain to take effect, or are fgfs
* Matevz Jekovec -- Tuesday 17 August 2004 14:29:
My question is when I run terrasync and fgfs and fly where there's no
terrain available yet, do I need to restart fgfs session for the new
terrain to take effect, or are fgfs and terrasync already synchronized
now and is the new terrain
Erik Hofman wrote:
Update of /var/cvs/FlightGear-0.9/FlightGear/src/Main
In directory baron:/tmp/cvs-serv1037
Modified Files:
metar_main.cxx
Log Message:
The next version of the two hourly metar update from Melchior: add proxy handling.
Melchior FRANZ wrote:
* Martin Spott -- Tuesday 17 August 2004 12:24:
vpngw: 12:07:27 ~ bin/metar -v EDLN
INPUT: 2004/08/17 08:50
EDLN 170850Z VRB03KT CAVOK 22/17 Q1008
METAR Report ^
[...]
Sky condition: clear skies
* Martin Spott -- Tuesday 17 August 2004 15:28:
I just realized you already calculate the rel. humidity from
temperature and dewpoint. You could calculate the cloud base from these
two numbers and the airport elevation as well - at least our instructor
taught us to do so in case of of doubt.
Melchior FRANZ wrote:
* Matevz Jekovec -- Tuesday 17 August 2004 14:29:
My question is when I run terrasync and fgfs and fly where there's no
terrain available yet, do I need to restart fgfs session for the new
terrain to take effect, or are fgfs and terrasync already synchronized
now
Erik Hofman said:
Matevz Jekovec wrote:
Why not simply name it 0.9.5.1 (latest kernel is 2.6.8.1 as well as they
found a tiny bug in 2.6.8 version). Letters behind a version could mess
with things like a for Alpha, b for Beta, RC for Release Candidate and
so on. I think 0.9.5.1 is
* Erik Hofman -- Tuesday 17 August 2004 10:53:
Not to mention a number of fixes in plib (including rather important
joystick fixes) and fgrun.
Oh, and not to mention the addition of the wonderful Spitfire and the
Concorde, both of which IIRC didn't make it into 0.9.5. :-)
m.
Jim Wilson wrote:
Erik Hofman said:
Matevz Jekovec wrote:
Why not simply name it 0.9.5.1 (latest kernel is 2.6.8.1 as well as they
found a tiny bug in 2.6.8 version). Letters behind a version could mess
with things like a for Alpha, b for Beta, RC for Release Candidate and
so on. I
Curtis L. Olson wrote:
I usually plan on a full week of *all* my non-work spare time plus some
to get a release out. Right now I'm getting hammered at work and at
home so I don't have *any* spare time. I have to go out of town for the
entire weekend which means I'll be playing catchup most of
i started looking at flight gear hoping that there would be a way to get
at
system internals from outside the box so that i could build my own
simulated
radio stack and hook it up.
can anyone tell me if there is already a part of your project devoted to
this,
or if you think it's even
Just a thought : on windows, there is a system call that enable a program to
receive events when a files in a subtree changes. I don't know for Linux and
other unix though. I already heard about something called FAM but I don't
know if it is built in the kernel now. And I have no idea about the
Matevz Jekovec wrote:
Just a thought : on windows, there is a system call that enable a
program to
receive events when a files in a subtree changes. I don't know for
Linux and
other unix though. I already heard about something called FAM but I
don't know if it is built in the kernel now. And I
Terrasync started out as a one-evening hack/demonstration so it was
never intended to be a full fledged solution and cover every angle and
possibility.
Yeah, but found itself a very useful tool among fgfs users. Maybe even a
start of multiplayer gaming, which includes terrain downloading from
27 matches
Mail list logo
