Ce sujet est fermé
In what ways is WASD not responsive enough? The inertia of starting moving? I'm not sure why would hold LMB+RMB alleviate this when at first glance it seems like it wouldn't be much different than holding LMB+RMB = holding W.
Just curious if the issue is something else and that LMB+RMB wouldn't innately fix that if that other issue wasn't addressed.
Hi Allan, I'm late back to this, so if I may:
I've played, now, on easy, a mage with the controls as they are (although see up the thread as to how I've rebound my keys).
I note your question to Brogan re: what is required. You mention you're a WASD player, and, essentially, I am as well--and yet I still found the controls clunky. I have, however, noticed I'm "getting used" to the controls (perhaps as you have) and this would make it easy to forget how good the DA:O controls are in comparison. If may suggest? Go and play DA:O for an hour or so. Remind yourself. I am finding that I am forgetting to use my mouse in WoW, now that I've played DA:I for a while. (Not Good: I prefer mouse movement for some raids and PvP Arenas so that I can use my hotkeys and keyboard for attack macros, as does my son. Other players I know prefer wasd movement in arena and point-click abilities. They don't have oceanic lag--I do. But, see, that's the point: choice. Always good. My way is not your way, and all that, kum-ba-yah).
Even as a WASD player, I like the option of using the 2 mouse keys. Gives my left hand a rest. Allows me to use my hotkeys 1 - 5, tab (which is the select key in WoW, too) with my lefthand, while moving with my right. Means that if I need to move sideways, attack and hotkey, I don't need three hands. It's also easier on smaller laptop keyboards--smaller board = cramping wrist if you use left exclusively for almost everything listed. For most games that I play with the option, I (rather effortlessly, if I do say so myself) switch between both styles of play without thinking too much about it, depending on what I want to do at that time. DA:I doesn't allow this. It's forcing square pegs into round holes, as a result.
But here's why left-right button movement can feel more responsive: Hold mouse buttons, move in direction of cursor, camera orients itself. All automated. With wasd, you're also using the mouse to orient the camera while using 2 or 3 buttons to direct your party. You can strafe using left-right button movement and autoattack and not even need to touch the keyboard. Can't do that with WASD alone. Again, try it in DA:O. It's easier to "see" that way.
Essentially, however, here's my suggestions:
1. It's been said, ad nauseum, but mouse support must improve. (Buttons/remapping). It's not just "point and click", it's also "move to cursor" with l-r button movement that is missing, here (something people have been confusing--perhaps that's clearer?) The ability to run using 2 mouse buttons, click to autoloot (click, walk up to item, loot NOT walk to item, hope you're in the right place, click as it is now--along with the long animation that accompanies each "looting", it makes the simplest of tasks in an RPG--picking stuff up after a fight or opening chests--tedious) with the left button as default, left click to talk to NPCs, right click to see the header of an enemy (rather than attacking out of tactical) and left click to autoattack should be the minimum standard. That is how DA:O and DA2 worked; that is how most RPGs have their setup. And then allow players to remap their keyboard AND mouse in any way they damned well please, as the last 2 games did, and as most RPGs do. Added note: the fact that, in tactical, you use right-click-see, and left-click attack when it is the opposite out of tactical... *insert Mal raised eyebrow WTF here*
ETA: I almost forgot: being able to, say, barrier your party by selecting the ability and then the avatar of the party member/s you want. Please bring that back. Again, on smaller screens, you can't always see your party on the ground when they're, say, behind a dragon (and by "wee screen", I am talking 16 inch lappy, here, I'm not using a notebook!). Simple functionalities, previously taken for granted in this franchise. So missing them. /sigh
2. By "click to move" I think people mean similar, again, to DA:O. For example, I miss, very very much, the ability to select my entire party and left click to run all of them to a specific point in front, behind... wherever. With those little gold arrowy things so you know exactly where everyone ends up. In one click. Essentially, the function is (sort of) now covered by the "disengage" button (tell party to stop attacking and follow) but this is less precise. You can move people, one by one, in tactical, but....geez. That's been covered by others so I won't belabour the point--just add my voice to the whhhyyyyyyy mob. 
3. This has been addressed, as well, but to reiterate: lack of mouse support greatly reduces the ability for anyone with any sort of hand/limb disability to play. You guys have done such a good job at promoting inclusivity in DA:I (I am not one who you will see complaining about all the choices for females for once, or whining about Dorian, who is effing fantastic, or Krem, for example). So the lack of disability support in KB&M seems like an oversight--probably an unintentional one, as I am aware this is being worked on.
4. Tactical camera, especially on laptop screens, with no real zoom up: try it. Especially when those rifts are way up there (like the level 12 one in the Hinterlands and, oh, the one with the first boss. Really. Try it. On a wee screen. You'll understand why I want to hit someone, badly, and not in-game. ;-)
5. UI comments:
a) mages and only 8 spells. [pouty]I hate you guys[/pouty]. I understand you want us to think about choices, blah blah, but it seems to be a bit... I dunno... bloody mindedness for the sake of bloody mindedness. Remember the UI bar you could click and drag across the entire screen in DA:O? It'd take me until Awakening to fill that--even using slots for pots and one to get to herbalism/traps etc--even on a mage. I'm also okay with DA2's bar (which is more console friendly, too, of course). EIGHT spells. Including for specialisations. Whimper.
b ) No. Just that. Only 8 slots.
Another note re: UI: it has been mentioned, by you guys, that you wanted a more "Skyrim" feel to the game. One of the very first things that was "fixed" by users for Skyrim was the effing awful UI. One you've emulated. Not really what you guys meant? :-D
SIDE NOTE: re: crashes. The engine is... um... imperfect, especially for lots of cutscenes, in a game with lots of cutscenes (and the memory leakage is appalling). I'm using the FPS fix so mine will play above 30, which mostly fixed it (although Varric's cutscene, disappointingly, after a certain event which requires you to make a certain choice in which I chose his friend [don't judge me! Alistair was the Warden! Why ohgodsmakerandraste, WHY!!!?], ran at about 2fps even with the fix). A simple line of code added to the startup to overcome the frostbite engine that is so simple it stumps me that this line was not simply added to the game. However, it is also worth noting that every single time I have had an actual "crash to desktop" event, the Origin client has been involved. It spikes to a 100k+ kb useage. Now, that is not a lot, it seems, in the scheme of things--but Steam only uses 40k kb when it spikes and Battlenet is similar. Steam usually runs at about 27k, bnet at 36k--and my entire Windows OS? 36k. Origin runs over 60k even when it is not spiking. Testing, these crashes have occurred whether the Origin client is online or offline and whether my computer is connected to the internet or not (so sending data back and forth is not a factor). I am not saying the Origin client is the problem, but it does seem to be involved. Something to send back to The Powers That Be Patching.
Hope that helps,
Beth. 
Retour en haut
