If you are getting Lb pounds in jets from Europe, then it is a problem with your ini file.

Not might be, not could be. Is

 

It is either:

1. Fixed options configuration set in the FMC options
2. File Permissions preventing .ini files from copying into the FSX / PMDG flder correctly on your PC.

 

 

I have been talking about the specific display config problems that are not explained away with an ini issue since everyone insists they are part of the AF fleet. PMDG may have updated their ini since then to address the LBS and C but that was an issue previously. You can go download the AF repaint yourself and you will find the range arcs, the angle of attack indicator, and the passenger no electronic or no smoking signs. None of these are on the real freighter fleet. And this cannot be explained away like everything else by insulting my technical knowledge, my past posting history, or my use of a picture from airliners.net. It's like playing a game on xbox all the kids hurl insults left and right behind anonymous user names.

I have been talking about the specific display config problems that are not explained away with an ini issue since everyone insists they are part of the AF fleet. PMDG may have updated their ini since then to address the LBS and C but that was an issue previously. You can go download the AF repaint yourself and you will find the range arcs, the angle of attack indicator, and the passenger no electronic or no smoking signs. None of these are on the real freighter fleet. And this cannot be explained away like everything else by insulting my technical knowledge, my past posting history, or my use of a picture from airliners.net. It's like playing a game on xbox all the kids hurl insults left and right behind anonymous user names.

 

 

All the LB/KG °C/°F Range arcs, AOA/G Pax/Electronics/Smoking signs stuff can be changed by you, or anyone at home with the FMC settings by pressing the Menu button on the FMC CDU in the cockpit, and selecting "Settings". All sorts of stuff in there. You can also save these changes to be specific to one livery, or to apply to the whole fleet. (ie every livery you have installed)

 

Don't like the way it's set up? Change it.

 

PMDG didn't update the ini file to change LBS to KG or °F to °C for the Air France file. I can tell this is the case because you didn't download it over again did you. Software updates aren't magic. You don't go from "Oh it's all wrong on my PC" to "PMDG changed a file on a server somewhere in cyberspace, so now it's all fixed on my own PC even though I haven't reinstalled anything".

 

 

 

and the passenger no electronic or no smoking signs. None of these are on the real freighter fleet.

 

Freighters have a Supernumerary section as mentioned above (FCOMv2 1.47), which has that signage.  So, that point is wrong.

That isn't a response. He did not address the tcas range arcs or angle of attack which are clearly not in the AIr France fleet. He tried saying it is a problem with my ini file.

 

Instead of beating this dead horse with a stick (by that I mean your constant mentioning of a wrong AF setup), did you even try Ryan's (Tab's) suggestion to see if your .ini files are installing correctly?

 

Also, you can just change them yourself. I do it all the time to experiment with different settings. That's what the Options/Displays menu is there for

That isn't a response. He did not address the tcas range arcs or angle of attack which are clearly not in the AIr France fleet.

You're right, he didn't specifically address the aforementioned issue, however, his response was a general response as to how they get the information to be able to come up with these configurations in the first place AND what they do if they aren't able to get the information for a particular airline. He gave you a suggestion in the last paragraph of his post. Did you even try it to see if that fixed the problem?

Freighters have a Supernumerary section as mentioned above (FCOMv2 1.47), which has that signage.  So, that point is wrong.

 

And now the "experts" are telling me that freighters all have no smoking or no electronic signs. This is great. It's like I'm posting on 4chan and all the "real pilots" come out to lecture me.

 

Now taking bets on what new insult I will receive because people for some reason can't admit I'm right. It's been over a week. Celebrating 8 days this afternoon of childish insults, and hard headed arrogance.

Now taking bets on what new insult I will receive because people for some reason can't admit I'm right. It's been over a week. Celebrating 8 days this afternoon of childish insults, and hard headed arrogance.

Don't own the PMDG 777, nor do I have access to the flight deck of an Air France Boeing 777 freighter, so I have no way of verifying whether you are correct or not.

 

 

Now taking bets on what new insult I will receive because people for some reason can't admit I'm right. It's been over a week. Celebrating 8 days this afternoon of childish insults, and hard headed arrogance.

 

David, i am not sure if you mean too but you come across as incredibly adversarial, bordering on rude.  

 

Ryan did provide you with a general answer, summarized as people who work for the airlines provided the configurations; i'll agree that he didn't answer your specific question, probably because he wouldn't personally know.  Do you work for the airlines in question, do you have any evidence beyond a couple of pictures?  If so then i'll repeat what i said earlier, why don't you send the improved and accurate configurations to PMDG and improve the 777 for all the people who care about these type of things?   

PMDG may have updated their ini since then to address the LBS and C but that was an issue previously. You can go download the AF repaint yourself and you will find the range arcs, the angle of attack indicator, and the passenger no electronic or no smoking signs.

 

 

Hi Folks!

Most people here seem to talk past each other, although everybody might be right at the same time (to a certain degree).

 

I freshly re-downloaded the PMDG AF T7F F-GUOC. This resulted in two different PMDG Aircfraft INIs:

 

File dated 2013-08-29 in folder "PMDG 777X/Aircraft/Backups":

MetricWeightUnits=1

TemperaturesInF=0

ND_RangeArcs=1

ND_TCAS_RangeRing=0

PFD_angle_of_attack_dial=1

Passenger Signs Type=0

 

File dated 2013-09-02 in folder "PMDG 777X/Aircraft":

MetricWeightUnits=1

TemperaturesInF=0

