That is mentioned in the step by step guide, i.e. do not engage LOC with more that 90 degrees difference to the ILS otherwise you may capture the opposite ILS beam and turn away from the airfield, I use around 70 degrees to be safe with enough time to comfortably capture the LOC. It's a bug in the default FSX auto pilot systems by the way.

 

Erm... Don't get me wrong, but i know what i'm doing. I am almost aligned with the ILS when i press 'LOC' and it just drifts away.

 

But thanks for the heads up.

Happens to me at loads of UK airports - both default and addons:-(

 

 

One can only hope. Many important issues still remain...

 

- Aircraft still climbs like nuts if you set FLAPS just near the maximum speed for speed protection. This often causes embarassment online as a controller will ask you "what are you doing?".

 

- It fails on many ILS captures, performing a full 360 turn prior to capturing.

 

- The TOD is still badly calculated. Either too close or too far away from the actual descent point. This isn't easy i know, but very important.

 

- Most STARs have problems. Yesterday flying to GMMN i had a left turn inbound the FAF for ILS35L and the aircraft decided to go right instead. The line was badly drawn on ND as it had an inverted semi-circle.

 

- Today while arriving to LPPT i had to change my arrival from RWY03 to RWY21. There were a few points remaining that i had to delete from the MCDU for the new approach. Once i deleted them, i got a flickering line on ND between the old unexisting waypoints and the new ones.

 

- When flying to coordinates (for ex 3820N or 3920N) the aircraft will usually ignore them and fly somewhere else. As an example, a widely used route from LPPT (Lisboa) to LPPD (Ponta Delgada, azores) by TAP Air Portugal which is BUSEN DCT KOMUT DCT 3820N DCT BEKUN will cause problems. Just after passing KOMUT and while flying to 3820N, the Airbus will go straight north instead of continuing west to 3820N. The same will happen once it finally reaches 3820N. No issues with the other waypoints.

 

Until these are addressed (and some more), i can't trust it online because it will run away from what a controller expects a pilot to do. I can only hope SP1 isn't far away and these are a thing of the past.

 

Hey mate, I hope you don't take offence to this, just reading your comment about not trusting the aircraft while online. If the automatics are not doing what you want just fly the machine raw data and switch to HDG SEL, V/S

 

Anyway, here's a good video, funnily enough it seems more relevant to simmers flying complex jets.

 

http://www.youtube.com/watch?v=h3kREPMzMLk&feature=youtube_gdata_player

 

 

Here's the Airbus version of that video. ^_^

 

More seriously, I understood the concerns about the trust as something like seeing lines on the ND, but also seeing that the AP doesn't follow them. Or pressing LOC and expecting to catch the localizer while the plane turns away from it. Something like that.

 

I'm still not in the position to test the new plane as my FSX rig as far away, but I'm exited about flying. That much I can tell. B)

but I'm exited about flying.

Ermmm, should have been excited. -_- Silly me.

is it possible to upload presaved flight plans by using fs commander or something like that? because i don't want to enter them manually.

If I got it right, it all depends on having a flight plan handler in place knowing about the syntax needed. As with other payware addons, the format of the flight plan has to be the right one as they can't import the FSX format too. So if there was a description of that syntax, the popular flight planning software could add an export feature for the AXE. Just like it did for iFly, PMDG, LevelD, CS, QW and so on.

 

Perhaps some devs can correct me if I'm wrong.

is it possible to upload presaved flight plans by using fs commander or something like that? because i don't want to enter them manually.

 

At the moment, no - the only way is to manually enter them. Once the flightplan had been manually entered, it can then be saved in the MCDU. However, there is a rather restrictive caveat in so far as waypoints cannot be saved in the MCDU, only airways / intersections.

 

Sent from my HTC Desire HD A9191 using Tapatalk 2

 

 

Hey mate, I hope you don't take offence to this, just reading your comment about not trusting the aircraft while online. If the automatics are not doing what you want just fly the machine raw data and switch to HDG SEL, V/S

 

No offense, but no solution either... We all know it can't be that way.

If I got it right, it all depends on having a flight plan handler in place knowing about the syntax needed. As with other payware addons, the format of the flight plan has to be the right one as they can't import the FSX format too. So if there was a description of that syntax, the popular flight planning software could add an export feature for the AXE. Just like it did for iFly, PMDG, LevelD, CS, QW and so on.

 

Perhaps some devs can correct me if I'm wrong.

 

The problem with this, is they use one file or flightplans, so new ones, would need to be appended to it, which as you know could become problematic. As it is it can't handle fllghtplans with back to back waypoints, only airways. So if you have a FP FLO-J55-HPW-191-RBV... That will work fine. If you input though FLO-J55-HPW-PXT-191-RBV, (Both of these are valid from Flightaware.) then it all gets scrambled.

Arrrrrrgh. I am now going to refer to this add-on as the Airbus X Exploded. Another CTD, this one an API.DLL fault on final after a 3.5 hour flight. Prior to installing this nightmare I had not had a CTD in something over a year.

 

Somebody should re-do the graphics for the box showing an angry simmer with joystick in hand looking at an empty Windows desktop...it'd be closer to the truth than a picture of an airplane.

 

This thing is really giving me a case of the beak.

 

/rant

 

 

That is mentioned in the step by step guide, i.e. do not engage LOC with more that 90 degrees difference to the ILS otherwise you may capture the opposite ILS beam and turn away from the airfield, I use around 70 degrees to be safe with enough time to comfortably capture the LOC. It's a bug in the default FSX auto pilot systems by the way.

Intercepting the localizer at a 90 degree angle, or even at a 70 degree angle is not normal in real life. It would be completely unreasonable and just poor technique by ATC to vector you to intercept at such an angle.

Perhaps a look over on the ProATC/X forums might help with importing flight plans :rolleyes:

 

http://www.pointsoftware.de/forum/viewtopic.php?f=2&t=4054&sid=8b6aea9e5ef63d1c70b91235e1f32ca2

My throttles will not move. I use FSUIPC for throttle cotrol.

Arrrrrrgh. I am now going to refer to this add-on as the Airbus X Exploded.

:lol: Not laughing about the actual error, but the description.

 

More seriously, it's sad to (still) read about the dreaded CTD stuff. I saw your initial posts, Bob. The ones with the 1.0 version and the hotfix. Then I was thinking that the later 1.02 new version (installer change) plus the 1.02C fix would rule out the CTD stuff. Well, so much for the hopes. :blush:

 

But it doesn't affect all users, right?