nigelgrant

Thx iniBuild for including the autopilot panel in the update, I had developed a work-around but having its own direct access panel is much more convenient Nigel

Hi BobCat Thx for all this, I was not aware of the Alt-1 series but will try and follow through on that. I have the Velocity One yoke and have all the control -1 series assigned to the 10 keys on the throttle quadrant which is pretty convenient, although I much prefer the piloting properties of P3D and FSX; it is hard sometimes trying to click a button in 2020 with the mouse (particularly as I am pushing 89!). So trying to get the autopilot panel into a view sounds a neat little challenge for me. Thx for the help. Nigel

Jeeze, that's enough to turn me off the aircraft! Autopilot is one of the main control panels and how even the real version has it hidden away seems very strange. MSFS 2020 is already quite difficult to fly without having to manipulate a view of the autopilot panel. Thanks for all this info, I will keep alert for updates which might fix it regards Nigel

How do you pull up the autopilot panel? The manual says it is under the trim lever. I see part of it but cannot get at any of its functions. We had one of these aircraft at BC Hydro back in the 70's - hard for the North American human frame to sit in it - built for short people! when it was flying it reminded me of a bug! Nigel Vancouver

Having created some flight plans in LittleNavMap, incorporating SID’s and STAR’s/Approaches, I have often been experiencing errors of “Not in Data Base” when entering the flight plan components into the FMS of the Just Flight BAE146 for MSFS 2020. These error messages all seem to be waypoints on the LNM map, within the SIDS or STARS or Approaches. Presumably these waypoints came directly from the MSFS database when building the scenery library? Also presumably, the JF BAE146 must be loading its data from the same MSFS database? Or another database? An example of this is waypoint I13RZ on the approach to 13L of LFML. I am posting this at both the LittleNavMap forum and JF146 forum in the hope that someone can advise me how to rectify this situation. Nigel Vancouver

Hi Alex Thx for your reply but sorry for the delay in acknowledging, but I have been away from the simulator and will be for the next few days. I presume you are referring to the disconnect I experienced, I will have to re-create the flight plan and try again and will report back. However I would like to determine why I have so much trouble trying to load a new CYOW flight plan into the FMS of the 146 but have yet to hear from anyone at Just Flight. regards Nigel

I am having a lot of difficulty achieving success with importing a flyable flight plan for CYOW_CYUL into the FMS of the JF BAE 146. Initially I tried using SimBrief but found it confusing. I tried an MSFS flight plan created with LittleNavMap (I find that a lot more intuitive and illustrative of what I am trying to create than SimBrief) from CYOW25gate28 to CYUL24R. I loaded this into the FMS and succeeded in deleting the discontinuities and the flight plan looked okay to CYUL. I managed to get airborne and connected to the flight plan through LNAV but before I reached Montreal there was a disconnect by the aircraft (at a “manual” waypoint, which had been apparent in the LNV plan, but did not show up in the FMS legs. So, I deleted that flight plan and created a new one CYOW32gate 28 to CYUL6L. But when I loaded it into the FMS it loaded the original CYOW25R plan, not withstanding I had deleted this original plan from both the LNM directory and from the LocalState folder in MSFS 2020. I cannot load the new flight plan into the FMS I am posting this both at Just Flight and LittleNavMap and would appreciate some assistance to resolve this issue - please. Regards Nigel Vancouver

Bert - ditto Nigel Vancouver

Reaper Go check out the AIG forum, lots of entries on this; I finally resolved the move problem, I found I could do a click and drag of the "aig-aitraffic-oci-beta" folder from the Community folder to the folder of my choice. Everything seemed to work out after that. Nigel Vancouver

bump............................................

I likewise have long bemoaned that Microsoft 2020 did not include the full screen cockpit view with mini-panel. It helped land the aircraft and was also great for scenery viewing. This message string and the other recent one in the AVSIM Tips and Tricks Forum brought me great hope but alas only frustration at the moment because I cannot even get to square one and save a camera.cfg file. I follow all the instruction to no avail and I think there must be something I am missing. I have never used the camera functions before and suspect there may be some fundamental on/off command I am missing. I have little to offer in the way of info – I get my cockpit view open on the ground and expand to the forward-most position then try ctr-alt -5 (or other numbers) with numlock on and off – no folder or camera.cfg created in the Airplanes folder (There already is one folder Asobo_C172sp_classic, with a camera.cfg file, presumably created as a default at some time). Any suggestions? Nigel Vancouver

Alex, thx for your prompt and informative reply - I have de-activated NaviGraph settings as you recommend, I hope the link works to my VFR flghtplan. regards, Nigel https://we.tl/t-FvhvDJ64wL

I am having problems sometimes being able to consistently load LNM flight plans into MSFS2020. IFR – Not necessarily a question but just an observation - I prepare the flight plan in LNM and save it, then save it to MSFS2020. I load this flightplan in MSFS into a TBM and it shows in the MDF window. I can then continue the flight successfully on autopilot. However if I modify this flight plan and save to MSFS2020, overwriting my previous flight plan, it will not show in the MDF panel of the TBM. But…. if I delete the flight plan in MSFS2020, then resave the LNM flight plan into MSFS2020 then it shows as noted above. Strange? VFR – Some questions – I prepare the VFR flight plan in LNM and save it, then save it to MSFS2020. I load this VFR flightplan in MSFS into a TBM but it does not show in the MDF window. Why? Curious - if you are flyingVFR, why would you want to create an electronic flightplan? And am I correct that the waypoints I create in LNM are electronic coordinated locations in space that the autopilot will follow on the NAV setting? Nigel Vancouver

Hi Bert Pleased to see you are getting a response from the author, I agree with your observations. I have found the large version of Vancouver is incompatible with the BC and VI meshes at flightsim.to - MSFS2020 crashes when it gets to the flight selection page. But if I replace the full version of Vancouver with the author's lite version, this start-up crash does not happen and Vancouver looks darn good (the scenery is quite incredible), just as good as the heavy version without doing a detailed analysis. Have you had this experience? I really want the two meshes installed since they add more detail to the mountains. Nigel Vancouver

Roman Superb scenery, thank you very much Nigel Vancouver