Culling Strike not killing at 10%

I've noticed that mobs that get hit below 10% aren't killed sometimes. Could be lag, could be that 10% doesn't graphically match up on the life bar. Somebody told me that the amount of damage you do matters. I don't understand how it would, so I just want to make sure they're wrong. Like he said that if a mob is at 10%, and you hit him with a tiny hit, it may not kill them. I thought that's the idea though.

I've noticed this thing too, when I was trying to do the last hit on elemental resistance rare with very low spell damage Arc + Culling Strike + Rarity + Quantity.

Probably lag. It definitely isn't damage related, because even with ancestral bond you can pick stuff off at 10% with power siphon.

Maybe you were outa mana and it was a default attack? Can happen with these super resist mobs.

That happened to me - I switched weapons when equipping gems, and didn't realise that power siphon had defaulted back to 'default attack'. I was wondering why power siphon wasn't culling stuff, until I realised I was just using the default attack!

I'm using Firestorm, so that's not it.

I actually removed Culling Strike, and noticed that it's even worse than I thought; an enemy will be at like 7% life, and I kill them with the next hit. So maybe not even Culling Strike doing it when they die after that next hit. Dunno, but not using it anymore.

I was using culling strike with firestorm over the weekend and noticed no issues. The mobs get gibbed at around 10%. And when I took the gem off as I shuffled skills around and lost a green slot for firestorm, it stopped killing mobs at around 10%. It was a noticeable difference between having culling strike on firestorm and not having culling strike on firestorm.

Be sure you dont have two firestorm gems or something, with one being unsupported by culling.

The damage is only relevant given the order of mechanics. You'll do the damage, then the game checks to see if the enemy is below 10%.

I've noticed this. It's probably a sync issue.