Admin > Dev App Testing

Dev App 1.3.7 (392)

<< < (6/7) > >>

Velvet:
would agree that there's already enough buttons a pilot has to hold down at any given moment anyway. I could live with scroll /keyboardto select and click to activate but I think that needs to have some good interface change to make the functionality clear.

that said I think you'd make certain situations more difficult under such a system. for example if you want to activate multiple tools in quick succession (moonshine+impact bumpers for a ram, or maybe hydro+moonshine for a fun ram or an escape) the additional button presses slow down the process and add an additional window to make critical mistakes (eg. selecting impact bumpers then switching to moonshine before you remembered to click).
with that in mind, I say remove the scroll wheel and go for the MOBA system of having toggled and activated abilities with keyboard hotkeys. with no scroll wheel there's really no need for the additional confirmation of a left click.
There's a few abilities (hydrogen and chute vent) that really would make more sense as activated abilities rather than toggles.

activated abilities would also add the possibility of cooldowns, which might allow for some more powerful and exciting tools that may be conceivably balanced in skirmish mode but would definitely be a nice addition to coop. eg. massive short duration damage reduction with a 90s cooldown.

redria:
Tick-box option. As an advocate for click-to-tar, I like it, but now I'm wondering how it would work for me. I have my tools set to key bindings, not scroll wheel. So now I have to hit a button and click to use my tools, which is not much but I'd prefer not to. So the option to choose either would be cool if we could go that route. :D

Queso:
Really great feedback so far. I think quick activate with keyboard keys or scroll and click for mouse would be a really cool paradigm because currently mouse wheel is basically impossible unless you are super careful. Tar is still going to ship click to activate just so it's useful again, and we'll look at feedback from there.

Richard LeMoon:
I see DevApp has just updated to build 380. What changes should we be watching for/testing?

Watchmaker:
This is a handful of small fixes as we eliminate possible causes of the performance issues so many people are seeing.  In particular, this one contains a fix to a memory leak that was causing extra effects objects to build up from match to match.

Navigation

[0] Message Index

[#] Next page

[*] Previous page