Nicholas Bell Posted April 14, 2016 Posted April 14, 2016 Here's how to stop your wingmen from "waltzing" from side to side in formation. Yeah, I know it's not really waltzing but that's what comes to my mind when they roll from one side to other in unison.I did a forum search and came up empty, so hope I'm not repeating old news... Each aircraft is a little different, and if you push the values too far they become too steady. Adjust to suite your taste - and post your edits on other aircraft.The critical factor is the MaxRollFormation. The common value of 5.0 creates overcorrection which starts the cycle of rolling from side to side.Examples:AlbatrosD3_Data.ini[AIData]..FormationSpeedForPosition=.4 //0.8FormationSpeedForRate=0.2 //0.5..MaxRollFormation=0.9 //5.0 <----criticalFormationRollForPosition=0.8 //0.01FormationRollForVelocity=0.05 //0.2.///////////////////////////////////CAMELF1_110_DATA.INI[AIData]..FormationSpeedForPosition=.4 //0.8FormationSpeedForRate=0.2 //0.5..MaxRollFormation=1.0 //5.0FormationRollForPosition=0.8 //0.01FormationRollForVelocity=0.05 //0.2.//////////////////////////////////PfalzD3_DATA.INI[AIData]..MaxRollFormation=0.8 //5.0FormationRollForPosition=0.8 //0.01FormationRollForVelocity=0.1 //0.2//////////////////////////////////Pup_Data.ini[AIData]..FormationSpeedForPosition=.4 //0.8FormationSpeedForRate=0.2 //0.5..MaxRollFormation=0.7 //5.0FormationRollForPosition=0.8 //0.01FormationRollForVelocity=0.05 //0.2. 2 Quote
Trotski Posted April 14, 2016 Posted April 14, 2016 See wot I mean 'bout the Mathmatiky voodoo....arrrgh ! Quote
mue Posted April 15, 2016 Posted April 15, 2016 (edited) The critical factor is the MaxRollFormation. The common value of 5.0 creates overcorrection which starts the cycle of rolling from side to side. Wrong. The relevant variable is FormationRollForVelocity. The default value is set to 0.2 in AIRCRAFTAIDATA.INI. You have to lower this value. Either globally in AIRCRAFTAIDATA.INI or in each <aircraft>_DATA.ini. I use 0.03. Depending on the aircraft, maybe you have to lower the value further. Edited April 15, 2016 by mue 1 Quote
Nicholas Bell Posted April 15, 2016 Author Posted April 15, 2016 Wrong. The relevant variable is FormationRollForVelocity. The default value is set to 0.2 in AIRCRAFTAIDATA.INI. You have to lower this value. Either globally in AIRCRAFTAIDATA.INI or in each <aircraft>_DATA.ini. I use 0.03. Depending on the aircraft, maybe you have to lower the value further. Huh. I wasn't able to get the results I wanted without reducing MaxRollFormation dramatically, although I only lowered the FormationRollForVelocity to 0.05. Rather than me just being "wrong" - I would suggest we are approaching the solution to the problem from slightly different angles. 2 Quote
mue Posted April 15, 2016 Posted April 15, 2016 Huh. I wasn't able to get the results I wanted without reducing MaxRollFormation dramatically, although I only lowered the FormationRollForVelocity to 0.05. Rather than me just being "wrong" - I would suggest we are approaching the solution to the problem from slightly different angles. Ok . It seems both parameter act together. I tried to isolate the relevant parameter. So I changed only one Formation parameter per test. And only FormationRollForVelocity seemed to make a difference. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.