View Single Post
  #225  
Old 05-15-2012, 09:17 PM
klem's Avatar
klem klem is offline
Approved Member
 
Join Date: Nov 2007
Posts: 1,653
Default

I did some tests using a modified version of a script called BlackBox which I found elsewhere on the forums to capture the RPM cut and G value.

Chart is attached. It seems the cutout is set to 0.5G and seems instantaneous. You can see the 'highest' G-value cut, the third red line from the left. Others are just more examples. 0.1G it definitely ain't.

The chart shows RPM vs G-force and the G-cut is easily seen just before the characteristic RPM overshoot that occurs after it recovers.

You Merlin flyers need to vote on this unless its already in hand. Many very minor bugs and features have more votes than this.
http://www.il2bugtracker.com/issues/230
Attached Images
File Type: jpg MerlinIII_cutout.jpg (757.9 KB, 18 views)
__________________
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; 05-15-2012 at 09:24 PM.
Reply With Quote