October 2, 20205 yr When i use LNM to find radio freq data for various airports, it will only show the ATIS freq and one single tower com freq (always the lowest in the list). Example: EBAW: FS gives: ATIS: 124.205 - GROUND: 121.905 - TOWER: 119.700 - TOWER 135.205 LNM gives: ATIS: 124.200 - TOWER: 119.700 Now with the LNM tower info not complete i'm left in the dark when using the returned tower freq in FS that i pull from LNM. FS uses 135,205 in game as tower freq for comms at EBAW and although it also mentions 119,700 as freq, i never get any ATC on this freq, So the info returned by LNM is useless. Any suggestions on getting the entire com freqs to show in LNM? Win11 Pro 64-bit, Ryzen 5800X3D, Corsair H115i, Gigabyte X570S UD, EVGA 3080Ti XC3 Ultra 12GB, 64 GB DDR4 G.Skill 3600. Monitors: LG 27GL850-B27 2560x1440 + Samsung SyncMaster 2443 1920x1200, HOTAS: Warthog with Virpil WarBRD base & hegykc MFG Crosswind modded pedals, TrackIR4, Rift-S for VR
October 3, 20205 yr What simulator? Which Navigraph AIRAC? LNM version? Scenery database settings (Navigraph for all features, etc.)? LNM takes the COM from the Navigraph database while getting the airport from the simulator database. For EDDF I can see four tower frequencies for cycle 2010, for example. Alex Alex' Projects: Little Navmap
October 3, 20205 yr Author Simulator: FS 2020 Navigraph AIRAC: ? LNM version: latest beta Scenery database setting: Navigraph - AIRAC Cycle 1801: Use Navigraph for Navaids and Procedures Update: Overlooked the "COM" tab in the information window. Q: Why is the freq rounded to (example) 135,200 while in FS it's 135,205 (and there 135,200 does not give any coms)? Edited October 3, 20205 yr by Lange_666 Win11 Pro 64-bit, Ryzen 5800X3D, Corsair H115i, Gigabyte X570S UD, EVGA 3080Ti XC3 Ultra 12GB, 64 GB DDR4 G.Skill 3600. Monitors: LG 27GL850-B27 2560x1440 + Samsung SyncMaster 2443 1920x1200, HOTAS: Warthog with Virpil WarBRD base & hegykc MFG Crosswind modded pedals, TrackIR4, Rift-S for VR
October 4, 20205 yr 16 hours ago, Lange_666 said: Q: Why is the freq rounded to (example) 135,200 while in FS it's 135,205 (and there 135,200 does not give any coms)? Good catch. This is a LNM bug. Frequencies should not be rounded to the next 0.025 MHz if using the new 8.33 kHz channel spacing. I implemented this already for X-Plane but it seems MSFS uses the same scheme. I will fix the problem. Alex Alex' Projects: Little Navmap
October 4, 20205 yr Author 10 hours ago, albar965 said: Frequencies should not be rounded to the next 0.025 MHz if using the new 8.33 kHz channel spacing. The offset "bug" can either be + or - 0,005 Mhz so not always rounded to the next 0,025Mhz, it can be rounded to the previous one to. Win11 Pro 64-bit, Ryzen 5800X3D, Corsair H115i, Gigabyte X570S UD, EVGA 3080Ti XC3 Ultra 12GB, 64 GB DDR4 G.Skill 3600. Monitors: LG 27GL850-B27 2560x1440 + Samsung SyncMaster 2443 1920x1200, HOTAS: Warthog with Virpil WarBRD base & hegykc MFG Crosswind modded pedals, TrackIR4, Rift-S for VR
October 5, 20205 yr 13 hours ago, Lange_666 said: The offset "bug" can either be + or - 0,005 Mhz so not always rounded to the next 0,025Mhz, it can be rounded to the previous one to. I'm rounding. This also means I can go down to the next 0.025 for old radios. But this is obsolete. For X-Plane and MSFS (next LNM release) I take the values without any modification from the database since they give the channels. Information base on this article. Alex Alex' Projects: Little Navmap
Archived
This topic is now archived and is closed to further replies.