August 4, 20214 yr I am using Windows version of LNM 2.6.15 and noticed that there's this waypoint called GOPLU added whenever I load my flight plan in MSFS. This is what my flight plan created in LNM looks like: After I load the flight plan in MSFS: What the flight plan looks like on my G1000 NXi (v0.2.0): And it the flight path on the approach phase doesn't seem to match as well. I was wondering if this could be a potential bug in the save file that's causing the flight plan to show up incorrectly. I have tried using the default nav data as well as navigraph nav data and it's still producing the same results. Edited August 4, 20214 yr by captain420 ASUS ROG Maximus Hero XII ▪︎ Intel i9-10900K ▪︎ NVIDIA RTX 3090 FE ▪︎ 64GB Corsair Vengeance RGB Pro ▪︎ Windows 10 Pro (21H1) ▪︎ Samsung 970 EVO Pro 1TB NVME SSD (OS Drive) ▪︎ Samsung 860 EVO 2TB SATA SSD ▪︎ Seagate 4TB SATA HDD ▪︎ Corsair RMx 850W PSU
August 4, 20214 yr Problems with FS2020. See the next post for Albert's response. Gigabyte x670 Aorus Elite AX MB; AMD 7800X3D CPU; Deepcool LT520 AIO Cooler; 64 Gb G.Skill Trident Z5 NEO DDR5 6000; Win11 Pro; P3D V5.4; 1 Samsung 990 2Tb NVMe SSD: 1 Crucial 4Tb MX500 SATA SSD; 1 Samsung 860 1Tb SSD; Gigabyte Aorus Extreme 1080ti 11Gb VRAM; Toshiba 43" LED TV @ 4k; Honeycomb Bravo.
Archived
This topic is now archived and is closed to further replies.