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

AI Strike package (RED) #13

Open
132ndNeck opened this issue Jul 8, 2019 · 3 comments
Open

AI Strike package (RED) #13

132ndNeck opened this issue Jul 8, 2019 · 3 comments
Labels
A-G Air-to-Ground help wanted Extra attention is needed

Comments

@132ndNeck
Copy link
Contributor

Is it possible to create a RED Strike package.

  • Assembling aircraft from various airbases.
  • Conduct AAR enroute to ensure fuel is filled up
  • Package consist of A-A (Escort) and A-G (Strike) (And Bonus: Any SEAD/DEAD)
  • Can strike target at map-objects, or defined strike zones in Blue territory?
  • Add option for routing? or random?
  • A 25% chance for the strike to be conducted in the mission.
  • Maybe have 2-4 different sizes, from a very large strike package (multiple flights 10+ aircraft), to a simple 2 flight package with 4 AC in total
@132ndNeck 132ndNeck added enhancement help wanted Extra attention is needed labels Jul 8, 2019
@132ndNeck
Copy link
Contributor Author

Primary airfields Shiraz and Kerman.
Type of aircrafts for this need to be identified, so they can be added to the enemy ORBAT both in the .miz but also on the OPUF brief page:
https://132nd-vwing.github.io/OPUF-Brief/Docs/Enemy/Enemy.html

@thebgpikester
Copy link

Target area can be randomised from a list. Targets are usually things like anything the weapon can hit in zone or a specific Bomb on a point. The types of target would be needed to be considered.

If using separate airbases then less randomisation can happen, would be harder to sync them. Will have to check the ranges with different aircraft.

AAR is a no-no, AI just use refuels only when they need it and refueling an entire package would desync the timings of staying together.

Routing can be randomised, probably easier to have a single place to form up then they proceed to the chosen area.

Timing is easily randomised, no constraint.

Types for Iran would be Fencer and Frogfoot, they can cover all types of attack including SEAD, but sometimes these can get a little out of control as they go for radars elsewhere. Things like a Ship can attract attention (needs tested)

The aim point would be a single reusable function that would look at various zones on a map, pick a target and launch and assemble with no further input, just a random timed trigger and a limiter to stop more than one happening.

@132ndNeck
Copy link
Contributor Author

  1. Copy on types of target. Should be a easy thing to setup. Just have some different areas in BLUE territory for long distance strike packages.

  2. Would be nice that using seperate airbases can be a part of the randomisation. Sometime a strike fly out of one airfield, other times it is more complex and consist of aircraft from both airfields.

  3. Copy regarding AAR. That sucks. I guess this will make it almost impossible then, as the distances from Shiraz and Kerman is very long?
    Would it be impossible to get AI to refuel?

  4. Yes, have a place to form up (Marshall area) and then procees to target area, or ingress from there sounds good.

  5. Sounds good regarding timing. Sometime it can happen early in a mission, sometime late in a mission, sometime not at all.

  6. Copy Fencer and Frogfoot. I will also be adding Russia in support of IRAN on the RED side, so we can use all aircraft from Russia. They can either forward stage on Shiraz or Kerman, or can send long range aviation (that can then start in the air, simulating coming from Russia).

  7. Copy regarding aim point. Sounds flexible and good.

@132ndNeck 132ndNeck added the A-G Air-to-Ground label Jul 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-G Air-to-Ground help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants