Questions and observations on CEP
Posted: Tue Aug 14, 2018 8:29 pm
How is CEP supposed to function in CMANO? Do CEP values represent best case or real world? Are there other factors that are taken into account in weapon accuracy besides just CEP? Things like visibility, weather, sea state, deflection, target speed, sensors, etc.
My understanding is that 50% of rounds should strike within the CEP value, 93.7% within 2x CEP value and 99.8% within 3x CEP. Only 0.2% should strike at greater than 3x CEP.
My observations are that at least for some weapons that this is definitely not the case. Using the 76mm/62 OTO Melera Super Rapido DART, DAVIDE, STRALES most impacts are greater than 2x CEP. This weapon is supposed to be a guided projectile. The witnessed accuracy of the DART/DAVIDE is just deplorable, even if it were unguided. With the 76mm/60 China H/PJ-26 (AK-176 Copy) I have seen rounds impact as much as 13.2 nautical miles from the target. I don't even know how that is possible because the weapons range is only 6 nautical miles. First time I noticed this was because I could see rounds impacting on the screen all over the place and then I looked in the message log and all the log entries were for impacts 13.1-13.2nm from the target. In this instance the weapon was mounted on a Type 056 Jiangdao.
If this isn't a bug that needs to be corrected then please help me understand what causes this behavior or what I can do as a player or scenario designer to achieve the published CEP values. Are there any passive or active sensors that may help to improve accuracy, such as laser range finders or weapon directors or fire control radars? These sensors were present on the platforms when this type of behavior was witnessed but I didn't check to see that the sensors were actually active at that time.
Also, at what distance is the CEP value calculated? Is CEP taken from the weapons maximum range or at some fixed distance, for example 1 nautical mile. CEP of 80 meters at a distance of 6nm is bad when converted to MOA but if it is calculated at 1nm then that is just atrocious. Is accuracy supposed to improve at reduced ranges, because I am really not seeing that?
All of these observations were made using v1.14 build 998.10 and database 474.
My understanding is that 50% of rounds should strike within the CEP value, 93.7% within 2x CEP value and 99.8% within 3x CEP. Only 0.2% should strike at greater than 3x CEP.
My observations are that at least for some weapons that this is definitely not the case. Using the 76mm/62 OTO Melera Super Rapido DART, DAVIDE, STRALES most impacts are greater than 2x CEP. This weapon is supposed to be a guided projectile. The witnessed accuracy of the DART/DAVIDE is just deplorable, even if it were unguided. With the 76mm/60 China H/PJ-26 (AK-176 Copy) I have seen rounds impact as much as 13.2 nautical miles from the target. I don't even know how that is possible because the weapons range is only 6 nautical miles. First time I noticed this was because I could see rounds impacting on the screen all over the place and then I looked in the message log and all the log entries were for impacts 13.1-13.2nm from the target. In this instance the weapon was mounted on a Type 056 Jiangdao.
If this isn't a bug that needs to be corrected then please help me understand what causes this behavior or what I can do as a player or scenario designer to achieve the published CEP values. Are there any passive or active sensors that may help to improve accuracy, such as laser range finders or weapon directors or fire control radars? These sensors were present on the platforms when this type of behavior was witnessed but I didn't check to see that the sensors were actually active at that time.
Also, at what distance is the CEP value calculated? Is CEP taken from the weapons maximum range or at some fixed distance, for example 1 nautical mile. CEP of 80 meters at a distance of 6nm is bad when converted to MOA but if it is calculated at 1nm then that is just atrocious. Is accuracy supposed to improve at reduced ranges, because I am really not seeing that?
All of these observations were made using v1.14 build 998.10 and database 474.