Matrix Games Forums

I would rather have all artilleri off map, I do want a CB construct but in an abstract way, that way I dont have to move the art units. Instead I give some limits to how long they can fire, the system then calculates when the guns becomes setup again. The longer I have them firing the larger risk of CB, so its a tradeoff. Yes between 1/4 or 1/6 would be correct depending on system and transport since they do have to reload with ammo as well. At the same time, then you cant have it all available at the initial bombardment

So we can't counter abstracted off-map units, and the *solution* is to subject ourselves to more off-map abstracted things that we won't be able to counter?

Seems pretty pointless to me. I can already abstract the primary challenges of an environment rich in counter-battery by purchasing meager amounts of arty, and modifying the ammunition quantities and response times in the database editor.

How much of a burden is it to order an on-map battery to fire a mission, and then move them when it's over? Or to see an enemy muzzle flash icon appear in the back of a map and choose whether to order a fire mission on it or not? It's so simple.

While people are asking for more abstraction we might as well abstract air defenses too. I hate having to bother with moving my air defense units into positions where they can adequately defend my main body, would be much easier to just click a button to activate an air defense god-shield for a length of time.

ORIGINAL: Gratch1111
I would rather have all artilleri off map, I do want a CB construct but in an abstract way, that way I dont have to move the art units. Instead I give some limits to how long they can fire, the system then calculates when the guns becomes setup again. The longer I have them firing the larger risk of CB, so its a tradeoff. Yes between 1/4 or 1/6 would be correct depending on system and transport since they do have to reload with ammo as well. At the same time, then you cant have it all available at the initial bombardment

This is somewhat close to FPC-RS option, plus give option for players to choose something like 'fire cycle'. Right? Looks like a good one and such all random option will require the least effort and manpower to work for devs.

However, proper RNG number will be very important otherwise all will be ruined. And some players will not convinced the result of RNG. Think of rouge-like games like FTL, and imagine the moment when the game RNG engine betrayed you. I really love FPC-RS but sometimes its all-random CB feels like a rouletting (only sometimes).

All you can do is praying for RNG god, no room for your tactically sound decision to involve in offmap arty's CB battle. This can be a serious issue in the far future, when MP is introduced in this AB. So I'm also not sure if such all-random approach is a good one. As a wargame, I think there should be punishment and advantage based on tactical decision.

ORIGINAL: Artillerist
So we can't counter abstracted off-map units, and the *solution* is to subject ourselves to more off-map abstracted things that we won't be able to counter?
Seems pretty pointless to me. I can already abstract the primary challenges of an environment rich in counter-battery by purchasing meager amounts of arty, and modifying the ammunition quantities and response times in the database editor.
How much of a burden is it to order an on-map battery to fire a mission, and then move them when it's over? Or to see an enemy muzzle flash icon appear in the back of a map and choose whether to order a fire mission on it or not? It's so simple.
While people are asking for more abstraction we might as well abstract air defenses too. I hate having to bother with moving my air defense units into positions where they can adequately defend my main body, would be much easier to just click a button to activate an air defense god-shield for a length of time.

Any wargame needs abstraction, and even several "hard-core" wargames can't escape from some form of abstraction and simplification. I guess real wargame simulators for real army staffs would have some degree of abstraction. Plus, coding is not that easy job. It really sounds easy when we brainstorm and suggest something, but when actually try to develop the idea and implement the concept via coding, things are not that smooth. Devs team is only 4 men team and the burden is real...

But fair points on your logic, especially about AA and others. Too much abstraction cam make game absurd, and will take out rooms for tactical decision which should be and can be punished or rewarded during game, and thus player's responsibility for his or her decision.

I still think, maybe, introduction of FEBA option can be a good solution:

1) Leave max playable map size as 15km x 15km, but introduce 0~10km depth zone as FEBA. (I wish more depth and more size, but it will be a burden to game engine and memory management)

2) In FEBA, allow only
- Radar SAMs (As far as I know, some radar SAMs were never allowed to operate in FLOT zone)
- Artillery (Distinguish rocket / towed tube / SP tube)
- Recon (including recon vehicles, recon infantry, light infantry, and SFs)
- Helicopter BPs
- Airstrike target
- Resupply station (if resupply is introduced)
==> Among them, allow artillery, recon, and SAMs to maneuver in both FLOT and FEBA zone.
==> Maybe, in this case, it might be possible to allow to "paint" zones for players (like no-go zones) for possible maneuverable area across FLOT and FEBA zone, for artillery, recons and radar SAMs.

