Reposting from discord:

That explains the variability in sync time then... Any chance it can get it like animateSource does, or suggestions to force a sync? (I guess remoteExecing it)

This seems to be related to the magazine being deleted when fired - if the magazine is modified to be deleteIfEmpty = 0; the effect plays

In T154359#2602895, @dedmen wrote:

We're switching from "the target that was last shot at" to "the target we are going to shoot at". I think that fits.

Works for me

In T154359#2602361, @dedmen wrote:

The weapon the unit is using, knows what its told to shoot at.
We could say "If you are told to shoot something, that should be considered target"
That would be doable, if unit has no assigned target, check if its weapon is told to shoot at something and use that instead..

I thought it was in the original post but after re-reading it I seemed to have missed it.

No the way it works is:

class sgun_HunterShotgun_01_sawedoff_F: sgun_HunterShotgun_01_sawedoff_base_F
{
    submunitionConeCoef = -0.5;
};

Unfortunately no luck.

Sorry missed the notification on this one - will give it a shot and report back

To explain what we're doing and why the error is happening:

I did some further investigating into this issue and i've confirmed the real issue is the 'wheel' animation source is whats broken and nothing to do with UVAnimations. Similarly I've found a better vanilla vehicle with the issue.

Did more investigation into it, it's not working as expected in 1.98 aswell - it just appeared to work. In v1.98 assignedTarget only works when the gunner has vision on the target(ie. if the gunner is in a tank turret, it will only update assignedTarget when the turret has turned to face the target) otherwise it remains objNull. Don't think it's weirdness is related to 2.00 so either it got broke earlier or it's always been this way

In T152567#2115522, @BIS_fnc_KK wrote:

with the release of 2.00 assignedTarget seems completely broken

It has not been touched

with the release of 2.00 assignedTarget seems completely broken and getAttackTarget only seems reliable when the AI is actively engaging.
CommandTarget etc will work with assignedTarget but if an AI leader is assigning targets, it never displays them. The previous release has no such issue

Other engine sources Ive tried is door and Reload, I'm pretty sure it's just wheel that's having the issue but I'm not 100% what sources are supported in the config

That's what I did, I used the user animSource instead of 'wheel'.
I tried both setting the user animation from where the vehicle was local and remote and both worked.

I just tried it with a user animationSource and the UV animation (and the physical wheels) works fine

Will confirm that for you, but I'm pretty positive the issue lies with config defined animationsources using 'wheel' as the animationSourcePhase wasn't changing on the remote vehicle

The chain i'm referring to is the one on the Kart's engine, connected to the back right-hand wheel

Here's a video where you can see the issue in a modded vehicle (the vehicle is remote) https://www.youtube.com/watch?v=2gHNuJICGa0

I too can say I was having this issue and it was resolved using the maxmem parameter

This continues to be an issue in 1.50

Sorry for not replying sooner, i can confirm this issue exists in 1.40 stable still.

Haven't tested in dev 1.41 will try that soon

Does this when a medic is using their medkit on someone too