BAe 146 Professional P3D v5 FMS/AP Issues
-
My issues on a clean 1.03:
- I could only select the first two SIDs from EPLB on either runway (07 or 25)
- A couple of times I was able to entirely lock-up the FMC whilst trying to edit the flight plan, causing it to go blank. Weirdly trying to turn it off fixes that?
- I can't select any RNAV STARs, examples are LHBP or EPWA
-
For me, the LOC/GS capture is still totally messed up and not usable in IMC conditions. Had to use the hdg bug and manually go down. Since the F/D also wants to turn away from the LOC, it wasn't usable either.
For some funny reason, the arrow on the HSI is pointing into the opposite directon, as per my understanding, this should point towards the VOR/LLZ.
http://prntscr.com/vudqb7 -
@Martyn said in BAe 146 Professional P3D v5 FMS/AP Issues:
- VNAV isn't functional on the 146 so please ignore that mode
Just in addition:
- ILS LOC capture does not stay on track once established, veers off.
- G/S not consistent degree path, always adjusting, maybe due to LOC issue, but more stable than the LOC.
- Trim needs to go beyond green band for take off. If left in the green band and departing, if I let go of the yoke it nose dives 100ft after departure, needs a fair bit of trim to get it set properly.
-
@ConcordeAG The HSI is fitted with a TO and FROM arrow. Here is a pic that I've just taken when flying to a VOR.
The course flag (white/red) is shown in your pic which indicates that the HSI doesn't have a valid VOR signal. I will double-check what the behaviour should be in the case of a localiser.
-
that looks better yes - Might be a relation to the intercepting/track issue of the LLC
-
@ConcordeAG Yes, I've now changed the behaviour of both the TO/FROM indicator and course flag when a localiser is tuned.
-
@ConcordeAG said in BAe 146 Professional P3D v5 FMS/AP Issues:
For me, the LOC/GS capture is still totally messed up and not usable in IMC conditions. Had to use the hdg bug and manually go down. Since the F/D also wants to turn away from the LOC, it wasn't usable either.
I'm still unable to reproduce that here. The AP/FD always intercept and then track the localiser/glideslope and never turn away from the localiser. Can you get in touch with the support team about that one so we can investigate further and try to reproduce then fix it?
-
@Martyn here the screenshots i just attached to the ticket - The small yellow diamond which stays at 000 - that's what it tries to intercept.
for VOR it works, not so much on the ILS.
Just tried to hookup NAV 2 - with that it works a bit, not as it should, but it intercepts and follows the general direction... Not with NAV 1
Intercept:
Turns away:
Chases the diamond:
-
LFSB, ILS15
-
@ConcordeAG said in BAe 146 Professional P3D v5 FMS/AP Issues:
LFSB
Are you using addon scenery such as JUSTSIM - EUROAIRPORT BASEL MULHOUSE FREIBURG?
-
FSDT in my case - but i have the same everywhere else too :)
So far:
- ORBX EGNX
- ORBX EGNT
- ORBX EGHI
- Aerosoft EDDK
- Gaya LOWW
- Digital Design EDDP
- FSDT LFSB
- ....
Basically everywhere the same.
-
Re the FMS issue I’ve managed to remove all trace of the aircraft form my computer via a registry edit, clean install of 1.3 with new activation...still no power or click spots on the FMS 😭 how do I get a refund?
-
-
Main problems I have so far are (some are the same as above)
The DTO doesn't go direct, this is a big problem especially when flying online.
The LOC capture always overshoots.
No STAR's for certain airports ( Hope this will be resolved with the new AIRAC).
SID selection problem (only first 2 selectable).
Weights are only in LBS. It's a British built plane, I expected it to be KG's.
The Clock face is incorrect ( goes from 22 to 22 instead of 22 to 23 ).
IAS doesn't hold the speed for the climb.
FO IAS does not function.
I am getting some weird coloured lights on the cockpit window at night (might be a p3dv5 problem).
FMC Pref page does not read the GS when flying so I get no ETA.
Trim on the aircraft doesn't work correctly at the moment. -
same issues reported by a few more, including myself. Aerosofts CRJ suffers from the same issue, it appears if you use default P3D code to capture the G/S LOC it can be unreliable. I believe the CRJ is getting a custom coded ILS system to overcome this.
