[klem]

I have been asked for the mission and script files I used for my tests. I'm attaching them plus a version of the output .csv file saved into Excel where I summarised some records for the chart and added a few calculations plus some conversion factors and odd formula memos at the top. If you want to save your output as excel then just copy/paste any .csv file data into it. The mission punches up some data on screen and even more data in the output file. Coders can play with he .cs file and add or change whatever they like.

First, how to use the files. Drop the .mis and .cs files into your /1C Soft club/il-2 sturmovik cliffs of dover/Missions/ folder where it is esy to find when you later run Multiplayer.... Server... and create the server ("OK")

Open the Performance.cs file with notepad and search for //FILEPATH
1. Set the filename for output file by editing the part in quotation marks
strfile = "Performance";
e.g. you can see that I have used the name of this mission (Performance.mis) and script file (Performance.cs) without the .mis or .cs extension. The name of the aircraft you test will be added automatically to the filename thus creating separate files for each aircraft tested,
e.g. Performance-SpitfireMkIIa.csv

2. Edit the output file path to your choice by editing in the following the first part in quotation marks (not the "-" or ".CSV" part)
fstring = "E:/CoD_data/BlackBox_Data/" + strfile + "-" + cur_ac.ToString() + ".CSV";

Be sure to create the folders you need in Explorer or the file output will fail!
Also be sure to close the .csv file before you run further tests or the mission cannot write ti the file.

Typical result for the above is a .csv file as follows:
"E:/CoD_data/BlackBox_Data/Performance-SpitfireIIa.CSV"

If you create your own mission you can still use the script. Just copy it and give it exactly the same name as your mission file, e.g.
MyMission.mis needs file MyMission.cs
Don't forget to edit the filename as 1. above to, say "MyMission" to get you MyMission-SpitfireMkIIa.csv

More about the script and output:-

Deep breath and one piece at a time....

The .cs file is a bit untidy with various rem'd out lines I didn't use in the end. Also it comes with a bit of advice...

The whole thing comes from data inside the game, the various C# 'References' parameters. You don't really need to go there but note the following.......

I could not make head or tail of the parameters Z_VelocityIAS or Z_VelocityTAS which I output as WIAS and WTAS. I took these to be IAS and TAS values from within the game parameters but they don't make sense. If anyone can shed any light, fine, but I didn't use these and I calculated the TAS, see below. I left them in the file in case anyone knows them.


G_z is from Z_Overload and is in fact what we would call G value plus 1, so instead I took G values from: parameter part.ParameterTypes.Z_Overload, n
where n is for fore and aft or left and right or up and down. In the output file these are titled Acc_for_aft, Acc_lft_rgt, Acc_up_down (the G value used to measure G-cutout). For those that want to know....
Acc_for_aft = cur_Plane.getParameter(part.ParameterTypes.Z_Overl oad, 0);
Acc_lft_rgt = cur_Plane.getParameter(part.ParameterTypes.Z_Overl oad, 1);
Acc_up_down = cur_Plane.getParameter(part.ParameterTypes.Z_Overl oad, 2);
All most of you need to know is that Acc_up_down is the vertical G value I used to measure G-cutout in another similar test setup.

Ht_m and Ht_ft are calculated from the parameter pos.z and taken as the True altitude. This is the target value when you want to set the Altimeter accurately.

TrueROCms and TrueROCfpm was my attempt to cross check the ROC gauge reading by calculating movement from positional shift but that didn't work out. I was too lazy to remove it. Ignore these.

I think everything else is self-explanatory.

So Finally, how did I create the chart? Well my flying wasn't too sharp as I couldn't easily trim the Spitfire (IMHO its an unrealistic b*tch to be frank) so I had to filter out that mass of data to where the height was the required height +/- 50 feet and the tightest range of Rate of Climb, on one set as high as about +/- 30 fpm (I have left the filter set up for the sea level figures at 0 - 50 feet). Then I looked for a decent set of consecutive records that indicated reasonably consistent flying and took one of those records as data for the chart. These were in any case good within a couple of mph. You'll see I have copied those to the bottom of the spreadsheet. I also added calculations for True Airspeed based on formulae in my earlier post and highlighted in green at the top of the Excel sheet (along with some other junk). For this I had to assume the cockpit indicator IAS value was correct (I scripted it out as IAS). This is because I couldn't find a TAS parameter inside the game.