Recommended Posts

Little Navmap 1.4.1.beta released

All Information about the release can be found in my Release Announcement.

Release 1.4.0.beta
Release Announcement on Github Pages

Release Page on Github

Direct download link Windows

Direct download link macOS

Online Manual (this links directly to the manual of 1.4 while the front page still shows 1.2 until the final release is out)

Little Navconnect is now bundled together with the Little Navmap download.

When starting version 1.4 the first time after using version 1.2:
* The scenery database has to be reloaded due to a schema change.
* Aircraft tracks are ignored and not loaded because the format has changed.
* The program will start with a default window layout due to changes in the configuration.

Short Changelog:
* Procedures, Approaches, Transitions, SIDs and STARs
* Airspaces
* TACAN and VORTAC navaids
* Offline GLOBE Elevation data - no known elevation errors and faster update. See here in the manual for installation instructions.
* New flight plan export formats: GPX (including flown track), PMDG RTE, Aerosoft Airbus FLP and X-Plane FMS.
* Ship traffic added
* Output in route string dialog can be customized.
* Little Navconnect is now packed together with Little Navmap
* Map colors and the colors for two GUI themes can now be customized in configuration files.
* Uncountable bug fixes and smaller improvements.

Note: TACAN, VORTAC, SIDs and STARs are only available with fsAerodata or another navdata update.
But you can still use the included approaches and transitions with a plain FSX or P3D database.

The long detailed changelog is here:
1.2.4 to 1.4.0 Changelog
 

Happy flying,

Alex

Edited by albar965
Added release 1.4.1.beta
  • Upvote 3

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

33 minutes ago, albar965 said:

Note: TACAN, VORTAC, SIDs and STARs are only available with fsAerodata or another navdata update.

I just noticed that the listing for all the SIDs and STARs appears to be missing the 5th character in the new beta 1.4. For example, the KSTL SID NATCA3 is  listed as NATA3. This is with fsaerodata installed.

Share this post


Link to post
Share on other sites
22 minutes ago, jabloomf1230 said:

I just noticed that the listing for all the SIDs and STARs appears to be missing the 5th character in the new beta 1.4. For example, the KSTL SID NATCA3 is  listed as NATA3. This is with fsaerodata installed.

Jay, sorry, that is a limitation of the BGL format. No more than five characters for waypoint names so they have to squeeze it.

See here. We're talking about the fixIdent.

Alex

Share this post


Link to post
Share on other sites

Great achievement, Alex! Congratulations!!! Been waiting for the new release... :)

Is it already possible to integrate LN with Navdata database? It will be cool to update the airways as well... Just asking, no problem if not...

Share this post


Link to post
Share on other sites

Hi Victor,

thank you. If you mean Navigraph or Aerosoft NavDataPro: No, that is in the works and my influence is limited there, but fsAerodata also updates the airways.

Alex

  • Upvote 1

Share this post


Link to post
Share on other sites

 

Hi, thank's for your work.

I sorry after saw the new release I jump and download and as you can see there is still a problem with the terrain wich is not like that after takeoff.

this is the flight plan

<?xml version="1.0" encoding="UTF-8"?>

