Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue 2917 #2980

Closed
wants to merge 3 commits into from
Closed

Issue 2917 #2980

wants to merge 3 commits into from

Conversation

zhexu14
Copy link
Collaborator

@zhexu14 zhexu14 commented Jun 9, 2023

This PR addresses Issue 2917 #2917 and allows CAS missions to be planned against airfields and FOBs

@codecov
Copy link

codecov bot commented Jun 9, 2023

Codecov Report

Merging #2980 (aaa7755) into develop (36c4bb8) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop    #2980      +/-   ##
===========================================
- Coverage    38.05%   38.05%   -0.01%     
===========================================
  Files          456      456              
  Lines        24985    24984       -1     
  Branches      4405     4405              
===========================================
- Hits          9509     9508       -1     
  Misses       15458    15458              
  Partials        18       18              
Impacted Files Coverage Δ
game/theater/controlpoint.py 49.36% <100.00%> (-0.06%) ⬇️

@DanAlbert
Copy link
Member

I don't understand how this works as far as flight plan layout goes.

if not isinstance(location, FrontLine):
raise InvalidObjectiveLocation(self.flight.flight_type, location)

That's unchanged in this PR, so I'd assume any attempt to use this crashes.

With that question out of the way though.... how should flight plan layout work here? The patrol start/end points for this are probably very different than they are for a front line.

I wonder if the FR is perhaps being taken too literally, and this is better suited to being a different type of BAI?

@Starfire13, which properties of CAS that BAI doesn't fulfill are you aiming for? Area attack (to cover multiple garrisons), patrol (stay on station for a fixed time even if you can't find targets), or both?

@Starfire13
Copy link
Contributor

Starfire13 commented Jun 13, 2023

@Starfire13, which properties of CAS that BAI doesn't fulfill are you aiming for? Area attack (to cover multiple garrisons), patrol (stay on station for a fixed time even if you can't find targets), or both?

Here's an example of how I typically set it up manually. I find it works well. Essentially, I just want them to clear out any remaining stragglers within the zone that would prevent capture, after all the DEAD and BAI have done their thing.
Screenshot 2023-06-13 110638

For control point CAS, you wouldn't need a 20 mile radius search and engage range since you're not clearing stuff out of an entire frontline. 10 mile radius would be good enough.

Having this feature will actually be very useful in the Exercise Bright Star campaign I'm working on for Sinai, because there will be no more frontlines after the first base capture (so players can no longer plan a CAS over the frontline and drag the waypoints over). All capturing west of the Suez Canal is going to be via air assault only.

@DanAlbert
Copy link
Member

Do you want that with or without a patrol though? It's not that we can't do the FR exactly as written, it just sounds like it may be one of those FRs that's trying to ask for the "simple" thing rather than something that's a better fit for the intent (and doing this isn't actually simple, because it forces us to make CAS do two things that have very little in common at the implementation level).

We probably do need to make this actually a new mission type (until my favorite #270 is fixed, any amount of variation in mission behavior is very error prone). What's not obvious to me yet is whether that mission type is:

  1. Area attack BAI (with a better name): like sweep but for ground units. Fly the route, shoot what you see in the area, leave. Do not loiter.
  2. Air assault CAS (also needs a better name): patrols the target area for the mission duration and attacks what it finds in the area. This is the FR as written, but with a different implementation.

@Starfire13
Copy link
Contributor

Starfire13 commented Jun 13, 2023

No, there is no need to loiter. They can simply clear the circular search area and leave. They are only dealing with static defences after all.

@DanAlbert
Copy link
Member

We should probably make a new mission type that's whatever the ground attack version of sweep is then. iirc there is a name for that but I can't remember it right now. It might just be a subclass of BAI?

@Starfire13
Copy link
Contributor

@DanAlbert
Copy link
Member

Closing to clean up since a different approach is needed here.

@DanAlbert DanAlbert closed this Jul 12, 2023
@zhexu14 zhexu14 deleted the issue_2917 branch November 2, 2023 12:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants