Hello!

I'd just like to know if anybody is successfully using this pitch and turn knob from the VC? I tend to fly exclusively from the VC and in 727 the only thing I can't do is change V/S from the VC.. I need 2d panel because instead of changing V/S I almost always initiate a heavy turn.. just can't grab and pull this knob forward from the captains seat. Any advice?

The turn knob is a bit tough to operate in VC, it was also a pain in the real plane. Too sensitive!

You could use the turn knob better than the pitch in the real 727-100. The 727-200 was much better in pitch since it had a pitch wheel.

In the CS727-100 I use the pitch knob portion with good success, however I find the turn knob part too much work so I use HEADING SELECT and steer the plane with the knob on the HSI - this I find works just fine.

I only fly in VC because it just looks better. I use SHIFT-F4 to place the autopilot controller on the screen and put it somewhere at the top of the picture, out of the way of the windshield. This way I have all the autopilot controls easy to use without moving the view. I sometimes use my Trac-IR when I fly, but I prefer the VC mode.

Lou

Hi.

I only use the pitch knob on the 2D A/P panel. I rarely use the 3D A/P panel in the VC because I find it too awkward to use. I do much same as Lou does. The 2D A/P panel is always open in my VC so I can access it when I need to. I have edited the panel.cfg to reduce the size of the 2D panels so I don't have them taking up too much room on my screen and was needing to be re-sized every time I fly the 727. I have the 2D A/P in the top right corner which tends to keep it out of the way of my view when flying.

http://i669.photobucket.com/albums/vv58/Markoz958/CS727Cockpit.jpg

Mark

Thank you both!
I do use the 2d panel for AP but I just wanted to know if others have the same problems with it in VC. But if the real pilots had the similar problem in the real airplane... well, who am I to whine about it.  :)

Since I installed the NAV/GPS button modification in my 727 I have found I can't use the AP knob (the 2D) to control climb and descent.  As soon as I engage the autopilot paddles during a climb the plane immediately goes into a 2 to 3K fps dive.  I keep clicking the 6 o'clock position on the knob and at first the angle becomes less steep but additional inputs have no effect.  The opposite happens during a descent, I can't control the rate and I have to disengage the AP and trim for the climbs and descents.  
Any ideas about how I can correct this problem?

Hi Trailboss.

There are two things I can think of for starters.

The first is the size_mm=, it needs to be able to fit the everything you need to see. If one gauge covers (sits on top of) another gauge, one can become unusable.

The second could be the gauge numbers: gauge00. The first gauge should be 00, then 01, 02 etc..

Here is how I did mine:

[Window03]
Background_color=0,0,0
size_mm=447,106
position=2
visible=0
ident=10005

gauge00=Captain_Sim.p721.P12!P12_001_ap,  20,0,427,106
gauge01=Cessna!Nav GPS Switch,  0,0,20,19
gauge02=Cessna!Nav_GPS_Annunciator,  0,19,20,19

You are welcome to copy and paste this into your panel.cfg file if you want. Or... You can post your autopilot entry from the panel.cfg and I will see if I can spot the error. ;)

Mark

Hi Markoz,
Your postings are always helpful and greatly appreciated.  I made the changes you suggested, but no joy:  During a climb in the 727-100 as soon as I engage the AP aileron and elevator paddles with the disc on manual the yoke goes full forward, the pitch angle rapidly goes negative and increases the dive the more I click or hold the increase position of the knob.  The knob controls turns accurately but if I push the knob at the 12:00 o'clock position that also increases the rate of descent.  Both 12 and 6 cause descent but not controlled. The only way I can control climb or descent is to constantly adjust elevator trim.
As I recall, before the GPS switch modification I could begin the climb, establish the rate of climb I wanted, and as soon as I engaged the AP paddles the AP held that rate of climb until level-off without any additional inputs.

Here were my panel.cfg settings before making the changes you suggested (but AFTER the NAV/GPS modification):

[Window03]
//Background_color=0,0,0
//size_mm=427,106
//position=2
//visible=0
//ident=10005
//gauge00=Captain_Sim.p721.P12!P12_001_ap, 0,0, 427,106
Background_color=0,0,0
size_mm=427,130
position=2
visible=0
ident=10005
gauge00=Captain_Sim.p721.P12!P12_001_ap, 0,0, 427,106
gauge01=Cessna!Nav_GPS_Annunciator,                   400, 106, 24, 22
gauge02=Cessna!Nav GPS Switch,                          376, 106, 24, 22

I changed the relevant settings to your numbers, only leaving the annunciator as gauge01 and switch with gauge02 as they were originally, but with the respective changes you suggested.

I'm wondering if something changed in the autopilot section of my aircraft.cfg file.  Here are the settings as they are now:

