I have not had any issues with LOC intercept, and I have flown many approaches to many different airports.. Am I doing something wrong? :He He:

 

I have no issues with LOC intercept either, and I have flown her many times now too. The only 2 main issues I have now, is the abrupt initial turn when the AP is engaged. It seems to settle down after that. The other issue is pitch/roll control effectiveness, right now I have to pull back on the stick quite a bit to get the plane to react. This makes it difficult to manual land with a good flare. I believe Joshua said that is in the next fix.

 

Me either. Mostly because this add-on usually causes a CTD long before I get anywhere near a localizer...

 

No CTD's either!!!

I have not had any issues with LOC intercept, and I have flown many approaches to many different airports.. Am I doing something wrong? :He He:

 

I haven't either, but FSX must have tens of thousands of ILS approaches, with a multitude of ways you can fly into the localiser for each, if the problem is somehow limited to certain approaches for whatever reason it's hardly strange that some people have had problems and others haven't.

If I'm understanding correctly you were trying to fly a selected heading? Did you left or right click on the heading select knob? What did your FMA read?

Yes

Well, Joshua has just confirmed that the localizer issue is in fact a bug. Not user error.

Well, Joshua has just confirmed that the localizer issue is in fact a bug. Not user error.

 

I wonder what the circumstances are that cause it? For me use ATC vectoring, and intercept at about a 30 degree angle at 180kts or less. Sometimes it will overshoot a little, but quickly recaptures, other than that she tracks the localizer as expected, and Glideslope capture is just about perfect. A lot tighter than the Wilco A320. Also since 1.02c the flare on autoland seems much better. No more 400+fpm touchdowns.

To who never had an ILS issue, just fly the ILS04L SHM transition in Sharm El Sheik (HESH). Loops every time.

 

I can do 20 ILS approaches there and it will always loop. I can do 20 ILS approaches in say Lisboa ILS03 and it will NEVER loop. I can even do a 90º approach to the ILS and it'll fly it good.

 

Bug Confirmed, Fix on the way.

 

The next update should fix several things that are ALREADY FIXED in our SVN software just that we are waiting for a few more to come in and we will push out a new version again.

 

Thank you very much. Just for the record, i am only trying to help here. If i sound harsh sometimes, it's just my way of typing i guess... Your work and support on the 'Bus has been very very good. Thank you again.

Me either. Mostly because this add-on usually causes a CTD long before I get anywhere near a localizer...

 

Sorry to hear you're having touble Bob,

I'm using Prear3D with very few CTD.

I had some BSOD's that were caused by a sound card (Xonar D1) which I removed and used the default sound card.

 

Have you a short (about 50 mins) route I can test that gives you a ctd?

Try EGCC => EIDW

CoRteName=EGCCEIDW01

ArptDep=EGCC

ArptArr=EIDW

RwyDep=EGCC05L

RwyArr=

SID=WAL1S

Airway1=UL10

Airway1FROM=WAL

Airway1TO=PENIL

Airway2=UL70

Airway2FROM=PENIL

Airway2TO=BABRA

Airway3=L70

Airway3FROM=BABRA

Airway3TO=GIGTO

Airway4=UL70

Airway4FROM=GIGTO

Airway4TO=SOPAX

Airway5=L70

Airway5FROM=SOPAX

Airway5TO=RAMOX

 

and see do you get a CTD.

Common STAR to EIDW is RWY28 LIPGO

To who never had an ILS issue, just fly the ILS04L SHM transition in Sharm El Sheik (HESH). Loops every time.

 

I can do 20 ILS approaches there and it will always loop. I can do 20 ILS approaches in say Lisboa ILS03 and it will NEVER loop. I can even do a 90º approach to the ILS and it'll fly it good.

 

 

 

Thank you very much. Just for the record, i am only trying to help here. If i sound harsh sometimes, it's just my way of typing i guess... Your work and support on the 'Bus has been very very good. Thank you again.

 

Sounds more like an issue with the AFCAD not the A320. Are you using the default airport or an AFCAD? If the latter let me know which one and I'll try it on my system.

 

Edit: Just looked at the approach definition for this airport (Stock) It has a back course beam, so maybe that is the problem. I've seen this on the Wilco A320, When the localizer first becomes active, it appears to reverse the beam, after about 1 or 2 nm into it, it well reset to the proper orientation. If I lock on to it before that it will do the same thing you describe. I have noticed the same thing at some airports with the Aerosoft A320 Initially the localizer appears reversed, then it resets properly a few moments later, though it never miscaptured. Are you seeing the localizer beam reverse when you have this issue?

I am using Aerosoft's HESH airport. But it's irrelevant, it happens in a lot of them, and no other aircraft does the same, i've done my homework.

I am using Aerosoft's HESH airport. But it's irrelevant, it happens in a lot of them, and no other aircraft does the same, i've done my homework.

 

I agree. It's irrelevant.

 

When I tune in any ILS when flying an "Airbus A320" I expect it to work without doing the merry-go-round on me. Because this is a problem within the AXE. I can do the same approaches a million times in the other add-on (you know which one) without any issues. However, don't ask me why some people flying the AXE get problems with the localizer and others don't.

 

Just glad the developers are on top of things now.

Glad to hear that this bug is getting attended to. I experienced the 360 once on approach to ILS rwy 28L at KSFO (no backcourse beam there).

I had been flying the AXE without issues, then 2 nights ago departing EDDF for LOWW it was following the route which dictated a turn to the right. The lines in the ND showed hard turns, no curves. When it came to the turn, the aircraft started a turn to the left away from the track instead of a right hand turn. I put it on heading mode but had no effect so hand flew it back on track and everything went back to normal.

Last night my departure from YMML was very good, the track shown in the ND changed from hard straight lines to a nice curve to show how the turn would be performed and it flew beautifully, but the managed descent wasn't so good. For some reason in full managed descent it put me 3000ft above ground with 30nm to go and only stopped when I changed it from managed to manual. Aside from these two strange occurrences it has been a lot of fun, so look forward to some more hotfixes and maybe a voice first officer (coming soon I believe from MCE), as things get horribly hectic when flying online and you have to chase the turns!

I agree. It's irrelevant.

 

When I tune in any ILS when flying an "Airbus A320" I expect it to work without doing the merry-go-round on me. Because this is a problem within the AXE. I can do the same approaches a million times in the other add-on (you know which one) without any issues. However, don't ask me why some people flying the AXE get problems with the localizer and others don't.

 

Just glad the developers are on top of things now.

 

Well I just flew a flight from HECA to HESH, and she captured the localizer for 4L perfectly, but that was with the stock airport. So the problem may be more with the Aerosoft HESH AFCAD, then with the A320.

Well I just flew a flight from HECA to HESH, and she captured the localizer for 4L perfectly, but that was with the stock airport. So the problem may be more with the Aerosoft HESH AFCAD, then with the A320.

 

Yeah, there isn't any logic to this that I can find. I have trouble both with default and add-on airports. Not all airports, maybe 50 %, Only with the AXE though.

 

Also note that we can argue about where the problem lies until the sun sets for good, but the developers have said there is a bug and are coming out with a fix for the bus.

Testing Top of page forum problem, I can't see your reply Daniel, which shows on the new reply section at the home forum page.

 

Edit: There it is, but interesting it's not at the top of the next page.