How accuracy works in SD44 - explained

[77Hawk77]

I was looking through the game files of SD44 with the mod tools to try and figure out how the accuracy works in this game. And found it to be quite obvious really, but thought I'd share the modifiers and values on here, so that people who don't know can have a better understanding of how accuracy works in this game. Don't lynch me if this isn't 100% right, the explanations for the files are in French, but I am pretty sure about this.

Firstly the accuracy values in a graph, because I love graphs.

Next some more visual aids.

I hope this helps if someone was confused.

- Some people have already come up with some good questions, once if I or someone else finds a really good answer to this I'll put it here in the OP so that you don't have to go through the thread.

[Q&A]
"How does stress affect accuracy?"

Extracted from DamageLevels.NDF:

10% Panicked = -1 to accuracy
20% Panicked = -2 to accuracy
30% Panicked = -3 to accuracy
40% Panicked = -4 to accuracy
80% Panicked = -4 to accuracy and morale = 0 = routing

 

[Death6]

This is exemplary work. Amazing stuff thank you!

 

[Max_Damage]

Thanks a lot i was looking forward to a guide.

 

[TulipSA]

Do you know the effects of suppression on accuracy? I'd also heard that accuracy is capped by veterancy, is that in the files or only found experimentally?

Aside, do you know the HE damage table or how to convert the in-game ROF to a meaningful one (yes I know it's ammunition by ammunition)? I knew these both in RD.

 

[Max_Damage]

One correction: i think a single star of veterancy doesnt give any acc bonus.
proof: http://imgur.com/a/6UkZX

I think that 2 stars give 1 bonus accuracy only.


Also, by consecutive hits you probably mean consecutive shots? even if they are misses.

 

[Max_Damage]

Also, worried seems to incur a -3 accuracy penalty. Proof: http://imgur.com/a/WwMEm

Being on the move also gives a penalty (for those fire on the move weapons ie vehicle MG, smg and autocannons). I think it is -2 or -3.

Also, cyhance to hit can be 0% with penalties and i have seen it.

 

[CyberianK]

So this is conformation there is 100% hit chance?
All these peoples complaining their flanking veteran tanks missing the Panther from closest distance and behind was all proven BSthen right?

Minimum accuracy 5 gun, vet 2 and close distance +3 means you can't miss because 2+10=12.
Which means you can remove luck from hitting and its only luck on the penetration then?

 

[77Hawk77]

Do you know the effects of suppression on accuracy? I'd also heard that accuracy is capped by veterancy, is that in the files or only found experimentally?

Aside, do you know the HE damage table or how to convert the in-game ROF to a meaningful one (yes I know it's ammunition by ammunition)? I knew these both in RD.

I do not know for sure, but I believe that each level of stress gives you a -1 acc. But I did not find that exact modifier yet.
I'll try to look into stress and veterancy and see if i can answer those questions, I also don't think the HE and ROF tables are even available to modders yet. It's very strange but only some very general things are a modable at the moment.

So this is conformation there is 100% hit chance?
All these peoples complaining their flanking veteran tanks missing the Panther from closest distance and behind was all proven BSthen right?

Minimum accuracy 5 gun, vet 2 and close distance +3 means you can't miss because 2+10=12.
Which means you can remove luck from hitting and its only luck on the penetration then?

I am 90% certain that 100% accuracy is possible. I don't see a single line of code which limits the maximum cumulative accuracy. I'll even say as much that it shouldn't be hard to get to. With 5+ base acc, +3 from range and +2 from consecutive hits, a Panther should have 100% hit chance at point blank range after hitting twice and not penning, just like you say. If veterancy counts as + 1 acc, which is not confirmed, 100% accuracy should be possible at 500-600 meters, maybe even futher if command tanks also confer accuracy.

Also, worried seems to incur a -3 accuracy penalty. Proof: http://imgur.com/a/WwMEm

Being on the move also gives a penalty (for those fire on the move weapons ie vehicle MG, smg and autocannons). I think it is -2 or -3.

Also, cyhance to hit can be 0% with penalties and i have seen it.

Sadly what it shows you ingame isn't always how it works, the ingame sometimes show wrong values on both cards on UI, at least in my experience from wargame. If you want to find real proof, you should opt into the modding version and find the code for it, it will be a lot better for understanding.

 

[nande]

Sadly what it shows you ingame isn't always how it works, the ingame sometimes show wrong values on both cards on UI, at least in my experience from wargame.

could you give some RD examples.

 

[77Hawk77]

could you give some RD examples.

The ROF in wargame red dragon, doesn't show the Rate of Fire for autocannons, but the amount of rounds in a burst IIRC. Same with machine guns and other hand guns. The accuracy of certain units was shown to be wrong occasionally too. If you read the patch notes for red dragon and go far enough back, you'll see several examples of them fixing the unit cards to show the reality. Which means that unit cards aren't directly connected to the values of the game.

 

[Sharkey Ward]

The only part of your table that MIGHT not be wrong is the range part, and only the positive modifiers for it, everything else is a severe misrepresentation of the mechanics in the game. You even got the final accuracy on your examples wrong.

 

[nande]

Which means that unit cards aren't directly connected to the values of the game.

no, this was never an issue in RD. At worst we had overly broad categories and amalgamations of stats. Perhaps CIWS quality was manually entered, but I cannot think of anything else. What I don't understand is why you mentioned the UI.

But disconnected values do appear to be an issue in SD, given that Pak AP bug earlier in beta (differing numbers on the unit card and icon).

 

[77Hawk77]

no, this was never an issue in RD. At worst we had overly broad categories and amalgamations of stats. Perhaps CIWS quality was manually entered, but I cannot think of anything else. What I don't understand is why you mentioned the UI.

But disconnected values do appear to be an issue in SD, given that Pak AP bug earlier in beta (differing numbers on the unit card and icon).

"FIXES:
- RoF display bug fixed on tanks with autoloaders"

I don't know how you interpret this, but I understand it as meaning that the RoF displayed wasn't the actual rate of fire. That is not that many patches ago, and it's not the only time they fixed what the unit cards show. If you go back to early patches there was more like this.

 

[nande]

"FIXES:
- RoF display bug fixed on tanks with autoloaders"

I don't know how you interpret this, but I understand it as meaning that the RoF displayed wasn't the actual rate of fire. That is not that many patches ago, and it's not the only time they fixed what the unit cards show. If you go back to early patches there was more like this.

unit card values were being rounded down on units with autoloaders after a change that slightly increased their time between bursts. The bug didn't have anything to do with use of unrelated numbers, but rather with them being truncated for display.
What are your issues with the UI, though. You clearly differentiated it from unit cards, and considering the context of the conversation, were you implying that the CTH displayed on mouseover/weapons isn't correct?

 

[77Hawk77]

unit card values were being rounded down on units with autoloaders after a change that slightly increased their time between bursts. The bug didn't have anything to do with use of unrelated numbers, but rather with the effects of truncation.
What are your issues with the UI, though. You clearly differentiated it from unit cards, and considering the context of the conversation, were you implying that the indicated CTH in both games isn't right?

I don't want a longer discussion with you, the unit cards in RD didn't always match, it's what I said, I gave an example. If you want anything else you can read the full changelog.

 

[nande]

in other words you're dismissing ingame proof such as that provided by Max_Damage just because you've glanced at snippets of code that aren't documented and that you've not written. Have you tried modifying it to see its effects, at least.

Sadly what it shows you ingame isn't always how it works, the ingame sometimes show wrong values on both cards on UI, at least in my experience from wargame. If you want to find real proof, you should opt into the modding version and find the code for it, it will be a lot better for understanding.

it's this overly authoritative approach to explaining mechanics that annoys me so much and perpetuates poor understanding.

 

[77Hawk77]

in other words you're dismissing ingame proof such as that provided by Max_Damage just because you've glanced at snippets of code that aren't documented and that you've not written. Have you tried modifying it to see its effects, at least.
it's this overly authoritative approach to explaining mechanics that annoys me so much and perpetuates poor understanding.

Then instead of nagging, why don't you contribute? If you make a better model i'll be happy to include it.

 

[Lurtz]

interesting.

 

[TulipSA]

I do not know for sure, but I believe that each level of stress gives you a -1 acc. But I did not find that exact modifier yet.
I'll try to look into stress and veterancy and see if i can answer those questions, I also don't think the HE and ROF tables are even available to modders yet. It's very strange but only some very general things are a modable at the moment.

I'm using an old RD modding tool made by power crystals, I'm in TAmmunitionDescriptor and can see TempsDeVisee, TempsEntreDeuxSalves, TempsEntreDeuxSalves_Min, TempsEntreDeuxSalves_Max, NbrProjectilesSimultanes, NbTirParSalves, and AffichageMunitionsParSalve, which I THINK is everything we need. What I don't have is the coding knowledge to dump it all into one big table, or the wherewithal to manually do it all.

No idea about the HE.

 

[Max_Damage]

This guide leads to an interesting conclusion.

Having 6 accuracy 1000 m gives a better chances to hit compared to 5 acc 1200. Yeah Pak40 is more accurate then m5 76mm even with less range.