ND_RangeArcs=1

ND_TCAS_RangeRing=0

PFD_angle_of_attack_dial=0

Passenger Signs Type=0

 

So "meanwhile" the entry PFD_angle_of_attack_dial has apparently changed from 1 to 0, resulting in AOA not displayed in PFD anymore. (Restoring that INI via the respective FMC function would result in loading the "old" version with AOA again enabled...)

From what I have seen on one photo (airliners.net, june 2009) is that F-GUOB has no AOA display in the PFD.

 

All other concerned values are the same within the two INIs:

Units=metric, temperatures=°C, ND-range-arcs=on, TCAS-range-rings=off. Passenger Signs Type=0 means "cabin sign selector"="No smoking". 1 stands for "No electronics" and 2 would actually mean "not installed".

From what I have seen on that photo is that F-GUOB has no cabin sign selector.

 

The differentiation between ND-range-arcs and TCAS-range-rings might have become confused during this thread, because PMDG range-arcs are on (if selcected via FMC MENU) , no matter if TFC button is pushed on or off. Only the TCAS-range-rings are switched on/off with the TFC button. The ATC XPDR switch does not change this interaction.

From what I have seen on that photo is that F-GUOB has no ND-range-arcs. I cannot identify if TFC is on and if respectively the TCAS-range-rings are visible or not.

 

(BTW: Changing the ATC-ID inside FSX's aircraft selection dialogue (details) directly affects the linkage of PMDG Aircraft INIs.

Example: LH-T7F D-ALFA (PMDG livery) and D-ALFA1 (Christian Mohr livery). They are RW duplicates but have everything "on their own": 

FSX texture, FSX aircraft.ini listing, FSX selection, PMDG Aircraft INI...

If ATC-IDs are used as duplicates intentionally (like PMDG N777F.ini for PMDG "House" and "Unpainted") everything works fine, but when duplicates become mixed up erroneously, it can get really complicated to unscramble everything "back to normal".)

 

Assuming that e.g. the June 2009 photo is "up to date", PMDG's "original(?)" INI for F-GUOC is actually wrong concerning

"range arcs, the angle of attack indicator, and the passenger no electronic or no smoking signs"

and PMDG's "actual(?)" INI for F-GUOC was only corrected concerning the "angle of attack indicator".

 

Greetings,

Claus

Now taking bets on what new insult I will receive because people for some reason can't admit I'm right. It's been over a week. Celebrating 8 days this afternoon of childish insults, and hard headed arrogance.

 

The thing is David, you are inviting this response by being so hard-headed and confrontational about this yourself. Ryan has explained at length how he gathers the information for the .ini files. If a respected airline source provides him details for an airline why should he question that? Yet you somehow seem to expect PMDG to have everything 100% accurate when they have no way of checking. If you know something is wrong it's extremely easy for you to fix it for yourself. You don't need PMDG to fix it for you.

 

PMDG have provided you with a product which includes a powerful and flexible way to control all the various operator options they implemented. Yet you seem to be complaining about this and expecting PMDG to admit it's just a gimmick for getting a few details wrong (in your opinion). If the AF livery download every had US units then it was a mistake in the ini file and not a problem with the options feature itself.

Yeah, I'm kind of lost as to what it is you're trying to accomplish here, David. You're complaining about eight days of all this going on. In those eight days, I would have just tried to solve this thing on my own, and probably would have gotten it solved in eight minutes rather than eight days.

 

 

Yeah, I'm kind of lost as to what it is you're trying to accomplish here, David.

 

One thing he has accomplished is to call attention to a really cool PMDG feature that otherwise I'd never have heard of. 

 

Hook

One thing he has accomplished is to call attention to a really cool PMDG feature that otherwise I'd never have heard of. 

 

Hook

 

He also managed to call attention to himself. Which may actually be the real purpose of the posting.

If I had asked the question and then had my attention drawn to the fact that I can easily and instantaneously fix the problem using the menu and settings features included in the product, I would have said thanks and gone into said settings and changed them. Not winge like a spoilt brat that I'm so right and PMDG sux.

And now the "experts" are telling me that freighters all have no smoking or no electronic signs. This is great. It's like I'm posting on 4chan and all the "real pilots" come out to lecture me.

 

Now taking bets on what new insult I will receive because people for some reason can't admit I'm right. It's been over a week. Celebrating 8 days this afternoon of childish insults, and hard headed arrogance.

You realize that you have had everyone try to contribute and say the exact same thing. Having the developer for the airplane give you the solution on a golden platter should be enough for you to listen to what people are saying. People are trying hard to help you, but you are telling them that they have no clue what they are saying and are wrong. Just try what they are saying. You may be surprised.

 

 

PMDG (ND-)range-arcs are on (if selcected via FMC MENU) , no matter if TFC button is pushed on or off. Only the TCAS-range-rings are switched on/off with the TFC button.

Hi folks!

I have to quote myself in order to avoid confusion about an obviously wrong statement from my side.

I wrote the above stated TFC push button behaviour while checking it at the same time in FSX. I was able to turn the TCAS-range-ring on and off via the TFC button while the ND-range-arcs remained on all the time.

Later I made a complete A/C startup form the original PMDG-C&D and now TCAS-range-ring and ND-range-arcs are turned on and off simultaneously all the time (again or as always)...

Probably "my" C&D-Startup or "Taxi"-Startup, which I used during writing, messed something up with the Aircraft-INI? I have no idea.

 

Greetings,

Claus

Disregard