Controls suddenly forgotten by CloD?

[corchard]

Has anyone been having a problem with CloD suddenly "forgetting" their controls mid-mission?

I use CH Fighterstick, Pro Throttle and Pro Pedals in "Mapped Mode" using CH's Control Manager software, which normally works very well.

Starting last night, though, while playing offline single missions I'll be firing away and suddenly my trigger button stops firing and starts opening and closing the canopy, and several of my other mapped buttons no longer work as programmed, either. I then pause, alt tab out, re-download my CloD profile back into my CH products ("Mapped Mode"), and return to the game, to have everything work properly again.

I had to do this several times during the same mission, and it also happened in at least one other mission. I didn't notice any consistent trigger for this behavior, and each time I alt tabbed out of CloD and checked the CH Control Manager software I saw it was always still in Mapped Mode.

I have never experienced the same problem when flying Rise of Flight.

I'm fine with CloD having a number of bugs still being addressed, I am just not sure if this controls problem is a known bug or something I can address in my own setup.

Charlo

[corchard]

With some help from Bob at the CH Hangar forums, I think I fixed the problem.

My Full_Left_Wheel_Brake key was CTL q and mapped to my left toe brake, and if I happened to let my left foot rotate hard enough so as to initiate the toe brakes (> 250 on that axis) while shooting, that combination of firing the machine guns (space) was sometimes being interpreted as a combination of CTL q and space, "control space" - which is the toggle for opening the canopy.

I changed my Full_Left_Wheel_Brake key to SHF q, and that fixed the problem.

I'll keep watching for any other combinations of commands that may inadvertently cause other buttons to react unexpectedly, since I now can see it is NOT a CloD bug, just a problem with my key bindings.

Charlo

[ChiefRedCloud]

Well I experianced something yesterday. I flew a few missions earlier and tried online with my controls working just fine. I came back later and went to fly and my HAT switch and throttle didn't seem to be doing much of anything. I could not look right or left without the keyboard. and with the throttle wide open I seem to be right at stall speed.

Now do take into consideration that I am new to CloD but still I know I set the controls and that they DID work. Then they didn't I've checked them in the options, and they look fien, but I've reset them again. I can looke right and left again with my HAT switch but the throttle still seems sluggishly slow.

[soldano]

Originally Posted by corchard

With some help from Bob at the CH Hangar forums, I think I fixed the problem.

My Full_Left_Wheel_Brake key was CTL q and mapped to my left toe brake, and if I happened to let my left foot rotate hard enough so as to initiate the toe brakes (> 250 on that axis) while shooting, that combination of firing the machine guns (space) was sometimes being interpreted as a combination of CTL q and space, "control space" - which is the toggle for opening the canopy.

I changed my Full_Left_Wheel_Brake key to SHF q, and that fixed the problem.

I'll keep watching for any other combinations of commands that may inadvertently cause other buttons to react unexpectedly, since I now can see it is NOT a CloD bug, just a problem with my key bindings.

Charlo

How could you manage to map CH propedals toebrakes as keys ?, mine are not recognized that way, I could map them only as axis.-
My toebrakes doesnt work with Spitfire and Hurricane, only with some German aircraft.-

[corchard]

Originally Posted by soldano

How could you manage to map CH propedals toebrakes as keys ?, mine are not recognized that way, I could map them only as axis.-
My toebrakes doesnt work with Spitfire and Hurricane, only with some German aircraft.-

Hi Soldano,

Inspired by pages 6 and later of this thread at the CH Hangar and Revvin's IL-2 Sturmovik: Cliffs of Dover FSPTPP, I use this cms script for my toe brakes:

script
CMS.B5 = [JS3.A1 > 254]; // Full_Left_Wheel_Brake (SHF q)
CMS.B6 = [JS3.A2 > 254]; // Full_Right_Wheel_Brake (ALT q)
endScript

I should add that I only know from personal experience that it works for the 109, as that is the only German plane I've used on the ground. It may work with other German planes. Note that brakes only come on when the toe brakes are pushed all the way (point 254 out of a 255 point axis).

It does not work with the Spitfire or Hurricane, the only British planes I've used on the ground. The only way I know to make the brakes work on the those 2 planes is to press and hold down the "b" key, which activates full brakes on both wheels as long as you are pressing "b".

This appears to be a known issue, either a bug or a design choice that reflects the way brakes worked on those British planes.

Charlo

[Blackdog_kt]

It's done this way on purpose, because that's how it also worked on the real aircraft: single brake lever for the main pneumatic line, then a differential valve that's tied to rudder pedal movement for dividing the amount of pressure (and braking power) between left and right break.

In other words, your toe brakes don't work because the RAF didn't use them