Yes, I've noticed when the killcam once
kept triggering incessantly for 5 times in a row that the killcam seemed to be forcing my arrows downwards, as if they were being fire from a lower elevation than they actually were. I used the .ini tweak to make arrows shoot more accurately with the cross-hair, but I'm suspecting that the killcam might actually disregard the .ini tweak when it fires off.
I'm thinking:
1) You're aiming at an enemy.
2) Conditions have been met that it is a killshot using the current parameters
3) Killcam is possible and so it triggers
4) Killcam uses aiming settings that disregard original .ini tweaks.
5) Killcam arrows fail
Note also I think there's just bad collision detection in a lot of places in the gameworld. Invisible 'walls' and 'edges' that block arrows that should clearly go over the edge. I've tipped my character right over the edge of cliffs, pointing at an angle, with tons of space away from the nearest edge - arrows still get 'blocked'.
Edit: Combination of .ini tweaks + mods would probably cause the miscalculations with arrow killcams might cause all this to happen. I'm using the Closer quivers mod as well, which might be causing miscalculations because the arrows were moved and enlarged by the mod I think.
Edit2: Apparently killcams need auto-aim or something, and if you use a mod that removes it, the killcams actually fail even more because they need the auto-aim to work O_o
Also I can give you the .ini tweak to remove ranged killcams, one sec...
[VATS]fVATSCastingAfterKillDelay=1.2000uVATSRangedPercentSneak=0uVATSRangedPercentGlobal=0bVATSIgnoreProjectileTest=0bVATSAllowNoKill=0bVATSMultipleCombatants=0bVATSForceRanged=0
This
should work to make ranged killcams never happen. I actually use a version that gives me a ranged killcam when possible because I really do like the look of it. Except for ranged magic killcams, they are ridiculously silly.
Also yes, it's actually called VATS XD
Which is funny because I wonder why locational injuries aren't bundled with Skyrim then T.T