Speaking of spares, just picked up an almost minty set (cursor needs fixing, im good at this kind of tinkering). Its s/n 18114 which doesnt show up in the old Cougar database. No one seems to respond to updating the data base, so i wonder if we should here in BMS forums?

Really appreciate the help guys.

Yeah I’d be up for a chat on TS3 Ice, just let me know what time you would be available.

You could if you used the keygen in the docs folder 🙂

@Blu3wolf:

If the X-65F were going to be resold, Id personally prefer it have the pickle moved. That was like at least half the reason I bought a Cougar in the first place, was accidental FOX TWOs.

I fully agree about the placement of the pickle. Also, the four-way DCM switch was too easy to activate inadvertently.

A question for the powers that be about the BMS Key File Editor if I may. Given that the original 16000 stick has been around for a while and is basically unchanged in the more recent FCS HOTAS version, are there any plans to place details in the KF Editor similar to the other main stick and throttle combos? Like others I am just starting this journey and plan on using DX as my mapping method, trying to prevent complications early on. While I am no computer wizard I plan on using the Cougar system to give me an idea about which functionality is probably most needed on HOTAS and am prepared to ‘give it a go’. If there were to be a TM 16000 FCS HOTAS tab in the Key File Editor soon ‘ish’ I would hold off on my child like self mapping attempt.
Thanks in advance

…I also have a real F-16 throttle arm assembly - with friction wheel/plate…8).

not sure if its still active in the code haven’t checked for a while but

in your cfg file add

should display analogue in bottom left of the HUD

BUT it is unrealistic As far as I know the F16 doesn’t have that display

I unistalled the opentrack software and now the right mouse button is working. Thanks anyway

Buddy guy right for the win bud

I’m tracking you and I have applied your wisdoms, thank you. Got the HOTAS set, working out an IR theatre occulus rift pov tracking quandary now. Looks promising! Much appreciated

@Mower:

I cant a way to LB2 work with any usb controllers…

It’s fussy in that it doesn’t seem to like it when more than one joystick is connected. Works fine with a Cougar (for example when rudders and throttle are connected via the joystick) or Warthog stuff when Combined but throw more than one USB controller into the mix and it goes all to hell. Shame really… plugging and unplugging makes it a pain in the ass, and as a result is getting alot less love from me than previously. Still hoping/wishing Andy Hollis is working on LB3, especially since the Longbow sim project (Combat Helo?) seems to be a dead rubber now.

@Malc:

I’ve kinda been won over by the “authentic” look, so am gonna leave it as is. Looking at Schnidrman’s throttle, it is not even close to being that worn and I realise now it has a way to go… Heck, it works fine, that’s all that matters, yeah? 🙂

Glad you came to your senses. There are stories to tell with that worn paint!

@Scotters:

Freemind, do you use the buttons on the Warthog Throttle’s base?

That was the idea and it should work. I was just to lazy to work on a keyfile and stoped using it altogether after I realised my VHF/UHF didn’t work as soon as I had assigned the HUD brightness to the right slider on the WH throttle. I will investigate further. As mentioned I will check out changing the device order.

@Scotters:

If that works, I may then get the TUSBA R2 for the cougar throttle, since what I like about the Warthog throttle is all the additional buttons and switches on it’s base, but I think the Cougar throttle would be more comfortable to use.

Sounds like a plan. I’ve got the Tumba R1 - don’t see any use in the R2 so far.

DX input is independent of your HOTAS. You only need to know which button is mapped to what DX number so you can map your callbacks appropriately.

All sorted 🙂 Thanks everyone.

I fly with a Warthog Stick and TUSBA Cougar Throttle with a keyfile I modified myself with the DX numbers of the different buttons. The Warthog throttle is also plugged in. Yesterday I accidentally unplugged the Warthog throttle and realized that the inputs of my Cougar TQS would not work in BMS. Quit the program, plugged the WH throttle back in and everything works just fine.

In order to avoid this - meaning I want to be able to unplug the stuff I don’t need – do I have to change the device order in the config file?
And would I than have to rewrite my keyfile with the then different DX numbers?

I’m a bit confused.

P.S.: Once I additionally set the HUD brightness on the WH throttle but then I lost a couple of buttons on my Cougar TQS. I thought that all devices have different DX numbers.

Good to hear.

You’re welcome. 😉

As you’re talking about Afterburnersounds: I once saw a video of a F-16 Afterburner Takeoff, there was a howling sound during the ignition of the AB. I freakin loved this sound and to listen to it so often. Are there existing soundfiles with such a howling AB-Ignition? I can understand, you would nearly to not hear it in the pit of your own jet. But there are a a lot of Take-Off’s before you in MP-Flights and Formation Take-Off’s, where your canopy is very near to other jets’ exhaust’s and you may hear it, even if significally dulled. I would love it!! I check for a reference video and will post it here.

Trying to find one but it’s nowhere to be found! Anyone help me out here?

Just a short note for those who are encountering these isues: I didn’t realize that the ccp after reboot loads a joystickfile by default. Because of my tinkering that file was not the correct one so everytime I had it fixed it, it was undone by the ccp with the following reboot. Very frustrating I tell you. So heads up…