bamboofats

Hmmm, in that case you may disregard my so called "fix", I am not aware of the real procedures for most of the airports. but just you know there isnt anything wrong with your setup or procedures(in engaging autopilot), Though there are many airports around in FSX whose ILS's are misaligned, especially in more remote areas and those without custom scenery. Using those will land you onto the grass. Check with real life charts if necessary. The fsx map can give you the placement of the ILs in the FSX world. Zoom to the closest level and see if the ils feather is in line with the runway line. If i am not wrong one example I can remember offhand is WMKJ. Regards Marcus Jian

I checked the FSX files, It doesnt appear to be your fault. The default FSX data for KBUR is kind of messed up. (i am not sure if Real life or FSX data flaw), The ILS is placed ahead of the runway, causing the airplane to "run out" of the localiser before it lands. So the autopilot disconnects. See your FSX map, with ILS display, for a visualisation.Regards.Marcus JianEdit, You may try this fix I just did for the airport sce file.http://www.mediafire...bd72r11u8x6mxg6Basically just repositions the ILS. You can try if your autoland works now.Place into FSX/Addon scenery/scenery folder2nd edit. Im assuming your airport in question is a default fsx one. I dont know if this will conflict with any custom airport scenery you may already have for KBUR.

I didnt read the crash log because then i was kind of like "arrghh". A small lag felt after the button was pushed and I knew the whole flight was ruined. I havent tried it again though. But it seems the fmc crashes I had always had to do with editing the waypoints. Much higher chance of getting it if stars/sids/ transitions are included with the plan. Rarely a program pin error will occur with adjusting the plan but it is usually recoverable by deleting and reentering the entire plan. But I still have the crash where exec, erasing or upselecting points will have fsx freeze completely for half a min and then CTD. I try to enter each waypoint in the STAR manually instead of just selecting it from the DEP/ARR page, in hopes that this eliminates the problem but it seems I still get it sometimes. Oh well. I think it's pretty random.Oh and btw, I was running only with ASE. All my scenery is tuned down. I was over the ocean and running at frames excess of 100fps using 2d panel.

Even now it is hard to create these arcs manually with the fmc. NGX currently does not support creating radial waypoints from prior custom ones. Hope this functionality is included in the future, maybe along with others.Marcus Jian

I also had a CTD with sp1b when using the fmc 2 days ago. Halfway through a flight, selected ARR rwyway. No stars or SIDs. Manually entered a custom waypoint near the runway, but decided to >ERASE changes. FSX crashed.Marcus Jian

Yes, if the aircraft is not accelerating (not changing speed or rotating), the effect is from pitch. So a higher descent rate paired with just the right increased airspeed would provide no change in the sensation as pitch is kept the same, ignoring increased vibrations etc. But this effect isnt significant for passengers as the different descent rates just mean a pitch angle difference of a few degrees, not easily noticeable. The G forces is the significant sensation felt, when aircraft changes speed, rotation. But still, I think it is incorrect to say that the pitch is transparent to the passenger, from a physics point of view.Marcus Jian

It is not entirely correct to say that in the presence of 1G, and without looking out of the window, the passenger cannot feel any difference between a high and low descent rate.Although the passenger is not experiencing any acceleration because of the constant descent speed, one can still tell a difference because of proprioception, how the body senses one's orientation in space.(via ear fluids and body contact forces) It is like on earth, where your G forces is 1, you can tell the difference sitting on a chair normally, and sitting on a tilted chair, blindfolded. The reaction to weight, from the chair onto the body, is applied on different parts of the body, For instance, standing up and lying down, the reaction to weight from the floor is acting on the feet and back respectively and the body can sense this.In the aircraft descending at 2 different, but constant descent rates, will need a different descent angle. This angle is like tilting the chair while you are on earth, although the effect may be less dramatic than G force changes with changing descent rate, but i believe one can still sense it if the angle is large enough. One extreme example is a pilot which decides to descent vertically straight down, unaccelerated(due to air resistance). The G force on the passenger is still 1G, but he can definitely sense something is wrong, as the reaction to weight on his body is not from the chair, but from his harness that prevents him from falling onto the seat in front.Marcus Jian

Give a search on google for overclocking your particular CPu model. Most likely there are tutorials by experienced users on this. Typically if your motherboard has the correct features,(prebuilt computers may not have these features) you can perform the overclocking and other system changes on the BIOS screen before you load your OS, no need for extra programs I believe. And as mentioned, the cooler is quite important for system stability at higher clock speeds.Marcus Jian

ALright, you got it. I'll just share with you what i usually do (not that I use the NGX very often),Normally I leave the SET FSX COURSE as on, because it works for most airports just fine.When you capture the localiser, have a look at the 'needle'. It should go rapidly to the centre and stop there firmly without hesitation, even in mild turbulence or crosswinds. This is what should be expected.The moment you see the dot stuck to the left or right of the centre, (bad airport) its time to pull out the FMC and disable the SET FSX CRS. Tweak the course settings until centered, if the dot is on the left, decrease, on the right, increase. Set the copilot course to match as well.Continue with your other landing procedures.After landing, can choose to enable the SET FSX CRS again.This isnt very realistic because it's not even a real world procedure, but it's a quick workabout and works with zero visibility outside. If done fast should not take more than 30 seconds.This technique (checking the dot) works for airports that have a perfectly aligned ILS but due to the outdated mag var, the dot is not centred.This must be differentiated from airports whose ILS are physically offset, (either deliberately or due to poor data), ie the ILS in the FSX map is visibly misaligned. In this case, the dot can be perfectly centred but your plane is not going to land centreline anyway.Regards.Marcus Jian

