Jetpack not Working

Does anyone else have problems with their jetpack only doing one burst and not being able to hold-press to fly higher? I am using an xbox controller for on foot stuff and a HOTAS for flight. I need 8 more people to help me confirm this issue or else it will never get looked at.

If you do have the same or similar problems, please add your voice to the issue tracker here:
- https://issues.frontierstore.net/issue-detail/38152
I would appreciate it so much.

Thanks.
 
It does one burst, then it has to recharge -- which takes a bit. Is yours not recharging, you mean? How high you can get is affected by the local gravity, too. If you jump, wait until the top, then burst -- that's as high as you can get.
 
It does one burst, then it has to recharge -- which takes a bit. Is yours not recharging, you mean? How high you can get is affected by the local gravity, too. If you jump, wait until the top, then burst -- that's as high as you can get.
Thanks but it's nothing to do with operation as in if i hold down A .. it does a small paltry burst and then stops, instead of continuing to fire until it's depleted. If I keep my A button held down it will not empty the jetpack's energy. I have to release the button and rapidly tap it again and again. This is obviously not working as intended.

However when I bind the jetpack button to my HOTAS it works correctly. So far I've only got two other cmdrs who have this bug too. I need more alas or it'll die an a timed out bug.
 
Which Suit are you using?

If you got on foot on your default flight suit, it has a really limited jump assist (it's called this way in game). The best stock jump assist is found in the Artemis suit, followed by the Maverick Suit, Dominator Suit and last, the default flight suit
 
Which Suit are you using?

If you got on foot on your default flight suit, it has a really limited jump assist (it's called this way in game). The best stock jump assist is found in the Artemis suit, followed by the Maverick Suit, Dominator Suit and last, the default flight suit
Nope it's not suit dependant. It's just not firing correctly because the hold function of the buttons is borked. It also happens with some hold functions in the galmap. conversely in the galmap it's the HOTAS that won't perform a hold function to quick route whereas the controller will. lol
 
For clarification: No matter how big or small the 'energy' bar of the suit is,, it never depletes if i just hold the button down. It is like the button only registers a press and will not register a hold function. It will use a tiny amount of the jetpack energy and I have to release the button and press it again mid air to get another tiny puff, I have to rapidly tap the button to use the jetpack at all and then it's still not as effective as when it works properly.

The hold function of the button is not working correctly. it only registers a press.
 
If I understand correctly, this does not occur if you unplug the controller or hotas?

To me this then sounds like your controller and hotas don’t play along nicely, which would not be fixable by updating the game. Did you try to test this for similar issues with other games?
 
If I understand correctly, this does not occur if you unplug the controller or hotas?

To me this then sounds like your controller and hotas don’t play along nicely, which would not be fixable by updating the game. Did you try to test this for similar issues with other games?
Correct.. once I revert to ordinary standard controls the jump function works properly.
 
The jetpack certainly doesn't work the way 100 other games would. I also had a hard time with it at first, but now I really like it the way it is. Like many other things in Odyssey that I hated passionately at first. Like the item wheel, for example, or the new UI, which I now find quite brilliant. As I get used to it, I'm becoming more and more effective with it. Especially with my favourite method, the keyboard (actually a game board that is). I am used to digital input as the main throttle, so I am used to controlled "pulsing" (in FA Off) anyway.
As stated before.. I know how the thing works. it works properly until I have my custom settings equipped. It is not a case of "getting used to something" but thanks for your help.
 
Can you screenshot your controls binding screen and post here please? Just in case?

(mainly curiosity)
Certainly!

20210716093304_1.jpg
 
Having just re-tested this now.. As I've said in my issue tracker post. When I bind the jump function to my HOTAS it works correctly but only on the HOTAS.

The same thing is happening in my galmap but in reverse.
When using the galmap the select function is bound to my A button. This time my HOTAS refuses to do the hold press function to plot a route quickly. But my controller works instead. This is despite both being bound correctly.
 
There is something not right with the double bindings on controllers.
Used to pop up with a screen showing binds when you held a button but that doesn't work in my setup.
Noticed it was working on one of the livestreams when the CMs were using controllers.

I had a setup to use Right button and Down for torch but that throws a grenade and then puts the torch on.
So I have to hold down first (shield) and then right button so the torch comes on and then turn the shield off. Better than a grenade going off.
In Alpha it worked fine but now all the individual button commands are firing at the same time as the command you are trying to activate.

I feel like I should wipe my old binds and start from scratch but I haven't got the energy for that amount of work.

If it wasn't for the fact I enjoy playing Elite on the big TV I'd go back to the Hotas setup.
 
Yes.. which would imply there is something funky going on with the hold function. it's going straight to a one time action without recognising a long press. Are you only having this problem when your HOTAS is connected too?? and if you are would you be so kind as to add your comments to my issue stated at the start, if it's the same problem maybe we can get them to look at it?
 
Do you have contextual menus activated for controller, and a combo binding on the jump key?
I always had the same problem in srv with the handbrake on default context, i had to put it on toggle. I could "free up" the key from other bindings to avoid the context menu, but there are things like sensors range shared with the ship which makes doing that too much trouble.
 
Do you have contextual menus activated for controller, and a combo binding on the jump key?
I always had the same problem in srv with the handbrake on default context, i had to put it on toggle. I could "free up" the key from other bindings to avoid the context menu, but there are things like sensors range shared with the ship which makes doing that too much trouble.
Are you saying that if I have other combo binds that include the B key that it is causing the prob??
 
Back
Top Bottom