I realize that the P-51 CoG was moved but,

[MaxGunz]

Originally Posted by horseback

While the motive might be considered admirable, where no data is available, it becomes a matter of the programmers' best guess and uneven treatment. Hence Japanese instruments that seemed to me to react near-instantly and much more accurately than their counterparts in aircraft from the country that supplied most of the licensed original designs.

In a flight sim where there is a one-eyed tunnel vision view instead of a full range field of view and an absolute dependence upon the instrument displays instead of a seat of the pants 'feel', accurate instrument displays in a full-real cockpit seem to me to be both fairer and more realistic than the current method.

I would assume that the 'correct' data would be available via Devicelink, which would confer an unfair advantage on those who were able to take the trouble and expense of setting up an accurate and/or (at least) legible cockpit display on a second screen. Isn't that the same class of exploit that the thrice cursed trim delay was supposed to defeat and make the game fairer?

cheers

horseback

Devicelink was set up to allow people to make and use their own instrument panels. It should reflect what you see in cockpit.

Do you have any difficulty making charges against Maddox Games and DT for not checking when you don't check what they have done? Just wondering.

[horseback]

Originally Posted by MaxGunz

Devicelink was set up to allow people to make and use their own instrument panels. It should reflect what you see in cockpit.

Do you have any difficulty making charges against Maddox Games and DT for not checking when you don't check what they have done? Just wondering.

My understanding was that in order to use Devicelink, one needed a second computer, like an old laptop to process the data and provide the second display area. Since I couldn’t use my company-supplied laptop for this purpose, I pretty much put it out of my mind as an option for myself, but occasionally looked at what other people were saying about it out of curiosity. The old Ubi forum had a long running thread dedicated to it, and occasionally Devicelink devotees would start new threads showing and sometimes offering use of their custom-built instrument displays. Most of these displays were fairly complete, and I figured that they would be used to display the same ‘accurate’ data shown in the Wonder Woman view, only in more convenient and legible format(s). In addition, during some of the trim debates on these boards, some people cited the outputs of Devicelink about tracking trim inputs, which would indicate to me that all of the game’s data about the Player’s aircraft would be available (in some form) via Devicelink.

Since the various Devicelink posts that I have read never specifically addressed the issue of delays or accuracy and since the ‘correct’ information is clearly also generated (and scrupulously tracked by the game), it made sense—and continues to make sense—to me that the Devicelink data would be the full accurate Magilla, including stuff like a climb and dive indicator, a turn and bank display, an altimeter, critical engine instruments and fuel states—even for aircraft whose cockpit displays don’t include these things or in the case of fuel tanks, don’t work in the cockpit display.

I am surprised and disappointed to hear that it might not, but since you clearly didn’t check your own assumptions and claims about the Mustang video I linked, you might want to back off on the righteous indignation. You say that Devicelink “should reflect what you see in the cockpit”; have you checked to confirm that this claim is correct or are you playing the “I (assume I) know and you don’t” card—again?

cheers

horseback