@cobragva There is something weird here: same number (129) for 2 different buttons.

In the profile, set 128 (129-1) for the LFMD.

SimCBEOSB_1L 128 -1 -2 0 0x0 126

Hello ,

I have an issue with pitch hold , not functional , falcon bms version 4.36.1 , when I trie to use it , I see a little shake on the throttle ???

Rgds

@jc1 jc1 is discontinuing use of the “Jc1 Profile” for Thrustmaster Warthog. I intended to use Alternative Launcher but found out that that Alternative Launcher could not recognize my devices correctly. I have Thrustmaster Warthog stick/throttle and CH pedals. If I remove the pedals AL is OK with that. If I add the pedals then AL AxisAssignment page thinks my stick and throttle is CH. Also AL can’t handle TrackIR pause. JoyToKey can handle TIR pause but JoyToKey is limited in what it can do. I got to have TIR pause on the throttle POV and make changes to BMS Full.key just as AL does with BMS - Auto.key.

I can do all that with my TARGET script “Jc1 Profile”. However, that Profile prior to BMS 4.36 was limited to 32 DX keys per device. Now with 4.36, 128 DX keys per device are available. I am in the process of finishing my new Thrustmaster TARGET “jc1-DX128 Profile” to make use of the 128 DX keys and should have it ready soon. All, not just 32, buttons and switches as one device will be assigned to the available 128 DX keys. That will make for ease in changing key assignments when desired and also better performance in BMS Falcon.

@Atlas
Hi, for what it is worth, I simply use the Alternative Launcher which makes it very easy to set up a Warthog hotas - you simply use the AL program and don’t touch the in-game HOTAS screens and you don’t touch the BMS keyfile.

I found I could not bind the throttle POV out-of-the-box with Alternative Launcher 2.1.0, however I have seen no one else with complaints on this, so it appears to be just me.

I then installed and used Alternative Launcher 2.0.0 and I could bind the throttle POV and the stick POV out-of-the-box with no problems.

@airtex2019 well, now in 4.36 the keyboard is id1. So, keyboard is 1, rudder pedals are 2, joystick 3 and throttle 4. On 4.35 rudder was 1, stick 2 and throttle 3. cheers

Thanks MaxWaldorf for your quick response.
At the moment it works well for me, 100% of what I use usually works. I’ll keep testing secondary keys to check.

<p>@sirvalley <br />Which AL version recently added the default templates, for many popular sticks and throttles… is that in 2.0? I’d recommend give that a try.<br /><a href=“https://github.com/chihirobelmo/FalconBMS-Alternative-Launcher/releases/tag/v2.0.0” target=“_blank”>https://github.com/chihirobelmo/FalconBMS-Alternative-Launcher/releases/tag/v2.0.0</a><br /><br /></p>

<p>Do you have the same throttle curves? Do you have the same windows calibration? Unless it is the same device on the same pc, I can’t see why it would be exactly the same. <br /><br />But how different are the throttles? If you are both flying together in formation and both go to a/b, is your speed the same once you both hit top speed?<br /><br /></p>

<p>@lrichings I use vjoy and Joystick Gremlin.</p>

<p>@badboy45 Configuration is on the Alternative Launchers launcher page. Look for an Orange icon with CFG marked “config”</p>

<p>@Necker <br />I think it’s one or the other (keyboard/hat -or- analog thumbstick) not both.<br /><br />There is a config option to control the overall speed of the cursor…<br /><br />Also, if you decide to use the analog thumbstick, there are some special cfg options to apply sensitivity-curves to the axes.<br /><a href=“https://forum.falcon-bms.com/topic/20793/how-do-you-slow-the-speed-of-the-x56-mini-stick-that-controls-the-cursor?_=1645415674255” target=“_blank”>https://forum.falcon-bms.com/topic/20793/how-do-you-slow-the-speed-of-the-x56-mini-stick-that-controls-the-cursor</a><br /><br />I haven’t tried it, but I’ve seen people recommend this setting in the cfg file:<br /><br />set g_nAxisExp_AXIS_CURSOR_X 50<br />set g_nAxisExp_AXIS_CURSOR_Y 50<br /></p>

<p>@drtbkj <br /><br />thank you, now all is set up correctly!! </p>

@drtbkj said in Warthog Slider as Gear Lever?:

@frederf said in Warthog Slider as Gear Lever?:

I have this kind of thing on almost every single TARGET script for aircraft with retractable gear: KeyAxis(&Throttle, THR_FC, 0, AXMAP2(3, DX1, 0, DX30));
TARGET takes your normal device/devices and disconnects them logically, replacing them with a virtual controller that the script programs. The script when run hides the non-excluded natural controllers and unhides the virtual controller. Windows 10 sometimes has an issue with a program (especially not admin rights) adjusting devices as that’s a security risk. I have occasional issues but for the most part works fine.

Then you bind the buttons 1 and 30 to gear up and down (or down and up) and you have a three position gear handle. The middle position is nice because you can leave it there and it won’t do either in case of an air or ground start.

