![]() |
|
#1
|
|||
|
|||
![]() Quote:
I think that we should probably correct all of our performance references to ISO standard atmosphere conditions to produce an overall aircraft performance database, and then convert performance data from that database to whatever the conditions on our chosen test map are. BTW, formation flying is the most obvious way to overcome the 1 d.p. limitations of the cockpit instruments, at least to some degree... |
#2
|
|||
|
|||
![]()
definitely a good effort, but let me just say one thing..
we need to know exactly what parametres are needed in order to provide usable data and not waste any time. It would be worth to try and talk to Luthier about this, so maybe we could be directed in the right way.. Viper has a factual approach to things that is quite the right way to go, but before you jump in this head first try and seek for some support from the guys at Maddox Games. |
#3
|
|||
|
|||
![]()
I don't understand anything you guys are saying here but I make darn good coffee!
|
#4
|
||||
|
||||
![]()
Viper, if you are leading this project I'm in.
Tuckie and me are trying to do the same in a spanish forum, so we can work together. Congrats for the idea. Cheyennepilot ( aka Lud)
__________________
Last edited by SG1_Lud; 04-28-2011 at 07:01 PM. |
#5
|
|||
|
|||
![]()
There's no use going by FM testing as detailed as this one yet. The FM is just as immature as the rest of the game is, so in a year a test like this one should be better suited.
|
#6
|
|||
|
|||
![]()
Does the engine have the capability to output debug data in digital?
Detailed info like rate of turn, G's, RoC, hp, IAS, TAS, boost, rpm etc. all in digital?? This is detailed data invaluable to defining the errors. I find the hp and boost in digital very useful in defining RAM effects at alts etc. Analogue gauges are just to vague to be really definitive, we don't even know if they are calibrated correctly. |
#7
|
|||
|
|||
![]()
That's useful data on early Spits, thanks.
|
#8
|
|||
|
|||
![]() Quote:
![]() Our learning curve is slower than developers speed of work ![]() Last edited by TUCKIE_JG52; 04-29-2011 at 09:16 AM. |
#9
|
|||
|
|||
![]()
My learning curve tells me that the mixture issue need to be taken care of, and that the FM needs to provide us with more feedback and certain elements of aircrafts behaviour before a FM test is justified. Otherwise mapping an aircrafts performance envelope will not be correct once the FMs have been changed. They know about those issues and I'm sure they are working on it. I'll say it like this: There's no use taking a Fiat Uno to Nürburgring to test lap times, if the race is classed as a FIA GT. But by all means, if you people need something to do just for the sake of doing it......
Last edited by kimosabi; 04-29-2011 at 04:09 PM. |
#10
|
|||
|
|||
![]() Quote:
![]() Yesterday I did pressure and temperature measurements. And got some conclusions that must be cross-checked. Pressure measuring method: 1. Place a Ju-88 in a beach (Sea Level). 2. Set altimeter to 0. 3. Read pressure in milibars directly from the Kollsman window, in the upper side of the german altimeter. Temperature measuring method: 1. Place a Ju-88 where you want to test the plane. 2. Read outisde temperature indicator ![]() Facts found: A) I get different values of pressure and temperature in the same place every time I reload the mission. Sometimes they'll repeat, but they tend to change more when a different plane is loaded in the same place. ---> Temperature and pressure are not always the same, there's some grade of randomisation. (This must be confirmed). B) Ambient temperature is different from water and oil temperature before starting engine. Clues to test: -There's the possibility to switch from the cockpit of one plane to another, at least altimeters can be cross cheched in that way; same mission load, planes placed together on a beach, check if all altimeters have the same pressure reading in Kollsman when altimeter set to 0. --> If same readings oK, reload the mission to test randomisation of parameters. |
![]() |
Thread Tools | |
Display Modes | |
|
|