Where to put the wheelbrake?

[hoover]

Hi folks,

I’ve started with a fresh Dunc_DX profile as something ate my keyfile trying to get the Android tablet software to work, so now I am wondering where to put the wheelbrake? I used to map it to the paddle switch, but now that I’ve learned about AP override I’d rather keep that function on the paddle and put the wheelbrake somewhere else.

I have a pair of racing pedals that I use as a virtual rudder (clutch & throttle), so would it be possible to map the wheelbrake to the brake pedal?

I know this wouldn’t be realistic, I’m just wondering what you’ve come up with. I could also map it to a button on my racing wheel which sits next to me on my desk when flying, but that would even feel more unrealistic than pressing the “k” key

Thanks Uwe

[GetMeThis]

The way I understood Dunc_DX profile to be is that the paddle switch does both AP override and wheel brake while on the ground. I might be wrong though, still learning

[hoover]

@GetMeThis:

The way I understood Dunc_DX profile to be is that the paddle switch does both AP override and wheel brake while on the ground. I might be wrong though, still learning

Indeed, thanks for the heads-up. I only tried the paddle in the config screen and sure enough it came up with “ap override”. I’ll give it a go tonight.

Uwe

[Red Dog]

back when i had no toebrakes, i put it on the radio switch down on the throttle but shifted with S3in (UHF PTT)

[hoover]

Sadly no wheelbrake via paddle on the ground using dunc’s profile, I’ll try assigning my brake pedal next.

Uwe

[GetMeThis]

Have you compiled and downloaded the stick and macro files to your cougar? I think that’s where that’s set to work. I have it working and can see the “key presses” emulated in that foxy tester window. Same for the shifted padlock view via the trigger. Hope this helps

[hoover]

Just tried it last night after compiling & downloading (again as I used it before and never changed it) the dunc_dx tmm file to my cougar, but still no luck.

the keytest window shows a continuous stream of "k"s scrolling down the test window, but the sim only ever sees the AP_override it seems.

Any idea how to fix this?

On a related note, I mapped my unshifted coolie hat to the manual trim function and it works great, much better than the shifted version. However I cannot use the hat now to rotate the outside view, is there a way to get this function back to the unshifted coolie hat buttons?

All the best, Uwe

[Blu3wolf]

Discussed specifically in Kolbes manual, found both here and in your own install folder:

http://blu3wolf.com/falconbms/Kolbe/Falcon%20BMS%20Keyfile%20Manual.pdf

[GetMeThis]

Hoover,
Here the test window also shows the stream of “k”'s. And as you say the UI only shows AP override, however when I taxi or land the paddle switch does engage the wheel brake. Have you tried that.
I know I may sound repetitive, but I had the same thing and thought it didn’t work.
Just my 2c

[hoover]

@Blu3wolf: Thanks for heads-up, I’ll check the manual then.

@GetMeThis: Yep, I tried applying the wheelbrakes on the runway via paddle but it didn’t do anything.

Cheers & thanks again for the help,

Uwe

[hoover]

N/M, found it. No idea why “locate” came up empty.

Uwe

[Blu3wolf]

Hmm, its in mine!

C:\Falcon BMS 4.32\User\Joystick\Generic\Kolbe

I use a Cougar - I use Kolbes keyfile (with some minor modification).

And I would recommend his keyfiles for just about any user, regardless of stick. I would also recommend that users not using a Cougar modify the assignments to suit their stick.

If you are using a Cougar, its basically plug and play - although iirc you wont get wheelbrakes on the stick with kolbes (default) keyfile.

[hoover]

Thanks, I’ll give the v1.6_full version a go this evening. What do I need to do about the dunc_dx cougar programming, does it have to be cleared from the stick in some manner or is loading the keyfile enough?

Looks like I made the biggest booboo of all straight at the start: Assigning keys using the BMS UI instead of a text editor.

Cheers, Uwe

[Blu3wolf]

so the cougar programming is inside the stick. Loading the keyfile in BMS wont to anything to the stick.

You need to clear the programming from the stick, then load the keyfile. Honestly it comes down to how you want to use it - I use purely directX controls. Everything is assigned using directX, the same way that it works in the UI when you assign controls.

If you want complex IF THEN kind of controls, then you need to use Foxy to create a tmm file for the Cougar. If you want simple ‘I push the button, it does something’ type controls, then directX is fine for that - but you will need to clear the cougar first.

[hoover]

Sorry for appearing to be so dumb, but how do I clear the programming? Simply compile & upload a tmm file with a comment in it and nothing else?

Thanks, Uwe

[Blu3wolf]

Well, that would be one way… you could reflash it, or you could put it in windows mode - which disables all the fancy emulation features that let it pretend to be a keyboard/mouse and whatnot.