[autopilot]
autopilot_available=1
flight_director_available=1
default_vertical_speed=1800
autothrottle_available=1
autothrottle_arming_required=1
autothrottle_max_rpm = 90
autothrottle_takeoff_ga=1
pitch_takeoff_ga = 8
max_pitch=10.0
max_pitch_acceleration=1.0
max_pitch_velocity_lo_alt=2.0
max_pitch_velocity_hi_alt=1.5
max_pitch_velocity_lo_alt_breakpoint=20000.0
max_pitch_velocity_hi_alt_breakpoint=28000.0
max_bank=25
max_bank_acceleration=1.8
max_bank_velocity=3.00
max_throttle_rate=0.10
nav_proportional_control=14.00
nav_integrator_control=0.35
nav_derivative_control=0.00
nav_integrator_boundary=2.50
nav_derivative_boundary=0.00
gs_proportional_control=20.0
gs_integrator_control=0.58
gs_derivative_control=0.00
gs_integrator_boundary=0.70
gs_derivative_boundary=0.00
yaw_damper_gain=1.0
autoland_available=0

Thanks in advance for any additional wisdom;  I'm flummuxed.

Hi Trailboss.

I compared you Autopilot settings with mine and they are the same. Although you have done you autopilot panel entry slightly different to me, they still work fine.

I copied and pasted your autopilot panel entry into mine and took the 727-100 for a flight, everything was working as it should for me. No diving or anything. Climbing and descending as per the A/P commands.

This does sound like you aircraft is nose heavy. Did you change anything in the weight_and_balance section?

For now, I would suggest you go back to the original files (You did back them up, didn't you?) and start the changes again. That could get it flying right again.

Mark

Maybe  you already checked.
Before takeoff, open FSX fuel/payload and look at C/G if is in side  the envelop. If yes, check your trim wheel indicator, if its remaining below 0 then plane will dive. Put the trim close to five and take off.

Markoz and Asanal,
Thanks for your ideas and I'll check them out and let you know the results.  Yes, I did back up the original panel.cfg file, having learned that lesson the hard way several years ago.

Markoz and Asanal,

Okay, I'm slapping my forehead vigorously.  I went back to the CS KB about the AP modification and found an warning saying "IMPORTANT:  Before using the autopilot turn and pitch button be sure to turn the altitude hold switch on and off."  When I did that today the AP knob worked as advertised.
Duh!  Sorry to bother you.

Has anyone manager to control vertical speed with physical buttons?

I´ve assigned the following commands via FSUIPC to one of my joysticks.

AP_VS_VAR_INC
AP_VS_VAR_DEC

In other planes, such as in Realair Duke, VS can be changed by pushing the buttons, but nothing happens in this baby.

I think that 727 has no VS control in autopilot. The VS is controlled with the pitch knob.

javiercuellar wrote on Oct 15^th, 2010 at 2:00pm:

I The VS is controlled with the pitch knob.

What FSUIPC command could be used to command the pitch? I´ve tried this & that, but nothing works. I wonder if pitch can be controlled with nothing but mouse.

I also use the the 2D A/P panel in the 3D cockpit but more and more often when I pass the cursor over the 2D A/P panel (which I normally put on the top of my screen) the entire screen goes black (only sound is still available) and the only option is to stop the flight and restart FSX again which is a real disaster. I tend to use the normal 3D A/P panel but as suggested above the pitch control is a real pain.

Has anyone else had the same experience and maybe found a solution?

pedrovazua wrote on Oct 25^th, 2010 at 3:15pm:

I also use the the 2D A/P panel in the 3D cockpit but more and more often when I pass the cursor over the 2D A/P panel (which I normally put on the top of my screen) the entire screen goes black (only sound is still available) and the only option is to stop the flight and restart FSX again which is a real disaster. I tend to use the normal 3D A/P panel but as suggested above the pitch control is a real pain. Has anyone else had the same experience and maybe found a solution?

Although I have had my FSX screen go completely black (Direct3D seems to stop working). It can happen on any FSX aircraft, not just the 727. I run FSX in "windowed mode" and it happens mostly if I'm go back and forth between FSX and other open programs (including Windows Explorer). I quite often have Acrobat, Windows Explorer, FSC 8.6 and others, running at the same time. I have found that my main culprits are Flight Sim Design Studio 3.5.1 and Gmax (both these programs hate sharing Direct3D with any other program).

I have not found a solution. I also found that it was worse when I had my Nvidia 1GB 9800 GTX+. I see it far less now with my current system. Maybe that's because it is more powerful. Could it be that you have FSX settings to high for you system? I never experimented that much with the settings once they looked just right. I liked where they were at. I would just swear at FSX and restart it when it all went black. I still do (swear at FSX and restart it, that is).

Mark

Thanks Mark for the answer. I will reduce a bit my settings, however I only get this black screen reaction when I pass the cursor over the Automotic pilot window, the rest of the time nothing happens. I have never have had any such black screen reaction in any other add-on aircraft or situation while using FSX. I think there is something wrong with the aircraft, may be Captain Sim can find a solution to include in the next patch.

pedrovazua wrote on Oct 28^th, 2010 at 2:00pm:

Thanks Mark for the answer. I will reduce a bit my settings, however I only get this black screen reaction when I pass the cursor over the Automotic pilot window, the rest of the time nothing happens. I have never have had any such black screen reaction in any other add-on aircraft or situation while using FSX. I think there is something wrong with the aircraft, may be Captain Sim can find a solution to include in the next patch.

i`m having the same problem, and this message sayng that the video driver has stoped and it was recovered (not sure if it is the actual words), but FSX is black and have to be restarted, losting the whole flt.

My GPU is nvidia 9800M GTS, with latest drive from nvidea.