![]() |
|
FM/DM threads Everything about FM/DM in CoD |
![]() |
|
Thread Tools | Display Modes |
#71
|
||||
|
||||
![]() Quote:
Quote:
Just make them the same then pilot skill will be the wild card ![]()
__________________
GigaByteBoard...64bit...FX 4300 3.8, G. Skill sniper 1866 32GB, EVGA GTX 660 ti 3gb, Raptor 64mb cache, Planar 120Hz 2ms, CH controls, Tir5 |
#72
|
||||
|
||||
![]()
We did that briefly in ATAG's Server #2 a couple of weeks ago. The Engine Temperature Management was temporarily switched off so we could evaluate the effects of radiator drag without overheating the engines. (Radiators are closed by default and cannot be opened). The 109 E4 and the Spitfire MK 1a 100 octane had the exact same speed at sea level at full WEP (109) and 11 lbs boost (Spitfire). Both aircraft would travel literally wingtip to wingtip for miles above the waves going full out - neither aircraft gaining an inch on the other. On cue (using Teamspeak) both aircraft were then pulled hard up into a vertical climb, engines remaining at full throttle WEP/11 lbs boost. Both aircraft climbed to the same height wingtip to wingtip, stalling out at precisely the same instant.
We did this online so we could easily do plane vs plane comparos, but you can test this easily offline with your favourite aircraft simply by unchecking Engine Temperature Management in your Realism Options. The flight models tested to be the same offline and online. This was a very brief test on Server 2, it was soon put back to Full Switch. But for a brief time it was exhilarating to fly a Spit in equal terms with a 109. Makes for some very long -- and exciting -- dogfights between equal pilots. Once Engine Temperature Management is turned back on, the Spits are saddled with huge, no......make that HUGE.....radiator drag penalties in terms of square area, drag coefficients, and no apparent modelling of the Meredith Effect.
__________________
Last edited by ATAG_Snapper; 09-06-2012 at 04:40 PM. |
#73
|
||||
|
||||
![]()
Don't get me wrong..
I think combat reports are great for many things.. Just not great for validating a flight model! Combat reports say more about the men and their mind set and their tactics.. But very little about the planes performance! I will say this, you can gleam flying qualities from combat reports.. Stuff like 'I felt a slight buzz in the stick just before the stall while turning with the 109'.. But that description tells you nothing about the stall speed at which this occurred.. As I already pointed out.. Most combat reports don't include enough info to recreate the scenario in the game to see if you get the same results in-game.. Unlike real world data (test reports) that are performed using strict and repeatable methods.. For example.. I can recreate an ROC test in-game using the same real world methods to see if the real world results match the in-game results.. But how do I recreate a scenario to test from a combat report that says.. 'In my Spitfire, I dove down on a 109, who spotted me at the last second and tried to evade me before I shot him down' You cant! There is not enough information there to recreate the scenario to see if the in-game results match the real world results.. That and the results depend more on the relative pilot experience.. That is to say assume you did try to re-create this scenario in the game.. Put a good pilot in the 109 and a Cherry in the Spitfire and there is a chance the 109 will NOT get shot down.. Does this test prove the 109 flight model is uber and the Spitfire flight model is broken? NOT AT ALL! All this proves is the relative experience of the sim pilots involved in the scenario affect the outcome more than the performance of the plane! Same can be said wrt the orginal combat reports (anecdotical evidence), you don't know how much of 'it' was due to the relative experience of the pilots! As in was the Spitfire pilot able to turn with the 109 because he was a better pilot? All in all do we really want our flight models tweaked based on the results of some sim pilot's atempt re-create of a poorly documented WWII event? I THINK NOT! But I digress! Combat reports are also useful to gain in site as to what was actually going in the trenches vs. what the generals thought was going on.. A good case in point is the whole 100 oct usage Quote:
Combat reports are great for determining how the pilots used these aircraft and the tactics they used.. Just not good for validating a flight model Like in the stick buzz example above.. We know it stalled (the event) We know the pilot felt something in the stick before the stall (the useful flying quality info) We DON'T know what the stall speed was (what is needed to validate the flight model) We DON'T know what the throttle setting was (what is needed to validate the flight model) We DON'T know what the flap setting was (what is needed to validate the flight model) We DON'T know what the e state was (what is needed to validate the flight model) We DON'T know what the altitude was (what is needed to validate the flight model) This list goes on but you should be starting to see my point TOO MANY UNKNOWNS! Quote:
That is the problem with human nature Where as with math 1 + 1 = 2 And nobody but raaaid could disagree with that! ![]() Quote:
But not a good example of how to validate a flight model All that statement really proves is the plane with a better 'e' state will control the fight, until that pilot does something stupid to give up his 'e' advantage! ![]()
__________________
Theres a reason for instrumenting a plane for test..
That being a pilots's 'perception' of what is going on can be very different from what is 'actually' going on. Last edited by ACE-OF-ACES; 09-06-2012 at 10:06 PM. |
#74
|
||||
|
||||
![]()
And here is a perfect example of what I was refering to, that being how two people can read the same 'accounts' and get different results
Where as 1 + 1 = 2 in real world test data and you would be hard pressed to find anyone to disagree with that! ![]()
__________________
Theres a reason for instrumenting a plane for test..
That being a pilots's 'perception' of what is going on can be very different from what is 'actually' going on. |
#75
|
|||
|
|||
![]()
1+1=10
![]() |
#76
|
||||
|
||||
![]()
__________________
Theres a reason for instrumenting a plane for test..
That being a pilots's 'perception' of what is going on can be very different from what is 'actually' going on. |
#77
|
|||
|
|||
![]()
ok maybe i got it completly wrong lol!
![]() i thought the slats were the to give stability at low speeds? but maybe wrong about that also ![]() And i think AoA is correct, math is math. it it adds up it cant be denied. best get your calculator out mate and get to work cos that sort of math well beyond me lol ![]() 1+1=11 ![]() |
#78
|
|||
|
|||
![]() Quote:
I think these planes are quite well documented, as opposed to WW1 planes for instance. I also wouldn't say that those two planes "feel" totally unrealistic regarding rollrate, turnrate or whatever in CloD, except for the too low speed of these planes, unlikely engine reliability (impossibility to run the Merlin using historical limits) etc. I don't think we would have many FM discussions, if the speed would be close to the avaliable data. |
#79
|
||||
|
||||
![]() Quote:
And here is a perfect example of what I was refering to, that being how two people can read 'pilot accounts' and get different results
__________________
Theres a reason for instrumenting a plane for test..
That being a pilots's 'perception' of what is going on can be very different from what is 'actually' going on. |
#80
|
||||
|
||||
![]() ![]() ![]() ![]() From the 1941 study, it sounds to me that hi-speed rolling was not a strong point
__________________
GigaByteBoard...64bit...FX 4300 3.8, G. Skill sniper 1866 32GB, EVGA GTX 660 ti 3gb, Raptor 64mb cache, Planar 120Hz 2ms, CH controls, Tir5 |
![]() |
Thread Tools | |
Display Modes | |
|
|