test content
Logo
What is the Arc Client?
Install Arc
Patch Took out my Logitech Extreme Pro 3D Controller
commander
Member Posts: 11 Arc User
Since the 25th patch, the game no longer recognises my controller, it worked perfectly fine before it, now the game ignores it. Does anyone know of a workaround? Without it I'm handicapped, due to health reasons I find keyboards difficult.
0
Comments
1. For each action you want to perform in-game, choose a keyboard keystroke. Example: 'p' for firing phasers.
2. In the Logitech Profiler, assign they keystroke 'p' to the control you want to use to fire phasers. Example: assign 'p' to 'Trigger'
3. In the game, open the game Options, select the Key Binds tab. Scroll down to the action "Fire All Phasers".
4. In the space at the right, click to assign a new keystroke to that action, and type 'p'.
5. Repeat this procedure for each action you want to execute, using a different keystroke for each action/button.
By doing this, you use the Logitech Profiler to generate a keystroke that gets transmitted when the control fires. The game reads the keystroke in the same way as a keyboard input and acts on it. Thus, 'p' = 'p' = 'Fire All Phasers'.
You can also manually keybind the controller via the chat dialogue using syntax like:
/bind p "FirePhasers"
Two caveats: 1. This only works if you have the Logitech Profiler software running in the background while you're playing the game. And 2. I can't guarantee how durable the workaround is under the circumstances; with this patch I keep finding new things broken and missing. I can only say that I went from a dead stick this evening to flying circles around the Tzenkethi at Gon'Cra. Good luck.
Mine too. I am also a disabled vet and the joystick makes a difference. Since it is more types than just my Logitech 3D Pro that are not working and ship weapons are on another string as not working, I had hoped todays (052721) update was to fix the patch but evidently it was not.
I submitted a work ticket on 052521. They (PW Support) acknowledged it. Still waiting for an answer. Replied to the acknowledgement and asked if there would be some compensation since we cannot do the events if our craft are out of commission.
It is in your root drive normally C: and is in C:\Program Files (x86)\Star Trek Online_en unless you selected to install it someplace else during the install. The executable is: Star Trek Online.exe
Ok, good work around and what I tried originally but... It does not allow for programing banking or other joystick functions which are automatic to the enable joystick controller option. This is replacing the 2 axis/throttle/twist/12 button joystick with a software interface with limited capability and could cause over/under reactions due to lag or game interface. Secondly, it only works if running the profiler in background, which some can do but not everyone has a Logitech or programable joystick. Thirdly, not everyone knows how to program the profile correctly, do incremental profiles or link the game so that the profiler runs first then the game. Forth, I can see also how running the game first, in an Administrator or dedicated mode in some setups could also block the Logitech software from overriding the keyboard. These are all things that can be worked around but since it was working before we should not have to.
This is indeed the case. Mapping the pitch, yaw and twist to keystrokes has resulted for me in significant loss of tight flight control, especially in the turns. I quite agree that whatever was working perfectly well and got busted in the patch needs to get un-busted right away. This workaround is life-support until help arrives, but it's better than trying to fly via keyboard.
Please, devs, can we have a fix for this?
I really hope they get this fixed, flying with the keyboard is stressful and half as efficient.
There are a couple of things you could look at to see if they affect this behavior on your system.
First, in the Logitech Profiler, in the top menu, select Options > Global Profiler Settings and see which radio button is selected. If "Apply persistent profile" is selected, try switching to "Apply profiles to games automatically" and see if that resolves the problem of repeated characters in text fields outside the game. If it doesn't, and "Apply persistent profile" was selected, you can return to normal out-of-game function by switching to "Do not apply profiles to games automatically" when you exit the game. You should probably also be sure to set up a profile for STO specifically so the Profiler is pointed directly at the game. "Apply profiles to games automatically" doesn't make the stick work in the game for me, but it might for you.
When using "Apply persistent profile", I have found it impossible to type in the chat input field because it fills up with characters, but it may be because I haven't set my stick up properly to recognize its resting state.
Which brings me to the second thing you can try: In the settings for the Axes, when you click on each one, you will find an option at the bottom for "Axis properties". Under this, there are options for adjusting sensitivity, dead zone, and range. Also by clicking on an Axis you can "Select Zone Assignment > New Zone Assignment". Select one of the zones at left and then click the button marked "Split". This divides the side of the axis into zones that can be assigned to different output -or more importantly, no output. In other words, you can set up a dead zone in which your stick sends no data. You can keep subdividing individual zones, or drag to size by percentage. Bear in mind that whatever dead zone you create will cause a break in the continuity of performance of the axis, so it will need fine-tuning for best results. ("Best results" in this case is a subject of dark humor.)
I'm still tweaking all this myself, trying to regain enough control so as not to get blown up by Nausicaans. Nausicaans. It's embarrassing.
I was never able to get my joystick to work "out of the box", but eventually came up with with a round-about solution that is as permanent as writing configuration information to files can be. Instead of using 3rd party software to remap joystick keys to keyboard keys and subsequently dragging windows into the mess, I used the games own controller configuration files to "remap" the in game button names to the corresponding buttons on the game pad. I then used normal key binds to assign actions to whatever I named the joystick buttons.
The button remapping only happens inside the game, so Windows should be none the wiser. No surprise button assignment conflicts, no Window-tantrums about permissions and there should be no more surprise crazy-go-nuts gibberish output from ... whatever that was from.
I know it sounds like a pain, but it really is far simpler than using an intermediate piece of software, and as chance would have it, I did a write-up on it a few years ago.
https://ufplanets.com/showthread.php?57634-Configuring-joysticks-for-STO
THAT BEING SAID ... while my game is still configured as described in the walk-through since I wrote it and it has not hurt anything, I have not used my joystick in some time. I cannot guarantee this still works and I am not in a position to test it at the moment. If someone wants to try this, I suggest you only make enough changes to get ONE button working on the joystick that was not working before. If it works, then the rest will to. If it does not, you have saved yourself some time.
The x and y axes do not currently work (they don't seem to be read as input by the game at all).
Button assignments through console buttons/variables do not work.
The only way people seem to be getting any stick functionality is by using third party software to assign buttons to the various joystick movements and buttons. This doesn't really work for me since I had reassigned things to look nothing like the standard keyboard.
I'm actually using my ground-based keyboard layout to fly since I kept those keyboard-movement based with mouse clicking of skills rather than stick-movement based with button pushing for skills. This "works" for some ships, but I can't fly any of my pilot ships worth anything with this layout. I'm guessing unless they get this fixed soon, my gamma recruit will end up in a tanky beam ship that barely moves. Or I may do just enough to get the gamma started and then stop playing for a while.