Steve4256

I just got this bug too the other day. EHSI stays on self-test mode. Seems to only occur at certain airports. Also when I removed the destination airport from the flight plan (in the world map), the EHSI worked. Don't know what's going on. If anyone figures out what's going on, please post it here.

Hello, Thanks AVSIM for so many great forums. I haven't been able to find info on what the process is to create a new User to User Support forum for a product. Can you advise? Also, where is the best place to post about a free demo that announces a new product? For a MSFS 2020 product, can that be done within the main MSFS forum? Thanks again.

Hi Alex, If possible, would be great if the "Load Scenery Library" could also do an incremental update if say one airport addon has been added to the sim and you could direct the database update to that one airport folder to add the custom airport to the database without having to wait for a whole database update. Thanks, Steve

Thanks. I'm aware the altitude can be manually changed. When I'm looking at different flight options I do quick dept / dest route descriptions for a number of options and each time I have to manually change the altitude back to the same altitude to get the correct flight info I'm after.

Hi Alex, Would it be possible to add a setting where you can specify a default altitude used when creating a flight plan from the route description? Seems the current default is 10,000ft or 11,000ft depending on east/west direction (IFR). Thanks! Steve

Can anyone help with how to import the below list of airports as Userpoints? https://forum.aerosoft.com/index.php?/topic/165562-what-airports-are-covered/ I've tried the Import CSV with a CSV file of just the airport codes but get an error about needing Longitude. Thanks

Tried the LNM new version and the CRJ flight plan export worked well. 👍

I loaded your flight plan above and it all worked. Dep, dep rwy, dest, SID, STAR, waypoints and cruise level. Nice one! I'll test the new LNM version soon.

And now just manually entered the flight plan in the CRJ FMC and saved it. And it saved the legs as follows fltno= dctwpt1=WEONE dctwpt1coordinates=33.525690,-85.122250 airway2=J239 airway2from=WEONE airway2to=JAMMR dctwpt3=OKW dctwpt3coordinates=33.237860,-87.249870 dctwpt4=NENRE dctwpt4coordinates=31.670860,-87.760870 dctwpt5=GCV dctwpt5coordinates=31.097960,-88.486130

I tried the Simbrief export with the same flight plan and it worked and looks like it's due to it not using airways and just using the waypoints. Even though the airway was in the flight plan description. FltNo= DctWpt1=WEONE DctWpt1Coordinates=33.525689,-85.122247 DctWpt2=JAMMR DctWpt2Coordinates=33.232136,-86.942319 DctWpt3=OKW DctWpt3Coordinates=33.237886,-87.249867 DctWpt4=NENRE DctWpt4Coordinates=31.670856,-87.760867 DctWpt5=GCV DctWpt5Coordinates=31.097961,-88.486128

Thanks for the beta version. Tried a few flight plans and they imported correctly in terms of dept, arrival and cruise level but some plans imported leg waypoints correctly and some didn't. Also tested with the current LNM released version and was the same. Seemed to be that some intersection waypoints didn't import. But others in the same flight plan did. Only a guess, but might be something to do with airways. For example, the below flight plan correctly imported the OKW, NENRE and GCV waypoints but didn't import WEONE and JAMMR FltNo= Airway1=J239 Airway1FROM=WEONE Airway1TO=JAMMR DctWpt2=OKW DctWpt2Coordinates=33.237885,-87.249870 DctWpt3=NENRE DctWpt3Coordinates=31.670856,-87.760864 DctWpt4=GCV DctWpt4Coordinates=31.097961,-88.486130 Can anyone else give any further feedback?

Yeah I didn't export any procedures. I believe those are meant to be entered manually in the aircraft. No worries

I just came back to the CRJ to do another flight (patch update 2 just released), and the new LNM multi-export function for the MFS CRJ exported a flight plan that imported correctly into the aircraft MCDU in terms of departure, destination, legs and cruise level. Those are the main flight plan details that I'm after, so that is great. Thanks! FYI - I did notice that the flight plan file had transition altitude & level of 18000 when the flight was in Australia which has transition alt 10000 and transition level FL110. And then after import the aircraft transition altitude (climb) in the MCDU was 0 and the transition level (descent) was FL110. Don't know whether the MCDU is supposed to import the flight plan transition alt/lvl or not.

Thanks for the file although it didn't work. FMS says "Load Error" and nothing loads. No departure, destination, cruise level, legs etc.

Yeah another export option would be great. Might be required anyway to get the Legs info to be displayed. Plus the FMS main Flightplan page only shows an 8 character filename for the Route entry.