Adam Dershowitz wrote:
I just downloaded from CVS and built 0.9.9 and have found a bug.
When it comes up the sound is muted. If I click file-sound
configuration it brings up the sound dialog box with Mute Sound
checked. If I uncheck it I get sound. But then I can't seem to get it
to again
Dave Perry wrote:
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
On Wed, 2005-11-16 at 15:56 +, Martin Spott wrote:
I just ran across this document
http://www.adacel.com/prodserv/downloads/MAXSIM.pdf
and thought: Isn't it great that FlightGear is so flexible to provide
the visuals for such an application without modification ?
Cheers,
On Thursday 17 November 2005 23:29, Ampere K. Hardraade wrote:
Other than the one taken during daytime, I think the rest should be kept
away from being presented. They are simply too dark.
Erm.. it's called atmosphere. FG looks very impressive around dawn and dusk,
and some of the rougher
Hello all,
I'm thinking, if it's a good idea to add a new
rendering option into FGFS: water shader, which will
make the sea and the experience of carrier taking off
and landing more realistic.
Here's a screenshot of a game using OpenSceneGraph,
and the technique is to load GLSL shader in OpenGL.
I'm thinking, if it's a good idea to add a new
rendering option into FGFS: water shader, which will
make the sea and the experience of carrier taking off
and landing more realistic.
It's certainly a good idea! go ahead.
Here's a screenshot of a game using OpenSceneGraph,
and the technique
--- Vassilii Khachaturov [EMAIL PROTECTED] wrote:
If you add the feature, you'll probably want to make it conditionally
enabled --- similar to the 3d clouds etc --- so that people with lower
end hardware could disable it.
Definitely. I thought I had fairly up-to-date graphics hardware until
Aircraft authors (or other interested parties.)
Take a look at the latest aircraft download page:
http://www.flightgear.org/Downloads/aircraft/
There are quite a few aircraft with no thumbnail.jpg created for the web
page. We need a 171x128 pixel image for each aircraft that has a 3d
model.
Hello everyone,
FlightGear v0.9.9 is now final. The source code is propagating through
to the mirrors. If you have built an 'official' binary version of
FlightGear in the past, it would be great if you could build a binary
for v0.9.9 as well. I'm going to make an 'official' v0.9.9
Curtis L. Olson wrote:
Hello everyone,
FlightGear v0.9.9 is now final. The source code is propagating through
to the mirrors. If you have built an 'official' binary version of
FlightGear in the past, it would be great if you could build a binary
for v0.9.9 as well. I'm going to make an
Finally! :)
Is there an official major changes list? Something to tell users what
has really changed since 0.9.8?
On 11/18/05, Erik Hofman [EMAIL PROTECTED] wrote:
Curtis L. Olson wrote:
Hello everyone,
FlightGear v0.9.9 is now final. The source code is propagating through
to the
Arthur Wiebe wrote:
Finally! :)
Is there an official major changes list? Something to tell users what
has really changed since 0.9.8?
Yup, I began assembling this list with the first v0.9.9 pre release.
Curt.
--
Curtis Olsonhttp://www.flightgear.org/~curt
HumanFIRST Program
Selon Jon Stockill :
Curtis L. Olson wrote:
Hello everyone,
FlightGear v0.9.9 is now final. The source code is propagating through
to the mirrors. If you have built an 'official' binary version of
FlightGear in the past, it would be great if you could build a binary
for v0.9.9 as
When running fgfs 0.9.9 I get this output:
opening file: /Users/arthur/Projects/FlightGearOSX/data//Navaids/carrier_nav.dat
/Users/arthur/Projects/FlightGearOSX/data//Navaids/TACAN_freq.dat
RenderTexture::BeginCapture(): Texture is not initialized!
On 18 Nov 2005, at 20:08, Arthur Wiebe wrote:When running fgfs 0.9.9 I get this output: opening file: /Users/arthur/Projects/FlightGearOSX/data//Navaids/carrier_nav.dat /Users/arthur/Projects/FlightGearOSX/data//Navaids/TACAN_freq.dat RenderTexture::BeginCapture(): Texture is not initialized!
Arthur Wiebe
Subject: [Flightgear-devel] RenderTexture::BeginCapture(): Texture is
notinitialized!
When running fgfs 0.9.9 I get this output:
opening file:
/Users/arthur/Projects/FlightGearOSX/data//Navaids/carrier_nav.dat
On 11/18/05, Vivian Meazza [EMAIL PROTECTED] wrote:
Arthur Wiebe
Subject: [Flightgear-devel] RenderTexture::BeginCapture(): Texture is
notinitialized!
When running fgfs 0.9.9 I get this output:
opening file:
/Users/arthur/Projects/FlightGearOSX/data//Navaids/carrier_nav.dat
Vivian Meazza wrote:
There should be no need to uncompress either file.
Unless zlib support is missing somewhere.
Jon
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Frederic Bouvier wrote:
Jon, you need to use fltk with multi-threading support.
Thanks. All rebuilt, and it's now working. The package has been updated.
(If version numbers are cheap, package revisions are even cheaper ;-)
Jon
___
Flightgear-devel
On Nov 18, 2005, at 12:45 AM, Erik Hofman wrote:
Adam Dershowitz wrote:
I just downloaded from CVS and built 0.9.9 and have found a bug.
When it comes up the sound is muted. If I click file-sound
configuration it brings up the sound dialog box with Mute Sound
checked. If I uncheck it I
On Nov 18, 2005, at 12:08 PM, Arthur Wiebe wrote:
When running fgfs 0.9.9 I get this output:
opening file: /Users/arthur/Projects/FlightGearOSX/data//Navaids/
carrier_nav.dat
/Users/arthur/Projects/FlightGearOSX/data//Navaids/TACAN_freq.dat
RenderTexture::BeginCapture(): Texture is not
Yes, that is correct. But, if I enable sound, the bug still shows
up. In other words, if I start with --enable-sound then it starts
with sound, as it should, but the dialog box does not allow me to
turn it off.
--Adam
I noticed that too but never thought anything of it. So I can confirm
Arthur Wiebe
On 11/18/05, Vivian Meazza [EMAIL PROTECTED] wrote:
Arthur Wiebe
Subject: [Flightgear-devel] RenderTexture::BeginCapture(): Texture is
notinitialized!
When running fgfs 0.9.9 I get this output:
opening file:
On 18 Nov 2005, at 22:18, Adam Dershowitz wrote:But then it continues to load and run. So I think that the error may be a red herring, and not the cause of the abort that you are seeing. The RenderTexture error is a red-herring, for certain, and by instrumenting SGThread I've found at least two
On Friday 18 November 2005 22:16, Arthur Wiebe wrote:
Yes, that is correct. But, if I enable sound, the bug still shows
up. In other words, if I start with --enable-sound then it starts
with sound, as it should, but the dialog box does not allow me to
turn it off.
I noticed that too but
James,
Sorry to hear you're having so much trouble. Unfortunately,
everything is working for me just fine with latest CVS...
opening file: /Users/arthur/Projects/FlightGearOSX/data//Navaids/
carrier_nav.dat
/Users/arthur/Projects/FlightGearOSX/data//Navaids/TACAN_freq.dat
I have the feeling this is actually a problem with the xcode project
files. I'm going to build using makefiles and see what happens. It
could be that something isn't be compiled correctly.
On 11/18/05, Ima Sudonim [EMAIL PROTECTED] wrote:
James,
Sorry to hear you're having so much trouble.
The inner gear (right and left) were hanging down and the main gear well was
sticking out from the fuselage with gear up. (I decided to hide the well
when the gear is up, rather than messing with the .ac-file.) I also
somewhat sorted out the numbering of the gears, in case someone in the
future
On November 18, 2005 07:26 am, AJ MacLeod wrote:
Erm.. it's called atmosphere. FG looks very impressive around dawn and
dusk, and some of the rougher edges in the scenery are hidden.
AJ
Sure, FG looks very impressive during dawn and dusk, but the planes are a
different matter. They look
On November 17, 2005 01:03 pm, Melchior FRANZ wrote:
I had hoped that this thread would grow and offer a whole set of
nice screenshots. :-)
m.
Perhaps we can have a weekly screenshot competition? The best screenshot of
the week get uploaded to FlightGear's frontpage.
Ampere
I have found the problem. My Xcode projects seem to be buggy. The PLIB
project is fine but something is wrong with the SimGear project.
I just built using the autoconf system and everything worked fine. It
even fixed my spash screen problem! :)
I'll try to have it fixed by tomorrow afternoon if
Arthur Wiebe wrote:
I have found the problem. My Xcode projects seem to be buggy. The PLIB
project is fine but something is wrong with the SimGear project.
I just built using the autoconf system and everything worked fine. It
even fixed my spash screen problem! :)
I'll try to have it fixed by
Ampere K. Hardraade wrote:
Perhaps we can have a weekly screenshot competition? The best screenshot of
the week get uploaded to FlightGear's frontpage.
Sounds like a great idea. Are you volunteering to manage it? :-)
Curt.
--
Curtis Olsonhttp://www.flightgear.org/~curt
I have found the problem. My Xcode projects seem to be buggy. The PLIB
project is fine but something is wrong with the SimGear project.
I just built using the autoconf system and everything worked fine. It
even fixed my spash screen problem! :)
I'll try to have it fixed by tomorrow
On 11/14/05, Geoff Air [EMAIL PROTECTED] wrote:
Hi WIN32 developers,
I too have had BIG PROBLEMS with compiling OpenAL
CVS with MSVC7.1 - maybe this will eventually be cleared
up by the OpenAL developer group ... maybe NOT ;=((
Part of the problem, is that for no particular good
reason
I checked out the CVS base lat night and tried to compile with an older
tarball source, which failed. I received advice through FG irc that I
should check the latest FG source out from CVS. I did that tonight and
the configure seemed to go normally, but the make failed:
Making all in ATC
make[2]:
36 matches
Mail list logo
