Hi Adam,
I too started out on the PC side researching various engines, and like many other people here ended up with Unity on a Mac. I’m not yet set on what genre I’m going to concentrate on, so my requirements were a little less specific than yours. (For example, it was one reason I decided to not use Torque, since it seemed a little too FPS-biased unless you wanted to do a ton of work.)
In any case, I tried Gamestudio A6 amongst others, and for me some of the biggest advantages of Unity were:
Quick code->test->code cycle. In Unity it’s all in one IDE, and you do some work, hit the play button in the corner to check it out, do some more changes, hit play again, etc. In A6 it was code, build, wait for build to finish, try it out and see the issues (in a separate window), then go back to coding, then build again, etc… Things just flowed much better in Unity.
Same for the asset workflow, I just found things much quicker in Unity in terms of dropping something in a project directory, having it pop up in the IDE, and dragging it into my project to work on.
I also really appreciated the easily available tutorials and documentation that Unity provides. A6 also had a large library of documentation, it just felt a little more scattered and version-dependent, IMHO. (Especially with their recent switch to lite-c)
Those were some of my reaons, but in the end I agree with the prior posters in that trying Unity out is the best and quickest way to see if it’s a “fit” for you. I really enjoy working with Unity, unlike some of the other tools, which just felt a little to much like work for me.
In any case, good luck with your research!
-Eddie