I don't have an ATI card, and apparently this doesn't work using nVidia's control panel. I guess you can edit a script to tell the game to turn AA on, but there is some debate as to whether that breaks the TOS or not. No way Bioware would ban people for that anyway...
So my shoulders are beginning to hurt from the awkward angle I sit at to manipulate my keyboard and mouse, so I spent a long time yesterday configuring my gamepad to play this game. It's really fun this way, but I have to reform my habits (skill rotations and stuff) so I made this diagram:
I'm not actually using a PS3 controller, but the buttons are the same, and this is how I best recognize them.
The triangle button is the modifier... holding triangle while pressing one of the buttons activates the quickslot on the bottom row.
I had to add keyboard buttons for the bottom-center hotbar (I used F1 through F12), then used Joy2Key to make my controller button presses send keyboard strokes that correlate with that quickslot. Joy2Key has an option where holding a button temporarily switches your controller configuration to another... so in my case, holding "triangle" remaps the buttons to the F1-F12 keys, or the bottom quickslot bar.
All in all, the only problem is that there are no in-game buttons for "move camera up" and "move camera down". My left analog stick moves forward and backwards, and strafes. The right stick turns left and right just fine by invoking the A and D keys. In order to look up and down, I had to set that axis to press the right mouse button, and move the cursor up or down however many pixels. It works, except diagonals cause me to strafe due to the right mouse button being invoked, along with the left/right axis invoking A and D. I'm basically emulating mouselook.
The solution to THAT problem, is to not use A and D for basic turning, and instead making the right analog left/right axis invoke the right mouse and move the cursor too. It was almost perfect, except that when your right stick hits your deadzone or leaves a quadrant, that rightclick command releases, apparently sending a "mousebutton up" message to windows, interrupting newer "mousebutton down" messages, which results in the cursor moving around the screen for a small moment, and no turning.
The reason I'm still playing this way is that the cursor actually loots for me when the right click releases, inadvertently saving me from having to incorporate some other looting solution.
tl;dr: I push X and I hit with my lightsaber now, like an action game.
Author
