Align to hotkey eve5/11/2023 "Align to" doesn't let you approach ships, at any range.įirst page | Previous page | Next page | Last pageĬopyright © 2006-2022, Chribba - OMG Labs. You don't deserve it, and you will lose it.ö ÔIf you're not willing to fight for what you have in ≡v≡à Àor bug report it under the category "stupid design decisions." Just kill the useless one, curse at CCP and move on. Yes, this was pointed out repeatedly during testing. Yes, the two should overlap, just like it does in the control box thingamajig. I can't remember which worked both ways right now (I think it was "align to") since it lets you both move towards something regardless of range. Just unbind one of them and use the other one. The button for these two actions is in the exact same place in the "selected item" window, so why give it separate hotkeys? Right now it's impossible to bind the same hotkey to align to a distant stargate, planet, etc as to approach a ship that's 10 km away. Okay, that has nothing to do with what I asked. They share the same button on the existing UI, so why give them separate keys on the new UI?Įver tried hitting approach on a ship that is a few hundred km away? Why are approach and align hotkeys different? They do the same darn thing! Additionally, you can never do both, so there's no reason to have them bound to separate keys. Thread Statistics | Show CCP posts - 0 post(s) » Click here to find additional results for this topic using Google Please take the last small but necessary steps to make the new system excellent.EVE Search - Approach and Align hotkeys. The difficult part is done, so why not polish the rest and get all the credit you deserve? The users ask one again please commit to excellence. The actual serverside execution is what CCP has to worry about.Īll of these fixes are relatively simple compared to creating a new hotkey system from scratch. This will give the users(including me!) the illusion that their commands are being acknowledged and having an effect. Solution 4: Provide instant feedback to all issued hotkey commands at the client level. Solution 3: Treat brackets as extensions of the overview, just like prior to the patch. Solution 2: Make all combat hotkeys valid as long as the hotkey is pressed. The delay between commands / command combinations, measured in seconds / miliseconds, should be allowed to be configured in the hotkeys option. Solution 1: Let the user to choose the sensitivity of these commands. My proposal for fixing the sluggishnes would be dealing with these problems, on a one-on-one basis. This causes combat hotkeys to be executed much slower than the user wants. All combat hotkeys somehow seem to be tied with Destiny's 1hz simulation rate. All Combat hotkeys don't support this functionality.Ĥ. Before the change on hotkeys, you could lock onto the target by using Ctrl+Click on the target's bracket. Once you misclick, you have to press the hotkey again.ģ. "Combat" hotkeys (all new hotkeys and the targeting hotkey) are only valid for one click. This can be remedied by changing the lock hotkey into something that's not ctrl/shift/alt, such as z or x.Ģ. When pressing Ctrl, the client "waits" for about 0.5 seconds before actually switching to "lock" mode. The general sluggishnes of the new combat hotkeys seems to be a four-fold problem, as described below ġ. However, the execution is so poor that it is now actually faster to use the selected items panel and ignore combat hotkeys as a whole. The new "combat" hotkey system seems pretty nice in paper it is supposed to save the effort trying to approach / align / warp to / dock using the small selected items panel.
0 Comments
Leave a Reply. |