Erik Hofman wrote:
Frederic Bouvier wrote:
Erik Hofman wrote:
Modified Files:
options.xml
Log Message:
Remove an obsolete option for airport-id.
Erik, the option require an ICAO id, so I think this is
the right option and find more logical to deprecate
--airport instead
David Megginson wrote:
Frederic Bouvier wrote:
Remove an obsolete option for airport-id.
Erik, the option require an ICAO id, so I think this is
the right option and find more logical to deprecate
--airport instead.
I'm with Erik on this one. Otherwise, we'd need to change --vor
Mathias Fröhlich wrote:
On Sonntag, 15. August 2004 12:00, Erik Hofman wrote:
I noticed that the fact that scenery loading is faster when pressing 'v'
is caused by the fact that FlightGear doesn't bother rendering the scene
in the mean time.
Maybe it would be a good idea to set
Matthew Law wrote:
David Megginson wrote:
Has anyone ever seen beacons on a tall tower like that in real life?
I saw one at Eloy, AZ a few years ago when I was there skydiving. It
wasn't a very tall tower though - around 40ft or so I'd say.
The beacon tower modeled is here :
Erik Hofman wrote:
Vivian Meazza wrote:
AC3D seems to add the material colour to the texture
No, it's OpenGL that does this. With everything related to modeling you
have to take into account the possibilities and requirements of OpenGL,
and not that of your 3d modeler program.
To be
Ampere K. Hardraade wrote:
One more:
http://www.fas.org/man/dod-101/sys/ac/Fig1big.JPG
Regards,
Ampere
On August 7, 2004 03:36 pm, Ampere K. Hardraade wrote:
That question was asked on this page:
http://flightgear.org/Docs/fgfs-model-howto.html
There is no need for someone to
Alex Romosan wrote:
i've collected some of the
screenshots at http://caliban.lbl.gov/fgfs-heli/index.html. for
comparison (although we didn't land on top of any of the buildings :-(
) the real pictures of sf are at
http://caliban.lbl.gov/sfhelitour/index.html.
The screenshots are nice but I
Alex Romosan wrote:
Melchior FRANZ [EMAIL PROTECTED] writes:
* Alex Romosan -- Friday 06 August 2004 21:31:
and i noticed that the collective is mapped backwards
(up goes down and down goes up).
Yes, and that's the way it should be and there's no way in hell to have
this changed. If
Ron Lange wrote:
Melchior FRANZ schrieb:
This release contains one feature that I consider very important for
fgfs: an excellent new UV unwrapper! Now there's no excuse for not
texturing the Bo105 any more. :-)
also the EC130 coming soon ;-)
http://www.ron-lange.de/ec130_stage1.jpg
Is there a way to create new instances of AIAircraft or
another kind on the fly, just by adding some nodes in
the property tree, or running a command from the telnet
interface, that is, without modifying the source code ?
Is there something planned in this direction ?
Thanks,
-Fred
Durk Talsma wrote:
On Wednesday 04 August 2004 14:41, Frederic Bouvier wrote:
Is there a way to create new instances of AIAircraft or
another kind on the fly, just by adding some nodes in
the property tree, or running a command from the telnet
interface, that is, without modifying
Vivian Meazza wrote:
Is that from a recent download? I updated again this morning, and still
get
166 if(cap 1) { continue; }
1 still doesn't seem to work with JBS models.
I also have 1. Are you dowloading with the cvs client or with
the flightgear.org viewcvs application. In the
Dave Perry wrote:
Help!
Since my CH Yoke and Pedals don't work with the new joydev driver in
Suse 9.1, I need to use my Saitek Cyborg Evo joystick. Both js_demo and
jstest show all it's axes and buttons working but ony the non DEFANGED
functions work in FlightGear (that is aileron,
Dave Perry wrote:
Help!
Since my CH Yoke and Pedals don't work with the new joydev driver in
Suse 9.1, I need to use my Saitek Cyborg Evo joystick. Both js_demo and
jstest show all it's axes and buttons working but ony the non DEFANGED
functions work in FlightGear (that is aileron,
Ampere K. Hardraade wrote:
Right now, if one wants to specify a new livery for some of the animation
files, he/she will have to do this:
aircraft-set.xml
+ main.xml
[ + livery1.xml
[ [ + animation1.xml
[ + livery2.xml
[ [ + animation2.xml
[
[ + animation3.xml
Maybe I am overlooking
Is there a way to avoid the initial lock for scenery loading ?
I understand this is a must have for users, but it slows
down development speed dramatically when you have to test the
apparence of a new building or landmark.
Another point: FPS counter is off by default now. It was on
before. Is
There is a caught exception ( so it is harmless ) in
the XML reader because files are not in the base
package. Those files are :
Data/AI/FlightPlans/KSFO-KSEA.xml
Data/AI/FlightPlans/KSEA-KSFO.xml
Are the names generated randomly or are they really missing ?
-Fred
Another point: FPS counter is off by default now. It was on
before. Is it intended ?
Oh, I see it is in the rendering option dialog ( I was going
to add it ;-) so it is probably better like that.
-Fred
___
Flightgear-devel mailing list
[EMAIL
Peter Larson wrote:
Boris,
thanks. It appears to be the Crease command. I created a box, removed the
crease and it imported OK (now I have to work through how to save the
scenery so that it gets picked up by the Sim!). As I said, I'm new to this
(as in just the last 4 days) and have no
Durk Talsma wrote:
On Saturday 24 July 2004 10:13, Frederic Bouvier wrote:
There is a caught exception ( so it is harmless ) in
the XML reader because files are not in the base
package. Those files are :
Data/AI/FlightPlans/KSFO-KSEA.xml
Data/AI/FlightPlans/KSEA-KSFO.xml
I get the same ground poly problems that you seem to be getting with your
new
ATI driver, except I've been getting them for some time now.
It actually only seems to be the airfield polys that are affected but
you'll
often see it with airfields that are a long way away, to the extent that
you
Vivian Meazza wrote:
Erik Hofman
Sent: 23 July 2004 08:52
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Latest CVS Aborts
Jonathan Polley wrote:
I just updated tonight and FlightGear no longer runs on the Mac. As of
last night, everything ran just file,
Vivian Meazza wrote:
I've re-downloaded the current cvs. Here's the backtrace
...
Can't say that it means anything to me! Is it any good to you, or can I do
something else?
It looks like useless garbage, sorry. Do you run fg with --log-level=bulk
or whatever is the most verbose ( I don't
Jim Wilson wrote:
Bernie Bright said:
Jim Wilson wrote:
globals-get_tile_mgr()-all_queues_empty() and cur_fdm_state-get_inited())
{
^^^
^^^
Same here.
That's a head scratcher. Never would have thought that would compile like
that. Learn something new everyday.
Erik Hofman wrote:
Update of /var/cvs/FlightGear-0.9/FlightGear/src/Main
In directory baron:/tmp/cvs-serv28544/src/Main
Modified Files:
fg_init.cxx main.cxx
Log Message:
Jim Wilson: This patch prevents FDM execution until intial scenery load
completes making
midair starts in the KSFO area
Durk Talsma wrote:
I don't see any traffic files at all so maybe that is the problem. It
looks like it all got removed on the last update.
I do see them in fgfs-base-0.9.5-pre2. In data/Traffic. Are you referring
to
CVS or to the pre-release. Erik has commited a few changes just about
Frederic Bouvier wrote:
Durk Talsma wrote:
I don't see any traffic files at all so maybe that is the problem. It
looks like it all got removed on the last update.
I do see them in fgfs-base-0.9.5-pre2. In data/Traffic. Are you
referring
to
CVS or to the pre-release. Erik has
Apparently, TrafficManager is complaining because Traffic/KLM/KLM.xml
is missing
Traffic/UAL/UAL.xml is also not there.
-Fred
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Boris Koenig wrote:
Frederic Bouvier wrote:
! if (!cur_fdm_state-get_inited() or
fgGetBool(sim/sceneryloaded)) {
^^
Are we silently migrating the code to Pascal ?
This doesn't compile with MSVC.
lol, GREAT :-)
don't know
Jonathan Polley wrote:
I just updated tonight and FlightGear no longer runs on the Mac. As of
last night, everything ran just file, but after updating everything
(SimGear, FlightGear, and base packages) I get an abort. The gdb
backtrace is:
...
It is the same for everybody until some
David Megginson wrote:
Chris Metzler wrote:
For example,
tweaking the diffuse/specular reflectivity parameters produces no change
whatsoever to the .ac file exported, even though the .blend file does
change.
Correct. Currently, the AC3D export scripts in blender do not export
Richard Bytheway wrote:
From: Jon Berndt
I have created a new OpenAL tarball that breaks ALut into a
separate DLL
http://www.vso.cape.com/~nhv/files/fgfs/openal_cyg.tgz
Is this tarball (or equivalent) still available somewhere?
I had a copy, but it got lost along the way.
Jon Berndt wrote:
I think this is what you are looking for :
ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/openal_cyg.tgz
-Fred
OK, I got it from the link that Erik supplied (thanks Erik). Now I have these files.
Can you tell me where I can put them?
Beware, the name seems to
Beware, the name seems to imply they are for MinGW, not CygWin
The link I provided is the tarfile from Norm that was on my harddisc
-Fred
I have MingW installed along with CygWin. This might be problematic, then? Is
FlightGear
under Cygwin normally NOT MingW built?
I think the
Vivian Meazza wrote:
The Cygwin build of FGFS-cvs appears still to have a problem with the
scenery path.
I've downloaded 0.9.5 scenery via Terrasync into /FlightGear/scenery
This works:
--fg-scenery=/FlightGear/scenery
as does this:
--fg-scenery=/FlightGear/data/scenery
this
Frederic Bouvier wrote :
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
Jon Berndt wrote:
I updated plib/simgear/flightgear/base from CVS. Built plib and simgear. Checked the
dates
on the libs - they're all current. The sources were updated from CVS. I tried
building
FlightGear and got this:
...
checking for simgear/version.h... yes
checking for simgear
Jon Berndt wrote:
What is the content of /usr/local/include/simgear/version.h ? ( or wherever you
installed SimGear ? )
-Fred
The version looks right, I think (but the $Id date is way off):
// $Id: version.h.in,v 1.1.1.1 2002/09/07 02:58:19 curt Exp $
Don't llok at the $Id, it is
#ifndef _SIMGEAR_VERSION_H
#define _SIMGEAR_VERSION_H
#define SIMGEAR_VERSION 0.3.6-pre1
...
It seems as though, then, that my installation of FlightGear is not looking for
the
correct pre-release version of simgear, but I don't know why. I've updated it
from CVS.
sonny hammaker wrote:
how about through a command line?
--turbulence=value
--wind=wind-desc-with-gust
--random-wind
see fgfs --help --verbose
-Fred
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
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
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
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
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
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
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
Indeed, the package only contains fg_os_sdl.cxx. I think it reflects
the packager's ( Curt ) own build option. And the package doesn't include
Network/jpg-httpd.* .
May I suggest to include all the files that are in conditional statement in
Makefile.am to be include inconditionally in an
Curtis L. Olson wrote:
I've started doing some of the pre-release work for FlightGear-0.9.5
(which is the next release.) That means I'd like to do our official
next release in the next week or two. Please take a few minutes to
download the tar balls and test this pre1 release. Please!
I wrote:
Curtis L. Olson wrote:
I've started doing some of the pre-release work for FlightGear-0.9.5
(which is the next release.) That means I'd like to do our official
next release in the next week or two. Please take a few minutes to
download the tar balls and test this pre1
Erik Hofman wrote:
Vivian Meazza wrote:
SimGear-0.3.6-pre1 will not compile under Cygwin. It fails in
[openal-test1.exe]: cannot find -lalut.
This is using Norman's prebuild libraries, isn't it?
Norman has integrated the alut library and the openal library so the
reference should then
Would these messages be removed before the release ?
WARNING: ssgLoad3ds: Texture coords missing.
WARNING: ssgLoad3ds: Texture coords missing.
WARNING: ssgLoad3ds: Texture coords missing.
WARNING: ssgSGIHeader::: Failed to open
'i:/flightgear/cvs/fgfsbase/Aircraft/MD11/Models/cowlings/SLEEVE.RGB'
Line 92 of globals.cxx seems ok. subsystem_mgr was allocated with a
new operator in line 45. Could you put a breakpoint at line 92 to see
if on your system, the destructor is not called twice ?
-Fred
Jonathan Polley wrote:
Since there is a new release coming, I decided to bring the Mac
Innis Cunningham wrote:
Hi Curt
I downloaded the windows binaries last night for
9.4 and the problem of the drop down menu's
locking the sim up still seem to exist.Even if you
go to exit FG and then select cancel the sim locks up.
Hey Innis,
you just downloaded the release that is 3
I was too quick to press the reply button. I now see your
motivations, so receive all my apologies.
Frederic Bouvier wrote:
Innis Cunningham wrote:
Hi Curt
I downloaded the windows binaries last night for
9.4 and the problem of the drop down menu's
locking the sim up still seem
Norman Vine wrote:
Frederic Bouvier writes:
Also I noticed that in the 9.4 base the runfgfs bat file has been
removed.
Was there a reason for this.
It has been supercede by fgrun that is much user frendly.
Until fgrun is distributed with FGFS I 'vote' for the batch file
Norman Vine wrote:
Frederic Bouvier writes:
Norman Vine wrote:
Frederic Bouvier writes:
Also I noticed that in the 9.4 base the runfgfs bat file has
been
removed.
Was there a reason for this.
It has been supercede by fgrun that is much user frendly
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 probably switched to another
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
One problem seems to be related to using combo boxes with
Curtis L. Olson wrote:
I want to bring a new subject before the group.
In the past we have discussed potential income sources for the FG
project, so I think it's fair to discuss another option since the
opportunity has introduced itself today.
There is a company that makes hardware (3d
Erik Hofman wrote:
Boris Koenig wrote:
Hi again !
I am just about trying to add some test-hooks to FlightGear, but
wouldn't like to have to rebuild the whole FlightGear build tree each
time (~ 350 MB ), just for 2-3 added small test-functions, hence I
came up with the following
Innis Cunningham wrote:
Hi All
I have run into a bit of a problem using the transparency
mask.
Firstly I have an engine texure that when the mask is
not present the texure is quite smooth but when I
add the mask to the texture the side of the engine
looks like a series of planks laid side
Lee Elliott wrote:
Splitting the fuselage into left and right hand sides only works from one
side
- the order is wrong from the other side.
And the normals are not matching at the join so there is clearly a seam
and an illumination artefact between the two sides. This is pretty evident
on the
Luca Masera wrote:
A : flightgear-devel
I've just downloaded the DATA directory in CVS; while in the old scenery
configuration
the elevation data and the objects were in the same directory, I've noticed that now
they
are splitten into Terrain and Objects. I've started a flight in KSFO,
Luca Masera wrote:
Now, there are two, bigger, problems...
If I don't add to the project fg_os.cxx and fg_os.hxx I've got
many error from the linker that doesn't find the body of the
functions declared into them (clearly).
If I add them, however, I've got a compiler error
(that I've
Luca Masera wrote:
Hi everyone,
I'm trying to compile the latest version of FlightGear. I've downloaded all the
libraries (from CVS) needed and I've compliled them. However I've two problems with
FlightGear, exactly:
-
Jim Wilson wrote:
Jon S Berndt said:
On Wed, 7 Jul 2004 17:35:31 -
Jim Wilson [EMAIL PROTECTED] wrote:
Mathias Frhlich said:
On Mittwoch, 7. Juli 2004 17:30, Jim Wilson wrote:
There doesn't seem to be support for the std::numeric_limits
references
added in the June
Ampere K. Hardraade wrote:
Is there any animation documentation out there that tells you what type of
animations have been implemented, and how they work, etc.?
http://cvs.flightgear.org/cgi-bin/viewcvs/viewcvs.cgi/*checkout*/docs/Model/fgfs-model-howto.html?rev=1.8cvsroot=FlightGear-0.9
Ampere K. Hardraade wrote:
On July 1, 2004 02:11 am, Frederic Bouvier wrote:
http://cvs.flightgear.org/cgi-bin/viewcvs/viewcvs.cgi/*checkout*/docs/Model
/fgfs-model-howto.html?rev=1.8cvsroot=FlightGear-0.9
Thanks. I will check that out.
From A320-fb.xml :
model
pathAircraft/747
Ampere K. Hardraade wrote:
I meant, if in such XML file:
?xml version=1.0?
PropertyList
pathMD-11.3ds/path
offsets
z-m0/z-m
x-m-25/x-m
pitch-deg-0.5/pitch-deg
/offsets
!-- Cockpit --
model
pathAircraft/MD11/Models/cockpit/cockpit.xml/path
/model
...
!-- Mesh
Alex Romosan wrote:
Erik Hofman [EMAIL PROTECTED] writes:
Andy Ross wrote:
Erik Hofman wrote:
Since FlightGear is linked to libGL at link time, the number of
dlclose calls would always be one less than the number of dlopen
calls.
In which case the dlclose() is 100% guaranteed to be
Alex Romosan wrote:
Frederic Bouvier [EMAIL PROTECTED] writes:
Anyway, a fix is in CVS now
not exactly. the fix is ugly beyond belief. it basically boils down
to commenting out dlclose() (despite all that code being moved
around). it also misses out a call to dlerror() after dlopen
Alex Romosan wrote:
Erik Hofman [EMAIL PROTECTED] writes:
Alex Romosan wrote:
you are mixing static and dynamic linking. andy is talking about
dynamic linking. i am not sure what you are talking about.
Statically linking a shared-object library only means it gets
dynamically
Alex Romosan wrote:
Frederic Bouvier writes:
The fact that you are using the function pointer *after* dlclose
is as broken as Erik's version. This is not good practise to
bet on side effects that are beyond your control.
_NO_, because the pointer now points to an object in memory
Erik Hofman wrote:
Ampere K. Hardraade wrote:
I have found another thing that is quite interesting. May be this have
something to do with the fact that the opacity of my objects is 98%, but
FlightGear seem to have trouble displaying multiple partially
transparent
objects that are
Erik Hofman wrote:
Alex Romosan wrote:
trying to debug why i wasn't able to run flightgear on my laptop, i
think i found a problem with SGLookupFunction. the problem is that we
call dlclose() before we return the pointer to the GL function, and,
if i understand things correctly, this
Roy Vegard Ovesen wrote:
I was looking at the clouds at KSFO today and noticed that the clouds were
moving towards the wind as indicated by the windsock. Windsock pointed
towards 80 deg and clouds were moving towards 260 deg.
I checked the environment subtree in the property browser, and
Alex Romosan wrote:
Frederic Bouvier writes:
So, if the library is really unloaded, the pointer access should be
really undefined and could lead to a segfault. Anyway, is it really
mandatory to do dlclose after getting the pointer ? It is if we do
dlopen every time we get a pointer
Phillip Jones wrote:
I just compiled 0.9.4 from source (using cygwin), and noticed the
aileron problem on the C172 (I saw the thread about this and know that's
its already fixed in CVS). What I find strange is that the pre-compiled
binaries do not have this same bug. Anyone know why this
chandrasekhar achalla wrote:
Hi,
I was wondering how can you read and modify .btg files, because I
couldnot get
PPE to compile ( I believe there is no support for PPE since the project
is dead). Is there any way to read and modify btg's ?
fgsd can read flightgear sceneries
-Fred
Erik Hofman wrote:
Chris Metzler wrote:
hi. the radio towers introduced all over the place in the new scenery
build don't appear to be present in the copy of the default area that's
in CVS. if i use the data rsync'd from Scenery-0.9.5 for the default
area, they're all over the place;
Josh Babcock wrote:
Jim Wilson wrote:
Josh Babcock said:
and bitmaps. However, one of the things that can currently only be done
in the
control's model file is orientation. I think this is a mistake.
Orientation,
like placement, should be defined outside the xml for a given control.
Melchior FRANZ wrote:
* Vivian Meazza -- Monday 14 June 2004 11:57:
I downloaded and built the CVS source code this morning (Monday) under
Cygwin/Xp - it builds without error. I also downloaded the data.
FGFS fails to run, stopping with:
Adding subsystem Traffic Manager
Unknown
Jacek wrote:
Curtis L. Olson wrote:
Is there any functionality currently built into FG to request that the
mouse pointer be turned off or hidden. This would be useful for
things like a dedicated visual channel.
Likewise, I quickly browsed through the source code and couldn't see
Norman Vine wrote:
Alex Romosan writes:
Norman Vine [EMAIL PROTECTED] writes:
Doesn't SGPath.apapend just do the right thing here ?
i.e. there shouldn't be a need to do the
! #ifdef _MSC_VER
! tmp.append( ;);
! #else
! tmp.append( :);
!
Alex Romosan wrote:
sorry, i meant sgSearchPathSep (as you correctly point out). the more
i look at the code in sg_path.cxx, the more confused i get. what
exactly is it being fixed by SGPath::fix()?
It changes all occurences of '\' into '/' because MS runtime is able
to cope with '/' and
I am getting this on the console :
WARNING: ssgLoad3ds: Texture coords missing.
WARNING: ssgLoad3ds: Texture coords missing.
WARNING: ssgLoad3ds: Texture coords missing.
WARNING: ssgLoad3ds: Texture coords missing.
Object Stabilizer01 not found
Object Stabilizer03 not found
Any idea ?
-Fred
June 2004 19:09, Frederic Bouvier wrote:
I am getting this on the console :
WARNING: ssgLoad3ds: Texture coords missing.
WARNING: ssgLoad3ds: Texture coords missing.
WARNING: ssgLoad3ds: Texture coords missing.
WARNING: ssgLoad3ds: Texture coords missing.
Object Stabilizer01 not found
Roy Vegard Ovesen wrote:
On Saturday 05 June 2004 00:25, Lee Elliott wrote:
This might be due to the ordering of the transparent objects relative to
the non-transparent parts. Is/are the model objects in .AC format?
I use Blender, and export to .AC format.
If so
(I don't know if this
Alex Romosan wrote:
Curtis L. Olson [EMAIL PROTECTED] writes:
How do I turn off the bump mapped cloud feature? Under some
conditions it looks great, and other times it looks horrible. I'd
like to turn it off to compare.
Here's what I'm seeing right now at KSFO:
Mathias Fröhlich wrote:
Mathias Fröhlich wrote:
No itoa is not standard. I have already a patch on top of Jons changes to
JSBSim in my local tree which uses stringstream which is standard C++
since ages.
The stringstream class would have the advantage that it is not error
prone
Roman Grigoriev wrote:
Hi guys!
I'ts nice to have this feature in flightgear and looks really cool
but another very nice feature is VBO (works on all PC videocards (ATI and
Nvidia))
I use it and have some speedup now I improved my version of ssgVtxTable on
VBO
if someone intrested feel
Keeyoung,
I just tried with the Windows 0.9.4 version and the CVS one and both work
for me. The heading is
set as well as the pitch. With the 0.9.4 version, if you use fgrun, add
/sim/view/config/heading-offset-deg=45
/sim/view/config/pitch-offset-deg=3
in the 'properties' page of the
Jim Wilson wrote:
Ampere K. Hardraade said:
Are we using spline for the taxi way at the moment?
No we are not.
We are using nurbs only to interpolate the terrain at
the airport area.
-Fred
___
Flightgear-devel mailing list
[EMAIL
Giles Robertson wrote:
This was sorted out by uncommenting lines 2829 of cloud.cxx:
// #if defined (__APPLE__)
// // any C++ header file undefines isinf and isnan
// // so this should be included before iostream
inline int (isinf)(double r) { return isinf(r); } //See below
inline int
(__MINGW32__)
inline int (isnan)(double r) { return isnan(r); }
#endif
Diff:
31c
inline int (isnan)(double r) { return isnan(r); }
Still don't understand what the problem is, though.
Giles Robertson
[EMAIL PROTECTED]
-Original Message-
From: Frederic Bouvier [mailto:[EMAIL PROTECTED]
Sent: 21
Vivian Meazza wrote:
It's well broken when trying to compile under Cygwin. Too many error to
even
start to list in clouds.cxx, I think, but by no means certain could be in
clouds_3d.
Any suggestions?
No suggestion if you don't list at least the first messages, sorry.
-Fred
Jim Wilson wrote:
Curtis L. Olson said:
David Megginson wrote:
I'm under a serious spam attack from an infected computer of someone
on the list. Here is where the spam is originating:
user-24-214-247-18.knology.net
Many of the spams are arriving with Curt's e-mail
David Culp wrote:
Nope, didn't help.
It seems like the problem starts when all flightplan objects reach their
destination.
I'm not getting segfaults here, but I do see that the AI objects are not
binding to properties properly. When I have one sailboat and two
airplanes
running I see
301 - 400 of 926 matches
Mail list logo