Dbarnea

https://ibb.co/kGXkc0c So I'll try to explain the picture. OSN is the second waypoint in the flight plan. can be seen in the Map and in the Flight planning grid. Plane is on its way to it according to the map. But according to the Elevation profile it is flying from the last end point to the first one. This is also what the grid shows. The purple line highlighted is the last waypoint. And I have a pretty good idea why it happened. I have messed the order of the points. So I created a plan, wasn't happy with it and moved the order of the point around. So the Flight planning grid is exactly like I wanted it to be (in terms of order). But somehow the tracking process didn't "catch that". Maybe the fact that the same airport is the source and destination contributes to that as well. At some point , the plane in the Elevation profile "turned around" and did follow the revised plan. Doron.

Very interesting. You're sayin, if you're not using your 60MHz screen for games, why load it on the Nvidia card ? Man, never thought about that. I will definitely try that and see what happens 🙂

My 5 cents here. I run 2 screens via my 1 NVIdia 1080. What you're describing happens to me all the time. I click on anything on my non simulator screen , it doesn't effect my simulator, but, when I get back to the simulator screen, it stutters for several seconds then calms down. Searched about it in the internet, found discussions about the fact that the 2 screens are different resolution and also the fact that one is G-SYNC 144 Mhz and the other is not G-SYNC and is 60 MHz. I don't know if that's what happens on my side (although the resolution difference and the frequency difference are indeed true). I didn't try to lower my 2K screen to by 1080p and 60 MHz in order to test that, maybe I will 🙂 Or, buy another 2K G-Sync 144MHz screen and check that as well. Anyway, I don't think it involves NVM at all. Weird your setup is like that for a long time and you never encountered it before.

Sounds perfect Alex, thank you 🙂

Hi Alex, I'm trying to insert new user points and get unique constraint exception. looks like for some reason it fails on the "abeam kea" ident. But that does not exist as user point, there is one similar in Australia while I'm trying to insert one in Greece. Here, try to import first the https://mega.nz/file/VXZlWI6Q#RaLxx9Iz9VhEF-nA3AVwQhVIm2mcSTM2aapnjDX_bhg Then this one https://mega.nz/file/QDIzyITQ#A_vdusZ9Fco59D38Xuzxa6-SY8O0vStapcAHDDydQ-k If you found a bug 🙂 and you're already in the fixing part, maybe you can also provide the functionality of ignoring import of user waypoints that exists on the same coordinates with the same type (VRP for example). This way I can just import more and more files from different sources (that has more coverage) but no duplicates will be created. Thanks, Doron.

It Does !!! :-). So funny.

How can I tell ? it's indeed an add on.

Hi Alex, Wind at 10 degrees on a rwy 18/36, should pick 36. seems like for 18 it calculated 5 kts headwind, which is really tailwind. Doron. https://mega.nz/file/oGo3ACAY#GCNIEWsqFbjpoM3oxS1_rcU1dpyV1PEWEmWzR1iwmw0

Hi Alex, Any chance you'll find time to fix 2 small things on the IVAO plan ? 1 - Departure time - now + 30 minutes 2 - DOF/<today date - YYMMDD> in the 18 Other Information section. 3 - less critical but will really really help. Altn Aerodrome can't be empty or equal to the 13 - Departure Aerodrome (issue warning if it does). All are IVAO rules. This way it won't get rejected on these things automatically which is what happens now. Thank you. Doron.

Weird. suddenly I could import it. ok, maybe there was something special in a plan that wasn't digested right. I will keep on trying, if I got something I'll attach it. Thanks.