3) Do not allow 'normal' units to go into FEBA zone.
==> But in this case, it might be possible to introduce time-based-control or game-progress-control of unit's entrance to FEBA zone. Like, do not allow normal units in FEBA zone for first 1hr of the game, but allow later. Or, allow normal units in FEBA zone if one faction took 80% of VPs or 80% of any other future victory condition.

4) It might be possible to force artillery unit / radar SAM unit maneuver as totally automated AI control, to depict something close to 'off-map' arty. Just like helicopters in this game. Player sets 4~5 FPL or firing point location (FPL should be forced to be placed near road network or good mobility tile), at let AI decides route & speed of maneuvering (but it would be preferable to prioritize to use road and fast move). Players can only command when and where to move, and when and where to fire. In this case, FPL should be allowed to be placed in both FEBA and FLOT zone.
Meanwhile, recons should be full player control.

5) Or, it might be just better to leave all player control for artillery and radar SAM just like all other units.

6) Despite of using more increased map size when compared to current AB game, I still think that FEBA idea could less burden the core of AB code when compared to allowing full control of all units in the same bigger map. Because, all normal units will be inside FLOT zone and for this part, everything will be the same with current AB. Only calculations for arty, radar SAM, recons, helicopters... should be considered for FEBA zone. As such, this FEBA idea could less burden the game engine of AB.

7) For some scenarios and conditions (no artillery game or surrounded situation), such FEBA should not be allowed (so should be set as 0km). In surrounded scenario case or geometrically confined case, all radar SAMs and artillery should operate in the FLOT (or in-map in current AB system)

Artillerist

Thanks, I have recommended AB to many friends who don't normally play modern wargames precisely because it is so accessible. I am glad the devs are seemingly sensitive to this aspect of play. I play some complex games. But I don't play this particular game for complexity. In the way back when I used to play Challenger, Challenger 2000, which had a separate roll for target acquisition, hitting the target, formation of the penetration, reactive armour (if any), and then the result of the hit (often just suppressed after all of this).

exsonic

I wonder if the CB enthusiasts will be able to agree on a particular mechanism. You seem to be having fun discussing it, and more power to you.

I hope there will be an option to (a) turn the feature on/off (b) automate the process if it doesn't interest a player.

@Exsonic: Imagine this;

Map size increased to 30km. You've got a brigade of combat power at your disposal. H-Hour is set. The brigade's direct support artillery battalion is settled into their AMAs, a few kilometers behind your FLOT. Further behind them is the artillery pushed down from division; a platoon of MLRS, and 2 Batteries of 155mm settle into their PAAs. The plan is simple, the artillery from division is going to begin by interdicting all crucial known targets in the objective area during initial movement to contact, and when finished, relocate and shift priority to counter-battery. Meanwhile the direct support FA battalion's batteries and the maneuver battalion's mortars are free to hit targets of opportunity and provide quick smoke during the brigade's movement to the objective/s.

Enemy artillery starts hitting you. The division artillery, having finished firing their initial prep and relocation are free to conduct your counter-battery fight. Red muzzle flash icons begin to appear in the rear of the enemy's sector. You plot your fire missions on the enemy muzzle flash contacts and hope the enemy hasn't relocated. As the fight drags on you start to see palpable effects of your counter-battery efforts manifesting in the form of diminished enemy artillery activity. You've maintained strict fire and move discipline and your own artillery remains strong. Slowly you're able to take and hold ground with less interference from enemy artillery, and your units, despite suffering losses are being provided with additional fire support as the need for counter-battery diminishes and your MLRS and additional 155mm batteries are able to shift priority to general support of your local critical fire support tasks. Your troops may be weakened but they're being hit less and what they've lost in manpower and equipment they've made up for in supporting fires.

The game ends. You open up the completely re-designed AAR complete with stats for all units, and breakdown of EKIAs by unit type, and start digging into the minutae. You analyze the effects and make your determinations for the future. "Hmmm... looks like my counter-battery 155mm howitzers didn't kill much, should have been massing on their targets instead of firing by battery. MLRS crushed it, I'll be sure to beg division to provide me a battery next time. My bombardment of "Objective Gettysburg" attrited the defending forces by ten percent, giving 2nd Battalion the overmatch they needed to successfully assault." Etc!

That's the future I'd love to see. Tell me that wouldn't be glorious!

