Hi,
Yep, it looks like a conflict indeed... the problem is that a script is defining "Animation" class without a domain and so it clashes with scripts trying to access UnityEngine own Animation Class.
try on a fresh project, with just playmaker and standard assets, if it does not conflict, then it's the urban asset.
Two ways to go about this.
-- contact author of urban traffic to check if he can add domains to his scripts, especially the one where classes are named like unity does ( like "Animation")
-- edit the playmaker action and explicitly call the class by their domain like 'UnityEngine.Animation' instead of just 'Animation', but that's going to be a real pain indeed...
try to delete the offending actions for a start, to see the scope of damage with this conflicts, it looks like only "Animation" is affected, let me know if you get different conflicts as well.
Bye,
Jean