September 13, 200322 yr Can someone advise the format of a LAT/LON fix please?As an example lets take North 51 degrees 53minutes 41 seconds West 0 degrees 15 minutes 09 seconds.Would that beN51.895W000.489 without the decimal points.OrN5153.68W00015.15, again without the decimal placesOrN5153W00015 ignoring the seconds bit.Or something else?ThanksDave
September 13, 200322 yr Always 13 characters :N51895W000489LDDMMmlDDDMMmL lat : N or Sl lon : E or WanthonyAnthony MertonPrecision Manuals Developmenthttp://www.precisionmanuals.com
September 13, 200322 yr Author Thanks Anthony and Richard.I'll see if fixing LUT via LAT/LON makes the ND display it in the correct place and not 20 miles and 10 degrees from where it should be.
September 13, 200322 yr Author OK, I give up :-(Just tried using that format to create a fix for a SID and now get an error in the FMC 'err at N51537W000151, line 8'. FIXES (this is line 7)FIX LUT LATLON N51537W000151FIX OLNEY COLOCATED BPK 318 33FIX LUT04 COLOCATED BPK 318 33ENDFIXESI have tried calling the fix LUT01, & LUT21 in case the system gets confused with the existing LUT which it misplaces but I still get that error.RgdsDave
September 14, 200322 yr Author This gets stranger and stranger.I have triedN51537W000151N51895W000489AndN515341W0001509Each of those gives me an error in the FMC.I have finally got Terry's converter to work and looking at the 767PIC converted EGGW file that locates the LUT NDB as FIX LUT LATLON N 51 53.68 E 0 15.15Now although the 'E' bit is wrong (or is that down to true vs magnetic?) that format does not produce an error from the FMC and changing the 'E' to 'W' locates LUT NDB in the correct place.Comments?RgdsDave
September 14, 200322 yr Hi Richard,It can be done a tiny bit more efficient:N51 Location: Vleuten, The Netherlands, 17.3dme SPL 108.40 | Simulator: FS2024 System: AMD 7800X3D - Gigabyte X670 - RTX 4090 - 64GB DDR5 - 2 x 2TB SSD - 32" 1440p Display - Windows 11 Pro
September 14, 200322 yr Ah sorry, I thought you asked the format to enter a latlon fix in the FMC...For SIDSTAR files the correct format is like in FIX (RID) LATLON N 49 56.34 E 8 9.92anthonyAnthony MertonPrecision Manuals Developmenthttp://www.precisionmanuals.com
September 14, 200322 yr Author Ah :-) thought the 2 would be the same Anthony, sorry for the confusion.At least now I have Terry's converter running I don't need to hand craft the SID/STARs I want Any idea why the LUT NDB is drawn out of position on the ND Anthony even though its correct LAT/LON is in Richard's wpNavAID.txt file?RgdsDave
September 14, 200322 yr There is an issue with FS9 when Windows regional settings are not set to US settings. Something with the comma and the decimal point.Could this be the reason on your setup ?anthonyAnthony MertonPrecision Manuals Developmenthttp://www.precisionmanuals.com
September 14, 200322 yr Author >There is an issue with FS9 when Windows regional settings are>not set to US settings. Something with the comma and the>decimal point.>>Could this be the reason on your setup ?>>anthony>>Anthony Merton>Precision Manuals Development>http://www.precisionmanuals.comNegative Anthony, in the UK so use a full stop (period) for decimal seperation.At least one other person has LUT misplaced in the ND, he also is in the UK so would expect the decimal point to be the same.Dave
Create an account or sign in to comment