BAe 146 Professional P3D v5 FMS/AP Issues
-
I don't want to be too quick in my opinion of the last update. But what I noticed is that with at TO weight well below limits en the aircraft well trimmed and configured, taking off was impossible this time. The aircraft stuck to the runway till there was no runway left. What I noticed as well, but only in a glance, so correct me if wrong, it seems the heading selector is again connected to the Course on the HSI. At least this time I could talk to the ATC while crashing.
-
@Elientje This information is a little bit vague to determine an issue with takeoff performance. Do you have the following details?
-Aircraft TOW
-N1% Ref used
-V-speeds used
-Flap setting
-Runway length
-Runway elevation
-Temperature
-Wind component
-Pressure setting
-Anti Ice On/Off**It's impossible to make an analysis on the take off performance without the above as a minimum.
Regards,
JL
@Jumbolino No, I didn't gather this information. I will try this take-off again and see how the aircraft performs. When the same happens, I will give the requested information.
-
Can we maybe split the topic? Performance etc. isn't really related to FMS/AP issues
-
Those that have been having issues with the FMC, could they please confirm by way of reply to this message if they were asked for the account details originally when installing v1.00?
@Craig yes I was asked the first time, but after uninstalling and reinstalling the new updates I was t
-
Those that have been having issues with the FMC, could they please confirm by way of reply to this message if they were asked for the account details originally when installing v1.00?
@Craig said in BAe 146 Professional P3D v5 FMS/AP Issues:
could they please confirm by way of reply to this message
Yes, I was asked to login - Like with other justflight installers.
-
Those that have been having issues with the FMC, could they please confirm by way of reply to this message if they were asked for the account details originally when installing v1.00?
-
The v1.3 update is now available - https://support.justflight.com/en/support/solutions/articles/17000111833-146-professional-changelog
appreciate the hard work you guys are putting in.
1.03 clean install.
Issues I have had:
1.FO ASI needles not moving.
2. Temp readout flickering between 9-10
3. FMS still cannot select a SID beyond selection 4
4. Landing gear does not retract at all after take off, Red light stays on when selecting landing gear up. Was working previously
5. FMS: selecting a STAR via menu page on the FMS it does not show any of the waypoints on the FPL page
6. FMS cannot delete arrival airport? is this correct to the system and you have to delete the whole entire flight plan?
7. FMS cannot delete a waypoint until Arrival airport is entered.
8. Not sure this is coded or not but VNAV ascending and descending on the AP doesn't work consistently. If I go to V/S mode and then back to VNAV, it will not function. Never got it to work for descent yet.Happy to provide screenshots if needed.
-
1.This is already fixed for v1.4 (manual fix info here - https://community.justflight.com/topic/1368/a-couple-of-snagettes/2)
4. I can't see any changes that'd cause that and it is working correctly here so hopefully just a temporary glitch somewhere
8. VNAV isn't functional on the 146 so please ignore that modeLooking into the others.
-
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 -
1.This is already fixed for v1.4 (manual fix info here - https://community.justflight.com/topic/1368/a-couple-of-snagettes/2)
4. I can't see any changes that'd cause that and it is working correctly here so hopefully just a temporary glitch somewhere
8. VNAV isn't functional on the 146 so please ignore that modeLooking into the others.
@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.
-
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@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
-
that looks better yes - Might be a relation to the intercepting/track issue of the LLC
