Flight Model (FM) Testing Spitfire Mk.Ia 100 oct v1.10.20332 Beta
 

Flight Model (FM) Testing Spitfire Mk.Ia 100 oct v1.10.20332 Beta

CONFIGURATION:
The following Top Speed per Altitude (TSPA) test was performed starting with a full fuel load and ammo load (no bombs) and the radiators/cowlings are set to full open (worst case).

PROCEDURE:
The top speed is tested at each of the following altitudes:

The test begins with an air start near sea level. At each altitude the plane flies for a distance of 15,000 meters (9.32 miles) before climbing to the next test altitude. Note at SL and max altitude there may be some 'pilot error' associated with the data (spikes), therefore you may have to ignore the 'spikes' in the data at these two extremes and visually extend the graphs using the data above and/or below the spike. I am working on C# code to do this automatically, but it is not finished.

During the flight all pertinent data is logged using a C# script. The TAS and altitude (Z_VelocityTAS & Z_AltitudeMSL) data is than graphed (see attached). The graph only plots the max TAS value per altitude. If you would like to viewed/inspected all the TAS values you can do so at my web site http://www.flightsimtesting.com/.

NOTE at my site you can compare one in-game plan to in-game plane, or an in-game plane to one of the many real world data sets that are uploaded at my web site. This was done to make it easier to see how well the in-game plane test data matches the real world test data. You can also change the units SI to imperial, and save any graph displayed by simply right-mouse-clicking on the graph and saving it as an image to your PC.

I am also in the process of allowing you to upload your own in-game and/or real world test data at my web site, after which you will be able to graph and compare data via my web site.

SPECIAL THANKS TO:
FST for double checking my C# script file
FG28_Kodiak for all his help with C# scripts
Ataros for all his help with C# scripts

can i ask how on earth you get over 340mph at 17000 in spit 100 octane? that is on par with real life specs

I am sure I can only get 320mph, thats with no fuel and radiator at 35% too. It currently only goes as fast as the hurricane 100 octane which can do 320mph (accurate)

Was the test done at 3000 RPM and +6.25 boost?

Yes.. I made a mistake during flying and forgot to enable the boost.. So in essance this test is limited to +6 boost.. So Ill have to re-do this test.

One thing to note, the speed matches that of the 87oct Spitfire Mk.1a, expect at higher altitudes. Two 'see' what I am talking about, goto my website and plot the Spitfire Mk.Ia vs. the Spitfire Mk.Ia 100 oct.

Keep in mind that I am using the internal (Z_) C# script values of TAS and Altitude, which dont have any of the 'issues' associated with the indicated (I_) values used to drive the cockpit guages.

Bingo...even RWorld Brit's "indicated" under reported

BTW AoA, how do you get in and out undetected, are you using the B6 monitor stealth mode

Hi AoA.

I'm afraid the IL-2 Cliffs of Dover link on your website won't work for me at the moment (11:45am UK 15/10/2021)

I'm surprised you managed to do the 3000rpm/+6.25lbs test, the engine runs roughly for me at full rpm and full boost at 10,000 ft and 20,000 ft in my tests so I gave up until they fix the problem. It is almost certainly the case at other altitudes too although 1,000 and 2,000ft were ok, returning 270 and 273mph Z_TAS after about 5 mins, BCO override giving 302 and 309mph. btw It was only carrying 65% fuel/5845lbs, a little under N3171 trials at 6050lbs (my error left over from the Hurricane tests).

We were experiencing similar engine problems on ATAG last night at various altitudes and power settings. Are you using your own in-game server? Could you post your mission and .cs file?

EDIT: btw Z_AltitudeMSL is true altitude above SL but is not representative of the Density altitude, e.g. in my 2000 feet test with indicated altitude 1658ft (Alt Baro set to 1013) I get Z_Altitude_MSL 1227ft, Pressure altitude 1664 due to CoD SL pressure (which should be close to Indicated but we cant set Baro to 1013.25) and Density altitude, the effective atmospheric altitude adjusted for temperature (or Standard Day), 2000 ft. At D.A. 10,000ft (well, 10,013) Z_Altitude_MSL is 9930ft and at D.A 19926 (close to 20,000) Z_Altitude_MSL is 21,367. There's a crossover around 12k.

Strange.. Granted it does take awhile to load after you click on the 'Il-2 CoD' tab.. So give it a few min before clicking on it again.

Strange.. Might have something to do with the way I did the test, as I pointed out to Banks, I messed up and need to re-do this test

No just a single mission

Here is a link

http://forum.1cpublishing.eu/showthread.php?t=34964

I think you and others will find it very handy when doing top speed per altitude tests.. In that I put ~10 miles worth of 'FLASHING RING' at each of the test altitudes, which in turn makes it a lot easier to maintain the altitude, in that you get a 'visual' feedback and basically all you have to do is fly through the FLASHING RINGS

Yup! That is why I use it over the others! ;)

What kind of defviation do you get flying through the rings? I try to stay within 10-20 feet of altitude.

But that means you can't compare it with historical data because Z_Altitude_MSL is the 'tape measure' altitude not the Standard Day or "meteorological" altitude.

EDIT: AoA, I wonder if the rough running is an on-line problem only? Would be interested to hear how you get on if you retry the SpitMkIa/100oct offlinre at altitude.

None.. I have flown many tests and have yet to S myself while flying! ;)

J/K!

The altitude of the rings are rock solid, as expected, and I can keep the gunsite on the center ring pretty well.. I have not looked at the data as to what my vairation of the alt was.. Not that it is not importnat, only that I know there will be some variation. What I am working on is a 'filter' that will not accept a TAS value as part of the MAX TAS per altitude if the ROC value is above a certain level.. That is to say if your are diving.. and pickup speed due to a shallow dive, the ROC value will be NOT be ZERO.. Thus if any TAS values that occur when the ROC is above a certain level will not be considered valid and thus not part of the MAS TAS graph.. Doing this will automatically remove any bad TAS values due to bad flying (i.e. not level flight).