<SimBase.Document Type="AceXML" version="3,2">
    <Descr>AceXML Document</Descr>
    <FlightPlan.FlightPlan>
        <Title>VFR Aeritalia to Sestri</Title>
        <FPType>VFR</FPType>
        <CruisingAlt>4500</CruisingAlt>
        <DepartureID>LIMA</DepartureID>
        <DepartureLLA>N45° 5' 9.43",E7° 36' 13.54",+000946.00</DepartureLLA>
        <DestinationID>LIMJ</DestinationID>
        <DestinationLLA>N44° 24' 48.57",E8° 50' 15.23",+000013.00</DestinationLLA>
        <DeparturePosition>28R</DeparturePosition>
        <DepartureName>Aeritalia</DepartureName>
        <DestinationName>Sestri</DestinationName>
        <AppVersion>
            <AppVersionMajor>10</AppVersionMajor>
            <AppVersionBuild>3</AppVersionBuild>
        </AppVersion>
        <ATCWaypoint id="LIMA">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>N45° 5' 9.43",E7° 36' 13.54",+000946.00</WorldPosition>
            <ICAO>
                <ICAOIdent>LIMA</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="MASW">
            <ATCWaypointType>VOR</ATCWaypointType>
            <WorldPosition>N45° 4' 12.00",E7° 31' 48.00",+000003.28</WorldPosition>
            <ICAO>
                <ICAORegion>LI</ICAORegion>
                <ICAOIdent>MASW</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="MAS1">
            <ATCWaypointType>VOR</ATCWaypointType>
            <WorldPosition>N45° 0' 0.00",E7° 31' 48.00",+000003.28</WorldPosition>
            <ICAO>
                <ICAORegion>LI</ICAORegion>
                <ICAOIdent>MAS1</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="MFSW4">
            <ATCWaypointType>VOR</ATCWaypointType>
            <WorldPosition>N44° 56' 24.00",E7° 33' 0.00",+000003.28</WorldPosition>
            <ICAO>
                <ICAORegion>LI</ICAORegion>
                <ICAOIdent>MFSW4</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="MZE1">
            <ATCWaypointType>VOR</ATCWaypointType>
            <WorldPosition>N44° 32' 24.00",E7° 42' 0.00",+000003.28</WorldPosition>
            <ICAO>
                <ICAORegion>LI</ICAORegion>
                <ICAOIdent>MZE1</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="MZSW1">
            <ATCWaypointType>VOR</ATCWaypointType>
            <WorldPosition>N44° 24' 36.00",E7° 35' 24.00",+000003.28</WorldPosition>
            <ICAO>
                <ICAORegion>LI</ICAORegion>
                <ICAOIdent>MZSW1</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="MZSE1">
            <ATCWaypointType>VOR</ATCWaypointType>
            <WorldPosition>N44° 23' 23.99",E7° 49' 48.00",+000003.28</WorldPosition>
            <ICAO>
                <ICAORegion>LI</ICAORegion>
                <ICAOIdent>MZSE1</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="MMSW1">
            <ATCWaypointType>VOR</ATCWaypointType>
            <WorldPosition>N44° 23' 23.99",E8° 2' 24.00",+000003.28</WorldPosition>
            <ICAO>
                <ICAORegion>LI</ICAORegion>
                <ICAOIdent>MMSW1</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="MJW2">
            <ATCWaypointType>VOR</ATCWaypointType>
            <WorldPosition>N44° 18' 36.00",E8° 28' 48.00",+000003.28</WorldPosition>
            <ICAO>
                <ICAORegion>LI</ICAORegion>
                <ICAOIdent>MJW2</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="MJW1">
            <ATCWaypointType>VOR</ATCWaypointType>
            <WorldPosition>N44° 23' 23.99",E8° 39' 0.00",+000003.28</WorldPosition>
            <ICAO>
                <ICAORegion>LI</ICAORegion>
                <ICAOIdent>MJW1</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="LIMJ">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>N44° 24' 48.54",E8° 50' 15.23",+000013.00</WorldPosition>
            <ICAO>
                <ICAOIdent>LIMJ</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
    </FlightPlan.FlightPlan>
</SimBase.Document>

 

Share this post


Link to post
Share on other sites
1 hour ago, albar965 said:

Jay, sorry, that is a limitation of the BGL format. No more than five characters for waypoint names so they have to squeeze it.

See here. We're talking about the fixIdent.

Alex

I never noticed that before, probably because today I just happened to look at KSTL with the Flight1 GTN 750. My apologies.

Share this post


Link to post
Share on other sites
12 minutes ago, jabloomf1230 said:

I never noticed that before, probably because today I just happened to look at KSTL with the Flight1 GTN 750. My apologies.

No problem. These BGL limitations are annoying at times.

18 minutes ago, simbio said:

I sorry after saw the new release I jump and download and as you can see there is still a problem with the terrain wich is not like that after takeoff.

Fabrizio,

I see no errors when using the offline data here. It is not fixed automatically. You have to download and extract the data. See here in the manual. 

Alex

  • Upvote 1

Share this post


Link to post
Share on other sites
1 hour ago, albar965 said:

Fabrizio,

I see no errors when using the offline data here. It is not fixed automatically. You have to download and extract the data. See here in the manual. 

Alex

 

Got it all fine now.

Thank's

Share this post


Link to post
Share on other sites

Hi Alex,

Just starting to explore this new release - but initial impressions are - WOW - what a superb and professional effort...

Thanks for all the hard work and dedication...

Regards,

Scott 

Share this post


Link to post
Share on other sites

Hello Alex:

Fantastic is the only way to describe your new version and your contribution to Flight Simming!  Thank you,

Mike H.

Share this post


Link to post
Share on other sites

Hi Scott and Mike,

thank you!

Scott: Did you notice the new drop down menu in the route description dialog?:smile:

Alex

Share this post


Link to post
Share on other sites

Hi Alex,

Umm - Nooo - but now I'm intrigued - I will and I'll add another thank you in advance... I won't be home until the weekend - will check it then...

:wink:

Regards,

Scott

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now