• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.

    Post 16 Update

    Post 17 Warning

2-D cockpit problem

Landman

Charter Member
I have a problem in my 2-D cockpit on an AT-6. The 2-D panel is not just showing up when I I look forward like it should but also when I press the joystick hat switch to look forward left and forward right. None of the other view directions are affected. The aircraft is the Alphasim AT-6 Texan/Harvard. I did do some modifications to the panel.cfg file like adding a pop-up VOR-2 gauge, added an RMI, added the FSX default Bendix-King radio stack so I could have a VOR-2 and standby frequencies on everything. These are standard additions that I do to all aircraft that I have that lack a VOR 2 and and RMI. I don't have this problem in any other planes, just this one. I tried messing with different part of the panel.cfg file and refreshing the aircraft each time but the problem persists. Can anyone offer a solution or suggestions?
 
So if you right click on your screen when the aircraft is loaded, you don't get the option of the 2d panel under cockpit?
 
Two things that might help. . . . A screen of what you see and your panel.cfg file as it is right now. That would go a long way to visualizing what your problem might be.
 
Back
Top