Hi Alex, I'm trying to import all the possible formats from LittleNav Map to navigraph, with no success. Here is a sample pln that I exported from Navigraph, pln format, that they call "Microsoft flight simluator 2020" format. <?xml version="1.0" encoding="UTF-8"?> <SimBase.Document Type="AceXML" version="1,0"> <Descr>AceXML Document</Descr> <FlightPlan.FlightPlan> <Title>EFMA/MHQ to ESSU/EKT (N806SB)</Title> <FPType>IFR</FPType> <RouteType>HighAlt</RouteType> <CruisingAlt>20000</CruisingAlt> <DepartureID>EFMA</DepartureID> <DepartureLLA>N60° 7' 18.84",E19° 53' 47.04",+000018.00</DepartureLLA> <DestinationID>ESSU</DestinationID> <DestinationLLA>N59° 21' 7.92",E16° 42' 29.88",+000140.00</DestinationLLA> <Descr>EFMA/MHQ to ESSU/EKT (N806SB) created by Navigraph</Descr> <DepartureName>MARIEHAMN</DepartureName> <DestinationName>ESKILSTUNA</DestinationName> <AppVersion> <AppVersionMajor>11</AppVersionMajor> <AppVersionBuild>282174</AppVersionBuild> </AppVersion> <ATCWaypoint id="EFMA"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N60° 7' 18.84",E19° 53' 47.04",+000018.00</WorldPosition> <RunwayNumberFP>21</RunwayNumberFP> <ICAO> <ICAOIdent>EFMA</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="KOXFU"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N60° 3' 11.94",E19° 50' 19.03",+000000.00</WorldPosition> <DepartureFP>OGLO1D</DepartureFP> <RunwayNumberFP>21</RunwayNumberFP> <ICAO> <ICAOIdent>KOXFU</ICAOIdent> <ICAORegion>EF</ICAORegion> </ICAO> </ATCWaypoint> <ATCWaypoint id="NARIL"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N59° 58' 37.12",E19° 46' 22.66",+000000.00</WorldPosition> <DepartureFP>OGLO1D</DepartureFP> <RunwayNumberFP>21</RunwayNumberFP> <ICAO> <ICAOIdent>NARIL</ICAOIdent> <ICAORegion>EF</ICAORegion> </ICAO> </ATCWaypoint> <ATCWaypoint id="OGLOB"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N59° 55' 59.00",E19° 27' 44.00",+000000.00</WorldPosition> <DepartureFP>OGLO1D</DepartureFP> <RunwayNumberFP>21</RunwayNumberFP> <ICAO> <ICAOIdent>OGLOB</ICAOIdent> <ICAORegion>EF</ICAORegion> </ICAO> </ATCWaypoint> <ATCWaypoint id="TEB"> <ATCWaypointType>VOR</ATCWaypointType> <WorldPosition>N59° 31' 54.10",E18° 12' 11.90",+000000.00</WorldPosition> <ICAO> <ICAOIdent>TEB</ICAOIdent> <ICAORegion>ES</ICAORegion> </ICAO> </ATCWaypoint> <ATCWaypoint id="PETEV"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N59° 12' 25.80",E17° 0' 43.50",+000000.00</WorldPosition> <ATCAirway>N872</ATCAirway> <ICAO> <ICAOIdent>PETEV</ICAOIdent> <ICAORegion>ES</ICAORegion> </ICAO> </ATCWaypoint> <ATCWaypoint id="LX"> <ATCWaypointType>NDB</ATCWaypointType> <WorldPosition>N59° 16' 31.70",E16° 42' 47.30",+000000.00</WorldPosition> <ICAO> <ICAOIdent>LX</ICAOIdent> <ICAORegion>ES</ICAORegion> </ICAO> </ATCWaypoint> <ATCWaypoint id="ESSU"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N59° 21' 7.92",E16° 42' 29.88",+000140.00</WorldPosition> <ApproachTypeFP>ILS</ApproachTypeFP> <RunwayNumberFP>36</RunwayNumberFP> <ICAO> <ICAOIdent>ESSU</ICAOIdent> </ICAO> </ATCWaypoint> </FlightPlan.FlightPlan> </SimBase.Document> Do you think you can support it in your export ? Thanks.

Caldur, what I did is listed the directories to a file and then updated manually the LittleNavMap file that holds this list.

Just for the sake of things 🙂 I have just updated my Jepp maps. it's there, dated 03 Feb 23. Formal Jepp chart, not any internet fake of some sort. I am pretty sure I saw another non oval circuit someplace, doing lots of VFR flight, so I definitely stumbled on some. Not very common, but do exist. If I'll find another one I'll let you know 🙂

https://mega.nz/file/QeQykTwY#_qQQCCqGQRmjhp_j_NnbKqNuVLlEORl_-SRnnpFaJY0

that's fine :-). Thanks Alex.

🙂 Nope, what I meant by "non standard" pattern is that it's not an oval pattern. look at LFRN circuit of RWY 14/32.

can I create a non standard traffic pattern ? There are lots of airports with non standards ones (I.E., not a perfect pattern).

Duplicate User waypoint crash #985 🙂

If someone tries to import that to their Garmins, for sure. but that's like cheating a VFR isn't it ? :-). If that's VFR, why put coordinates in your Garmin/FMC 🙂 Anyway, if you find a way to enable that by configuration, then I guess whoever wants to import it will not tick it and whoever wants to fly real VFR online, can tick it on. I can say that I fly tons of VFRs online, using coordinates will always get rejected by the controller. on a different topic :-), just because it happened 2 minutes ago, if you try to add a userpoint that has an existing Ident , LittleNavPoint crashes :-). Doron.

Hi Alex, Is it possible that for VFR flight plan, you will supply the route with the Name for the User way points rather then the coordinates when exporting to IVAO/VATSIM. When flying online, you can't put something like "DCT YNN DCT 3943N02137E DCT 3957N02137E DCT". The YNN is fine (it's a VOR), but the rest is info that is not really acceptable by the online controllers (and for a reason :-)) . In this example, the preferred way is "DCT YNN DCT KALABANKA DCT KARPERO DCT". I would say, if it's a user waypoint and it has a name - use it. If not - the coordinate. Maybe flag that with an option "Use waypoints names for VFR flight plans". Thanks, Doron.

cool 🙂

Hi Alex, Is it possible to allow us to define additional content directories to MSFS in order to enable you to scan them as well even if they are not active ? The rational behind that is that the more sceneries enabled , the more time it takes for the Sim to load, so I enable / disable them as I need them with directory links.But that requires me to load the scenery library again in NavMap every time to "see what is active", which takes lots of time as well. You already have the option to "exclude" directories, can you add one to "include" ? :-) Thanks, Doron.

In the context of a VFR flight, and I'm not a real pilot so maybe I'm wrong, when I'm filing a flight plan (to IVAO for example), there is no meaning to coordinates and , I assume, no one will try to import such a plan to Garmin or any other instrument. It's a VFR, not IFR. What I'm after is being able to export your plan to IVAO. That won't work either way (not coordinates or coordinates/ident). If it's a VFR, no one should care about coordinates. I think. Anyway, thanks for considering a solution for this.

Hi Alex, Is it possible that when exporting VFR flight plan (To Ivao, to clipboard, I guess everywhere) that has known Ident waypoints, keep the Ident and not convert to coordinates ? https://mega.nz/file/hKZ3VbYS#Qe4JDDJWIk-vuVqMyJpROl4355G68tXKtFnbKinm0C8

worked 🙂