LOGIRich

@Elof - does it do the same thing in other titles? Also, when it starts occurring in DCS if you alt-tab out of DCS and look in Game Controllers, is it now doing it in there? @fagulha Are you running with a profile loaded from our software or just assigning within DCS? Also, does it do the same thing in other titles?

@Elof Have you been through the recalibration steps for both regedit and the stick firmware? Regedit: https://support.logitech.com/en_us/article/Recalibrate-controller-axes-RegEdit Stick firmware: https://support.logitech.com/en_us/product/x56-space-flight-vr-simulator-controller/faq#link_Recalibrate-the-X56-H-O-T-A-S-Axes-Firmware

Hi, Have you been through and reassigned the controls for the F/A-18C in DCS's control options?

Hi there. So, no lights on the throttle at all? Or are you saying the throttle doesn't operate the in-game throttle? If the former, have you tried different USB ports on your PC? Is the throttle showing up in Game Controllers in Windows (type joy.cpl into the Windows search window to access)? If the latter, have you been through the assignments process in DCS?

There won't be any further updates to the software as it is I'm afraid. The plan is to integrate the HOTAS into G HUB along with all other Logitech products and then you'll have access to the G Shift function which could be assigned to the pinkie. No timescale on this yet though I'm afraid. In the meantime Akula's suggestion should get you what you need.

You need the first post in this thread but, essentially, the black/grey version is the improved version of the X56 and the only one that will be made going forwards.

The support agent will typically run through troubleshooting as part of contact so they will have been able to diagnose if there's an issue - often this involves them asking the customer to take video to show the issue. So, whilst it doesn't achieve Wilbur81's desire to be avoid being completely without a working HOTAS, it does result in a reduced time that this would be the case as we're cutting out the shipping time back to us as well as it then being analysed. Please do get in touch with our support though as it does sound like there's an issue with the Y axis pot in that mini stick assembly I'm afraid.

If it turns out to be faulty, with a relatively large box item like the X56 our support will normally ask you to snip the USB cable and send a photo as proof of destruction and then send you the replacement unit. Curious to know exactly what's happening here though. Is the axis spiking down on its own? Is it happening when you touch the mini stick? Can you replicate this behaviour in the test screens in joy.cpl?

Crab's beat me to pretty much exactly what I was going to say. The key point to remember is that the throttles on the X56 ARE the X and Y axes. That doesn't matter though. Provided you've correctly assigned the axes then you should be fine - follow Crab's picture as the comparison.

Confirmed! I repeat though: please do take the correct anti-static precautions.

No barrage felt here - comments always welcome. I'm not omnipresent though so if you ever want to draw my attention then please feel free to PM me as Akula did. @Akula if the throttle tension knob isn't working then it may be that the application of damping grease was too excessive or has migrated somewhere it shouldn't. You will find that this eases with use but also please feel free to open the throttle and remove some of the grease - you have our blessing, just please take the usual precautions for anti-static/ESD to ensure you don't damage the unit. Regarding customer support, we have many ways of reaching them - I always recommend the phone option wherever possible. We're always looking for ways to improve customer support though so your feedback is appreciated. For those wondering about my role at Logitech, I'm the Global Product Manager for Simulation so I can say to Sandman that there are no plans at this stage to produce an extension, I'm afraid.

@HiJack The control panel is still there - we can’t remove a Windows component! Type joy.cpl into the run window and that will take you there. The twist spring is deliberately stiffer than the X52 due to feedback on that product; the same is true of the throttle. Happy to answer any further questions to the best of my ability to do so.

Hey there, sorry to hear that. We're still covering support on the X55 so if you get in touch with our support team then they should be able to help. One thing to check before you do is to make sure that the contacts on both the removable grip and in the gimbal are clean, as well as ensuring that it has been tightly secured with the screw collar. If it's still not working then please get in touch through support.logitech.com

There's no recall in place for the original X56. Please get in touch with our support team if your X56 has an issue though.

Yes, that will be the new one - they just haven't updated the images. The X56 throttle has no detents.

