Maximilian_Groeber

Do you want to display a rad/dme position or do you want to enter such a waypoint? In the latter case the syntax is FFFFFRRR/DD.D (FixRadial/Distance without any spaces) and you type it into the FMC's scatchpad (LEGS page). Then you may insert this point anywhere into your existing route and the aircraft will fly to it. If you just want to display a certain radial or a dme circle on the ND (dashed green lines, if I remember correctly), then you seem to be alright... Go to the FIX page, enter the identifier into the scratchpad and push the LSK next to the FIX line (2L, I think). Below that FIX line, you have three lines that look like this: ---/---. Each line can be used to enter a radial, a distance or both. Just a three-digit number would represent a radial (358), a slash followed by a number would represent a given distance (/30) and a combination of both would be entered like 358/30. However, this is nothing the aircraft will fly to in LNAV. It is displayed on the ND, you may read ETAs (and predicted altitudes?) from the FMC.

Well - I came across this thread (Alaska Airlines' milk run)... That's fun! There is a nice scenery that covers especially many short Alaskan fields: Snow Dog Tours V2 (just search flightsim.com for "Snow Dog" - I didn't find the new version on Avsim). If you want to test your skills on runways that are only 6000ft long, this scenery is definitely something to try! SFP maybe useful :-)

Well, something similar happened to me using ActiveSky Evolution... Sometimes, there seem to be some errors fetching weather. I flew NZAA-NZCH. On the approach, the radio altimeter became active while I was way above any terrain around (I thought). I also pressed "B" - and suddenly, my indicated altitude dropped multiple hundred feet. I got a real strange barometer setting (extremely low, not as low as yours indeed) and the "disagree" message. The atmospheric pressure continued dropping for a short time and then slowly reverted back to a more reasonable number. I have had ASE to smooth my pressure changes. Probably you got the same problem without smoothing the pressure changes thus dropping your plane right out of the sky... As I said, it lasted only a short time (maybe some minutes) and the "smooth" setting probably saved me from crashing straight down. To me, this seems to be related to weird weather reports, not to the weather engine (REX or ASE or whatever). I read a strange METAR with a 5-digits pressure number once, so there might be a errourneuos 3-digits report as well. Perhaps you may fine tune the interpolation of weather station reports and transition smoothing?

Hi Folks!I'm just flying some miles west of Yakutsk (UEEE). Suddently, the cover of my right throttle lever guide grows all across the cockpit!This seems to be a "geographical" problem. I never hat this problem since yesterday descending into UEEE, coming from the east. And it occurs only at a certain altitude (roughly 30.000-34.000ft).Can anybody confirm this glitch? Or am I the only one? Well, I can live with that then...My system is a VAIO F13 Notebook (nVidia GeForce GT425M).Maximilian Gröber

Ahh, now I guess what you're aiming at... You have certain altitude restrictions at certain waypoints which you would manually "connect by drawing a straight line" and you don't want the aircraft descend below that imaginary line, is that correct?Well, the aircraft exactly does this as long as you don't enter "above" or "below" constraints. You would enter the final GPA on the approach reference page. This is what you can use for an IAN approach, and the aircraft will try to descend down this path as long as you do not specify something different. As soon as you enter altitude constraints, they have priority over the final GPA. You can't specify multiple angles, as far as I know but you have to use altitude constraints. However, charts always outline the altitude restrictions as well so that should make things not too complicate. A little example I just flew 30 minutes ago :-) The VOR/DME approach RWY 05 into Christchurch. If you'd like to have a chart, look here. At the last waypoint, you end up about 2.250ft above a standard 3° GP. I entered all the constraints into my CDU and the aircraft just flew like drawed on the approach plate profile, completely ignoring any GPA. Of course, you then have to make sure that you reach the runway without a parachute... For example you may fly a circle at NZQN just in front of the runway. The same thing works for approaches with different descent angles, for example VNKT. I tried the VOR/DME approach RWY 02. There you have a nice mix between various descend angles. The aircraft may fly a bit too high, especially if you enter the constraints "at or above", but it never descends below that imaginary profile line that connects the minimum waypoint altitudes. Just remember: The GPA is important for an IAN approach and if you want the FMC to auto-calculate the altitude restrictions for the IAF/FAF. But if you have constraints on that, they have priority.And if you'd like to hit the specified altitude prior to any waypoint, you have to select FLCH or V/S and use the autopilot "manually". Hope that helps... Maximilian Gröber

Hmm, I don't know if this is exactly the point you are aiming at, but, the VNAV approach profiles usually contain altitude constraints "at or above" until you reach the IAF or the FAF. In this case, the aircraft will continue on a constant descent, that's true. You can alter the altitude restraints to "at" at certain points, at least at the start and the end of your desired intermediate descent segment. Then the aircraft will descend according the entered altitudes (it even will level off in VNAV if programmed so). Just have a look at the FMC altitude constraints and make sure there are no unnecessary "A" or "B" letters. In the VSD you will notice a hour glass symbol (two arrows above each other) as well. Hope that is what you'd like to know... Maximilian Gröber

Well, I recentliy discovered a nice solution ;-) I always had the "zone temp" warning too as soon as the engines were running... Just try this: As soon as the engines are running and bleed air is used for air conditioning, rotate all temp knobs a little bit (counterclockwise if you want to lower the duct temperature) and if it's rather hot outside, switch off trim air. Then wait a moment until the duct temperature stabilises and turn the knobs back to their former position. It works perfectly for me! Afterwards I can tune the temperature very comfortably. No zone temp issues (at least, as long as the outside temperature is not too high) and the duct temperature doesn't rise above all limits as soon as I turn any knob just one little click... Maximilian Gröber

