yeah this is great idea especially for instrument training, something like the
attitude indicator, plus single engine flight in the twins is always interesting.
Paul
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman
I just got the MacOS X 10.1 version of FlightGear build and submitted to Darrell. The
compiler used by 10.1 REALLY doesn't like the GL* type warnings that are present in
the 3D cloud subsystem. It always aborted the build, even though they were warnings
instead of errors.
Any idea as to how l
What kind of failts would you model. In the Big Sims (as you have probably
seen) you may have the ability to set particular variables to a particular
value, or delta-value, at a scripted time, or several at once, along with
flags, etc. How do you plan on implementing fault values? A malfunction
fla
I'm looking at doing some fault modeling ... things like failing
various instruments, CDI, GS, to/from flag failing, and quite a few
other things with avionics, electrical, fuel, flaps, engines, etc.
What makes the most sense to me is to create a section for faults in
the property tree /sim/faults
On Saturday, December 14, 2002, at 08:20 pm, darrell.l.walisser.1
wrote:
I would like to get joystick support included soon (this would involve
working on PLIB). Is anyone else already working on this?
I am about to, by porting Max Horn's work in SDL to plib. I've got as
far as reading over
I updated SimGear, FlightGear, and fgfsbase Friday the 13th in the
evening. I also updated the nvidia driver to 1.0-4191 using source
RPMS. After compiling the fgfs stuf and installing the new nvidia
drivers, I get a segfault trying to load the first tiles. I went back
to a version of Flight
Martin Spott wrote:
Martin Spott wrote:
...
Oh, you get heavily increased torque from the ailerons for manouverability
and you get much more lift from large wings at low speed - especially
because on the current design at least 90 % of the wing area suffers from
the down-wind generated by th
Jon Berndt <[EMAIL PROTECTED]> said:
> I don't really think that the CG (or anything like it) should have
> anything to do with a common reference point. I think it should be
> something you can readily see. The nose/prop hub tip is about as
> unambiguous as it gets. Due to the nature of defining
> Yes, I knew this would sound a little complicated with swept,delta,body
wing
> aircraft. But making it the nose really just puts the decision on to
the 3D
> Modeler where to some degree the flight model designer could have a
better
> idea. Isn't there some way of deriving an average or nominal
I've posted a build that works on 10.2 (not binary-compatible with 10.1).
I didn't have the problem with ATCVoice like Jonathan did because I cvs
up'd and got the new version that fixed the problem (the original code had
endian issues which caused a crash when loading the wav file).
http://homepag
Jon Berndt <[EMAIL PROTECTED]> said:
> It's neither impractical nor complex. FWIW, there really is a standard
> already out there, and we use it. That is, the structural frame, as I have
> outlined before. The only problem I see is that the FDM and the 3D model
> rendering code need to have a stat
John Check [EMAIL PROTECTED]
Sat, 14 Dec 2002 13:52:27 -0500
Previous message: [Flightgear-devel] comments
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Saturday 14 December 2002 1:06 pm, paul mccann wrote:
> [Flightgear-devel] patch and screenshot
>
> John Check [EMAIL PRO
> Really we just need the FDMs to agree on something. Or maybe
> not...maybe the
> idea of sharing 3DModel configs between FDMs (c310-jsbsim,
> c310-yasim pointing
> to the same model.xml) is impratical or too complex? Certainly if one
FDM
> models gear compression and the other doesn't, that is
Jon Berndt <[EMAIL PROTECTED]> said:
> Tony wrote:
>
> > Are we sure we want to put the 3D model origin to cg offsets in the FDM
> > config file. IIRC, having multiple 3D models for any one aero model is
> > pretty standard fare in the MSFS world.
>
> The only thing we'd do different in JSBSim
Jon Berndt <[EMAIL PROTECTED]> said:
> > IMHO it'd make the most sense to put the offset (from the nose or
> > tail) to the
> > 3D model origin location into the FDM's aircraft config xml file. This
> > location should be on the leading edge of the wings and z axis
> > centered on the
> > nose a
Tony wrote:
> Are we sure we want to put the 3D model origin to cg offsets in the FDM
> config file. IIRC, having multiple 3D models for any one aero model is
> pretty standard fare in the MSFS world.
The only thing we'd do different in JSBSim is to say where the nose/prop
tip is. This would giv
On Saturday 14 December 2002 1:06 pm, paul mccann wrote:
> [Flightgear-devel] patch and screenshot
>
> John Check [EMAIL PROTECTED]
> Fri, 13 Dec 2002 16:05:52 -0500
>
> Previous message: [Flightgear-devel] patch and screenshot
> Next message: [Flightgear-devel] Fwd: Re: preferences.xml change
> Me
On Saturday 14 December 2002 12:17 pm, paul mccann wrote:
> Umm the patch for the hsi and rmi was slightly broken. The
> c310-ifr-set.xml was not right, so I changed that and everything is working
> again.
>
> patch is here
>
> http://members.verizon.net/~vze3b42n/patch9.1.tar.gz
>
Cool thanks. I
[Flightgear-devel] patch and screenshot
John Check [EMAIL PROTECTED]
Fri, 13 Dec 2002 16:05:52 -0500
Previous message: [Flightgear-devel] patch and screenshot
Next message: [Flightgear-devel] Fwd: Re: preferences.xml change
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On T
Man, I've been busy with real life lately[1][2], so I need you guys to tell
me what I need to know in order to update the FAQ[3] and Developer
Locations page[4].
If you have any questions you are tired of answering, send me the
question and answer, and I'll work it into the FAQ. Some things have
Jim Wilson writes:
> Norman Vine <[EMAIL PROTECTED]> said:
>
> > In your example you may not see the error but .
>
> What I meant was that offseting to the varible center of gravity wouldn't be
> visible either outside or inside the aircraft. The FDM already provides the
> attitude effects,
> Martin Spott wrote:
>> This does not have to be as difficult as it is with the V-22. The Osprey is
>> designed for being stuffed into _very_ small space below a ship's deck.
>> If they had more space then it would have been possible to improve security
>> simply by increasing the wing span,
>>
Umm the patch for the hsi and rmi was slightly broken. The c310-ifr-set.xml
was not right, so I changed that and everything is working again.
patch is here
http://members.verizon.net/~vze3b42n/patch9.1.tar.gz
updated screenshot
http://members.verizon.net/~vze3b42n/fgfs-screen-001.jpeg
Paul
On Sat, 2002-12-14 at 07:26, Jon Berndt wrote:
> > IMHO it'd make the most sense to put the offset (from the nose or
> > tail) to the
> > 3D model origin location into the FDM's aircraft config xml file. This
> > location should be on the leading edge of the wings and z axis
> > centered on the
>
> IMHO it'd make the most sense to put the offset (from the nose or
> tail) to the
> 3D model origin location into the FDM's aircraft config xml file. This
> location should be on the leading edge of the wings and z axis
> centered on the
> nose as described above. The 3D modeler's could refer t
Norman Vine <[EMAIL PROTECTED]> said:
> In your example you may not see the error but .
What I meant was that offseting to the varible center of gravity wouldn't be
visible either outside or inside the aircraft. The FDM already provides the
attitude effects, it is the change in axes that wou
Arnt Karlsen wrote:
Helicopters
---
Bell AH-1S SuperCobra
Kaman K1200 K-max
Sikorsky UH-60 BlackHawk
..use/develop the fdm from http://autopilot.sourceforge.net/ ?
I *think* we get the message by now ...
;-)
Erik
___
Flightgear-devel mai
David Megginson wrote:
OK, finally I understand the problem. What we need to do, then, is
apply the euler angles to the CG rather than the origin when rotating
the 3D model. We need only two steps:
1. have the FDMs report the current CG relative to the origin (if they
don't already); and
2
28 matches
Mail list logo
