JerryH

It would help to know the specific aircraft and/or whether your problem is with a jet or a turboprop aircraft. The only PID settings I'm aware of are the ones in the autopilot section that control tracking of the NAV and Glideslope. As far as I know, the only autothrottle variables are autothrottle_max_rpm and max_throttle_rate. If there are others, they probably are not accessable by the user. Regards, JerryH

I haven't noticed any downside to lowering max_throttle_rate when applied to turboprops. But, you can't hurt anything by trying it. Just backup your original aircraft.cfg file (including the original value for fuel flow gain), then hack away at the max throttle rate and see what happens. Is it true that you're concerned about jets rather than turboprops? Regards, JerryH

I don't recall having this problem with any of the jets, but it almost always occurs when I add the autothrottle to a turboprop aircraft. I don't know how many "real" turboprops have A/T, but mine seem to like it just fine. The solution that works for me is to edit the aircraft.cfg file. Go to the [autopilot] section and locate max_throttle_rate. This value is always set to 0.10 by default. Start by cutting this value in half to 0.05 or less. Then set up a flight test and experiment until you're satisfied with the result. Each time you change the value, exit the sim, edit the .cfg file then restart the sim. Let us know if this helps. Regards, JerryH

Brian, I'm using that panel with the B737-200. As far as I know, it's a Greg panel because the filename is greg7372.zip. It may be available here, but I found it at FlightSim. Regards, JerryH

Thanks for providing all the details. Before reading through your comments, I thought it could be a problem with a sloppy autothrottle and variable airspeed that caused the altitude changes. But you said the throttle is set manually. My guess at the moment has to do with pitch control or stability that can be tweaked in the aircraft.cfg file under the [flight_tuning] section. I would try one or all of the following parameters: - pitch_stability - elevator_effectiveness - elevator_trim_effectiveness The default value is 1.0 for all of those. My technique would be to change each value individually and run a test flight. Double the original value for starters to see if it makes a difference. If so, you can fine tune it later. If pitch_stabilty changes don't help, for example, set it back to the original value and try the next item. Be sure to back up the aircraft.cfg (or take good notes) before you mess with this. The problem could be caused by one or all or none of the above. Good luck. Regards, JerryH

Martin, it's impossible to help you without more info. Please give us the specifics of the aircraft model, plus the altitude, airspeed and weight during this problem. Are you using AP and/or autothrottle? Add anything more that you can think of. Otherwise, all you will get are more responses like this one. Regards, JerryH

To add to John's list, this website has lists of ATC airlines, types and models: http://www.homepages.mcb.net/bones/Flight_Sim/download/downloads.htm This may not cover everything, but should include the codes that exist in the FS9 voicepack. This includes code "L101" that will get ATC to say "L-1011". The last time I looked there were some omissions that can corrected with the EditVoicePack software. Regards, JerryH

Martin, If you're talking about the Milton Shupe Dash-7, you can expect the performance numbers to be correct. The "Performance=" section of the aircraft.cfg contains specs for the aircraft. These can be edited, but will have no effect on the simulation. Most of the values in the [Reference Speeds] section are supposed to be KTAS, not KIAS. The exception is the value for Max Indicated. At any altitude above sea level, your True Airspeed will be higher than your Indicated Airspeed. While cruising at 180 KIAS, your True Airspeed could be as much as 220 KTAS or higher depending on the cruise altitude. Also, max cruise speed will usually increase at lighter weights. Regards, JerryH

If I understand correctly, the easiest way to fix the problem is to go to Settings and click on Traffic. The Traffic page has a section of options for Aircraft Labels. Put a check mark in "Show Aircraft Labels" and check the options you want. Choices include Manufacturer, Model, Tail number, Distance and Altitude. I believe there may be more options if you want to edit the FS9.cfg file. Give it a try and let us know if it helped. Regards, JerryH

The only thing I can think of is the B727's weight is too high for an approach at 132 KIAS. That could cause you to stall at some point. This could also be the cause of the up and down pitching during turns on your approach. Turning requires more lift to maintain altitude and you may be near the lift limit (stall point) of the wings.If my overweight "guess" is correct, try the same flight after removing three-fourths of the fuel. Otherwise, I'm stumped.As far as editing the .air file is concerned, that's usually not necessary. In most cases, the aircraft.cfg file can be edited to accomplish the same thing. Many entries in the aircraft.cfg simply override the same thing in the .air file.Good luck, Robert. Let us know how it goes.Regards,JerryH

Sorry, but I missed a "key" point in the post above. The command to change views cannot be set within the FS9 Key Assignments. It must be added to the FS9.cfg file under the [Keyboard_Main] list. Mine is set up as:see_own_ac_toggle=86,9You may want to be sure that Shift-V isn't being used for something else before you add this to the FS9.cfg file.Regards,JerryH