ORIGINAL: Artillerist
@Exsonic: Imagine this;
Map size increased to 30km. You've got a brigade of combat power at your disposal. H-Hour is set. The brigade's direct support artillery battalion is settled into their AMAs, a few kilometers behind your FLOT. Further behind them is the artillery pushed down from division; a platoon of MLRS, and 2 Batteries of 155mm settle into their PAAs. The plan is simple, the artillery from division is going to begin by interdicting all crucial known targets in the objective area during initial movement to contact, and when finished, relocate and shift priority to counter-battery. Meanwhile the direct support FA battalion's batteries and the maneuver battalion's mortars are free to hit targets of opportunity and provide quick smoke during the brigade's movement to the objective/s.

Enemy artillery starts hitting you. The division artillery, having finished firing their initial prep and relocation are free to conduct your counter-battery fight. Red muzzle flash icons begin to appear in the rear of the enemy's sector. You plot your fire missions on the enemy muzzle flash contacts and hope the enemy hasn't relocated. As the fight drags on you start to see palpable effects of your counter-battery efforts manifesting in the form of diminished enemy artillery activity. You've maintained strict fire and move discipline and your own artillery remains strong. Slowly you're able to take and hold ground with less interference from enemy artillery, and your units, despite suffering losses are being provided with additional fire support as the need for counter-battery diminishes and your MLRS and additional 155mm batteries are able to shift priority to general support of your local critical fire support tasks. Your troops may be weakened but they're being hit less and what they've lost in manpower and equipment they've made up for in supporting fires.

The game ends. You open up the completely re-designed AAR complete with stats for all units, and breakdown of EKIAs by unit type, and start digging into the minutae. You analyze the effects and make your determinations for the future. "Hmmm... looks like my counter-battery 155mm howitzers didn't kill much, should have been massing on their targets instead of firing by battery. MLRS crushed it, I'll be sure to beg division to provide me a battery next time. My bombardment of "Objective Gettysburg" attrited the defending forces by ten percent, giving 2nd Battalion the overmatch they needed to successfully assault." Etc!

That's the future I'd love to see. Tell me that wouldn't be glorious!

Of course, your idea is dream of all wargamers who wish to enjoy hypothetical cold war in computer. I'm sure that it will be too glorious so that I will need to change my fully-wet pants every 30 minutes, I'm really serious. [:D]

But, for current AB, those ideas require too much things to implement. Advanced & detailed AAR, accurate description of formation and ORBAT including artillrey units... I think those are in the list of dev's future work but it will take a lot of time and resource to implement.
For example, I really want to see accurate description of formation and tree-like realistic order of battle like other computer wargames. (FPC or Command Ops 2) This will enables the differentiation of corps/division/reginement/brigade artillery units, and this will enables to better comtrol of company in this game, separating platoons from company. But currently in AB, concept of formation is very abstracted for easier coding. Fixing this will require huge amount of time and resources.
https://steamcommunity.com/app/1089840/ ... 310654481/

Well, sort of. When the system was made, there was few factions and only 1987 so company formations usually had just 9 or 12 vehicles. The idea was to get 20% point discount to offset worse coordination.
Ideally, the company should be made by listing platoons and sections rather than units, but it is a significant rework of the code and database. Plus the addition of some sort of Company AI behavior to coordinate different platoons as a part of a parent formation.

I think this was not a good idea to start in this way, but current AB is already designed way it is. Same goes to replay and AAR. Full replay like Eugen's Wargame franchise, or at least simplified replay using NATO icons for all unit types (SB Pro replay) + AAR & kill list like Eugen's Wargame or SP Pro style would introduce this game much much bigger sense of rewarding and immersion.

Unfortunately, it will take a huge effort to change this core of the game. So I think if we want to see those it will take really really long time. That is why I'm saying it would be better to start one by one, small by small. I also admit that my idea of "FEBA" would not be easy and will take a lot of effort, but I think those might be a doable within current AB's core engine and frame.

But again, don't get me wrong, I do wish to see such crazy and dramatic battle of hypothetical cod war. To my knowledge, there is no PC wargame for ground-battle oriented which could satisfy all of people like you and me in current market, isn't it?

