Repository navigation
Add Afghanistan terrain - #447
Merged
Merged
Conversation
Collaborator
|
please rebase |
…ort_import.py, projection fitted on the map's own beacons.lua positions, bounds/bullseye from the terrain config)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the Afghanistan terrain (DCS 2.9.x, all four map parts installed).
How it was built (same path as the other terrains):
airports.py:tools/airport_import.pyover the Mission Editor airdrome dump (dumpairportdata()from that tool's docstring, run once by placing an aircraft on the map). 26 airfields with runways, parking slots (sizes,slot_version = 2) and ATC frequencies as the ME reports them.projection.py: transverse Mercator fitted on the terrain's ownMods/terrains/Afghanistan/beacons.lua, whose 49 beacons carry both DCS metres (position) andpositionGeo: central meridian 63, false easting -300150, false northing -3759657, k 0.9996. Every beacon round-trips within 0.07 m. (tools/export_map_projection.pygets the terrain registered too.)afghanistan.py: bounds from the terrain config'sSW_bound/NE_bound(km -> m), default bullseyes fromdefaultBullseye, UTC+4:30. Monthly temperatures are the Kabul climate (they only seed the ME weather, as in the other terrain classes).Checked:
Mission(Afghanistan())builds flights at Bagram/Kandahar with payloads from a real install, saves, andload_filereads the .miz back asAfghanistan; six liveAirbase:getPoint()positions from a running Afghanistan mission land within ~1.5 km of the airport reference points (the same spread Caucasus shows between the ME reference point and the in-game airbase point); the repo's test suite is unchanged before/after (the same install-dependent livery tests fail on a machine without DCS).