@Madbrood:

Sorted - axismapping.dat was set to read only! Thanks!

Happy Days. Enjoy the HOG.

Something you may want to look into, is that Windows 10 powers down usb ports. There are settings that can be adjusted to fix that issue.

I just installed 4.33 and don’t see a “kolbe’s keyfile” in the docs folder. Can I use the code you pasted to “plug and play” with my warthog? The idea of binding all that stuff manually sounds like a nightmare and like OP I have never used the target software.

@Frederf:

As I understand it the script isn’t all of the binds. If you don’t explicitly bind a button TARGET will do it for you anyway. To actually get a null result the button must be explicitly bound to 0, a.k.a. the null output. A comment “handled by key file” suggests that the explicit bind was omitted from the script and the key file relies on this secondary behavior.

The other possibility is that particular TARGET script is excluding the joystick but puts the comments in the script for the joystick anyway as a reminder.

So if I understand correctly, its safer to bind in TARGET. The TM script manual is very basic. I wish there was something more comprehensive out there. There is scripting in some of the profiles that is not really covered that well in the manual, and TM’s support kind of sucks.

Prior to the issue, I was aware of the sorting issue. But I didn’t think it applied to rudder pedals as it has not buttons. I guess it does…Something good to know.

Thanks for you thoughts on the matter.

Hi,

I found a solution for my set-up.
I made a backup of target.tmh in the folder

\Users\Prot\AppData\Roaming\Thrustmaster\TARGET\Scripts

excluded all lines concerning MFDs and use now the DirectX assignments in the .key file for controlling functions in BMS via MFD-frames.

Greets
Prot

yes you do need to start target before running BMS. If you start target, from there you can link bms exe to run when script starts. my advice would be to create a script or gui. many more configuration possibilities

Hey Wingedsky, I ust got my FSSB pedals and ran into the same problem. Contacted Thrustmaster and they gave me no help there is no firmware for the pedals. when I ran the script with joystick and throttle and rudders, thrustmaster combined work but the rudders were connected to the Throttle. So I got around it by unplugging the pedals and then plugged them back in before opening BMS. In the UI they show up as t-rudder and work fine. It’s a pain but until Thrustmaster come up with something we’re stuck.

Rhino

Well, restarting Windows worked for me.
I suspect shadow play or FRAPS to be the culprit.
Most likely a double mapped hotkey or something.

Gesendet von iPhone mit Tapatalk

I think i feel you.
I traded my cougar for a warthog last year and found myself struggling with BMS configuration more than any other sim i use (probably due to how seamlessly integrated the cougar was to falcon4).
what i came to realize was that at the same time that we all moved from the cougar, there was also a shift in the tendency to highly-script everything into our Foxy profiles like we used to.
i remember, you could find tons of profiles, and many of which allowed you to be up and flying immediately with just some axis assignments.
the new method was , for sake of speed (which i dont entirely agree with since we all are now running USB3 in very fast CPU/Northbridge platforms that were not around, nor performant enough, years ago.) is to go with just DX strokes, instead of all the keyboard-mapping we were doing in Foxy.
So now, most everyone is actually not running much beyond the included profile in your C:\Falcon BMS 4.33 U1\Docs\Key Files & Input folder and just DX profiling. we also no longer need to save axismapping.dat - maybe thats why.

i personally miss all the automation i had in my cougar profiles customized, holding a button down for 2 seconds to get a third function, or even a macro of strokes, was pretty fun and it really made you get to know the keyboard strokes.

You can save the bottom lines from the key file, opening in Notepad, and then paste them into the new edited key file.

I got it working like it used to be.

I saved the BMS key file with a different name and in BMS setup and mapped the buttons on the stick and save the new key file.

Then i closed BMS and opened the key file with notepad and change the shifted keys

@Coco:

Hey Viking… check your messages

Checked. Thanks!

@Jasajas:

During early dev of the sidestick controller for the F16 it seems they set a"…… breakoutforce of no more then 1lb and no less"

http://www.dtic.mil/dtic/tr/fulltext/u2/a085085.pdf

A deadzone set to small seems to be a pretty good simulated break-out force.

: If the dev of the flight model have stated somewhere here that the response should be without any deadzone, then I definitly would thrust that above all else. Has he?

Cheers!

/Jaws

yes he has

No it´s working fine! Thanks a lot guys! 🙇

Hey guys,

I have fixed this problem, by simply reinstalling drivers (same as Trukeydriver; http://ts.thrustmaster.com/eng/index.php?pg=view_files&gid=1&fid=3&pid=311&cid=1) and have reorganized Morphine’s profile (as suggested bvy Sarg55). I am a happy camper (again 🙂 ). All I need to finally conquer is Air-to-Air Refueling.

On a side-note, W10 seems to be stable and BMS is a joy to fly.

Cheers,

Andrej

After experimenting with this script in Target I found 12 degrees to be too much and was then over correcting so instead settled with somewhere inbetween.
I think it really comes down to where the stick is located in relation to your body on whether the offset is needed.

Problem solved. indent key installed wrong way up. Thanks guys for your time

I believe I have it worked out. It was a matter of mapping the correct Axis Setup in the Cougar Control Panel and the corresponding axis in the TARGET Script Editor.
Now to figure out how to get the dual function of the Pinky Switch to work. (FOV & DX Shift).

Cheers!
-Growler

You can install the driver without touching the firmware. These firmware versions have also been around already for some years.

thank you for your quick response…