is as solid as a rock with the default turbulence all the way down the
glide slope. With the turbulence zero, both behave the same.
The SenecaII wing rock with light turbulence appears to result from a
very exaggerated adverse aileron yaw. So I did the same experiment
with the c172p and
On 07/10/2007, Jon S. Berndt [EMAIL PROTECTED] wrote:
I looked at the configuration file for the Seneca II in flightgear cvs. It
appears to me (at least given the quick glance I took) that adverse aileron
yaw (Cnda) is turned off - the data is all zeros.
I'm not sure about the exact
On 10/8/07, James Reinsberg [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED]:~/applications/FlightGear/source$ fgfs
*** glibc detected *** fgfs: free(): invalid pointer: 0x08746e10 ***
=== Backtrace: =
/lib/tls/i686/cmov/libc.so.6[0xb74037cd]
2007/10/6, Thomas [EMAIL PROTECTED]:
plib (0.9.11pre) version:
http://www.rato.us/flightgear/builds/plib/20071005plibexe.zip
Just in case you'd like to try that version:
http://www.rato.us/flightgear/builds/osg/20071005osgexe.zip
Thanks Thomas for your exe's!
But I got this, after
On Monday 08 October 2007 02:17, dave perry wrote:
While optimizing the aitopilot config files for the Century IIB and III
autopilots for the pa24 and the Altimatic IIIc for the SenecaII, a
significant difference between the values of parameters (gains in
particular) that give non oscillatory
Is auto-coordination enabled? I don't think this is effective for
YASim
aircraft but it may be complicating things on JSBSim aircraft. Also,
are you
getting the same frame-rates with both aircraft? Last time I ran FG I
found
that the autopilot PID controllers ran at the frame rate and
leee wrote:
On Monday 08 October 2007 02:17, dave perry wrote:
While optimizing the aitopilot config files for the Century IIB and III
autopilots for the pa24 and the Altimatic IIIc for the SenecaII, a
significant difference between the values of parameters (gains in
particular) that give
Vadym Kukhtin wrote:
2007/10/6, Thomas [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]:
plib (0.9.11pre) version:
http://www.rato.us/flightgear/builds/plib/20071005plibexe.zip
http://www.rato.us/flightgear/builds/plib/20071005plibexe.zip
Just in case you'd like to try that
Hi,
A video of Sea Kings starting and landing an a ship:
http://pilotservices.streamlinenettrial.co.uk/videos/*Sea_Kings_on_Deck.wmv*
this video is not of very good quality, but it's more than worth to see.
Maik
Robert Black schrieb am 08.10.2007 03:03:
On Wednesday 03 October 2007 19:05,
Reagan Thomas ha scritto:
Vadym Kukhtin wrote:
2007/10/6, Thomas [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]:
plib (0.9.11pre) version:
http://www.rato.us/flightgear/builds/plib/20071005plibexe.zip
http://www.rato.us/flightgear/builds/plib/20071005plibexe.zip
Just in case
Roberto Inzerillo wrote:
Reagan Thomas ha scritto:
Vadym Kukhtin wrote:
2007/10/6, Thomas [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]:
plib (0.9.11pre) version:
http://www.rato.us/flightgear/builds/plib/20071005plibexe.zip
Hi All,
Please find below a patch for the vulcan to fix the liveries on plib.
I'd be grateful if someone would commit it to CVS.
Thanks
-Stuart
Index: vulcanb2-set.xml
===
RCS file:
I think Jon B. is onto something by asking how turbulence is
implemented in the various fdms.
Thanks for the ideas,
Dave
Does anyone know what typical values are for these two properties:
/environment/turbulence/magnitude-norm
/environment/turbulence/rate-hz
The fact that the first
The SenecaII wing rock with light turbulence appears to result from a
very exaggerated adverse aileron yaw. So I did the same experiment
with
the c172p and pa28-140 which both use the kap140. With the default
turbulence, the c172p oscillates so bad that you cannot complete the
approach
On Monday 08 October 2007 02:17, dave perry wrote:
The SenecaII wing rock with light turbulence appears to result from a
very exaggerated adverse aileron yaw.
So I did the same experiment with
the c172p and pa28-140
I agree that they both exhibit unrealistically bad handing
On 08/10/2007, Jon S. Berndt [EMAIL PROTECTED] wrote:
Does anyone know what typical values are for these two properties:
/environment/turbulence/magnitude-norm
/environment/turbulence/rate-hz
The fact that the first property is named magnitude-norm (emphasis on the
*norm*) makes me suspect
Csaba,
Indeed. I have a Radeon X1950 pro. Am I out of luck?
Thanks again,
Jim Reinsberg
Csaba Halász [EMAIL PROTECTED] wrote:
On 10/8/07, James Reinsberg wrote:
[EMAIL PROTECTED]:~/applications/FlightGear/source$ fgfs
*** glibc detected *** fgfs: free(): invalid pointer:
I helped implement this with Tony a few years ago. As I recall, the
value was from 0 to 1, where 0 represents no turbulence, and 1
represents the most severe turbulence that we model. You couldn't
represent turbulence simply in feet/second, because it consists of
both movements and
I don't think that's the primary issue ... although there
might be a /secondary/ issue with the kap140 being more
vulnerable to bad handling characteristics than some other
autopilots are; I don't know. I recommend fixing the
flight dynamics first, and only then looking to see what
More on turbulence. At least in the copy of JSBSim.cxx that I have there is
this code in Copy_to_JSBSim:
tmp = turbulence_gain-getDoubleValue();
Atmosphere-SetTurbGain(tmp * tmp * 100.0);
tmp = turbulence_rate-getDoubleValue();
Atmosphere-SetTurbRate(tmp);
There are two gains
20 matches
Mail list logo
