HCCE and automatic defensive behavior (Full Version)

All Forums >> [Current Games From Matrix.] >> [Modern] >> Larry Bond's Harpoon - Commander's Edition



Message


Flunkie -> HCCE and automatic defensive behavior (5/17/2007 4:42:50 AM)

Can anyone tell me if HCCE has an automatic defensive behavior like H3 v.3.8? This defensive behavior turns on ship and aircraft radars and fires missiles automatically. Even with weapons tight and all Staff Handles off. I don't like this. Will HCCE do anything like that?




CV32 -> RE: HCCE and automatic defensive behavior (5/17/2007 4:15:41 PM)

HCCE's defensive model is quite different.

You control your ships' sensors, choosing to energize all your air search radars, your surface search radars, your active sonars, or all of them. You can't pick and choose which individual sensor types to activate, eg. turn on the SPS-49 air search but not the Sea Giraffe air search. You might be prompted to activate them, if for example you are "painted" by an enemy sensor, but you must choose to do so.

As for defensive systems, you can control your SAMs more than your guns. Defensive gun systems engage enemy targets automatically. The SAM model is a bit different. There are Staff Option settings which you control across your entire fleet.

You choose the "Surface SAM Fire Rate": the options are Light, Normal and Heavy. IIRC, these equate to 1 v 1, 2 v 1 and 3 v 1 ratios in terms of the ratio of defensive SAMs to targets.

You also choose the "AAW Auto Fire Rate": the options are Optimum, 1/4 Max, 1/2 Max and 3/4 Max. This determines the range at which your defensive systems begin to engage.

So, the HCCE model is certainly simpler, but it works very well. Tony may wish to add some meat to my crude explanation.

Hope this helps. [:)]




TonyE -> RE: HCCE and automatic defensive behavior (5/17/2007 6:39:30 PM)

Quite right Brad. 

The system works quite well but fits best in typical Cold War blue water engagement with fairly long range SAM systems.  In a more confined geographical area the existing model does some unexpected things like firing SAMs at an enemy aircraft that wouldn't be a danger until it has travelled another 100nm toward the target.

In HCCE you will also occasionally be frustrated by a distant Tico firing SAMs at incoming ASMs that are a much better candidate for a closer escort to handle.  Brad and other database designers also use some tricks in platform development to help make sure a proper weapon is chosen.

The limitations tend not to be a big deal in most scenarios but that hasn't stopped me from wanting to improve upon the situation.  Back when I was a programmer for HC I began writing a new SAM employment model, still automatic but smarter.  Perhaps some time after HCCE release when I get back into being a HC programmer we'll be able to flesh out the new model.  Some of the emphasis of the new model:
  • Platforms are selfish, the in the utmost protect themselves, secondarily their own group, and neighboring groups only when the firepower can be spared.  This is different from the current HC approach that every ship is as important as my own ship.
  • Platforms will not bother with sending SAMs against an incoming where the SAM cannot hit (imagine triangle setup, Tico in upper left, target at bottom, incoming ASM upper-right).  The SAM in this made up case would hit the target before the Tico could get an intercepting SAM to the ASM.  The obvious thing is not to fire the SAM at all.  The current HC model in most cases will fire that hopeless SAM.
  • Platforms will use the optimal weapon for intercept.  Broad statement, what I mean is if the ASM is already in ESSM range, the platform won't fire a 75nm ranged SM-2 missile at the ASM unless only SM-2 are left.  HCCE currently engages with the first weapon in the mount list that matches the range need, here is where the smart database editor adds weapons to a platform in a certain order to get the benefit in HCCE without changing the game code.
  • Intercepts will factor in the speed of the incoming ASM, so that 1650kt monster will get the priority it needs, in front of the 450knot slow ASM.  The current model pretty much leaves them treated equally, often with explosive results.

The new model does not aim to:
  • Order threats by type (such as noticing that that airplane far away is a Tu-22 with long range ASM and should be shot down before the closer Yak-38 with iron bombs).  Maybe some day, but I'm all for modest improvements that happen vice extreme improvements that never happen.

There is always the possibility of adding a manual engagement capability but it almost certainly won't happen unless and until the AI gains at least the capability listed above.  We should for the most part have the same smart or stupid ship's complement that the AI does to keep the game somewhat 'fair'.  Architecting AI improvements will be a constant side-project once HCCE is released.  Improving the AI is terribly painful but otherwise we just give improvements to let the player bludgeon an AI that doesn't know to use nor how to use the improvements.




DonG -> RE: HCCE and automatic defensive behavior (9/16/2007 11:01:50 PM)

So if i understand it correct,it's not possible to target an airtarget induvidualy unless the target is within the ships weapons parameters..




TonyE -> RE: HCCE and automatic defensive behavior (9/17/2007 12:17:50 AM)


quote:

ORIGINAL: DonG

So if i understand it correct,it's not possible to target an airtarget induvidualy unless the target is within the ships weapons parameters..



Correct, all surface to air engagements are handled automatically, the only real input you have is turning your radars off to prevent SARH SAMs from firing.





Bungle -> RE: HCCE and automatic defensive behavior (9/17/2007 1:47:03 AM)

Guys, guys all this talk is making me sweaty for the game! Im really liking what Im reading here AA wise, the AI might actually have a bit of I, need  dose of 'classic' goodness!
Just been over to the HCCE page, the new database pic library looks great and I think Im getting used to the textured terrain too.




Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.671875