Locking helps with preventing collisions, but honestly the issue is still always communication. Why are people even touching files they shouldn't be touching?
Meanwhile perforce is a pain for code heavy projects and requiring a central perforce server. Git works great there.
The issue is neither is a silver bullet for the others workflow and needs, and they both suck horribly for mixed code and binary asset workflows.
That's not even considering cost.
Meanwhile film studios generally prefer keeping the considerations separate and using symlinks or URI to their data store and that works really well. But that doesn't work great for remote workflows.
So again, I think you're applying a very p4, game centric view to this. There are lots of different use cases and team structures that none of these version control systems are able to address in their entirety.