Hi All
If John is using AC3D 4.0 then there is a problem using
those models in FG.There is a crease statement that FG/Plib
can't handle.So to get around the problem you either have to
text edit all reference to the crease statement in the AC3D file
(tedious) or build the model using AC3D 3.6 or
Frederic Bouvier writes
Norman Vine wrote:
Frederic Bouvier writes:
FG is not using the latest features new cards are offering and the
'old'
features are pretty maxed out now. This is not an explanation for
worst performance but just for lack of improvement. In the meantime,
you
Ampere K. Hardraade wrote:
Please tell me that you don't play FlightGear in wireframe mode. =P
Neh, my O2 does support filled triangles.
Just kidding.
Oh. ;-)
Erik
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
Alex Perry wrote:
I'd observe that it would be nice to turn _off_ texturing of the models,
both the aircraft I'm sitting in and the AI aircraft around the airport,
and turn _on_ texturing for the head up display (needed for PLIB fonts).
That would make it much easier to fly with unaccelerated 3D
Innis Cunningham wrote:
It is quite possible that the new graphics card/system is not set up for
FG.I will have a play with it and see if I can improve the situation.I
think
anisotropic filtering is on.
The point I was trying to make is people trying FG for the first time will
be dissuaded from
I'm new to flightgear, though I allways wanted to play
it. Nearly the first thing I did on my new compu, was
to try to compile FG. Unluckyly I ran into three
problems.
First one is with the file
src/FDM/JSBSim/FGJSBBase.h. It requires
numeric_limits included for limits.h. This is only
implemented
Jonathan Polley wrote:
Fred,
It turns out that the problem should exist on every FlightGear
system, not just the Mac. On exit(), fgExitCleanup() is called which
deletes the globals class and then calls fgOSExit(). The only thing
that fgOSExit() does is turn around and call
Frederic Bouvier wrote:
Jonathan Polley wrote:
Fred,
It turns out that the problem should exist on every FlightGear
system, not just the Mac. On exit(), fgExitCleanup() is called which
deletes the globals class and then calls fgOSExit(). The only thing
that fgOSExit() does
Erik Hofman wrote:
Innis Cunningham wrote:
It is quite possible that the new graphics card/system is not set up for
FG.I will have a play with it and see if I can improve the situation.I
think
anisotropic filtering is on.
The point I was trying to make is people trying FG for the first time
will
Richard Harke wrote:
On Saturday 17 July 2004 07:08 am, Innis Cunningham wrote:
I had a GeForce 2 Titanium with a PIII Xeon at 550MHz getting about 15 fps
over SF Video card crapped out (even has a red LED come on to tell you
it has crapped out) so I bought a Geforce FX 5200 Frame rate dropped to
Erik Hofman wrote:
This is the penalty for those who want eye-candy. If specular
highlighting is supported it will be enabled an make FlightGear slower.
I noticed some enhancements in the new rendering dialog, and would like
to ask how feasible it would be to integrate even more
Frederic Bouvier wrote:
What do you want to prove with a field so narrow ?
I don't want to prove anything, that was just an example -
e.g. I encountered the problem when I created controls whose
width was insufficient for the string to be displayed.
And that's exactly what I pointed out with
Innis Cunningham wrote:
Hi All
If John is using AC3D 4.0 then there is a problem using
those models in FG.There is a crease statement that FG/Plib
can't handle.So to get around the problem you either have to
text edit all reference to the crease statement in the AC3D file
(tedious) or build the
Jacek wrote:
Do you really distinguish those ... and ---? ;-)
Well, to be honest only since just recently - there are some fairly
decent morse code training applications available, so if you keep
hearing the same stuff for an hour a day you start to get it one
day ...
But it's the same problem
Boris Koenig wrote:
Erik Hofman wrote:
Well, if we turn all that off, people start to complain that
FlightGear looks like crap and will search for something else. At
least now they start asking questions ...
Then how about optionally offering to disable such things in the
(advanced) rendering
Boris Koenig
Frederic Bouvier wrote:
Combo arrows are 16 pixels wide, so the input is -6 pixels . ( The width
is not in
characters but in pixels )
thanks for the explanation, but I was aware of that.
And NO, this problem did not only occur with a width
specification of = 16, but rather =
Jonathan Polley wrote:
Fred,
It turns out that the problem should exist on every FlightGear
system, not just the Mac. On exit(), fgExitCleanup() is called which
deletes the globals class and then calls fgOSExit(). The only thing
that fgOSExit() does is turn around and call
Frederic Bouvier wrote:
What about calling SDL_Quit in a function installed by 'atexit', remove
fgOSExit and only rely on exit in all the program ?
The problem is that plib has taken the liberty to call exit() whenever
they feel like it
Erik
___
Boris Koenig wrote:
There seem to be some issues regarding the XML file processing
and FlightGear's stability:
#Nasal parse error: empty subexpression in command, line 3
#Failed to execute command nasal
#Segmentation fault
The XML you posted contains no Nasal script, so I'm at a
Andy Ross wrote:
Boris Koenig wrote:
There seem to be some issues regarding the XML file processing
and FlightGear's stability:
#Nasal parse error: empty subexpression in command, line 3
#Failed to execute command nasal
#Segmentation fault
The XML you posted contains no Nasal script,
Boris Koenig wrote:
Frederic Bouvier wrote:
In fact, the combo's arrow is 16 pixels wide and an input must be at
least 15 pixels.
That means that every combo that are 31 pixels or less
are causing a segfault in a function named chop_to_width
in puInput.cxx.
okay, makes sense - even
This patch should fix the problem with src/Navaids/navlist.cxx choosing
the wrong localizer on a runway with localizers at each end on the same
frequency. [There seems to be quite a few in the UK like this, EGLL,
EGLC, EGSS]. Selecting the autopilot 'LOC' without this patch causes
planes to turn
Ed Sirett wrote:
This patch should fix the problem with src/Navaids/navlist.cxx choosing
the wrong localizer on a runway with localizers at each end on the same
frequency. [There seems to be quite a few in the UK like this, EGLL,
EGLC, EGSS]. Selecting the autopilot 'LOC' without this patch
Hi,
Just discovered Flight Gear last night, and it installed relatively well,
apart from the missing fs_os.cxx problem which I finally tackled by using
the file from CVS (before I had the chance of reading Erik's comment on
the tarball hickup)... Anyway, great work you guys have already done!
Remy Villeneuve wrote:
Hi,
Just discovered Flight Gear last night, and it installed relatively well,
apart from the missing fs_os.cxx problem which I finally tackled by using
the file from CVS (before I had the chance of reading Erik's comment on
the tarball hickup)... Anyway, great work you guys
Hey guys,
Did we introduce a memory leak when paging scenery recently? I left FG
running all night (with ATC and AI traffic disabled) and memory usage
was stable. Then I went for 2-3 hour flight and just about filled up
all my main RAM + Swap on my linux machine before I finally killed
Remy Villeneuve wrote:
Hi,
Just discovered Flight Gear last night, and it installed relatively well,
apart from the missing fs_os.cxx problem which I finally tackled by using
the file from CVS (before I had the chance of reading Erik's comment on
the tarball hickup)... Anyway, great work
Curt,
I do remember seeing something similar happening, on a long haul test flight
between Tokyo and Sydney, which judging from the timestamp on the scenery
directory, I did around the 22nd of June. Same problem: Huge memory leak, up
to the point where the aircraft became uncontrollable. I
Durk Talsma wrote:
I do remember seeing something similar happening, on a long haul test flight
between Tokyo and Sydney, which judging from the timestamp on the scenery
directory, I did around the 22nd of June. Same problem: Huge memory leak, up
to the point where the aircraft became
I wrote
Sent: 17 July 2004 15:22
To: 'FlightGear developers discussions'
Subject: RE: [Flightgear-devel] Next release of FlightGear
Erik Hofman wrote
Sent: 17 July 2004 14:51
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Next release of FlightGear
Vivian
That patch worked just fine. Hopefully it can be rolled into CVS
before the release.
Thanks!
Jonathan Polley
On Jul 18, 2004, at 7:40 AM, Frederic Bouvier wrote:
Frederic Bouvier wrote:
Jonathan Polley wrote:
Fred,
It turns out that the problem should exist on every FlightGear
system, not
What you are looking for is called fgrun and is here :
http://sourceforge.net/projects/fgrun
-Fred
PS: fgfs, not fsgs ;-)
Yeah... ahemm... sorry about the typo... 10 years of Flight Simulator
habits to shed on my side... ;-P
Thanks for pointing me to the existing project!
On another side
Ehm, to both of you, was this using the real-weather option turned on or
anything other which might be related?
Euhhm, yes, I always have turned the real-weather option on by default.
Cheers,
Durk
___
Flightgear-devel mailing list
[EMAIL
Durk Talsma wrote:
Ehm, to both of you, was this using the real-weather option turned on or
anything other which might be related?
Euhhm, yes, I always have turned the real-weather option on by default.
Are you using the old or the new Scenery. There was some changes in the
animation
The new scenery (the 0.9.5 release, downloaded using terrasync)
Cheers,
Durk
On Sunday 18 July 2004 23:08, Frederic Bouvier wrote:
Durk Talsma wrote:
Ehm, to both of you, was this using the real-weather option turned on
or anything other which might be related?
Euhhm, yes, I always
Durk Talsma wrote:
The new scenery (the 0.9.5 release, downloaded using terrasync)
Cheers,
Durk
On Sunday 18 July 2004 23:08, Frederic Bouvier wrote:
Durk Talsma wrote:
Ehm, to both of you, was this using the real-weather option turned
on
or anything other which might be related?
[EMAIL PROTECTED] wrote:
Erik Hofman wrote:
IRIX and Solaris binaries also include it by default.
I'm not sure about other distributions, but I would
encourage them to include it with the distribution.
I include it with the slackware package too.
Is there likely to be a new release of fgrun
Hi,
Sorry to have got things messed up.
Attached is the patched file against the latest CVS version.
Below is a diff -c patch.
I've attached the file as well in case line wrap screws things up too.
It's great to be able to make a contribution even if
it's only a small patch.
I also
Does FlightGear provide some sort of way to determine distance between
the aircraft and a stationary object?... ie, building, mountain.
I'm working on an autonomous flight controller and need to have this
sort of feedback.
If not, could anyone suggest how this could be done? Where in the source
Not sure if this has been reported yet, but I just built 0.9.5 pre1 on fedora
core 2 and it seems that the file fg_os.cxx is missing. If I use the
--enable-sdl option, the code compiles since it uses fg_os_sdl.cxx in place of
fg_os.cxx.
However, when I run the code it aborts with a message
Hi
While trying to correctly tweak the FDM and PID controllers for the L1011-500,
i though it would be really nice to have some sort of standalone app running
on a remote machine, plotting selected property(es) oscilloscope style (in
my case, i'd like to make it run in my old P133).
I saw
I had forgotten that FlightGear has been moved over to OpenAL. I downloaded the new
base
package to see if there is an L1011 there (I didn't see one). But, now, my FlightGear
executable doesn't work with the new base package, so I tried downloading plib, but
plib
cvs doesn't seem to be up at the
Never mind. I guess the CVS repository for plib has changed/
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Jon Berndt
Sent: Sunday, July 18, 2004 9:23 PM
To: Flightgear-Devel
Subject: [Flightgear-devel] Building the latest ...
I had forgotten that
43 matches
Mail list logo
