Forums » Suggestions
Turbo Lock
Random Thought: Is turbo lock still achieved only by manually creating one with an alias? If so, for the sake of the newbies, would it be difficult to incorporate it into the standard key settings? In other words, make it a default key instead of having players make a bind for it. I just realized tonight that newer players or at least incoming players might not be familiar with the turbo lock bind and are still flying around with sore fingers from holding their turbo keys.
Yeah, not very important. Okay, not important at all. But quick and easy?
Yeah, not very important. Okay, not important at all. But quick and easy?
or if that is to much work add it to the tutorial
Slippery slope toward making VO a massive jumble of incoherent and contradictory bind declarations some guy somewhere once thought might be useful to include in the default install?
Great! Love it!
Great! Love it!
This isn't 'not very important', in my opinion. Even some free MMOs nag their users about not playing for too long and sitting in a well-lit room and whatnot.
VO should strive not to cause RSI, as well, I think. Very much in favour, especially since it should be a quick fix, like Ghost said.
VO should strive not to cause RSI, as well, I think. Very much in favour, especially since it should be a quick fix, like Ghost said.
VERY good suggestion! I've finally memorized the binds from all the times I've had to implement it (I know I know, all two lines of it!), but it should definitely be default. Is "v" used for anything? That's my key :)
v is the default secondary fire key, if I remember correctly.
It should absolutely be there by default.
Shift-tab?
As far as I know the game doesn't recognize Shift+Tab as different from Tab. I say this because the way I lock down turbo is to hit my turbo key, hit Shift, release my turbo key, and release Shift. This makes the game think my turbo key is still down, because I've released the Shift+key associated with it. I tried this with Tab, and it didn't work.
shift-key is just a side effect and it has issues like being stuck etc.
There should be a proper solution.
There should be a proper solution.
How about c? I moved secondary fire to c, and turbo lock to v.
c is secondary fire, v is primary fire. I recommend one of the F keys.
One of the flaws about the turbo lock bind is that if you run out of energy, it automatically halts you without any functional difference in the self-writing bind. In such a circumstance, to begin again requires that you tap either turbo button an additional time. If you do not remember how you turned off your turbo the last time, (the choices being by running out of energy, or hitting a key) then you can never quite be sure how many times you must hit the button before a turbo actually initiates. One too many, and no change occurs.
I use this plugin to rapidly check for rising energy levels after a turbo is initiated. When such a situation occurs, it resets the bind to the "off" position. If a turbo cannot be initiated unless the ship has at least as much energy as it had when it would be automatically shut down due to lack of energy, and if energy levels are constantly shifting, then this plugin will reset the bind to the "off" position if and only if the turbo was automatically shut due to lack of energy. I believe that is the case.
TLDR: The bind sucks. It needs to use Lua or something to not suck.
One of the flaws about the turbo lock bind is that if you run out of energy, it automatically halts you without any functional difference in the self-writing bind. In such a circumstance, to begin again requires that you tap either turbo button an additional time. If you do not remember how you turned off your turbo the last time, (the choices being by running out of energy, or hitting a key) then you can never quite be sure how many times you must hit the button before a turbo actually initiates. One too many, and no change occurs.
I use this plugin to rapidly check for rising energy levels after a turbo is initiated. When such a situation occurs, it resets the bind to the "off" position. If a turbo cannot be initiated unless the ship has at least as much energy as it had when it would be automatically shut down due to lack of energy, and if energy levels are constantly shifting, then this plugin will reset the bind to the "off" position if and only if the turbo was automatically shut due to lack of energy. I believe that is the case.
TLDR: The bind sucks. It needs to use Lua or something to not suck.
I don't know what bind everyone else uses. I use:
alias -turbolock "+turbo"
alias +turbolock "+Turbo 0"
bind F8 +turbolock
Which is basically just a reverse of the turbo key. I have found few if any faults with this bind. Using or tapping the standard turbo key overrides this one.
In many situations, turbo is already on, but not working (I ran out of energy, changed sectors with turbo on, etc...), and the only way to get it to work again is to turn it off before turning it back on. This bind does that. It is also still serviceable for turbo tapping, just in reverse.
As for having it in the default config... I can foresee a minor problem, that if a newb doesn't even know how to use turbo, and hits the turbo lock, then they could get stuck in turbo.
Perhaps just stick the aliases in, and not bind them to any key. When a newb is qualified to enter in a simple key bind, they should be able to handle turbolock.
alias -turbolock "+turbo"
alias +turbolock "+Turbo 0"
bind F8 +turbolock
Which is basically just a reverse of the turbo key. I have found few if any faults with this bind. Using or tapping the standard turbo key overrides this one.
In many situations, turbo is already on, but not working (I ran out of energy, changed sectors with turbo on, etc...), and the only way to get it to work again is to turn it off before turning it back on. This bind does that. It is also still serviceable for turbo tapping, just in reverse.
As for having it in the default config... I can foresee a minor problem, that if a newb doesn't even know how to use turbo, and hits the turbo lock, then they could get stuck in turbo.
Perhaps just stick the aliases in, and not bind them to any key. When a newb is qualified to enter in a simple key bind, they should be able to handle turbolock.
But it doesn't clear itself, ie. pressing it again won't turn it off.
It is a turbo lock, not a turbo toggle. Pressing and releasing the turbo button (tab) will turn it off.
I bound turbo to a side button of my mouse...
Yes Roda, i realize, it's still suboptimal because of that, at least for me.
hehe, my turbo lock is quite simple too. I rest my joypad on the tab button and against my screen.
Good point tho, Ghost.
Good point tho, Ghost.