Some observations and suspected bugs
-
In regards to state saving with this aircraft, if it is enabled and i end the game with the chalks in place and the auxilary GPU running, will it be on the next time load into the aircraft, if i for example exit the flight in a "turnaround" state with the GPU attached and on?
-
@Sergekoko It seems like the state saving (which I have enabled) remembers everything except that the EXT AC switch was set to OFF, thus when I start MSFS again, the EXT AC switch is in the middle position instead of the OFF position and the aircraft thus has power.
-
On my last flight the GS did not capture even though I engaged APP mode coming in below it. I had to turn AP off and on again and engage APP mode with it within one dot for it to work. I engaged LOC mode first and then APP mode when the purple rectangle appeared. Should I wait until it's less than one dot away before doing that?
-
@OwlInFlight Did you get a green LOC mode on the PFD before you armed APP and when you armed APP, did you get a white GS mode?
-
I've also had problems with VORLOC.
If I'm in LNAV mode and arm VORLOC, the aircraft won't capture the localizer, however, if I'm in HDG mode and arm VORLOC, it will capture the localizer.
In addition, it seems to struggle with large intercept angles as it will overshoot quite a bit if I come in at an intercept angle of 90 degrees.I've already sent in a ticket with all my findings but I sent in a ticket regarding the 146 over 1 month ago and still haven't gotten a reply in that ticket so I'm writing here too to cover all bases.
-
@smashingjonor Thank you for the detailed feedback. I'll leave some comments below in response to the points you raise:
- Brake fans are simulated. I have just tested this in the simulator by moving the BRK FANS switch to ON (or AUTO) and the brake fans can be heard on the exterior of the aircraft.
- The brake cooling varies depending on the brake fans selection. We have based the cooling times on feedback from RJ pilots on our testing team.
- We have logged a bug on our internal tracker where exiting a flight with the GPU connected causes the EXT AC switch to connect external power at the start of the next session.
- We have logged a bug regarding the EXT AC PWR AVAILABLE annunciator extinguishing when the batteries are powered off.
- We have logged a bug regarding the MWS chime when disconnecting EXT AC with the batteries switched OFF.
-ENG VIB - As far as I'm aware, the autopilot uses whatever altitude is indicated by the main altimeter. So in order for the same altitude to be displayed across all altimeters (and Vars) all altimeters must be set to the same barometric pressure.
- The ground service logic is correctly simulated, however, we have just found a bug with the GND SERVICE switch in the galley that is preventing that from functioning as intended. Thank you for spotting that!
- The ENTRY/FWD GALLEY light logic has been adapted to work around some limitations within the simulator. The ENTRY/FWD GALLEY switches will only correctly control the respective lights when the cockpit door is open. When the cockpit door is closed, the forward galley lights are forced off to prevent the cabin lighting from bleeding through the cockpit door. The ENTRY light switch has also been simulated as a two-position switch as a spring-loaded switch wouldn't be user-friendly in a simulator (similarly to what we have done with the DC PUMP switch).
- The current EGPWS voice is used as that is what we have the reference material for. We do have the alternate set of EGPWS callouts logged on our internal feature request tracker as something to look into further.
- The logic we are currently using for the cabin calls is that the current call must be cancelled before a new call can be made. Therefore, only one double-chime can be heard. The FCOM isn't too specific on this point, so we'll make a note of this and ask for clarifications from the RJ pilots on our testing team.
Thanks again for the feedback.
Mark - Just Flight
-
@smashingjonor I have just tested capturing a localiser with VORLOC mode armed after LNAV and the localiser has been captured as intended. Difficult one for us to comment on further though withour a video/screenshots of what was occurring in the simulator at that time.
The general localiser capture is an area we have identified as something we would like to improve in the future. However, I seem to recall the FCOM also recommends against capturing localisers from such large angles.
With regard to the support ticket, that is definitely not what we are expecting to hear, so we apologise that it has taken that long. Would you be so kind as to provide us with your ticket number so that we can investigate that, please?
Mark - Just Flight
-
Mark also in the RJ when the external power is connected to the bus bars, EXT AC PWR AVAILABLE remains illuminated - I don't think this happens in the 146 and am not wholly sure it's correct. Can you investigate?
-
@Mark The ticket number is #82222. You will find that most of the items in that ticket were the same as in this thread but for the 146 instead. Some of the items have been fixed in the RJ.
-
@rondon9897 That should be correctly simulated in the RJ. The FCOM is fairly sparse on the exact logic, but from what we can gather the EXT AC PWR AVAILABLE annunciator will illuminate whenever external power is acceptable. The change will be carried across to the 146 in a future update.
Mark - Just Flight
-
@smashingjonor Thank you. I have passed this onto our support team to investigate.
Mark - Just Flight
