On 02/12/2011 12:59 PM, Torsten Dreyer wrote: >> By the way. The filtering that will remain in the c172p action-sim.nas >> for the nav radio could be moved to navradio.cxx. Here again, the >> needle damping and the needle behavior when tuned to an out-of-range >> frequency or when the gs is out of range is device dependent. The >> filtered values are used by Aircraft/Instruments-3d/vor/vor.xml and >> vor2.xml. I was afraid that modifying navradio.cxx to achieve realistic >> needle behavior for this vor model might break other vor/gs head or hsi >> models. > We can now easily use the autopilot filters for that, just add a file with the > content > > <PropertyList> > <filter> > <name>CDI0 lowpass</name> > <debug>false</debug> > <type>exponential</type> > <filter-time>2.0</filter-time> > <input>instrumentation/nav[0]/heading-needle-deflection-norm</input> > <output>instrumentation/nav[0]/filtered-cdiNAV0-deflection</output> > </filter> > <!-- > More filters here > --> > </PropertyList> > > And add > <autopilot> > <name>A very descriptive name for this file like Instrument-Filter</name> > <path>Aircraft/c172p/path/to/that/file</path> > </autopilot> > > to c172p-set.xml under /sim/systems > > No need for coding here, too. > > Greetings, Torsten > I had not tried the kap140 in checking out the changes I submitted today for the c172p. While implementing similar changes to the pa24-250, I noticed that neither the Century IIB not the Century III autopilots work with the above filter method. So I flew the c172p again and sure enough, the kap140 is also broken by the above filter method. Apparently having two autopilots in the same AC "ist verboten". Torsten, have you tried two autopilots on an AC in the past?
I also tried using <PropertyList include="NAVandGSfilters.xml"> at the top of the actual autopilot xml file so the "new" filters in NAVandGSfilters.xml should have been as if they were part of the autopilot xml file. This gave no load error but also, the filters were not functioning. If I just copy the filters from NAVandGSfilters.xml into the actual autopilot xml right after the <PropertyList> tag, everything works including the new filters. This feels like an ugly hack. Should either loading the new filters as a 2nd autopilot of including the pseudo autopilot in the <PropertyList> tag have worked? Cheers, Dave P. ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
