![]() |
|
|||||||
| FM/DM threads Everything about FM/DM in CoD |
![]() |
|
|
Thread Tools | Display Modes |
|
|
|
#1
|
|||||||
|
|||||||
|
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
I understand that you have no experience with virtual dogfight. Your theoretical knoweledge is useful but you would die in combat if you tried to apply it.
__________________
Bobika. Last edited by Robo.; 09-18-2012 at 08:17 AM. |
|
#2
|
||||
|
||||
|
Quote:
__________________
Last edited by Crumpp; 09-18-2012 at 03:02 PM. |
|
#3
|
||||
|
||||
|
Quote:
fixed that for ya.
__________________
Intel Q9550 @3.3ghz(OC), Asus rampage extreme MOBO, Nvidia GTX470 1.2Gb Vram, 8Gb DDR3 Ram, Win 7 64bit ultimate edition |
|
#4
|
||||
|
||||
|
Quote:
Of course not but what you're saying has nothing to do with the ability of the aircraft to turn in a combat situation. You got it right with the best performance velocities - and that's all the turnfight is. The fact that the 109 at say 400km/h can turn better than a Spitfire at say 250km/h is irrelevant. Useful in combat, but not for turnfight. It's called 'turn and burn' where the opponents get the best use of turn rate advantage. In this particular case, Spitfire has got the advantage. Quote:
If you could perhaps describe how exactly would you outturn a Spitfire Mk.I in a Bf 109E, I am very interested. Everything you are saying is true but you would be dead in a turnfight because you're wrong about what is important in actual combat.
__________________
Bobika. |
|
#5
|
||||
|
||||
|
There is some debate on this issue.. But one thing that I am sure of (99%) is the guage values are.. well.. not great!
__________________
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. |
|
#6
|
|||
|
|||
|
Quote:
Last edited by MusseMus; 09-18-2012 at 07:25 AM. Reason: Typo |
|
#7
|
|||
|
|||
|
Don't forget the inherent display bug on all RAF ASI's .... that is the needle drops rapidly in response to G. You can drive the RAF ASI any way you want with minor applications of G. So any time you are pulling G the RAF ASI bug will result in a grossly low IAS that bears no resemblance to your real IAS. The German ASI's are not "afflicted" by this bug.
The current bug renders the RAF ASI totally useless as a manoeuvre/energy cue. its only useful in 1G flight. |
|
#8
|
|||
|
|||
|
Here's a quote from the Spitfire, Hurricane, Curtis and 109E trial carried out by the Germans at E-Stelle Rechlin.
"Before tuning fights with the ME109E, it must be noted that in every case, that all 3 foreign planes have significantly smaller turning circles and turning times" Just thought I'd throw that in.. |
|
#9
|
||||
|
||||
|
Quote:
Z values for IAS, TAS are given in 'world co-ordinates' units, e.g. 130.5 means 130.5 world co-ordinate units. I did some tests of distances on the CoD map versus Google Earth and to cut a long story short 'world co-ordinates' are effectively in meters, e.g. if you subtract one from another (using pythagoras unless you travelled perfectly east or west) the distance is in metres. In one set of Spitfire tests I did I registered 249.83mph (402.06kph) on the IAS gauge at 10,000 feet (thats a scripted-out value that is fed to the gauge graphic, the needle can't be read that accurately and the tooltip rounds to whole numbers). Using rough conversion 2% per 000 feet that's 299.79mph TAS or 482.47kph TAS. More accurately using Density altitude that calculates as 290.72mph TAS or 467.87kph TAS. The Z values were 132.09 IAS and 134.92 TAS. Assuming these to be metres per second (nothing else fits) that's 475.52kph Z_IAS, 485.71kph Z_TAS. More confusion because I understood the rough conversion to TAS is 2% per thousand feet which should put the Z_TAS at 475.52 * 1.2 = 570.62kph not 485.71. OR... Z_TAS should put Z_IAS at 485.71 / 1.2 = 404.76. If we trust Z_TAS the IAS begins to look right and Z_IAS wrong. If we trust Z_IAS the IAS gauge and Z_TAS are wrong. Conclusion? Who knows but Z_TAS and IAS gauge have more going for it, after all the IAS value has to come from somewhere. so at 10,000ft IAS mph....IAS kph.....Z_IAS kph......IAS kph (from Z_TAS) ...Z_TAS(kph).....TAS@D.A.(kph from IAS) 249.83......402.06........475.52.........404.76......................485.71.....................4 67.86 (remember TS@D.A. will be different because its calculated for a standard day) Now you could argue that according to the Z_IAS value the Spitfire is travelling 18% faster than the IAS gauge says. Alternatively..... Z_TAS converted to IAS says the IAS gauge is near enough correct. If that's right then the small difference between IAS gauge and IAS from Z_TAS could be caused by atmosphere factors (standard day to CoD day). We have to be sure we're testing these aircraft properly. With respect, "I tested it at 10,000 feet and it isn't as fast as it should be" is very subjective because: 1. It was being tested using the IAS gauge which now falls under suspicion (for ALL aircraft). Or does it? 2. It "isn't the same top speed as the historical" data because it isn't being tested at or converted to a 'standard day' which is how historical data is published. How many of you know that the default SL pressure for CoD on line is 995mb, not 1013.25 as on a standard day? And that doesn't take account of CoD's SL temperature which is never the standard day 15C. 3. We don't really know if/which IAS, Z_data or whatever is truly accurate but I'm more inclined to trust the Z data and particularly Z_TAS. I have never tested the 109 but I will after the patch although it would be nice to have some other guys help.
__________________
klem 56 Squadron RAF "Firebirds" http://firebirds.2ndtaf.org.uk/ ASUS Sabertooth X58 /i7 950 @ 4GHz / 6Gb DDR3 1600 CAS8 / EVGA GTX570 GPU 1.28Gb superclocked / Crucial 128Gb SSD SATA III 6Gb/s, 355Mb-215Mb Read-Write / 850W PSU Windows 7 64 bit Home Premium / Samsung 22" 226BW @ 1680 x 1050 / TrackIR4 with TrackIR5 software / Saitek X52 Pro & Rudders Last edited by klem; 09-18-2012 at 10:46 AM. |
|
#10
|
||||
|
||||
|
Quote:
__________________
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|