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.
May 24 2022
Jan 27 2022
Oct 16 2020
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
with the release of 2.00 assignedTarget seems completely broken
It has not been touched
Oct 15 2020
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
Jun 10 2020
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
Jun 9 2020
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
Jun 8 2020
The chain i'm referring to is the one on the Kart's engine, connected to the back right-hand wheel
May 29 2020
May 10 2020
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
May 10 2016
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