Ryan has given his input on this, He suggested that it may be a SP1 bug they accidentally introduced. You might want to check the recent topic How to arm G/S, when ILS is not in database?, which has quite a bit on discussion on this.RegardsMarcus jian

But even if it is not an NGX bug as you put it, this means that the NGX cannot capture a glideslope on any airport that is not listed under the Navigraph data, such as those in more remote areas, or ones that Navigraph lacks data for.Even with appropriate ATC support, and custom fixes entered to simulate the ILS approach, as long as it is not under Navigraph the GS is useless for the NGX? To me that seems quite a big limitation. Even other 'less functional' airplanes can capture the glideslope at those custom approaches just fine, and it isnt any less realistic in these cases.Marcus Jian

This could be a bug, or some feature/ functionality adjustments. I'm not sure if this change was intentional or accidental, (if this was working fine pre SP1), but either way I don't really fancy the idea of being able to activate the GS only when a corresponding data is in the FMC, given that FSX's and AiRAC datas do not cover all airports well. Perhaps PMDG or someone knowledgeable could help here.Marcus Jian

I think SP1 may have removed this (i may be wrong), because if i recall, I had the GS ON/OFF option prior, just selecting a runway with no approach specified. Now it seems that you need to enter the approach as an ILS in order to have the GS option. This was especially bad, when faced with certain airports that had an ILS in fsx, but no ILS approach because the AIRAC did not have data for it, and the NGX could not capture the glideslope.Marcus Jian

to see this airport's error. spawn on runway 27R. notice the magnetic heading on the 737 as 268.Now go to FSX map (you need to pause the sim), under world | map. investigate runway 27R and its ILS, they will report 265.This 268, 265 difference is what causing the misalignment. The scenery local mag var does not match the global ones at those coordinates.You fix this you have to download the specific scenery bgl file for that particular airport, either from someone who corrected it, or if youcorrect it yourself using some airport editor.I tested that airport, I adjusted the course until it was 266, then i had nice centreline landing. You can give 266 a try.The FSX SET CRS settings of 268 brings you too much to the right.using the manual course adjustment method, if you are too much to the right, decrease course, too much left, increase it.marcus jian

Ok, i think for now there are 2 choices for him.- leave SET FSX CRS on, fine for most airports. But may cause centreline issues for certain ones.- disable SET FSX CRS, means you have to manually set the course for all airports, will get a bit messy, and you have to use experimentation to line up the ILS, especially if your charts, the AIRAC data, or airport headings or any of the combinations do not match. But you can avoid the centreline issue because the course knob is not fixed in this case. This method may also be unrealistic. (pilots dont tune around the course knobs to line up the plane, they already know what course to enter)Regards Marcus Jian

Hmmm, but proper FSX data doesnt necessarily mean correct data, if the FSX data is wrong in the first place. Somehow if rsperge did not get the desired localiser path when using that feature, maybe try turning it off and trying another technique for that particular ILS.marcus Jian

I haven used the 737 for a while but I'll try to help. The set FSX LOC CRS makes it easier to fly a localiser as it adjusts the course to match the heading given by the localiser automatically, without the consideration if the data is outdated, or different from your charts. This should work for most cases. However, for some airports(maybe the ones you experienced centerline issues), the FSX LOC CRS doesnt not really work because the 'hidden' heading for those airports is wrong. The local mag variation, like what ryan said, is incorrect. Thus the MCP auto sets a course that is different from the local heading reference because of this mag variation mismatch. You wont see this on the ND, but when capturing the localiser, you will notice it , like how you did.If i recall the solution from pre-SP1, (i haven used the plane after SP1), you have to either-fix the local magnetic variations. This is tedious as it involved fixing the scenery files for all airports with issues that you use, hundreds of airports in FSX probably have this due to seriously outdated data,or you can download some of the fixed afcad files proposed by Leffe . But if you encounter another airport not covered by this list, you'll have the offset issue. I believe the easy, apply for all, global, 2010 magvar file does not solve this issue, it helps with aligning the ND to latest AIRAC data, but not localisers.-the other is to disable SET FSX LOC CRS, giving you freedom to adjust the course indicator. FOr the incorrect localisers, you must set 'incorrect' course settings to get the plane on centre. How much left or right to correct is a bit of experimentation. Usually it is a few degrees needed.Im not sure if SP1 fixed it so my points are valid or not, but from what you mentioned, it looks like this its the same situation. Anyway, you can correct me if im wrong on some of them.Regards, Marcus Jian

