While I am very impressed with the 737 in fact I would have to say all in all it is a delight and I have not had any glitches or problems so far until last evening doing a flight Sydney to Norfolk then Auckland.

For some reason the HSI displayed course information incorrectly both tracking the VOR and the ILS. In all cases I could not get the HSI course needle to centre no matter how many times I intercepted track using the VOR and the ILS localiser path was the reverse of what it should be (that is the opposite side indicating I was left of the localiser when I was right etc., that is what I would expect of a back course but not a vector onto the ILS and final, nor could I obtain a proper intercept the ILS either (in the end i didn't because the localiser needle stayed deflected to the right,  took me ages to try and work out what the hell was happening given my spatial situation vis a vis the arrival aerodrome. No flags and ident ok, so go figure. Went visual and used the GPS to finish.

Just curious has anybody else had this issue or it may be a scenery/navaid bgl glitch?  :-?

Going to do some more testing on different places with the 737 tonight.

Testing completed at YSSY and YSTW in Australia.

Appears there is a bug or malfunction with the HSI in my copy or all perhaps. Ticket submitted.

For information for other users:

ILS Glide Path and Localiser are frozen at 2 degrees down for Glide Path and 2 Degrees right and needles do not respond to appropriate interecepts or attitude altitude changes on the ILS.

Dual RMI gauge shows accurate track course and relative bearing of navaids information by comparison.

Same problem when using VOR 2 degrees to right continuously and track interception poor but can be achieved but needle centre and course or track capture cannot be maintained with needle centre. Course needle will move to right and sit there.

Nav mode is selected on the Nav/Com Box and testing produces no needle shifts but appropriate test cycle on the DME.

737 is basically grounded for me until this problem for me can be resolved as unable to fly VOR or ILS approaches in the 737. Accurate navigation via VOR is also not possible.

As they say - bummer!  :(

This happen all the way from Sydney to Norfolk, then on to Auckland? As well as on the route from Sydney to Tamworth? Strange, I just did a flight from YSSY to YSTW and it worked fine for me. :-/

Well I did a repair (reload) of the models. Tried again, same outcome with the 200, glide path remains static at 2 dots down and localiser needle remains static at 2 dots right. Dual RMI guage is working fine. No flags and nav selectors as per the manual. It is almost like the unit of gauge does not come out of test mode even though it is properly selected on the frequency and nav control box on the pedestal but it is reversed. I can be perfectly lined up on the RMI and visually confirmed for the runway but the needles do not shift except on back course where they go to the opposite side.

This one has me stumped.

CoastalDriver wrote on Sep 3^rd, 2012 at 9:41pm:

Well I did a repair (reload) of the models. Tried again, same outcome with the 200, glide path remains static at 2 dots down and localiser needle remains static at 2 dots right. Dual RMI guage is working fine. No flags and nav selectors as per the manual. It is almost like the unit of gauge does not come out of test mode even though it is properly selected on the frequency and nav control box on the pedestal but it is reversed. I can be perfectly lined up on the RMI and visually confirmed for the runway but the needles do not shift except on back course where they go to the opposite side. This one has me stumped.

Sorry to hear that. Have performed many approaches into PANC and PAFA with no issues.  

Well problem solved, how? absolutely no idea. I relocated to a reliable airport Sydney then proceeded to conduct about 6 full ILS approaches with 6 different aircraft models, some CS some not. They all worked fine including the CS 707 and 727. I started with the 737 (same problem) switched to a DC-3, then a Baron, then to a Twin Otter, to the 707, the 727 all worked normally and as expected, finally back to the 737 and lo and behold now it worked as it should. Go Figure I have no idea. The only thing I can think of that resetting all the aids autopilot etc on another model some how reset for the 737 at the end.

Still reckon there is some thing dodgy with the panel switches on the 737 that I have installed sometimes they work sometimes they don't for some reason. Ah well. Then again maybe it is just FSX.

Happy again.  :)

Yeah and one other thing I am done with ILS approaches for awhile too much work, reminds of work in past times, crappy days and instrument approach after instrument approach (with the odd missed approach due to not getting to minimums - meaning you went round and did it again), had you completely stuffed by the end of the day.

8-)Off to do some VFR stuff.