Hello!

 

This post is related to the original panel limit question asked on FS2Crew forum (can be found here: http://forum.avsim.n...ew-with-voxatc/)

 

A short summary:

 

MD-11 uses almost all of the available panels in FSX. I currently have the following programs that would like to add their own panels to the planes config:

• VoxATC (2 panels)
  
• FS2Crew (2 panels)
  
• FS FlightKeeper (1 panel)
  
• AS2012 (1 panel)
  

On PMDG's site, there is a post that specifies that only 2 panels can be added without adverse effects. This means that I'm 4 panels short at the moment.

 

I spend ~90% of my time flying in the virtual cockpit. Are there any panels that I could disable to gain more available panel spots?

 

If you use one or more of the products I listed, how have you managed to handle the panel limit? What (if any) panels did you disable?

 

Thank you for your help!

 

- Jarkko

Anyone? Does this mean that I'm the only one addicted to add-ons?

The choice is really up to you and what you use. Why don't you disable the 2D popups related to instruments that you can already see and click on with the most ease in the VC anyway, such as the MFDs, the Mode Control panel, or anything you don't use.

The choice is really up to you and what you use.

 

Thank you for the reply! You are absolutely correct and I should have given more info, so here we go:

 

0) The PMDG FAQ I was referring to, was this one http://support.preci...BSearchID=93256

 

1) I have never disabled any panels in FSX so I don't know how to do it (and what I it might break by doing so).

 

2) What files should I backup before attempting to edit anything?

 

3) Are there other MD-11 users who use more that one add-on that adds it's own panels to the aircraft? If so, have you noticed any problems?

 

The reason I'm asking for help (and not just trying out things and see what happens) is that I have only a couple of hours a week to "fly". I would like to spend most of this time flying and not experimenting with something that is doomed to fail from the get-go

The file you want to work with is the panel.cfg file. You will see in there a bunch of entries [WindowY]. You can simply comment the old panel entries out with "//" and replace with your new panel entry, one for one. Just back things up, don't be intimidated, and I think you'll find that once you take a look at the file, you'll easily understand how it works.