Running FG under cygwin allows the socket output to be set to the broadcast address,
192.xxx.xxx.255. But under linux Fg returns an error
that make_client_socket failed for the broadcast address. Looks like cygwin is
faking it.
Not necessarily. Did you declare that to be the broadcast
so it sounds like it's best to leave the defaults alone and run from
/usr/local/bin. And should one assume
that by putting the base in /usr/local/FlightGear/ requires NO argument to
set the root for fgfs
Err, I've got my base in /usr/local/lib/FlightGear and I don't recall
over-riding
Anyway, like I said, I'll go with the flow on whatever the consensus is,
but I would really prefer a situation where rm -rf Aircraft/whatever
would remove an entire plane. Does it make sense? To me, yes.
I would like every directory to contain a file that lists the relative path
to every
The statement in question is this:
Many pilots have not been made aware that full rudder inputs,
under certain conditions, can jeopardize the integrity of the
vertical tail fin and that in some airline modes, rudder
deflections can be achieved with relatively small pedal
http://web.mit.edu/newsoffice/nr/2002/robochopper.html
Their ground station seems to have telemetry but no visualization ...
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
checking for gluLookedAt in -lGLU... (cached) no
checking for gluLookedAt in -lMesaGlu... (cached) no
checking for glutGetModifiers in -lfreeglut... (cached) no
checking for glutGetModifiers in -lglut... (cached) no
It's possible that those are static on SUSE, so aren't installed
if
So, what you are saying is that my having set the visibility to 90
statute miles was not a good thing? ;) Any ideas as to what I should
expect for a worst-case visibility? The reason I chose such a large
visibility is because the fog effect looked, to me, more like fog and
less like
Not
being a pilot, I am sure that may visibility range is set too high
If you want realistic numbers to try (for the US pacific coast) ...
* Set the time to 3pm local and visisility to 6 statute miles.
* Or 9am and 20 statute miles.
* If you want to pretend it's a cold clear sunny day after
You don't expect a software rendering 386 to give decent frame rates, do
you?
Haven't tried that yet, because just the FGFS base is 50MB ... and that PC
only has a 100MB HD. My 486 doesn't do very well, due to software 3D.
If I come across an ISA 3D card spare, I try it ... it might be
To explain what Erik's talking about: You don't get an appropriate video
card that you can use in an SGI for just $50. 2x 4 MByte Texture RAM to
upgrade an Octane SSI to MXI cost more than $1000 - and you can't use
FlightGear's textured scenerey without TRAM
In my last job we ran a
Alex, what sgi hardware features are you referring to, and are these
available on any of the machines our developers have access to?
I'm still not sure what special graphics features sgi provides (that
something like a mid-hi level geforce card doesn't) that we'd be
interested in.
I'm
Someone should actually go through all the entries and pick
appropriate non-texture colors for each material. I thought it would
be intresting to taket the average of all the pixels in the texture,
but never got around to seeing how well that would work. But it's
something you could then
Hi Guys!
Yerstaday i had to reinstall my linux and my second CD from mandrake linux
distribution was scratched
so i download missing developers (zlib,jpeg,png) packets from internet in
rpm format and install them using rpmdrake utility
but when i run ./configure script i see this results
Alex warns:
JSBSim actually works very hard to simulate realistically and uses
the processor; with logging turned on, it does significant disk I/O.
If you're short of memory and having to swap, the extra disk load
can crucify the performance of Windows to keep the application running.
Jon
From: Alex Perry [EMAIL PROTECTED]
Under Debian, the headers for the compiler are separate from the binaries
for runtime. Did you install both parts ?
yes i've installed all parts from rpm packages I have library libpng.a and
libpng.so in /usr/lib directory
and when I installed runtime
Real time plotting is something I've always wanted to do. There is the
remnant of a socket interface in FGfdmSocket, and it is/was used in
FGOutput. I actually wrote a small program that accepted data from a JSBSim
output stream a couple years ago. I haven't seen xoscope. What is it?
Alex Perry writes:
Disused airfields are fairly common in the UK, can I suggest the
ability to handle these is something add to the 'to do' list?
Basically, we just need to support closed (X) runways, then make
airports where all the runways are closed. CYOW, my home
From my research on the Web, the C172R default panel configuration
(and the typical C172R for sale on the Web) comes with a simple GPS
(not yet modelled), two NAVCOMM radios, ADF, transponder, and
autopilot (no altitude control). There are two VOR gauges, one of
which has a glidescope, and
In some ways, it was harder than it would be for a real pilot, since I
didn't have the peripheral vision or the motion cues (I cannot feel
when I'm in a slip, for example, or when I'm descending rapidly, and I
cannot feel any force feedback from the controls).
Don't be too sure; once you're
Open source software may also be tested, legally, also to
airworthiness standards. And, by the FAA too.
..which leaves closed source software behind as, _un-certifiable_.
That's true for various categories of avionics, which have coverage tests,
but not for inspection and training tools,
We can, though -- what kind of a noise should it be?
Kind of a fluttering noise; lots of burbling.
In high engine power conditions for prop planes, there is another sound
that is due to the prop disk loading being asymmetric when uncoordinated.
The other reason for prop asymmetry is due to
Disused airfields are fairly common in the UK, can I suggest the
ability to handle these is something add to the 'to do' list?
Basically, we just need to support closed (X) runways, then make
airports where all the runways are closed. CYOW, my home airport, has
one closed runway itself.
I'm not terribly familiar with the airport database code, but I can't
believe these would be difficult to support. Just make up a few new
runway textures with big yellow X's on them. The hard part will be
finding the data for the ancient runway locations. Anyone?
The NOS charting service
Could we abandon MetaKit completely please?
The 2.4.2-32 version which is supplied by SimGear doesn't compiler
properly. I vote for using David's plain text sulution (at least for now).
I don't recall David's solution.
It seems to me that we're only using MK for doing simple record lookups
3. it uses a single audio buffer, instead of the commonly accepted
dubbel buffering principle.
The PLIB itself is single buffered, but that's ok because the sound
driver itself on Linux and Windows (dunno about irix) is multi-buffered.
___
On the other machine, using current FGFS CVS stuff, takeoff works fine.
What versions of stuff were you using and having trouble with ?
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Why? When you fill up the tanks at the airfield, does the pump count in
pounds? I think a better solution would be to leave it as a volume
measurement and setup a fuel weight-per-gallon value in the FDM. Having
to set the fuel amount as a weight value seems non-intuitive to me.
For light
I've twice committed a patch wich gets audio (sort of) working for Irix
(audio realy is crap in plib anyway) but it didn't get included, without
a reason, without any notice.
It took me some consistent hassling, too.
So plib devlopers can do their own business, but I'm moving on.
Don't
On Tue, 2002-01-15 at 07:19, Christian Mayer wrote:
What we really need here is for our resident flight control systems
expert to whip us up a program for generating the control law gains
based on the config file ...
It's probably easier to adapt the autoconfiguration algorithms for PID
Well, JSBSim theoretically has the building blocks for an autopilot, same as
for an FCS. I have mentioned before that this is one thing I'd like to add
in. The caveat of course is not to break anything that currently exists,
piss anyone off, or preclude some other FDM from working correctly.
PS: Are there already some volunteers for LinuxTag?
Show floor is open on 6 June to 9 June inclusive, in Karlsruhe Germany.
I'm on the notification lists for the event. As far as I know,
they are not accepting presentation topics or booth requests yet.
It would be nice if we could freeze and release 0.7.9 in the next two weeks.
That way, people visiting the LWCE booth in New York will be able to download
something that looks like the version being demonstrated at the show.
Currently, the release is six months out of date, and a lot has changed
You are correct; I'll have to look at it too, now.
I believe the to/from is independent of aircraft heading and only denotes position
left or right of the orthogonal vector to the selected radial.
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
Going thru the FG nav code for FG I noticed the To/From flag calculation in
radiostack.cxx.
I think it's ok; you might be confusing the nav_heading variable with the
aircraft_heading variable; the former is simply the actual radial.
Using the latter would give the behavior you're implying.
I added some uruguayan airports to default.apt in the alphabetically
corresponding place:
I think you need to rebuild the relevant part of the scenery with the
modified default.apt before using the airport.
That'll give you runways. You also have to rebuild the database file,
since that
It would be nice if the newmat.cxx would check some global
property, set in the preferences.xml, to determine the
highest resolution texture that is acceptable. That way,
it can load whatever file is appropriate and (if needed)
force a minimum mipmapping level on the basic texture.
Any machine
I'm having problems with WinCVS
I don't use it, but ...
cvs checkout -P -d var/cvs/FlightGear-0.7 var/cvs/FlightGear-0.7 (in
directory C:\FlightGear-0.7.8)
Don't you need a leading slash inside the -d var and the module name
is simply FlightGear without any additional elaboration.
This sound system seems to work very
well in Windows. Might be better than
what is now used? Linuxable also.
As a matter of policy, please review the mailing list archives before
starting discussion threads on topics that have already been examined.
Since the PLIB project is considering
On my computer sound stops playing after 5s!
PC/Win98.
Surprised; it works fine on both my Linux and Windows machines.
Are you running accelerated ? ... i.e. a framerate above 1 sec ?
Do you have the engine running ? Have you tried using a nav radio ?
First, the obvious solution is not to run 1.2.x ...
after all, the 1.4 series has been released stable.
Second, from memory (back when I was running 1.2)
the bug was only a problem with navaid sound effects.
I have tested this several times .. even with my self
compiled version. The sound
Well, from _my_ point of view (aka PLIB and SimGear from CVS on Debian)
it builds fine ... and has done for months.
Can someone please
give me an opinion on these, even if it's 'shut up Ross, you idiot!'. :)
Well, I won't say that ... but my standard response is not much more helpful:
Sigh ...
I just try to find a sim that makes the job. Hard to find!
Different people have different goals for use of a simulator.
If you can't find the simulator you want, then you have to write it,
or pay someone to write the code you want to have available.
There's a dozen projects out there
Not true!
I dispute that.
All windows should be equal after 95.
Yes, they should.
No, they aren't.
They all use the same WIN32 core.
No, they don't.
And they even
run the same exe files!
Yes, they do, but
I don't see what that has to do with the filesystem.
For a programmer there
Not to disagree with what you said
lowsy physics.
I think the word is lousy meaning infested with lice. Appropriate ?
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
For some reason I always envisioned flying through the ground like it
wasn't even there, except once you arrive underneath it's all fire,
and molten lava, and pitchforks, and screaming, and stuff, and it's
all dark and you aren't allowed to climb back above the surface
That's a good idea;
My question is how to auto shutdown slave computer when I power off master
computer? Maybe write script that use rsh?
I'd have the slaves ping the master's IP address every six seconds for a
count of 10 (i.e. one minute). If no response whatsoever is received,
shut down the machine. That
Yup, support for these sorts of signs is in the code, but right now
you have to manually place them which is tedious. It would be nice to
figure out an automated way to place the signs ... they wouldn't
necessarily be true to life, but at least believable. But I haven't
even thought about
I dont know if it is a realistic effect, but, since some cvs versions ago,
the compass is stalled most of the time, so it is impossible to know the
real magnetic heading.
I find that most noticable with the C310 -- I wonder if it's because
the accelerations (etc.) are much higher than
$ ./configure
creating cache ./config.cache
./configure: line 542: syntax error near unexpected token
`AM_INIT_AUTOMAKE(FlightGear,'
./configure: line 542: `AM_INIT_AUTOMAKE(FlightGear, 0.7.9)'
$
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
* [EMAIL PROTECTED] (Alex Perry) [2001.12.21 16:15]:
$ ./configure
creating cache ./config.cache
./configure: line 542: syntax error near unexpected token
`AM_INIT_AUTOMAKE(FlightGear,'
./configure: line 542: `AM_INIT_AUTOMAKE(FlightGear, 0.7.9)'
$
configure.in hasn't changed
The reason I wanted to add this feature was for aircraft fitted with
variable pitch props. As it is, its a bit too easy to set a given rpm
and manifold pressure for cruise. In the real world as the rpm is
changed by changing the prop lever the manifold pressure should
change very
No, you're switching it back. :-) We want it inside the xml/ directory
just like it is in the simgear source tree. What's in CVS is correct.
Make sure you update your Simgear sources too because the Makefiles have
changed to fix the install location.
True, sorry. I noticed that make
1. they make the airports easier to spot from a distance, and
Yeah, but unless we put buildings everywhere, the airports will be too
easy to find. It is already easier to spot airports on the simulator
than they are in real life; let's not make it too trivial.
2. they give the user a
You see aircraft three ways ...
Yes, of course. You are kind of biased, though
Yeah, but think of it this way ... do you really think many people want
to dogfight with C172s ? I mean, it's one thing to do a highres dogfight
model of a fighter, or an aerobatic biplane ...
When did we get bullets, or collision detection? First things first.
Collision detection (with bullets) is relatively easy. And anyway,
I thought someone was implementing secondary aero bodies 8-)
___
Flightgear-devel mailing list
[EMAIL
The one time I tried running flightgear between two linux boxes using
glx, I was very successful. So I think you stand a good chance of
working with linux - linux or sgi - sgi, but cross platform
doesn't seem to work very well in my experience.
The two big problems I've seen are ...
1. NV
It might have something to do with endianness i guess ?
I don't think so, as I was able to run 'glxgears' Linux - SGI (oder ISDN!),
A lot of the problems happen when you start texturing ...
and gears does not texture. Try running the arbtex demo or similar.
Mentor, the monthly magazine of the National Association of Flight
Instructors, recently ran an article that describes how a PCATD might be used
to conduct 10 hours of basic instrument training. It's interesting to note
what aspects can, and cannot, currently be performed using
The SGI-based developers of FlightGear might be interested in this ...
If we submit a team entry, do we all get free passes to the conference ? 8-)
Subject: SGI Developer Edge - FLASH
From: [EMAIL PROTECTED]
D E V E L O P E RE D G E
It occurs to me that some developers who're interested in FGFS
having distributed simulation capabilities might want to see this ...
http://spie.org/Conferences/Calls/02/or/confs/OR21.html
Similarly, this conference stream seems aimed at Curt's work
and the whole visual display XML
I also tried getting Atlas up and running on my debian machine.
The configure script should be checking for plib and simgear being present.
In any case, atlas works fine with Debian; I'm using it under potato and woody.
Although flightgear itself is packaged for Debian, I have no idea whether
The controls work, but there is something wrong with the aero model;
I thought it was that the elevators are incredibly weak, but that's not it.
Try doing a straight power on stall, both for slow and for fast entry.
It's so wrong, I'm not currently sure what to blame the effect on ...
1) Bad idea? Good idea? Why?
* If you use typedefs in a header file that are easy to switch over,
* so that groups of calculation are consistently done in one mode,
* and you don't do stuff that would pipeline on a vector machine,
then it is easy to benchmark the effect. The impact should be
401 - 463 of 463 matches
Mail list logo