As far as I remember the NGX engines do not spool up a bit when using anti-ice, but that's a more technical thing. You basically have two different systems on the NGX. Anti-ice for the engine nacelles (TAI or engine anti-ice) and wing anti-ice. Engine anti-ice is used to prevent the buildup of ice, so you normally switch it on at temperatures below 10°C (TAT) and visible moisture. Wing anti-ice is used to melt ice away from the leading wing edges, so you switch it on when you actually see some ice accumulation and you switch it back off when your wings are clear (there are some Youtube videos where you can see the effect very nicely). Somewhere it was stated in this forum that ice effects are not modeled on the NGX, because the real aircraft has very efficient anti-ice systems and is not really prone to those effects. Control surfaces normally don't freeze inflight. You would perhaps apply anti-ice fluid before takeoff, but that works another way... Maximilian Gröber - edit: also see the post above - I was too slow...

Well, AFAIK this has been noticed as a bug somewhere in this forum... The problem, as you stated above, is the custom waypoint that you entered (MIAXXX). It's just the way you described it: When you enter a custom waypoint and select it thereafter via the corresponding LSK, the FMC will copy down the raw data. So you will always enter a new waypoint this way and your discontinuity will just step down one fix. Other PMDG planes don't show this behaviour. I also can reproduce this behaviour every time I deal with custom waypoints. Perhaps this is like the real thing - I just don't know. I just remember another thread about this. Maximilian Gröber

Hi guys! I just flew a few times with the GOL livery (SFP installed) - of course I tried SBRJ :-) - and now I'm wondering whether the FCOM has exact information on the 737-800 SFP performance. There are all the tables that I need for calculation but they seem to refer only to the "standard" 737-800. Are there any hints how to calculate the different weight limits? All I found was some generic information (for example from the post of Jane Rachel or google). Is there something that I just dind't see? Especially at short runways I'd like to be able to calculate whether my aircraft is too heavy or not. At the moment I'm using the standard limitations of the 737-800 at an imaginary weight of 1.700 kg less than it actually is, and it works rather nice. And if I'm not 100% shure, I just try it out - this is still a game :-) ! But is there any table of correction or some completely different tables to determine MTOW/MLW, V speeds etc.? Thanks,Maximilian Gröber

Have you tried this little trick Jordan mentioned?At least it's sufficient to switch *once* to 2D view and back (Shift+A / A). I often encounter this problem when flying over a vast landscape without any airport in the vincinity (the sea, for example). When you step through the different views, FSX won't find a tower view and the next time you arrive in your VC, it looks freezed - although the aircraft flies and reacts properly to your inputs. The important thing is just to switch between 2D and 3D cockpit view. This way, FSX reloads the panel itself but won't hang because any missing view. Perhaps it works... :-)Maximilian Gröber

Hi guys! I'm still fascinated about all the major and minor quirks that are simulated here, but I think this one is not "as real as it gets"... When I switch on the panel lights (the backlighting for switches etc), some components light up at full brightness immediately, some are dimmable. Especially switches always are lit very bright.This curiously does happen with all panels except the overhead panel. The same thing happens with the flood lightling (not dome) of the pedestal. At some "parts" (mostly the flat ones) the light is literally switched on, at others (mostly knobs and other 3D modeled things) the light remains dimmable. I think the technical problem might be the same, so I only attached three pictures of the main panel lighting - one has the lights turned completely off, the next one was taken after one single right click at the brightness knob and the last one has the lights at full brightness.The very early demo video (Youtube - interior lighting demo) doesn't show this particular behaviour. I also couldn't find a related topic. I'm running the version with the hotfix 16AUG11 although the issue showed up from the beginning. (Interestingly I dind't loose my liveries when I installed the hotfix - but at the next start of FSX I got all those prompts to allow the new software, so I think it's installed correctly...) I can live with that anyway - but if there's a fix, i would be happy :-) Thank you!Maximilian Gröber

Hi all MD-11 enthusiasts!I've a slightliy special question, at least I didn't find any precise explanation in the manuals or this forum.If the External Power connection (3rd MCDU) is set to auto, when will external power and external air be connected after landing and shutdown?Thanks for your help!Maximilian

I recently encountered a little nice bug...I flew through Russia and for almost every approach there, ADF beacons are essential.Now the MD-11 FMS offers an autotune feature for ADF as well as for Nav1/2. But, the frequency is tuned with the decimal point being at the wrong digit! For example, an ADF has a frequency of 230 kHz. Then the FMS tries to tune it at 23.0 kHz. The same with a frequency above 1000 kHz, like 1080 kHz. The FMS displays (and tunes to) 108.0 kHz.Has anyone experienced a similar behaviour yet?As it may be useful... I'm running FS9 (with MD-11 for FS9, of course :( ) and Vista Ultimate 32bit.Maximilian