F14 Module Logitech/Saitech X56 Hotkey assign not registering. Seriously?

[M4ND4L0R3]

 

Draconus, man..

Sometimes I dont know if your actually helping or deliberately trying to argue with me on the forums.

Please, have a good look at this:

On 5/2/2021 at 9:25 PM, IronMike said:

They are being registered as a press when you move them, set them, but the stick does not communicate this "press" continuously. This means it works when pressing both buttons together, or in the menu for a short while and after spawning in game, but once you switch it again, or atfer a while, or for any other reason why the stick stops communicating the button press, it will not work anymore.

 

I realise english isnt your first language mate, but I feel like theres been several times where things have been misunderstood.
The problem ( regarding to using the ingame modifiers/switches ) is that the stick stops communicating with those three " mode select " buttons. That line itself is enough to show that trying to use those three buttons as a long turn solution is not going to work, either as a modifier or as a switch, due to the lack of communication between the game and controller. So logically with that explanation:

 

5 hours ago, draconus said:

I don't know if your mode switch can work like

 

It wont. And doesnt, Ive already tried it when I first bought FC3 and was trying to figure all of this out. Ironmikes explanation of whats happening with those buttons makes crystal clear sense with the amount of hours ive sunk into testing WTF is going on with those buttons. ( in regards to using the ingame control assigns )

And overall, lets look at this logically:

 

- Logitech sells a controller with a " mode select " button

- After hours upon hours of issues, finally revealed those buttons dont work with the game because they stop transmitting and the controller loses " where it is " when playing with the in-game control settings.

- An alternative is provided to using the " mode switch " by instead using a button on the stick to act as a modifier.

 

Am I then going to continue to f*** around with trying to set switches as well using the same alternative? and try to remember if I clicked the " switch " button on the stick/throttle/rudder or not? Or would I just use the more efficent choice between the two, and simply use the button press modifier so I dont forget where I am in my map? THE ENTIRE POINT of the " mode switch " ergonomically in the design of the controller is to allow you to easily identify where you are in your map. Yet its not working with this module. 

So again, logically, the most efficent process would be to use the button press modifier as suggested by iron mike, rather than set up a switch somewhere else on the controller where I cant easily identify where I am in my control map. As a DCS player, I would think you would understand with the amount of s*** going on when your flying, the last thing you want to be worried about is " Did I click my switch modifier? "

Can you see where my frustration comes from reading/responding to your post's man.... im honestly trying here..

 

 

5 hours ago, draconus said:

You're confusing the switch with modifier and that's the only difference.

 

No, Im not. I actually tried switches in the first place, because thats how I thought the game would accept the " mode switch " buttons in the first place, not as modifiers. If you check my first video from 1:35 you can see when I bring up the controls page I already had a " Mode 1, Mode 2 " etc set up in the switches, attached to those buttons, from when I was testing the profile previously.

So no, theres no confusion, at least not on my side.

 

 

Also, as an additional point:

On 4/29/2021 at 8:45 PM, draconus said:

Obviously I will not be able to test "modes" on my HOTAS.

On 5/2/2021 at 9:25 PM, IronMike said:

This even counts for the Thrustmaster software, with Thrustmaster being an ED partner.

 

5 hours ago, draconus said:

I already tested it and told you how to set it up.

 

Correct, a T16000M doesnt have mode select and your even using a hardware provider thats partnered with ED, so to be fair any kind of testing you could be doing is irrelevant in my situation and kind of useless. Its kind of like comparing two different manufactuers of cars " Oh well I got in my car and turned the key and it turned on, so I guess you could be more specific as to what your issue is? "

Your never going to be able to replicate the issues I am having with the game.


Its resolved dude, for now. Let it rest, we are done here, RTB and move on.

[draconus]

That's OK that you're fine with the module, M4ND4L0R3, for now. I just gave you tested info - what you do with it is not my problem. Please don't quote Mike's elaborations on modifiers when I talk about switches, which again, are not required to be held, so they don't stop or start communicating anything, just one push and you have a toggle switch. As already said, your low-res video is of little use, as one can't read the bindings there, and also it uses external software and no actual bindings assigned to the controller itself (that we can see) - so irrelevant.

Your hardware/vendor is not so special as you may think. It connects to USB and works in Windows/DCS without any additional driver or software. You push the button and it registers. Simple as that. And stop being so touchy.

[M4ND4L0R3]

Seriously cmon man...

Read the information. Please.

 

6 hours ago, draconus said:

. Please don't quote Mike's elaborations on modifiers when I talk about switches, which again, are not required to be held, so they don't stop or start communicating anything, just one push and you have a toggle switch.

 

Im just not sure what your missing, I thought Mike's explanation was like 110% clear what the issue was with the hotas, im kind of lost as to why this conversation is still going or how you think your information is still relevant but I enjoy responding to you for some reason lol....

 