- Using graphic of real units, not icons. Preferably 3D but 2D is fine.
- Proper & realistic & historically accurate formation and ORBAT. But allow players to make their own battalion / regiment / brigade size formation and ORBAT (in realistic fashion) and save such formations.
- Realtime or WEGO turn control (Current AB's round mod is also a good idea IMO. )
- Massive scale map which depicts 15km x 15km zone or wider.
- Ability to depict large scale battle, brigade or division scale if possible.
- Stick to historical accuracy.
- MP available.
- Detailed AAR and replay with time control of reverse and forward.
- Easy modding and modding support.
- Easy but realistic custom scenario and campaign builder.
- Dynamic and various mission objectives and battle types.
- Realistic engineering feature including bridge build and bridge detonation.
- Strategic arsenal with political consideration, like chemical, tac-nuke.
- Command delay and degree of communication strength.
- Realistic inter-unit information sharing.
- Proper description of recons, SF teams and light infantry, and ability to deep-behind-the-line operations for those.
- Depiction of many layer as possible, EW + ELINT + SIGINT, artillery war and CB, battlefield radar, and realistic thermal - smoke dyanmics and etc...

Such thing will be holy grail of PC wargame for tank/ground battle of hypothetical cold war scenario. Of course there should be abstraction and simplification, but covering of those features with proper abstraction would be enoufh for me, as we cannot 100% implement "literally everything" in game. But I never saw anything satisfy all of my wishes so I'm trying several different ones...

AB covers some of my wishes, but not enough. But I think devs of AB really try to improve as quick as possible even with their low manpower issue, which I really like, so I expect we will see better future for AB, maybe... and I wish AB fulfills my dream, at least for some from my wishlist. [:D]

ORIGINAL: ChortleBuffer
exsonic

I wonder if the CB enthusiasts will be able to agree on a particular mechanism. You seem to be having fun discussing it, and more power to you.

I hope there will be an option to (a) turn the feature on/off (b) automate the process if it doesn't interest a player.

CB is not difficult mechanism to implement, it is just matter of choice. I'm just brainstorming and providing idea to devs but it is dev's call to choice one and I have no power to do anything.

I already listed reasons of why CB should be implemented in AB. I believe any "historically accurate" PC wargame for cold war or modern battle should implement CB of artillery. Impact of artillery on battleground is immense, CB will introduce additional tactical layer to this game and will balance artillery. I believe this concept is just too important and crucial to ignore in the name of simplification for the description of cold war or modern battlefield, so, unfortunately from this point you and my opinion will be parallel. Of course you have right to have different opinion from me.

But maybe automation of CB might be possible. I think my FEBA idea + automation of artillery control (like helicopters) will enable some sort of automation for CB but this will depends on devs.

@exsonic
I can only imagine that detailed AARs must be tough for AB, otherwise we'd have them already, but for whatever reason; Steel Beasts Pro PE, Flashpoint Campaigns and Combat Mission all manage to both show indirect fire kills, as well as doing a better job of breaking down the actual data than Armored Brigade. The report file generated for steel beasts is incredibly in-depth, and is the gold standard in my opinion. Flashpoint Campaigns does a nice job of breaking down the stats by units and target type (including artillery and air support). Combat mission lists kills by off-map units to the Forward Observer's that called in the individual missions. Something about AB though, when you tic that 'indirect fire only' box in the database prevents the game from tracking killed targets.

As far as complexity of the mechanics behind on-map counter-battery; in the database there's a box for muzzle signature, which I imagine influences the possibility that a muzzle flash icon will appear in the absence of actually spotting a unit that's firing. In my quest to model a simple counter-battery function on my own, the logical path has always seemed to jack up that value for on-map fire support resources, ergo, every time a howitzer for example fires, it triggers a muzzle flash icon. Never had any luck though. Maybe I haven't set it high enough, maybe there are other limiting factors.

I would suggest for on-map counter-battery it would be better if Juha could implement a system that detected the “tracers”. I think, knowing the program and the programmer, it could be accomplished. Plus being able to do that could lead implementation of Active Protection Systems, necessary for eventually bringing the database into the 2020’s. (😁Plus holy crap it’s almost 2020!!)

ORIGINAL: Artillerist
@exsonic
I can only imagine that detailed AARs must be tough for AB, otherwise we'd have them already, but for whatever reason; Steel Beasts Pro PE, Flashpoint Campaigns and Combat Mission all manage to both show indirect fire kills, as well as doing a better job of breaking down the actual data than Armored Brigade. The report file generated for steel beasts is incredibly in-depth, and is the gold standard in my opinion. Flashpoint Campaigns does a nice job of breaking down the stats by units and target type (including artillery and air support). Combat mission lists kills by off-map units to the Forward Observer's that called in the individual missions. Something about AB though, when you tic that 'indirect fire only' box in the database prevents the game from tracking killed targets.

As far as complexity of the mechanics behind on-map counter-battery; in the database there's a box for muzzle signature, which I imagine influences the possibility that a muzzle flash icon will appear in the absence of actually spotting a unit that's firing. In my quest to model a simple counter-battery function on my own, the logical path has always seemed to jack up that value for on-map fire support resources, ergo, every time a howitzer for example fires, it triggers a muzzle flash icon. Never had any luck though. Maybe I haven't set it high enough, maybe there are other limiting factors.

I guess AB's code is not ready for such full scale AAR which we are seeing from other examples. I also do wish those, and this will depends on dev's schedule.

In somewhere, I read, in AB, recon helicopters (at night) can detect muzzle flash from enemy mortars if recon chopper is not that far from the mortar position. But I also never tried those options before.

ORIGINAL: 22sec
I would suggest for on-map counter-battery it would be better if Juha could implement a system that detected the “tracers”. I think, knowing the program and the programmer, it could be accomplished. Plus being able to do that could lead implementation of Active Protection Systems, necessary for eventually bringing the database into the 2020’s. (😁Plus holy crap it’s almost 2020!!)

Glad to hear that news, and I also believe all in-map artillery would be the ultimate solution for everything. Regarding your "tracer", I guess this will very looks like Eugen's Wargame style, is this correct? I wish if there is a way to deflect the quality of CB radar and each army's doctrine (ex: possible arty position icon size, renewal time frequency of possible arty position, etc). It would be also possible to comment cold war artillery doctrine in manual or something to suggest players. However, those idea might make game too complicated... So, I'm OK with "Wargame" type solution.

Good news about APS!! This would be a great game changer for any 2015+ games. But there are more things to be implemented for modern battlefield... Well, I wish they share us their road map, so that players would know what could be expected for future.

I don't think code is unsuitable, it is just that we never thought about implementing such a detailed AAR. It is more of work on UI than on engine itself.

Regarding on-map artillery, I know what you two wicked guys are up to! You want bigger maps, because current scale is not suitable for ranged weapons over 15km. [:)]