I submitted a ticket to PMDG to check on this issue. Paul says he is looking at it but from my guess I say that this support for custom waypoints was not added. Perhaps PMDG could release a documented change list on various new features, elaborate on what 'more robust support' offered. I cant really help much because it would be mostly guessing.Marcus Jian

How to I delete my post, its not relevant. I think i made a mistake looking at the wrong needle.Marcus Jian

I noticed this as well. It seems that if you are using the *Instruments side by side* option, the ENG and SYS buttons are changed to INOP, and you cannot access the brakes page anymore. I tried switching back to the default instrument view and its accessible. I'm not sure why it is like this, I'll wait for someone to clarify.marcus jian

Assuming you disabled auto set course.One of the possible solutions (if you dont want to pause the sim to check the FSX map), is to set your best guess into the course settings, typically your current heading once your quite parallel to runway heading. Then you see if your too much left or right of the needles, which means your not tracking the ILS correctly. If your too left of the runway, increase course until the needle is centred. And the other way for right. At least this works for me 'on the go' for now. Adjust both pilot and co pilot if your doing the CAT3 autoland. Of course you have to confirm that your not landing at an offset ILS, but a runway parallel one that isnt working so correctly.Offset ILS- your needles are centered and you're flying at an awkward angle.Problem ILS- you're flying at an awkward angle, loc needle never completely centred, no matter how long you wait. Depending on how badly screwed the FSX data is, you can have ILS 'errors' that you barely notice, to ones where you'll land on the grass. Marcus Jian

(BTW - Does anyone know how to trigger a VERIFY IRS POSITION message? I really don't know how to do this.) If i recall correctly, at this current build of NGX, you can trigger that message by switching off your GPSs and Radio guidance (through NAV inhibit page),while your IRS are fully aligned but Im not sure if this is the scenario your talking about. Marcus Jian

Hi, I checked this issue a while ago so I thought I'll just tell you what I think. If you auto set FSX course, there are times when it doesn't track exactly in the middle of the beam. Take for instance an example problem ILS where the AFCAD magnetic declination is messed up. The ILS is (in this case) fully aligned to the runway, so both runway and ILS loc have a heading of 140. Your "auto FSX course" will also set to 140. Everything seems normal. However you could be offset to the beam to the right or left. What happens is inside the AFCAD ILS magnetic dec difference causes the ILS to be assigned a hidden heading of eg 135. You can confirm this by using the FSX map viewer. Your parallel to runway, heading of 140, ILS is also parallel to runway, but click on the localiser, its heading is reported as '135'. So to actually fly ILS exactly, your course should have been 135, instead of 140 as assigned by "Auto set", while your heading is still maintained at 140. So possible solutions at this time, is fix the airport such that the ILS course accurately reflects 140 like everything else,2) do not use "AUTO SET" but adjust course to the "wrong" value (135) in order to fly straight on the right (140) heading.3) Or 737 NGX is patched to extract the hidden heading of 135 for autoset, instead of 140, which I am not sure is possible for FSX or not. RegardsMarcus Jian

I think if your AC power was just cut for a while, you should have waited for about a minute or so for the GPSes to come back online. Then your data will be restored. Apparently they need some warm up time after being cycled off. Your IRS will be covered by dc power so its still there. However, once you break the IRS using ALIGN or OFF, your never ever get them back in flight. (only on ground). The little NAV stuff is gone even if your GPS turn on after 1 minute or so. (NOTE!!, from my observation, may not correspond to real life). At the same time your FPS (with this current build), should drop heavily (although unnoticable in straight level flight), while waiting for your gps to come back. Ryan mention the FPS drop will be fixed. Marcus Jian

What I referred to is not an offset approach. I would know the difference between both situations. For that airport(s), the 737 tracks the runway with an offset. But if you were to look at the localiser needle/star, its also off by a few dots. Repeating this ils with the default 737, and it tracks the ils perfectly in the centre, and in this case, its straight towards the runway(no offset). If you were talking about a deliberate ils offset, when tracking it successfully, your localiser needle would be right in the centre, not 'off by a few dots' in this case. In this thread, the problem isnt differentiating between normal parallel ILS and offset ILS like what you mentioned, its about whether the 737NGX is able to track an ILS accurately such that the needle is right in the middle. (doesnt matter where the ils is pointing). I can even have a localiser right in the middle of the ocean and get the 737 to fly an approach into the water, but if the mag dec between that area and the ILS is different, the default course you set will cause the plane to be 'off' the beam. There isnt a need for approach plates for this one. One airport which I encountered this is KPAE, runway 16R. Default FSX airport, using 2010 Magnetic Dec Data. No/little winds(as a control). The ILS is not an intended offset one. Zoom in on the FSX map if you wish to verify. For me the needle doesnt track exactly. (PMDG settings use auto set FSX course). Not sure if everyone would have this problem. If you do not use auto course, note that for the needle to be exactly centred, your course setting would not be the same as the direction your headed towards(or ILS heading). Regards.Marcus Jian (i'm not criticizing the 737NGX, its due to inaccuracies in multiple different datas in FSX that could be causing this)