BAe 146 Professional P3D v5 FMS/AP Issues
-
@Mikealpha said in BAe 146 Professional P3D v5 FMS/AP Issues:
I think the plane deserves a custom ILS routine. Currently there is no other choice than to fly the ILS manually.
I'd vote for that too... And would be nice to see the first attempt of some fixes for the FMC, the DTO Bug really spoils online flying
@ConcordeAG agreed the DTO is the main fix the fmc needs, sids and stars have easy work around such as request vectors but when getting a dto and you start going off course, atc are quick to pull you up on it.
-
I have noticed these two issues :
- FMC: select SID/STAR - I can't select all of the listed SIDs or STARs. E.g. I can only choose 1 and 2 , even though 4 are displayed. 3 and 4 are not selectable (e.g. at EGNX). If 7 or 8 SIDs or STARs are displayed, only the first 4 are selectable.
- already mentioned further above : LNAV overshoots waypoints too much, struggles to come back on track.
@Mikealpha I have the same issue...
-
Very odd but will keep trying to reproduce this. For us it correctly intercepts the ILS (both glideslope and localiser) and doesn't turn away, presumably intercepting the reciprocal. Just to confirm, do you get the same issue if intercepting the ILS 22 at KEDW (Edwards)?
FYI it does have custom rather than default ILS logic.
-
Very odd but will keep trying to reproduce this. For us it correctly intercepts the ILS (both glideslope and localiser) and doesn't turn away, presumably intercepting the reciprocal. Just to confirm, do you get the same issue if intercepting the ILS 22 at KEDW (Edwards)?
FYI it does have custom rather than default ILS logic.
@Martyn said in BAe 146 Professional P3D v5 FMS/AP Issues:
Very odd but will keep trying to reproduce this. For us it correctly intercepts the ILS (both glideslope and localiser) and doesn't turn away, presumably intercepting the reciprocal. Just to confirm, do you get the same issue if intercepting the ILS 22 at KEDW (Edwards)?
FYI it does have custom rather than default ILS logic.
That's odd indeed. I just tried KEDW and indeed V/L works, but GSL doesn't.
Not sure if you noticed my screenshot further above, so I might repeat it here. Can you spot anything wrong there ? Airplane just overflies LOC without any attempt to turn. That's EDNY Rwy06
Could be a problem with Addon Sceneries ? Did you try it with Addon airports on your end ?
-
Very odd but will keep trying to reproduce this. For us it correctly intercepts the ILS (both glideslope and localiser) and doesn't turn away, presumably intercepting the reciprocal. Just to confirm, do you get the same issue if intercepting the ILS 22 at KEDW (Edwards)?
FYI it does have custom rather than default ILS logic.
-
@Martyn said in BAe 146 Professional P3D v5 FMS/AP Issues:
Very odd but will keep trying to reproduce this. For us it correctly intercepts the ILS (both glideslope and localiser) and doesn't turn away, presumably intercepting the reciprocal. Just to confirm, do you get the same issue if intercepting the ILS 22 at KEDW (Edwards)?
FYI it does have custom rather than default ILS logic.
That's odd indeed. I just tried KEDW and indeed V/L works, but GSL doesn't.
Not sure if you noticed my screenshot further above, so I might repeat it here. Can you spot anything wrong there ? Airplane just overflies LOC without any attempt to turn. That's EDNY Rwy06
Could be a problem with Addon Sceneries ? Did you try it with Addon airports on your end ?
@Mikealpha We typically use default scenery during testing in case the add-on scenery has any issues. Can you confirm what scenery you are using for EDNY? I've just tested it here using default scenery and it correctly intercepts the localiser/glideslope for 06 when approaching from the left or right:
-
@Martyn I have it everytime I try to land on runway 28l at Dublin when intercepting from the south. 278 course 111.35 frequency.
@alanbyrne94 Can you confirm if you are using default or add-on scenery? Does it make any difference whether you intercept the localiser or glideslope first? Here's a pic of it behaving as I'd expect when intercepting EIDW 28 from the south:
-
@Mikealpha We typically use default scenery during testing in case the add-on scenery has any issues. Can you confirm what scenery you are using for EDNY? I've just tested it here using default scenery and it correctly intercepts the localiser/glideslope for 06 when approaching from the left or right:
@Martyn said in BAe 146 Professional P3D v5 FMS/AP Issues:
@Mikealpha We typically use default scenery during testing in case the add-on scenery has any issues. Can you confirm what scenery you are using for EDNY? I've just tested it here using default scenery and it correctly intercepts the localiser/glideslope for 06 when approaching from the left or right:
Yes, I can indeed confirm that. I uninstalled the Aerosoft EDNY Addon scenery and it works with standard scenery. Installed Addon scenery again and it does not work , so it is reproducible.
As I have around 200 Addon Airports, it didn't work on any I used so far, so that also confirms it.
And your KEDW example with standard scenery again works.So, do Addon sceneries generally define the ILS different than P3D standard scenery ?
Mike
-
@alanbyrne94 Can you confirm if you are using default or add-on scenery? Does it make any difference whether you intercept the localiser or glideslope first? Here's a pic of it behaving as I'd expect when intercepting EIDW 28 from the south:
@Martyn my dublin is payware as is all the airports I use.
-
@Martyn my dublin is payware as is all the airports I use.
@alanbyrne94 said in BAe 146 Professional P3D v5 FMS/AP Issues:
@Martyn my dublin is payware as is all the airports I use.
I just checked, I can confirm EIDW RWY28 does not work, with MK Studios Dublin installed.
Standard scenery works.Mike
-
I've tested this with Aerosoft's EDNY scenery in P3D v4.5 and v5.1 but both continue to work fine for me:
We'll continue testing with other scenery but in the meantime we'll need to send you a test gauge via the support team to see if that helps track down the cause.
-
Version 1.4 and a DLL file from jf support has done the trick, fms now has a click spot to power up and a working pop up. Thanks jf team for ironing out this little problem