Would it bring easement if in the AAR window next to the 'Lost' number there was (Art: X) to show the number of casualties caused by artillery/mortars (if there has been any)?

@veitikka it absolutely would bring easement!

ORIGINAL: Artillerist

@veitikka it absolutely would bring easement!

We experimented with different UI solutions, but in the current simple AAR view it would look very out of place to have the artillery kill numbers crammed there. I think they will need to wait until we have a more detailed AAR mode in the future.

@veitikka This brings me much sadness! I'm holding my North Africa Mod hostage till we get movement on this!

ORIGINAL: Veitikka
We experimented with different UI solutions, but in the current simple AAR view it would look very out of place to have the artillery kill numbers crammed there. I think they will need to wait until we have a more detailed AAR mode in the future.

If AAR screen is not possible, how about just showing artillery kill list from OOB screen only?

It would be great if you could include broad "artillery" inside OOB.

If that is not possible, then would it be possible to regard all artillery kill as HQ kill (this option is what FPC-RS using) and show all artillery kill to the player HQ's score or the most top HQ's score? I mean, inside OOB screen.

I really dont care if I see kills by tanks or art, even if I understand the point. CB is a much more desirable feature to make the game more realistic, next would be different types such as light, med, heavy and MRL/MRLS of different types

I would prefer to keep artillery abstracted as much as possible. I think that as the combat commander on the ground at the level the game is played, you are usually not moving artillery or ordering counter battery fires. You are usually just calling for artillery, and it is either available or not and shells either arrive or don't, and you have little direct control over that. I could see artillery support assets being better defined. I can see a chance of not receiving request artillery support put into the game. I can see other abstractions. I would rather not be moving artillery around on the screen or fighting the artillery counter-artillery battle myself.

ORIGINAL: jwarrenw13
I would prefer to keep artillery abstracted as much as possible. I think that as the combat commander on the ground at the level the game is played, you are usually not moving artillery or ordering counter battery fires. You are usually just calling for artillery, and it is either available or not and shells either arrive or don't, and you have little direct control over that. I could see artillery support assets being better defined. I can see a chance of not receiving request artillery support put into the game. I can see other abstractions. I would rather not be moving artillery around on the screen or fighting the artillery counter-artillery battle myself.

