I bought the B727-100 and 200F yesterday and I am highly satisfied with the product.
I am just wondering:
If I add a 2D panel to my model, may I share it with other via this forum by a link? A panel zip file without any files of Capt Sim can not be used by any other person anyway.
Nobody have to download it anyway. If it is not allowed just too bad.

I prefer to use a 2D panel, and without the yoke.

Johan,
Please feel free to share your work.

Thanks.
That is to say if I did not speak too fast.
Maybe I will not succeed satisfactory and then everybody will laugh at me anyway.
I have not started yet and I lost much needed sleep because I kept on flying this bird till late this morning.

I have started with the 2 Panel, but now I have a question of opinion for 2D panel users.

An aircraft's panel is designed of such a layout that the pilot is sitting on the left and he will only see the left third of his instruments right in front of him, with his eyes directed in front of him (in the case of this CS B727, the Attitude Director Indicator (ADI) right in front of him - This gauge is basically the center of his view or his third of the panel). He has to turn his eyes or head to the right to see the Engine Instrument Panel.
In a 2D panel the author do the lay-out so that the pilot will see the left two thirds of the whole cockpit instrument panel (to include everything from the left to the landing gear handle). Unfortunately the new center gauge will be the radar altimeter. I don't have a problem with that as I would like to see as much of the instruments simultaneously. Will that be a problem to other 2D users? I can make it with the same views, but the the Engine Instrument Panel will have to be a separate panel.

Maybe I will have to think in the line of two designes, where the user have a choice whether he/she will use which one.

I would like your comments please.

As seen in other 2D models, they have the a place in the main screen (on top of a gauge or in the right boundaries) where you click and the new panel appears.  Clicking again the new panel in an specific place will close it. For the engine panel to show up, that clicking section could be low right section of panel.

Example. For the engineer panel, will show the upper panel. Click at the bottom and shows lower panel, click at top and again upper panel.

hot click area will require gauges to perform that action. While it is easy to program a simple xml gauge to do the job, it is even easier to just use the simicons included in MSFS to swap views. The IFR and VFR views are great for building a 3/4 panel and a 1/3 panel. The engine stack can be used for the FEs position and there are multiple options in the FSX simicons for different views. Using a program like FSPS makes it all WYSIWYG.

The problem I ran into with building a 727 panel is that CS did not build any 2D switches (with the exception of a very few). Thus 90% of what you need to interact with the airplane will need to come from other sources.

KenG wrote on Jan 30^th, 2010 at 6:08am:

The problem I ran into with building a 727 panel is that CS did not build any 2D switches (with the exception of a very few). Thus 90% of what you need to interact with the airplane will need to come from other sources.

Hey Ken - yep, and it gets worse because most of the gauges use local variables that link to the C++ .gau file. I found out the hard way when I tried to add altitude callouts to the 727. The radioaltimeter did not use the "radio height" and "decision height" FSX variables, so I had to first rebuild the gauge using them, then add the callout gauges.

To partially address the lack of a 2D panel I made another custom cameradefinition for the VC so that every time I hit the button assigned to VC I get the same view where almost all of the key gauges are visible & clickable.

I'll paste it in this thread when I get back to my desktop.

OK, as I alluded to above - if you want to get a 2D panel-like view in your VC, add this cameradefinition after the last one that is already in the aircraft.cfg:

The entry above is for the 727-100 and 727-100F

[CameraDefinition.008]
Title = Virtual Cockpit Mod
Guid = {C95EAB58-9E4A-4E2A-A34C-D8D9D948F079}
Description = Modified virtual cockpit view.
Origin = Virtual Cockpit
MomentumEffect = No
SnapPbhAdjust = Swivel
SnapPbhReturn = False
PanPbhAdjust = Swivel
PanPbhReturn = False
Track = None
ShowAxis = YES
AllowZoom = TRUE
InitialZoom = 0.7
SmoothZoomTime = 2.0
ZoomPanScalar = 1.0
ShowWeather = Yes
XyzAdjust = TRUE
ShowLensFlare=FALSE
Category = Cockpit
PitchPanRate=30
HeadingPanRate=75
PanAcceleratorTime=0
HotKeySelect=1
InitialPbh=13,0,0

For the 727-200:


[CameraDefinition.009]
Title = Virtual Cockpit Mod
Guid = {C95EAB58-9E4A-4E2A-A34C-D8D9D948F079}
Description = Modified virtual cockpit view.
Origin = Virtual Cockpit
MomentumEffect = No
SnapPbhAdjust = Swivel
SnapPbhReturn = False
PanPbhAdjust = Swivel
PanPbhReturn = False
Track = None
ShowAxis = YES
AllowZoom = TRUE
InitialZoom = 0.7
SmoothZoomTime = 2.0
ZoomPanScalar = 1.0
ShowWeather = Yes
XyzAdjust = TRUE
ShowLensFlare=FALSE
Category = Cockpit
PitchPanRate=30
HeadingPanRate=75
PanAcceleratorTime=0
HotKeySelect=1
InitialPbh=12,0,0

For the 727-200F:

[CameraDefinition.008]
Title = Virtual Cockpit Mod
Guid = {C95EAB58-9E4A-4E2A-A34C-D8D9D948F079}
Description = Modified virtual cockpit view.
Origin = Virtual Cockpit
MomentumEffect = No
SnapPbhAdjust = Swivel
SnapPbhReturn = False
PanPbhAdjust = Swivel
PanPbhReturn = False
Track = None
ShowAxis = YES
AllowZoom = TRUE
InitialZoom = 0.7
SmoothZoomTime = 2.0
ZoomPanScalar = 1.0
ShowWeather = Yes
XyzAdjust = TRUE
ShowLensFlare=FALSE
Category = Cockpit
PitchPanRate=30
HeadingPanRate=75
PanAcceleratorTime=0
HotKeySelect=1
InitialPbh=12,0,0