- I tried the switches. Its a low res video, sure, but you can still see how I have it set up, and I still explain it in the video. Im assuming your not deaf, so for someone who should be familier with the game you would know what screen im on and I physically tell everyone what I had them set to.... the main point of the video was to show that the inputs were not working/not being recieved by the game. This also doesnt require HD, you can see if the screen moves on the control menu whilst I am pushing something that the game is receiving information, if it DOESNT move you can see that its not working. Im unsure why you keep mentiong the low-res when you dont need 4K fidelity to hear/see what is going on... lol. But whatever. Sorry you cant watch it in HD man im not sure what to say, my friends in Australia can watch it and understand the issue fine.

 

- The mode select switches on my hotas stop transmitting. This still directly applies to using the switch, which, as I said already, I initially used but was having issues and was continiously having to flick the switches on/off to get a response because EVEN THOUGH I ENGAGED THE SWITCH, I would still accidently turn my engines off  after a period of time because the game no longer registered the switch was active. Does this make sense? Because it does to me.

 

See the below, if you really need to have clear mapping diagrams and 5 page essay's for you to understand.

 

 

Red circle is the " mode select " switch, with 3 settings, M1, M2 and S1 ( but I just call it M3, relevant button maps are Buttons 34,35 and 36 on the logitech throttle, I mentioned this before.... )

 

For my F18 map, Yellow toggle was:

 

- > M3 = Autostart

- > M1 = ATA Mode

 

 

Now if what you said was true and worked ( but it doesnt because the red switch stops transmitting after X amount of time ), then yes. I would just click the switch and Autostart would only happen whilst the switch had activiated " M3 " ( Throttle button 36 ) , and ATA mode would only activate once M1 ( Throttle button 34 ) had been activated by the switch, right?

 

Wrong.

Because these buttons stop working, the game loses the information of what " switch " is active, and I would initiate autostart instead of ATA mode ( M3 was my landing/take off settings, M1 was Flight/Radar ) So, Thus, Therein, Therefore, Visa-vi, Mike's " elaborations" on modifiers are still 100% relevant when it comes to the mode select switch on the HOTAS, which, has literrally been the entire focus of this thread, Just incase that wasnt apparrant.

 

Once again...

If the mode select switches cant work, then Mikes suggestion of using the stick button modifier in tandem with the throttle buttons is the most efficent method.

 

You are 100% correct. I could set one of these other buttons as a switch, and it would work. But as I said earlier, then I would need to remember if I activated the switch or not and I felt like  in my situation that this was not a very efficent method to use.

 

I have only ever been relating to the mode select buttons/logitech software in this post, because as mentioned my other process works with the other modules. 

 

Ok?

 

6 hours ago, draconus said:

I just gave you tested info - what you do with it is not my problem

 

Exactly! Its irrelevant information as its not the same setup thus any data you find during whatever testing you do is literrally useless, as this thread is literrally naming the issue hardware. Again, using cars as an example, if my forum post says " Help my BMW has an issue ", you are literrally a guy who owns an Audi saying " Well man I tested my car and it works fine so yeah stop making such a big deal " lol.... Would you like another example of how helpful your testing is on different hardware?

As they say in Thailand, " Same Same But Different "

 

6 hours ago, draconus said:

Your hardware/vendor is not so special as you may think. It connects to USB and works in Windows/DCS without any additional driver or software. You push the button and it registers.

 

Absolutely! This has never been an elitest " Im pro logitech " forum post, I have not slandered nor belittled other hardware. I have simply asked for assistance with my hardwear setup and issues with the game. I suggested in my video's that maybe DCS should integrate with logitech and other hardware providers, and then Mike told me that actually ED is partnered with thrustmaster, which is great really, to be honest. I have a thrustmaster lying around that I use for some other games because it has the throttle/stick linked to the same control input.

My main point, is that, I CAN use the software provided with the hardware ( which to be fair is actually pretty good and makes the hardware even more diverse etc etc etc ), yet it doesnt work with the F14 module. 


What else shall we argue for literrally no reason about?

 

 

 

[Whiskey Greg]

Mike, 

 

I'd love to see your X-55 control scheme. I use the X-56, but it is just about identical.

[draconus]

17 hours ago, M4ND4L0R3 said:

You are 100% correct.

I know, you could have skipped the rest. Look, this thread is not just for you and your mode switch. It will be here for many years and many users will read it looking for info and they just might reach a different conclusion, that's all. Sorry if you had a feeling that I try to convince you to my way of controls setup.

Edited May 5, 2021 by draconus

[M4ND4L0R3]

8 hours ago, draconus said:

I know, you could have skipped the rest. Look, this thread is not just for you and your mode switch. It will be here for many years and many users will read it looking for info and they just might get a different conclusion, that's all. Sorry if you had a feeling that I try to convince you to my way of controls setup.

 

Haha, your absolutely right man.