I think movement of artillery can be abstracted and automated even when they are visualized on the map. I guess it might be also easier for devs to use rotational wing control model for artillery units:
- 1) Set 3~4 firing positions.
- 2a) Set frequencies for firing and maneuvering for each artillery platoon / company.
- 2b) Or let players decide when to move among firing positions for artillery platoon / company, just like gunships in this game.
But this requires larger map size. 20km x 20km or 25km x 25km. If such huge map is hindered due to game speed or calculation amount, then my FEBA idea would be good too. This way, artillery units can be modeled and visualized in here, but player would have minimum burden for artillery control. This way, current artillery support command box still could be used.

But this might depends on the doctrine. Artillery units are trained to
1) Halt the move on the road
2) Prepare and fire even in the middle of the road,
3) Fire, and move full speed again.
So... instead of setting up fire positions, maybe it would be better to introduce "fire" button and "move" button in the artillery support command box, for each artillery platoon / company. In this case, "firing positions" would be the same "BP" like helicopters but just for artillery. "Move" button will initiate maneuvering of selected artillery units (platoon / company) along the road or fastest route. "Fire" button will initiate the set up / aim / firing process for selected units. Target setting of artillery would be the same for current method, player or AI draw the box on the map.

============================

I respectfully argue that counter battery, and reward / penalty of tactically sound decision regarding counter battery and artillery maneuvering should be introduced in AB. Otherwise game will flow to arty noob style game, and every one will spam recon infantry and huge amount of artillery, depending on terrain and scenario. Current AB AI cannot try this neither counter this, and things will become serious if MP is introduced in the far future.

For CB, Eugen's Wargame style (showing tracer/bin of artillery shell can be used for counter battery) is a good option. However, I wish to suggest that it would be better to use current AB's style, by implementing new icon of "signature of artillery", something similar with current icon for "muzzle flash / sound signature", the circle of yellow dashed line. Maybe it would be possible to introduce something similar for artillery, something like circle of orange dashed line with explosion icon in the center. Let size & position accuracy of such "artillery signature" circle decided by:
1) Distance from the closest friendly units including recon (recon helicopter have a bit more bonus)
2) Sound contact or visual contact of enemy artillery firing.
3) Existence of operating counter battery radar.
4) (If CB radar was operating then) Performance / accuracy of counter battery radar.
Considering CB radar performance, it would be better to introduce specific amount of enemy artillery shot, assuming the minimum enemy artillery amount to triangulate or estimate enemy firing position. We can assume that this "required time / salvo number for CB targeting" would be shorter as technology develops. If we cannot find any technical data sheet for such "required time / salvo number", I insist that it should be OK to assume those numbers for this game, as we will never going to get classified data.
This "time delay for initiation of CB fire" can be modeled as delayed appearance of "artillery signature" circle icon, assuming the time requirement for computer or FDC to calculate / triangulate the position of enemy artillery. In this case, CB-moded artillery units don't need to wait or delay to initiate CB fire, as such delaying feature is already represented in delayed appearance of "artillery signature" circle icon.

Player or AI can select artillery platoon / company and set them as CB mode. Once the "artillery signature" circle appears on the map (orange colored dashed circle with explosion icon in the center), then let CB mode artillery units engage against them after specific amount of time (this time delay can be set by artillery doctrine or CB radar performance or FDC's estimation based on recon's observation). Let CB fire target the center of "artillery signature" icon. Let player/AI set the size for CB fire box. If CB mode artillery units were moving, then they would require more time to set up and fire CB mission. Assuming the communication failure or CB radar malfunction, let's give slight chance of CB-moded artillery units not reacting against "artillery signature".

I guess the use of "artillery signature" circle, similar system with current "fire signature" circle, would have merit of easier coding as two systems are similar in description. But "artillery signature" circle would require CB radar data part, but I think this should not be terribly difficult for Juha if enough time is given (I trust you [:D]). But finding or estimating possible data for artillery control, maneuver, fire preparation time, aim time, etc... would require some book reading or data searching.

============================

But again, I'm also OK with full control of artillery units (I enjoyed this option during Eugen's Wargame franchise experience). I'm just suggesting something for the option of "indirect control" of artillery units.

Regarding minimum number of artillery for control, how about forcing one section as the minimum arty unit? Currently in AB, inside the artillery fire control box, player/AI can manage artillery guns one by one, by each individual gun level. I'm not sure if this is correct doctrine. If AB could make this "possible minimum artillery units for control" as section level, it would be easier to code and describe the artillery operations.