Hi, Frederf, If I understand this correctly, it sounds like what I want to do, which is to make the slider a 2 posit DX switch. Please check my procedure

When I saw what you entered above, it looked to me like something that would go in a Config file. I looked in the TARGET GUI for such a place and found “view script” in the axis part of TARGET. I replaced the stock KeyAxis(&Throttle, THR_FC, 0, AXMAP2( LIST( 0, 39, 69 ), with what you wrote above. I went into the Virtual keyboard and saved the DX 1 and 30 commands to the events I tried this with the THRFC axis at the stock Dx_Slider_ Axis and at “none”
In all cases I see the same results. The “Gear Handle” works but the other switches do not.
Either I’m doing something wrong, or we’re back to what Sobo wrote: TARGET overrides AL and UI . And because of that , the only way this will work is if I program the entire throttle/base with TARGET. Do you concur with that?

You possibly goofed the .tmc file that the GUI creates. The GUI is just a pretty interface to write a script file for you. Both TARGET GUI and TARGET Script Editor are TARGET. Once the script is generated/written and run there is no difference between GUI and hand-written script as far as other software is concerned.

Then input-output chain goes like this: Joystick hardware -> logical controller -> Falcon configuration files -> F-16

Without TARGET in use the hardware and logical controller are fixed. You press trigger, button 1 comes out; can’t change it. TARGET virtual controller is an entirely separate logical controller from the game’s point of view. Running the script “unplugs” the logical controller and “plugs in” the virtual logical controller which is why you hear the USB plugging noises when you run a script. From a game’s perspective this is indistinguishable from unplugging one real piece of hardware and plugging in a different real piece of hardware. If Falcon is configured to use the normal Warthog controller and you change to the TARGET virtual controller you have to start all over.

Changing the TARGET script changes how the logical controller acts depending on the hardware input. (TBC)

@windnc60 This is fixed as well. Reassign x-y axis on the throttle and the avionics page and then go back to Joystick as the main Flight Controller.

@drtbkj - on the RL grip/stick the Paddle isn’t part of the grip - the only one to get this right and leave the Paddle off is Real Sim, even though they didn’t get the part anatomy and/or number of switch positions strictly “correct” either. In RL the Paddle is part of the stick itself, mounted on the top of an electronics box on the stalk.

The issue with small hands is what concerns me most - someone with smaller hands is really going to notice. I have pretty medium-sized mitts and the RL grip fits my hands like it was made for them…and I really notice how much bigger the TM one is. An even bigger issue would be if the button forces were to match the RL grip - they are much lighter than a real one, and maybe this is a reason why.

Personally, I like/prefer the heavier buttons and stick forces. Just plain feels more like an airplane.

OK, i managed to find how i do it.

I removed the PULSE+ from the 2 lines in the script and it works like a charm 🙂

Thanks guys 🙂

@mypc said in Warthog F-16 Joystick vs. CH Pro - anyone made the switch to TM?:

@icer [Thread hijack]
Thanks.

So, looking at this: MapKey(&Throttle, IDLEROFF, PULSE+DX51); If I had a simple dx32 game, that would put the switch in that position out of use and no longer sending a command, even when in that position?

I’m not sure, but if a game does not “see” DX33-128 (like BMS) I would say the script should not be run at all. You may be better off with something like Joy2Key for that but I really don’t know…

@drtbkj:

Well, this has been educational- It turns out button 7 is my airbrake full forward posit. And , 25 is the throttle based switch I have Launch Bar-Retracted to. When I turn those switches off, then the Game Controller “stuck” indications went out. I had to slap my head with that one. ;).
This has got me thinking that the issue may be in AL. Perhaps my DX Pinky shift got corrupted?

Yes, DX7 is AirBrake extend, DX8 is AirBrake Retract, center position is null. On my (stock) Warthog up position is DX25 (labeled Radar Alt to NORM), down is Null (I use it for Laser On\OFF (release) with Alt Launcher).

Just install Alternative Launcher and use it’s KeyMapping\AxisAssign setup and be done with it…

@Frederf:

I’m saying when you press keyboard Q, 5 lines are responding to that input. I do not understand how but clearly that works to step through the pages of the menu. My first attempt to try to “Q” with a DX button would be to exactly replicate those 5 lines but with the DX button input instead of the keyboard Q input.

e.g.
RadioAWACSCommand 34 -1 -2 0 0x0 -1
RadioMessageSend 34 -1 -2 0 0x0 -1
OTWRadioMenuStep 34 -1 -2 0 0x0 -1

Something like that. I do not know how it works.

Yes I tried those 3 lines but BMS/DX only reads the last line (MenuStep) and skips the first 2 lines - so nothing happens, unless I first press Q on the keyboard first to get the menu up, then it will turn the menu page. Thanks anyway.

Update: My work around eventually was to map those radio commands (Q, W, E, R, T, Y) using JoyToKey running in the background, which worked very well and exactly like the keyboard presses, ie it brings up the menu page and turns it as well. Incidentally, I got the Coolie switch to work using JoyToKey also.