If I remember correctly, you can do the same thing by pressing Shift-V. There are some side views that I like and others that look rather cluttered to me. Shift-V allows me to change views while FS9 is running.Regards,JerryH

My reference speeds are identical to yours for both versions of the B727. I'm totally out of ideas at the moment. When I get the time later today, I'll fly the bird and test it at higher speeds to see if I can make it shake.Please let us know if you ever figure it out.Regards,JerryH

I have the B721 and B722 from Vistaliner. In the aircraft.cfg files for both of them, under [Reference Speeds], are two speed limit values. I believe these are the ones that determine the overspeed setting. Check yours to see if they agree.max_indicated_speed=341max_mach=0.82Your speed of 220 KIAS is also near or over the limit for takeoff flaps, but I don't remember if that affects the flight model. Of course, I'm sure your flaps are up well before 10,000 feet, but just thought I would mention it.Regards,JerryH

Glad you got it sorted, Jont, and Cheers to you.JerryH

I turned "Crash detection" OFF years ago to avoid having an AI aircraft ruin an entire flight. Now, if an AI flies right through me when I'm on final, I just laugh it off and continue on to the runway.For me, having "Crash detection" turned ON just isn't worth the frustration.Regards,JerryH

Jont, you should be able to add the "zoom" lines below to the panel.cfg file for the 172. Be sure to backup the panel.cfg before you try this in case it doesn't work as advertised.If there's already a [Views] section, add only the zoom lines to it.[VIEWS]VIEW_FORWARD_ZOOM=0.750VIEW_FORWARD_RIGHT_ZOOM=0.750VIEW_RIGHT_ZOOM=0.750VIEW_REAR_RIGHT_ZOOM=0.750VIEW_REAR_ZOOM=0.750VIEW_REAR_LEFT_ZOOM=0.750VIEW_LEFT_ZOOM=0.750VIEW_FORWARD_LEFT_ZOOM=0.750Please let us know if this works for you.Regards,JerryH

I learned recently on one of the forums that hitting the Backspace key will fix it. And it does!Regards,JerryH

I'm glad you got it fixed, fogerty. Like I said earlier, it was a shot in the dark. Fortunately, you saw that the filetype was .fst instead of .gvp. and made the fix. Looks like Traffic2005 uses .fst to backup your original, but forgets to change it back when you uninstall. We learn something every day.Enjoy your next flight!Regards,JerryH

This is just a shot in the dark, but when you uninstalled Traffic2005 you may have lost the main ATC sound files. Shouldn't happen, but anything is possible. Look in your main Sound folder and see if USEnglishBig.gvp and USEnglishASOS.gvp are there. If not, you can get the files from one of your FS9 CD's. The contents of each CD are shown at http://www.cat-tamer.com/flightsim/faq001.html. Let us know if you have any luck. Regards, JerryH

I had a similar problem about four years ago that drove me nuts, but I only realized the similarity today. It has nothing to do with FS9 or add-ons. I found the culprit by running "Filemon", which I think was a predecessor to "Process Explorer"In my case, a small program named "SetIcon" was interrupting the PC about every 5 seconds. It belonged to a Western Digital external hard drive that I had purchased back then. I don't remember the reason for "SetIcon", but it wasn't needed.For my Win XP setup, it was simply a matter of running "msconfig", selecting the Startup tab and unchecking the SetIcon program. Next, I rebooted and ran FS9 ..... and finally, No More Stutters!! I have no idea if Win7 works the same as WinXP for shutting down unwanted programs, but I hope this gives you some more ideas. Good luck.Regards,JerryHEdit: I just re-read your first post that implicated FSUIPC and realize my comments may not apply. But maybe it will help someone else with an external WD hard drive.

Larry, there's one right here in the AvSim library:nca_cv580_66.zipIf you don't already have it, you'll need the base pack from CalClassics.Regards,JerryH

Thanks for the feedback, Hans. That was very good detective work. As you suggested, the .air file still has some secrets that can't be modified by the .cfg file. Hopefully, the CLS crew will see your fix and make adjustments.Regards,JerryH

Hi Hans,I've never dealt with this problem in civil jets, but have had some success in "fixing" turboprops. As usual, it's a trial and error procedure. In the aircraft.cfg file, find the 'autopilot' section. The parameter to fiddle with is the max_throttle_rate. It has a default value normally set at 0.100. For starters, I would suggest cutting that in half to 0.05. Give it a try and see what happens. If it's better but not good enough, reduce it further. If it's now too sluggish, crank it back up a little.You must restart FS9 after every change is made. Please let us know if this was of any help.Regards,JerryH

This is just a hunch, but take a look at Settings and click the Realism page. Be sure you have chosen to Display Indicated Airspeed. Never have it set to Display True Airspeed. It makes a huge difference.Regards,JerryH