Gun Accuracy Question

[Tom_Holsinger]

What are the factors which Gun Accuracy models? I ask because accuracy per se is obviously only one of those. Rates of fire have to be involved too, because those varied so much from one gun to another - the American 5" 38 caliber DP gun had a firing cycle of 3-4 seconds while battleship main batteries were a minimum of about 30 seconds.

And fire control also made an enormous difference, particularly for the U.S. Navy where the Mk 37 fire control director made it possible for ships with it to to maneuver wildly (such as in "salvo chasing") to throw off enemy fire control while maintaining accurate fire on the enemy themselves. This was critical in the daylight battles of the Komandorski Islands and Samar.

I would particularly like to know if the WITP-AE definition of gun "accuracy" includes factors for fire control equipment.

[JWE]

ORIGINAL: Tom_Holsinger
What are the factors which Gun Accuracy models? I ask because accuracy per se is obviously only one of those. Rates of fire have to be involved too, because those varied so much from one gun to another - the American 5" 38 caliber DP gun had a firing cycle of 3-4 seconds while battleship main batteries were a minimum of about 30 seconds.

And fire control also made an enormous difference, particularly for the U.S. Navy where the Mk 37 fire control director made it possible for ships with it to to maneuver wildly (such as in "salvo chasing") to throw off enemy fire control while maintaining accurate fire on the enemy themselves. This was critical in the daylight battles of the Komandorski Islands and Samar.

I would particularly like to know if the WITP-AE definition of gun "accuracy" includes factors for fire control equipment.

Not a simple question to answer Tom. Acc parameter is used in many different contexts (SurfCom, AirCom, LandCom, ASWCom, ...) so simply saying it does THIS, might lead people to optimize its value for THIS, which would have a very deleterious effect when the program fetches the value for THAT.

Because of its multiplicity of use, there is no "historical" basis for calculating a specific value. Best to say it represents what the code uses. Please don't be confused by a "text string" name next to an editor data field. Just because "name" is something, doesn't mean that "value" is always that something. We had to name the data field something, and in a wargame, "accuracy" looks better than "parameter-5", but in this case, you should probably think of it as "parameter-5".

[Tom_Holsinger]

That well answers my question, thanks. You had to give a game variable some name.

Please consider compiling a list of things players should not edit, starting with A for Accuracy.

[JWE]

ORIGINAL: Tom_Holsinger
Please consider compiling a list of things players should not edit, starting with A for Accuracy.

We are in the midst of a major analysis of 'acc' parameter, among others, for Da Babes mod. Looking at better optimizing for surface combat, without deleterious effects on AAA. But, many parameters "play" together, so it is not a simple matter of just adjusting one number to suit our fancy. The edge of the cliff lays in that direction.

However, understand that modders want to "mod", so as soon as we get the math right, will publish our best take on where the "sweet spot band" is, and give an indication of where the edge of the world lays. Ya'll can mod to your hearts content within a relatively simple "rule".

Can't do this, just now, because there may be some tweaks for a patch that might cause our paradigm to be skewed, with respect to the latest code algorithm, but will report as soon as the smoke clears.

Sorry, but no peeks under the hood. Ya'll will have to be content with derived boundary conditions and response relationships and vectors. But I believe these will be wide enough and explained sufficiently well, that a legitimate modder can have quite a bit of fun.