945-000058 and 945-000059 are both the new version. 58 is the US packaging version 59 is the European packaging version The product inside is exactly the same though.

If you edit the axis curves in our software then those are the responses that are sent to your PC via HID because they're saved directly into the stick. DCS's deadzones should then layer on top of that info that comes through HID, so you may want to remove those from DCS.

It's not intentional. The X56 has a very long handle and as a result a tiny amount of play around the centre appears to be a fair amount more when you translate that up to the head of the stick (where most people measure it). There's other factors at play here that I can't answer for though - everyone is different and holds their stick in their own unique way, some of which may result in unexpected behaviour such as this. In those cases the above are the recommendations that I'd make to see if it helps. If I had to guess I would say that altering the response curve of the axis is most likely to help you, but do please keep me updated on any progress.

There's always a balance to be struck between responsiveness and not having everything happen as soon as you so much as touch the stick. The flipside of your position if we didn't allow reading of this movement would be from those who say "Well the stick's moving, so why can't I see any response from it?" There's a few ways that you can approach this: Change the spring to a stiffer one Set a small deadzone. Yes, a small one - I'm aware that many people think that deadzones of any kind are the work of the devil, but a small deadzone can be a very wonderful thing Adjust the response curve of the X axis in the software. You could introduce a curve around the centre where you're flattening out the response to make it less responsive and that should help alleviate it too. In fact, many people love to set the curves this way as it means you can be far more precise around the centre of the stick movement but still get the full range of axis response as you move the stick to its extremities.

You shouldn't see any keypresses in the test screen when you move the mode switch... unless you have programmed the mode switch positions with keypresses of course! If you send me your profiles then I can have a look at them and see if you like - just upload them via something like WeTransfer and I can take a look.

@STRYC Sorry to hear that - it's one of the reasons why I keep an eye on various forums and I usually ask people to PM me their ticket number so I can chase it up. It looks like you're getting somewhere though so hopefully you're good. @bell_rj It's certainly unusual for it to do so, even if you've cleared the profile. Usually in situations like this the issue is caused by another piece of software being introduced which doesn't get on with our programming software. Other programming software interfaces from other game controller manufacturers can be one such example. Just to check - had you made any changes to the default profile? (literally the default.pr0 file)

@wilbur81 The wiring in the throttle was something that had already been addressed with the first version of the X56. The wiring issues in the X55 were not necessarily the cause of the ghost button presses - often that's cleared up by using a powered USB hub and ensuring the throttle is the only device on it. It's also highlighted by the fact that the same unit might exhibit this issue on one PC, but not on another. @NineGzuz The ergonomics are the same. There are plenty of positive comments about the ergonomics as well though - the best thing to do is to try it!

Can you add the software as an exception/white list item in your A/V software? Which A/V software is it?! Regarding the File Explorer windows popping up, there's got to be a command that is being activated on the HOTAS, although looking at the profile I can't find any button that has the Windows key assigned (File Explorer can be brought up by pressing Win + E) so that is unusual. Can you shed any light on where the Windows keypress might be coming from? (It could be any other device)

@tothesky I think you may be misunderstanding my line of inquiry. The profile works fine when we test it (and I'm sure others here would confirm the same) so the issue is with the way the software is working (or rather, NOT working) on your PC. As I said, I was simply suggesting getting the X56 set up within the game whilst we try and work out why the software isn't working. Are you able to test other profiles, or indeed create a simple test profile to see if those work please? This is a good first step on troubleshooting this issue. The second question would be whether you have a second PC that you can test the X56 on to see if the software does the same thing there. Again: not suggesting this is a solution, just troubleshooting.

As CoBlue and dburne have mentioned, it's perfectly valid for you to just set up all of the controls in DCS whilst we try and work out why the software isn't profiling. Indeed many people prefer just setting things up from within the sim! For our software I assume you've tried reinstalling the X56_HOTAS_x64_8.0.134.0.exe install file that you downloaded from our site? Also, if you create your own quick profile with just one or two commands assigned to buttons as a test does that do the same thing?