#121
|
|||
|
|||
At what speed and altitude? Compare the whole Ps graphs.
Consider the drag as size and coefficient, P-51 is bigger. Where is the supercharger working best compared to the alt? The speed of the plane has much to do with the optimal blade angle but mostly... When you command more prop rpm than the plane has power to support, the prop will flatten a bit and you'll lose some thrust. Most IL2 planes have some form of pilot-controlled CSP and some are even more automated though there are pre and early war models that don't have CSP all the way down to fixed props. |
#122
|
|||
|
|||
Quote:
The Mustang is a bit different. If you look at the 10k charts, there is a point at which the Mustang at 2700 rpm will accelerate more quickly than at 3000rpm, and it reaches top speed much sooner after the three or so earlier 10 kph intervals. In the thicker air at 100 meters, this doesn't seem to happen, or at least it isn't as obvious. Currently building my 5k database, which will probably show a transitional difference somewhat less than the 10k tests for the Mustang at 2700 vs 3000rpm; it will probably be more pronounced at 15k and 25k. cheers horseback |
#123
|
|||
|
|||
Would you need to do as much trim change in a constant TAS climb as you do in a constant height drag race? You'd probably use trim just to adjust IAS as needed every few 100 to 1000 ft.
Climb rate = Ps analog at 1 speed and many alts. P-51 can climb at speeds the SpitIX can only be losing alt to maintain. Throw that in with the percentage statistics, performance has scale as well as percentages. |
#124
|
||||
|
||||
First of all, it is always appreciated and respected when somebody "do the walk".
Now the bad part. 1. This kind of tests is best done with the utility written for such purpose. You can find it here. http://lesnihu.wz.cz/autopilot/autopilot.html It is easy to set it up and it will execute script which will control the plane instead of you. It is much easier to test planes that way and what is even more important this is way more precise and repeatable test method. 2. Flying the plane is just half of the job, second part is logging the flight parameters. You can do it your way but there is a better and easier way. Use UDPGraph, you can get various parameters on the screen and in the file. Download it here: http://avcpage.achilikin.com/il2dl/graph_en.htm Once you get these two utilities working you will be able to watch TV while your PC is doing the work for you and as a bonus you will get much better results.
__________________
|
#125
|
|||
|
|||
There's still merit in doing it "by hand" though, Horseback made a lot of useful observations about the difficulty of trimming some planes as they accelerate. I am curious about how much difference trim makes though, maybe someone familiar with that tool could set up a similar test for a couple of the planes that Horseback thought were hard to trim to see how much better the results are.
|
#126
|
|||
|
|||
Quote:
This highlights some of the reasons that the ai so consistently outperform human players in certain aircraft and why some aircraft that should have many more users based on their historical records are less successful with occasional users. cheers horseback |
#127
|
||||
|
||||
Quote:
Quote:
__________________
|
#128
|
|||
|
|||
Quote:
In my opinion, many of the 'hard to trim' class seem to be hypersensitive to minor stick inputs as speed increases; I use the same low stick sensitivities for all aircraft testing, as well as 50% filtering, and attempting to maintain level flight in the 'hard to trim' group with the stick and pedals is just as difficult as trying to add or subtract elevator and rudder trim with button or axis inputs, and sometimes worse. Quote:
Regardless, the "Book" numbers are a basis of comparison for the average pilots; if plane a can accelerate from 270 to 450 kph in under 40 seconds and plane b takes almost a minute with the same pilot, their "book" numbers should be at least proportional. When other factors intrude or are artificially injected, the proportional differences can get a little lopsided. cheers horseback |
#129
|
|||
|
|||
And when you don't understand what's going on you can believe any conclusion you might come up with.
Now it's time for me to watch the new UFO's from Niburu video. |
#130
|
|||
|
|||
Maybe I'm wrong, but it seems to me that you -- horseback and woke up dead on the one side, and FC99 and MaxGunz on the other -- grind in two mills. One issue is the performance of aircrafts optimally exploited by the AI, and another is the ability/inability of the human pilot to achieve that optimum using standard game controllers (i.e. a short stick), watching a monitor less than 90 cm in diameter, and relying on flight data as displayed on the cockpit gauges. These limitations on the human player's side vary from user to user, but still there they are, and should be addressed properly when we discuss 'realism' (whatever it means for us). 'Correct' flight performance is one issue, it's actual 'feasibility' is another. Simply because we don't use the same peripherals as the AI does or r/l pilots did.
|
|
|