Steve Knoblock wrote:
On Tue, 08 Nov 2005 11:26:51 -0600, you wrote:
freeglut (fgfs): Failed to create cursor
freeglut ERROR: Function glutSetCursor called without first calling
'glutInit'.
I installed freeglut, all three packages found in the SuSE library.
Restarted and ran
Jim Wilson wrote
-Original Message-
If you contributed something that is missing, or poorly described here,
please send me something better.
Hi Curt,
This may not be helpful at this point (haven't been reading for a few
days).
Here's an addition:
* Material
Andy Ross wrote:
Again: I've run fairly rigorous tests on both Sparc and PPC at this
point with no failures, so I think we've pretty much ruled out
endianness.
Ok, I've test compiled the simgear/nasal library using gcc on IRIX and
linked it with the MIPSpro build version of FlightGear and
On Tue, 2005-11-08 at 17:16 -0800, syd wrote:
Andy, (or whoever is maintaining the b1900d), I hate to do this to you,
but I think I have spotted another bug to do with fuel and engines.
When you run out of fuel the engines continue to run, despite
/engine/engine/out-of-fuel[0]='true'
* Georg Vollnhals -- Tuesday 08 November 2005 21:00:
Melchior FRANZ schrieb:
but for now I think we can live with that.
That is ok, I think it should only be fixed before the new version gets
officially out.
You don't seem to understand: this is a very *minor*, almost cosmetic
glitch, and
Melchior FRANZ wrote:
The funny thing is, though, that nobody came up with an alternative
'theme' yet.
And why should one? The new style is very nice, not too intrusive when
flighing at night. And it works now, so what more coule one want?
Nine
* Georg Vollnhals -- Tuesday 08 November 2005 21:00:
[dynamic dialog components lost after them switching]
That is ok, I think it should only be fixed before the new version gets
officially out.
Oh, well. You just can't rely on what I say. I felt like fixing
that, too. Will commit later today.
Ima Sudonim wrote:
Next on the list are
the Nat. Cathedral, Basilica of the Immaculate Conception, Mormon
Temple, Pentagon and then the Mall. Not sure what timetable I'm looking
at though. If you can think of any other big visible structures that you
would like to see (sorry, I'm not
Melchior FRANZ schrieb:
one more serious problem:
- adjust HUD transparency
does not switch but after you leave the menue ('cancel') the *main*
How is this more serious? This is by *design* and was like that since
ages.
Melchior, you cut off the very *important* part of the
* Georg Vollnhals -- Wednesday 09 November 2005 17:11:
- does not switch but after you leave the menue ('cancel') the
*main* menue is frozen (no reaction on clicks)
In my eyes something is serious when you make a legal keypress and
afterwards a big part of the programs functions don't
Melchior FRANZ schrieb:
I didn't criticize that
you reported it -- that was the right thing to do. I just didn't share
your opinion that it had to be fixed for the next release. Someone
has to spend the time after all. And there will be a release after
0.9.9, or two. ;-)
m.
This is ok :-)
* Georg Vollnhals -- Wednesday 09 November 2005 17:39:
This is ok :-) - other priorities and limited time is an important factor!
After all, I am really happy with this new GUI style
And it's even fixed meanwhile, and I'm quite satisfied with the result.
(Now it even re-opens the Nasal
On Wednesday 09 November 2005 16:49, Melchior FRANZ wrote:
* Georg Vollnhals -- Wednesday 09 November 2005 17:39:
This is ok :-) - other priorities and limited time is an important
factor! After all, I am really happy with this new GUI style
And it's even fixed meanwhile, and I'm quite
* Thorben -- Wednesday 09 November 2005 20:22:
i patched my code to disable dialog boxes when making screenshots, because
they were quite annoying. shouldn't we do something about that in general?
I just made two nice shots for the screenshots page, which are *supposed*
to show menu and
Erik Hofman wrote:
Ok, I've test compiled the simgear/nasal library using gcc on IRIX
and linked it with the MIPSpro build version of FlightGear and it's
working like a charm.
great sigh of relief
Excellent. Thanks for your work, I was completely out of ideas on
this. :)
Ok, I've test
As some of you may have noticed, I completed a prerelease of
FlightGear-0.9.9(pre1) and SimGear-0.3.9(pre1). I haven't heard any
complaints about the prerelease, so I am planning to do a pre2 release
this week.
If all goes well and we have no major show stoppers, I would like to
start
Hi,
some time ago a new version of the joystick configuration file for
Logitech Wingman FF 3D was committed, containing a change to the
throttle-handling.
Shortly after that I couldn't get the engines down to idle. As I
noticed, jsdemo reports that the throttle axis returns +0.3 when on
Hello all,
I'm messing around with waypoints, ie race track loop around airports,
etc... but found the [EMAIL PROTECTED] command doesn't seem to work with
multiple waypoints altitudes... The plane eventually has it's own mind with
regard to what altitude it wants to fly. I also tried the
Using a Saitek stick, I've noticed a peculiar bug in the brakes which I
still haven't pinned down. The nasal function interpolate() works on left
wheel only, not the right wheel, making the plane twist when brakes are
applied (or released). One can see it by watching the internal properties
* Thorben -- Wednesday 09 November 2005 20:22:
i patched my code to disable dialog boxes when making screenshots, because
they were quite annoying. shouldn't we do something about that in general?
In case you mean the popups that have the annoying habit of not going away
when fgfs is paused:
[EMAIL PROTECTED] wrote:
I'm messing around with waypoints, ie race track loop around airports, etc... but found the [EMAIL PROTECTED] command doesn't seem to work with multiple waypoints altitudes... The plane eventually has it's own mind with regard to what altitude it wants to fly. I also
On Wednesday 09 November 2005 12:58 pm, Ralf Gerlich wrote:
...
some time ago a new version of the joystick configuration file for
Logitech Wingman FF 3D was committed, containing a change to the
throttle-handling.
Shortly after that I couldn't get the engines down to idle. As I
noticed,
Joacim Persson wrote:
Using a Saitek stick, [..] The nasal function interpolate() works on
left wheel only, not the right wheel, making the plane twist when
brakes are applied (or released). One can see it by watching the
internal properties (controls/gear) while applying the wheel
brakes.
I reserve the right to make the final determination (and all
non-included aircraft will still always be available for separate
download from the web site ...)
Given that new aircraft have arrived on the scene since the last
release, do we want to make any changes to the list of default
Hi,
Dave Culp wrote:
On Wednesday 09 November 2005 12:58 pm, Ralf Gerlich wrote:
[SNIP]
Shortly after that I couldn't get the engines down to idle. As I
noticed, jsdemo reports that the throttle axis returns +0.3 when on
idle. I'm using Linux on a 2.6.8 kernel.
That configuration file
On Wed, 9 Nov 2005, Andy Ross wrote:
Which stick, and which aircraft?
Saitek Cyborg Evo (but the code is copied from Saitek to other sticks)
And it's the same for all aircrafts I've tested, including uiuc-models (so
it's probably not the FDM engine. Not that I have full understanding of
how
On Wednesday 09 November 2005 19:04, Dave Culp wrote:
That configuration file applies an offset of -0.3 prior to the scale. That
shouldn't be allowed, and I guess someone's personal configuration snuck in
by accident?
I don't think so in this case. That offset apparently worked for most
FlightGear v0.9.9-pre2 (second prerelease for v0.9.9) is now available
for downloading and testing from the FlightGear web site
(http://www.flightgear.org)
It would be great if as many people as possible could download the
tarballs for this release and build and test it on as many platforms
Joacim Persson wrote:
I've also experimented with commenting out the lines about left gear
in the joystick config file (and thus tie the button to right gear
only), to see if it had something to do with nasal per se. (as in not
being able to handle two interpolate simultaneously) But the right
On Wednesday 09 November 2005 19:31, Curtis L. Olson wrote:
Just glancing through the list very quickly, potential candidates for
inclusion might be the b1900d, Citation Bravo, Concorde, dhc2, F-8E,
Hurricane, Marchetti, MiG-15, seahawk, Spitfire, tu154 ... (?)
Any opinions? Note that if you
On Wed, 9 Nov 2005, Andy Ross wrote:
Theory: the right brake property is flagged as a boolean in the
property tree, and is clamping all values to 0 or 1. This can be
complicated to debug -- you need to figure out where it's created.
Sounds plausible. Some sort of type mismatch. But I figure
Buchanan, Stuart wrote:
--- Steve Knoblock [EMAIL PROTECTED] wrote:
I am unsure if I can help, I do hope to convert a model of
the Cape May Light I made for MSFS for FG once I understand the tools.
As a first pass, you could place a generic lighthouse (from
On Wed, 9 Nov 2005, Andy Ross wrote:
Theory: the right brake property is flagged as a boolean in the
property tree, and is clamping all values to 0 or 1.
Confirmed.
I tried a setprop to 0.3 for right wheel in the js config file, and got a
1.0 in the browse internal props dialog. Somewhere
Curtis L. Olson wrote:
I am currently targeting the official v0.9.9 release for late next week
(time permitting.)
Is there any preferred version of OpenAL for this release? Just
wondering if there's a recommended version for linking against for the
binary packages.
Also, is there an fgrun
* Joacim Persson -- Wednesday 09 November 2005 21:30:
I tried a setprop to 0.3 for right wheel in the js config file, and got a
1.0 in the browse internal props dialog. Somewhere control/gear/brake-right
is set to 'true' (i.e. not zero).
Is this the development version (cvs/head)?
m.
On Wed, 9 Nov 2005, Melchior FRANZ wrote:
Is this the development version (cvs/head)?
Yes, but it has been the same for shipped versions too.
How can I tell which version of fgfs I'm running? fgfs --version didn't
work on the version I have installed in /usr/local/... anyway. Think it's
the
--- AJ MacLeod [EMAIL PROTECTED] wrote:
I would be interested to know if anyone has a Wingman Force 3d which
gives the
correct full range of throttle values with the new config...
Mine does, but then since I sent in the patch I probably don't count...
I wonder if it is OS or USB specific?
Before 0.9.9 is released I think one problem should be resolved: on some
planes (like the 737, f16, Concorde, fokker100) the engine sounds are
missing. Specifically Sounds/jet.wav is not audible.
I discussed this problem some weeks ago on the IRC channel and tried to
find out what's causing
Jon Stockill wrote:
Is there any preferred version of OpenAL for this release?
The CVS from 1st April this year appears to be a good choice - BTW,
this is what FreeBSD folks decided to stick to ;-)
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends
Hi,
attached are two small patches for giving the 737 nosewheel some
animations. Namely it rotates when steering and compresses on breaking.
For the latter I attached a one line patch that let's JSBsim expose
compression-norm to the property tree just like YaSim.
I don't know if this is in
Title: Message
Hello
all,
I'm trying certain senarios
via waypoints and varying altitudes by using flightplan/.fgfsrc file. I
plan on implementing a data input change for route manger code to read a file
with my data, but in the mean time I was wondering if there's a reason why [EMAIL
Curtis L. Olson wrote:
I reserve the right to make the final determination (and all
non-included aircraft will still always be available for separate
download from the web site ...)
Given that new aircraft have arrived on the scene since the last
release, do we want to make any changes to
I have pinned down the exact moment in gdb when brake-right is set to 1.0
(without a cause, so to speak), but I feel I don't have enough knowledge
about how FG is designed to come further.
gdb backtrace below. This is after initialisation is done, FG is up and
running and the fire button (apply
Georg Vollnhals wrote:
Curtis L. Olson schrieb:
man touch ?
Curt.
Yes. My 13 years old son is actually a co-user on my PC. He does not
ask, he does not think a lot - just trial and error method.
Very good if you have all your important data burned on CD/DVD and have
a good firewall,
Jon Stockill wrote:
Buchanan, Stuart wrote:
--- Steve Knoblock [EMAIL PROTECTED] wrote:
I am unsure if I can help, I do hope to convert a model of
the Cape May Light I made for MSFS for FG once I understand the tools.
As a first pass, you could place a generic lighthouse (from
Joacim Persson wrote:
Andy Ross wrote:
Which stick [...]?
Saitek Cyborg Evo
[...]
I have pinned down the exact moment in gdb when brake-right is set
to 1.0 (without a cause, so to speak), but I feel I don't have
enough knowledge about how FG is designed to come further.
What this is
On Wed, 2005-11-09 at 21:54 +0100, Joacim Persson wrote:
On Wed, 9 Nov 2005, Melchior FRANZ wrote:
Is this the development version (cvs/head)?
Yes, but it has been the same for shipped versions too.
How can I tell which version of fgfs I'm running? fgfs --version didn't
work on the
Josh Babcock schrieb:
Or you could run linux, then he could only mess up his own files.
Josh
Yes Josh, that's my way for the future :-)
I already created a second partition for Linux some months ago and tried
Suse, Fedora, Kubuntu, Knoppix and Kanopix (Debian version).
The last was the
* Andy Ross -- Thursday 10 November 2005 00:37:
stepping through the joystick initialization (or, alternatively,
selectively removing files from your Input/Joysticks directory) to
figure out which stick is being incorrectly loaded, and why.
... or simply look in the property browser under
A bit off topic: does anyone have success in compiling FlightGear and related
libaries using GCC-4.0?
I want to get my system sorted before I test the pre-release, but I might
ended up not being able to test FlightGear if GCC-4.0 has trouble compiling
FlightGear.
Ampere
Ampere K. Hardraade [EMAIL PROTECTED] writes:
A bit off topic: does anyone have success in compiling FlightGear and related
libaries using GCC-4.0?
I want to get my system sorted before I test the pre-release, but I might
ended up not being able to test FlightGear if GCC-4.0 has trouble
Curtis L. Olson writes
We haven't officially decided, but right now we are talking about doing a
v1.0 release after the dust has settled on 0.9.9. That would likely happen
sometime early 2006 after the holidays.
This sounds good I have a 737 on the go but it won't be finished in
a week.I
Syd,
I didn't intend that to be a criticism of any sort.. I much appreciate
the effort of all involved with the modelling of any of the planes and
models.
Otherwise, it looks and feels great :-) While I haven't seen a b1900d,
it seem around the mark, tend to enter a spin when air speed drops
Hi Stefan
Stefan Seifert writes
Before 0.9.9 is released I think one problem should be resolved: on some
planes (like the 737, f16, Concorde, fokker100) the engine sounds are
missing. Specifically Sounds/jet.wav is not audible.
I discussed this problem some weeks ago on the IRC channel
Ampere,
A bit off topic: does anyone have success in compiling FlightGear
and related
libaries using GCC-4.0?
I have only one problem, building src/FlightGear/src/Instrumentation/
od_gauge.cxx. I mentioned it in october here:
Ima, that problem can be fixed with a small patch to simgear.On 11/10/05, Ima Sudonim [EMAIL PROTECTED]
wrote:Ampere, A bit off topic: does anyone have success in compiling FlightGear
and related libaries using GCC-4.0?I have only one problem, building
Ima Sudonim [EMAIL PROTECTED] writes:
I have only one problem, building src/FlightGear/src/Instrumentation/
od_gauge.cxx. I mentioned it in october here:
Alex,
I guess you're not seeing this problem with 4.0.3? Nice to know it's
been fixed! (assuming it's not a private patch) 8-) Now
Hi all,
I am having a problem compiling the lattest ( 1/2 Hour ago )
flightgear. I have also updated simgear and recompiled.
the error I get is while making flightgear as follows,
Making all in MultiPlayer
make[2]: Entering directory `/root/source/src/MultiPlayer'
if g++ -DHAVE_CONFIG_H
On November 9, 2005 02:46 pm, Curtis L. Olson wrote:
The more build errors and platform bugs we can catch now, the smoother
the v0.9.9 release will be for your favorite platform!
Well, I still can't get FlightGear to run under Xorg at 24bit depth. I am
still getting the following messages:
X
59 matches
Mail list logo
