mirror of
https://github.com/dcs-retribution/dcs-retribution.git
synced 2025-11-10 15:41:24 +00:00
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:
parent
26851520c8
commit
aaa06a5e88
@ -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}",
|
||||
|
||||
@ -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:
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user