Fubar512 Posted July 11, 2007 Posted July 11, 2007 Most default and third-party aircraft have too low a deployment velocity for their countermeasures. A bit of research shows that 30 meters per second is the approximate average muzzle or ejection velocity achieved by CM dispensers in real life. Below is an example of the CM values I'm currently using on one aircraft model I was involved with. [FlareDispenser] ReferenceName=AN/ALE-40 SystemType=DECOY_DISPENSER EjectPosition= -3.0,-4.15,-0.05 EjectVelocity=-30.0,0.0,-30.0<---statement and value of interest The first number in the value-set is -30.0. This tells the dispenser to eject the flare towards the left at a velocity of 30.0 m/s. A positive number (30.0) would throw the CM towards the right, likewise at 30 m/s. The second set of numbers would impart forward (positive) or an aft (negative) velocity to the CM. In this case, we're using zero, so the the CM does not have a longitudinal vector. The final number, "-30.0", imparts velocity in a vertical vector. Negative values for down, positive for up. Next, using the SFP1E tool, extract the countermeasureobject.ini file from the objectdata.cat. By default, a copy will be extracted into the objects directory, where it can be edited and where it will reside. Edit it to match the data posted below: [ChaffData] EffectName=ChaffEffect RadarCrossSection=100.0 <---this is a fairly accurate "average" value derived from web research. MaxVisibleDistance=300 <---limits any possible hit on rendering speed (FPS) DragFactor=5.0 <---may possibly be higher in RL LifeTime=15.0 Length=5.5 <---this is a fairly accurate "average" value derived from web research. VelocityDeviation=0.3 [FlareData] EffectName=FlareEffect MaxVisibleDistance=3000 <---limits any possible hit on rendering speed (FPS) HeatSignature=100.0 <---series specific DragFactor=1.00 LifeTime=4.0 <---this is a fairly accurate "average" value derived from web research. VelocityDeviation=0.3
Recommended Posts