Fix possible conficts in runway data

In case 2 carriers are present and have the same name, the kneeboard information gets screwed up...
This commit is contained in:
Raffson 2023-03-12 14:36:04 +01:00
parent 26851520c8
commit aaa06a5e88
No known key found for this signature in database
GPG Key ID: B0402B2C9B764D99
2 changed files with 2 additions and 2 deletions

View File

@ -529,7 +529,7 @@ class GenericCarrierGenerator(GroundObjectGenerator):
# they aren't exposed as such to the game. Should
# clean this up so that's possible. We can't use the
# unit name since it's an arbitrary ID.
self.runways[self.control_point.name] = RunwayData(
self.runways[self.control_point.full_name] = RunwayData(
self.control_point.name,
brc,
f"{brc.degrees:03}",

View File

@ -1246,7 +1246,7 @@ class NavalControlPoint(
fallback = RunwayData(
self.full_name, runway_heading=Heading.from_degrees(0), runway_name=""
)
return dynamic_runways.get(self.name, fallback)
return dynamic_runways.get(self.full_name, fallback)
@property
def runway_status(self) -> RunwayStatus: