Profile of Vipper

Let me clarify something:
1) Mortars and similar units as far as I know do not go through accuracy checks at. For instance the pack howitzer has an accuracy of 1 and it would always hit if did go trough accuracy check.

As I already have pointed outed different weapons types like "ballistic", "explosion", "Big explosion" and the projectiles behave differently.

2) Focus fire is weapon property and not squad property and it does allow the damage to spread to more than one model. You can clearly see this with kubel that damage more than entity when it fire.

3) Small arm do not have projectiles because it would really mess up the engine to calculate the thousand of round fired in 4vs4 game. They can damage world objects PTRS destroying cover is prime example but that was done by the engine without a projectile being involved.

3) Shared veterancy is gained when the unit near gain veterancy (as far as I know) and since the target unit gain veterancy for taking damage the unit with shared veterancy would also gain.

The shared veterancy does not work with all units but specific units like infatry, hmg, mortars. Else units with shared veterancy near a tank would gain XP like crazy

4) Think faust bug is improved but not fixed completely.

Hope this helps.

That's what I thought, honestly. "hit" shots apparently ignore collision calculations in the same way as hitscan bullets do, I think the only functional difference between a rifle bullet and a tank shell is that a tank shell can still do damage on a "miss". (Though "missed" rifle/machinegun bullets can damage terrain such as wooden fences/carts/etc... so perhaps this isnt strictly the case either? Is it possible that a "missed" bullet can still hurt a model if it intersects with it during its scatter? Has anyone tested a 0% accuracy MG42 against a point-blank model? If this is the case, that sort of changes things dramatically as far as unit positioning is concerned.)

There is no collision with infatry entities even for weapon with projectiles.

Small arm do not have a projectile to begin with.

Some weapon can hit entities via another mechanism available to HMG/ST44/BARS... called "focus fire"

Artillery doesn't actually target anything, so that's sort of to be expected, isnt it? Artillery is basically a glorified "Attack Ground" from an invisible unit, to my knowledge, so there's no "hit" calculation for it to bother with.

I was not referring to barrages.

Mortar shots, scott shots..., aim at things but can not "score" hits they can however score collision hits.

I tried this on the test range map with cheatcommands and a 100% accuracy shot will go through other vehicles and terrain*.

I basically put a JPIV to shoot a JT, while there were a bunch of other JTs in the middle.
In regards to terrain, you know how if you delete a base building the ground below sunk? Well i just parked a JP4 so it was basically below ground.

Seem someone beat me to the test and things where as I suspected.

Great work, well done.

The only other similar case I know is faust bug where the projectile should hit the target and collides in process and even then I have not checked it it actually uses accuracy check.
(maybe this is something worth looking into as a fix to faust bug)

From what I recall, flamers actually DO use a projectile. Their collision_type is tp_throw if I recall correctly, which can travel through most objects in the game with some exceptions. Perhaps those cliffs are one of them? Any map makers know the exact name of those in the editor?

But if the weapon has an accuracy of 1 why would it not hit in the accuracy check?

Even if there is a projectile why would it create an issue unless is somehow connected with the faust bug?

There is also this that might relevant:

"Projectile Tuning

Modified the behavior of tp_homing_inf projectiles to not collide with a number of world objects such as bushes or light fences. In effect, this change will increase the strength of any weapon using this projectile type. This will impact the reliability of hand held AT like the Bazooka and flak weaponry like the Ostwind or 251 Flak Half-track. These weapon types will no longer continuously hit world objects, thereby missing their targets."

I mean the way CoH2 works you can't exclude anything, but I'd still go for the easiest solution.

I have seen this "no damage" issue regularly, I think I remember seeing it even in tournament casts. From what I know it does not depend on elevation, nor on cover, formation or whatnot. It usually got fixed once the flaming guy got two steps closer.

I think it has to do with some weird range calculation and flame damage, that the game thinks the flamer is in range so it stops walking while it actually is only at the border.
I don't know how exactly flamer damage is calculated, but there might be some kind of random chance to it. But this is just speculation.

As I said, walking just a little closer fixes the issue for me.

As far as I know flamer work like most small arm weapon and in order to fire the entity has to be in range and it goes through an accuracy check although the weapon has higher accuracy than most weapons.

The weapon simply has an AOE damage in addition.