Jump to content

NTTR map, Beatty BTY location is wrong


Redglyph

Recommended Posts

DCS 2.0.4.59428.142 / release 1.5.5.60565.216

 

In the file R_NAV_data_Nevada.lua, the location of the BTY beacon is incorrect, which makes it unusable.

 

Fixed file in attachment.

 

 

	{	
	airbase = 'BEATTY', --15
	lat = [b][color="Red"]38.80056[/color][/b],
	long	 = 116.74750 * long_modifier,
	alt = 890,
	rwy = -1,
	length = -1,
	code = '-... - -.-- ' --/N/ BTY_
},

 

 

should be

 

	{	
	airbase = 'BEATTY', --15
	lat = [b][color="SeaGreen"]36.80056[/color][/b],
	long	 = 116.74750 * long_modifier,
	alt = 890,
	rwy = -1,
	length = -1,
	code = '-... - -.-- ' --/N/ BTY_
},

R_NAV_data_Nevada.lua


Edited by Redglyph
updated file

System specs: Win7 x64 | CPU: i7-4770K | RAM: 16 GB | GPU: GTX 980 Ti 6 GB | Thrustmaster HOTAS | MFG rudder pedals | SATA3 SSD | TrackIR

Link to comment
Share on other sites

  • 2 weeks later...

Reported on the bug tracker (if it's still used).

 

Any idea when we can hope an update of the Mig-21 in 2.0, by the way? It would be nice, for instance there are no flood lights.

System specs: Win7 x64 | CPU: i7-4770K | RAM: 16 GB | GPU: GTX 980 Ti 6 GB | Thrustmaster HOTAS | MFG rudder pedals | SATA3 SSD | TrackIR

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...