|
|
|||||||
| FM/DM threads Everything about FM/DM in CoD |
|
|
Thread Tools | Display Modes |
|
#11
10-15-2012, 11:43 PM
|
||||
|
||||
OK
 Yes ROC is not right. You might like to think about: Z_Accel_x = cur_Plane.getParameter(part.ParameterTypes.Z_Overl oad, 0); Z_Accel_y = cur_Plane.getParameter(part.ParameterTypes.Z_Overl oad, 1); Z_Accel_z = cur_Plane.getParameter(part.ParameterTypes.Z_Overl oad, 2); x = accleration fore/aft y = accleration left/right z = accleration up/down z lets you know if you are accelerating up or down (changing height). I 'filter' by eyeball when assessing the records I get back, looking for 1.0, +/- about 0.03 to get a stable string of records. I also cross check for stable altitude +/- a few feet but within about 20 feet of the test altitude and for the IAS or TAS staying at best speed for good level flight. Its surprising how quickly it settles down, maybe 5 minutes, and how stable and predictable the returns are even over minor changes in height and Z_Accel_z ('G'). Makes it easy to see where speed is changing and why and to pick out the most appropriate result.
__________________
klem 56 Squadron RAF "Firebirds" http://firebirds.2ndtaf.org.uk/  ASUS Sabertooth X58 /i7 950 @ 4GHz / 6Gb DDR3 1600 CAS8 / EVGA GTX570 GPU 1.28Gb superclocked / Crucial 128Gb SSD SATA III 6Gb/s, 355Mb-215Mb Read-Write / 850W PSU Windows 7 64 bit Home Premium / Samsung 22" 226BW @ 1680 x 1050 / TrackIR4 with TrackIR5 software / Saitek X52 Pro & Rudders Last edited by klem; 10-15-2012 at 11:46 PM. 
|
|
|
Threaded Mode