n0taurius

Good day All, I’ve been mucking about with this for sometime this morning. All I can say is this is not as straightforward as I thought it might be. My findings so far can be best described in two words – “Results Vary” 😊 Using the flight plan generated by @Greyheart, I get very different results depending on the GPS unit it is loaded into. For preliminary tests I used both default Cessna 172’s. One with the G1000 and the other has the GNS 530. Since MSFS 2020 SU5, loading a direct flight from the World Map will result in two extra waypoints added (they appear to be some type of departure and arrival reference points). In the 172 with the G1000 they are not named in the flight plan but are represented by an indirect route graphically (in this case a curved flight path upon departure from KSEZ and an initial DTK of 214°. Then loading overtop using FSUIPC7 you will notice the DTK of 245° (the correct angle) to the waypoint JUWSO. However, the graphical display does not change. Using the non-G1000 172 has more dramatic and easily seen results using the same steps as above because the waypoints added by MSFS 2020 are named and are erased when the flight plan is reloaded via FSUIPC7, I don’t normally fly the models with the glass cockpit so my statement that FSUIPC7 overwrites the flight plan needs to be qualified as described above. A newly generated flight plan will not overwrite an existing flight plan. Having said that, spawning to an airport and loading a flight plan via FSUIPC7, I find, does work. When I loaded the flight plan @Greyheart generated into the G1000 model the waypoint JUWSO did show in the FPL screen so I don’t know why it didn’t when @Greyheart loaded it. @John Dowson, I don’t think there’s much you can do at this point as I see this as not being a FSUIPC7 issue, and I’m sure all will change again when SU6 is distributed. I will continue to experiment and once I have something definitive and consistently replicable, I will revisit this post.

@John Dowson Understood. Thanks for for this. Hopefully with some testing we can arrive at an understanding of what works and what conflicts. Cheers Brent

I can't do any more today, but I will do some experimenting and upload results tomorrow. Brent

@John Dowson and @Greyheart, I don't have the mods @Greyheartmentioned. However, and I don't know if this would impact (permissions maybe?), but I have the MSFS Packages folder, which normally resides in the C:\Users\Username\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages when MSFS 2020 is initially installed, moved to a custom folder in the root of C:\ to avoid potential security permission issues when interacting with third-party apps and the Community Folder. It was recommended & I followed this youtube video as a guide. Like I said, I don't know if this would have any impact, but only mention it as a change to a typical install.

I think we can rule out the plan or aircraft as I used the exact model aircraft @Greyheartused and we both used a plan generated in and exported from LittleNavMap. The only difference was the loading via FSUIPC7 worked for me. But thanks for looking into this because if you could get this sorted, you would make a lot of users very happy. Cheers Brent

Well John, I didn't see your last message about making a copy of the WASM in the Community folder until well after the fact. However, happily or unhappily (depending on which side you are standing) v.7.2.9 has no effect on my ability to load flight plans via FSUIPC7. Everything works as intended and I am able to load flight plans while in-Sim with no issues. I sure wish I knew why it works for me so I could share. Brent

Hello John, According to a post in Discord, @Greyheartfollowed the same steps as I explained in my response above but the flight plan generated in LittleNavMap failed to load. I cannot account for why it works for me. (Maybe I have a rogue SimConnect version). I'm not savvy enough to determine the 'Why'. I wish I were because it is such a great feature to have working. Having said that, I am not in any hurry to update to the latest version of FSUIPC7 in case there is an issue there! 🙂 Brent

Hello John, I, unfortunately, was the person who informed Greyheart that loading flight plans via FSUIPC7 worked. And if the above is the "official" response, I understand. However, in actual practice I have MSFS 2020 - latest version; LittleNavMap - latest version; and FSUIPC7 - version 7.2.1 (from June I think). My workflow is simple: I plan the flight in LittleNavMap and under the File Menu I choose Export as MSFS 2020 .PLN. In MSFS 2020 I spawn to the departure airstrip and then using the "Load flight plan" feature in FSUIPC7's File Menu, I load the aforementioned saved flight plan. I have yet to have it fail to load. What I really like is having the ability to over-write flight plans while in-Sim. FYI, I just tried it before writing this and it worked flawlessly. Just my observations from a current User. Brent