Coolie hat inop
-
I’ve setup the Warthog via bms controller UI, and I’ve setup the majority of essential hotas buttons with the exception of the coolie on the throttles. I highly desire to use that but I am stuck to get it functional. It works perfectly in DCS A10C. So I know it’s a programming hurdle on my end to tackle, but I just don’t know how. Anyone know what I need to do?
Sent from my iPhone using Tapatalk
-
Search the forum.
Asked and answered a gazillion times.
In short…due to shortcomings of the DX programming it can not be used through DX.
The only way known to use it in BMS is through Target which is the preferred method in the BMS community.
Search the forum for profiles. -
BMS doesn’t recognize joystick POV except that of primary device.
Here is one Example of my TARGET Script, you may modify this anyway you want.
I binded Coolie hat switch DX buttons, actually I wanted to handle axis with CS but somehow it didn’t work properly.
(Could somebody tell me what was wrong?) -
Search the forum.
Asked and answered a gazillion times.
In short…due to shortcomings of the DX programming it can not be used through DX.
The only way known to use it in BMS is through Target which is the preferred method in the BMS community.
Search the forum for profiles.Thanks for the reply. I did search under coolie hat in the warthog section with no clear results as to my question. Weird that it has been answered a gazillion times without a search result. That’s why I made a clear cut thread with topic of “coolie hat inop”, plus I am not familiar with the Warthog anyways. So, it sounds like if I absolutely need the coolie hat then I need to learn how to use and implement the TARGET software. I’ll do a search and see what comes up for tutorials on that.
Sent from my iPhone using Tapatalk
-
Ugh…. all this programming and scripts and profiles is making my head go into a flat spin (out to sea). Is there any ‘idiots guide’ or simple fix to my problem? I’m not much of a programmer and don’t really have the patience to learn this form of art. Any help will be greatly appreciated. I see people talking about target and dx and many other technical terms that are beyond my understanding. I’m not a pro at this sort of thing.
Sent from my iPad using Tapatalk
-
Ugh…. all this programming and scripts and profiles is making my head go into a flat spin (out to sea). Is there any ‘idiots guide’ or simple fix to my problem? I’m not much of a programmer and don’t really have the patience to learn this form of art. Any help will be greatly appreciated. I see people talking about target and dx and many other technical terms that are beyond my understanding. I’m not a pro at this sort of thing.
Sent from my iPad using Tapatalk
There is no magical key to press to fix the situation so no. Direct X programming of the devices (DX) brings with it the Windows limitation you are seeing. Software can get around that limitation (A-10C, TARGET) but for BMS there is no built in programming of the Warthog button functions. This leaves you with a few choices.
Option one: Borrow someone else’s programming and skip learning it. Up side is you don’t need to learn how it works but the down side is if anything goes wrong or doesn’t work properly you are still dependent on outside help to get it to function. There are several people who have donated their setups in this very forum.
Option two: Same as option one but digging in and learning how it works. The heavy lifting has been done already but with new knowledge you can fix your own problems and make modifications as desired to fit your own wants. This option demands more time investment than option one but has a bigger payout than option one since you can take advantage of more complex TARGET functions.
Option three: You live with current DX limitations and lose those abilities in BMS.
Obviously that is not an all inclusive list but I figure making another option where you just learn how it works and start from ground zero in building your own TARGET program file is a non starter. Option one is the option that demands the least time investment but there is no guarantee that you will be able to get something to work that you don’t want to bother to learn or that you will find a profile that suits your desires as to what switch does what.
The only option I can think of that minimizes programming is one I have never tried and I’m not sure if it could be done. That would be using TARGET to only program the axes and the coolie hat and using DX programming through the keyfile for the rest. Even if that would work you’d probably need to set up a device sorting file to verify the TARGET combined controller would always be in the correct position.
-
If you like, try use mine. Chihirobelmo’s Profile - Never Disappearing Warthog Setup Script. I updated the code since #3 comment of this thread.
In my code it is written
| MapKey(&Throttle, CSU, DX21); |
| MapKey(&Throttle, CSD, DX20); |
| MapKey(&Throttle, CSL, DX23); |
| MapKey(&Throttle, CSR, DX22); |And each lines mean “Map DX21/20/23/22 key to Cooliehat Switch Up/Down/Left/Right”.
DX## just means “##rd number button of your joystick” its just like “A” button of XBOX controller.
-
There is no magical key to press to fix the situation so no. Direct X programming of the devices (DX) brings with it the Windows limitation you are seeing. Software can get around that limitation (A-10C, TARGET) but for BMS there is no built in programming of the Warthog button functions. This leaves you with a few choices.
Option one: Borrow someone else’s programming and skip learning it. Up side is you don’t need to learn how it works but the down side is if anything goes wrong or doesn’t work properly you are still dependent on outside help to get it to function. There are several people who have donated their setups in this very forum.
Option two: Same as option one but digging in and learning how it works. The heavy lifting has been done already but with new knowledge you can fix your own problems and make modifications as desired to fit your own wants. This option demands more time investment than option one but has a bigger payout than option one since you can take advantage of more complex TARGET functions.
Option three: You live with current DX limitations and lose those abilities in BMS.
Obviously that is not an all inclusive list but I figure making another option where you just learn how it works and start from ground zero in building your own TARGET program file is a non starter. Option one is the option that demands the least time investment but there is no guarantee that you will be able to get something to work that you don’t want to bother to learn or that you will find a profile that suits your desires as to what switch does what.
The only option I can think of that minimizes programming is one I have never tried and I’m not sure if it could be done. That would be using TARGET to only program the axes and the coolie hat and using DX programming through the keyfile for the rest. Even if that would work you’d probably need to set up a device sorting file to verify the TARGET combined controller would always be in the correct position.
I would like to do option two, but I can’t seem to find a guide or ‘how to’ on the topic. Most of this stuff is all over my head. Is there any literature that can help me understand this?
-
If you like, try use mine. Chihirobelmo’s Profile - Never Disappearing Warthog Setup Script. I updated the code since #3 comment of this thread.
In my code it is written
| MapKey(&Throttle, CSU, DX21); |
| MapKey(&Throttle, CSD, DX20); |
| MapKey(&Throttle, CSL, DX23); |
| MapKey(&Throttle, CSR, DX22); |And each lines mean “Map DX21/20/23/22 key to Cooliehat Switch Up/Down/Left/Right”.
DX## just means “##rd number button of your joystick” its just like “A” button of XBOX controller.
Okay, this is good info for me. So what is the difference between a profile, a key binding, a script? Also, I’ve seen videos on how to load someone’s “profile” but I’ve tried it and wasn’t able to get things to work right. So I went back and uninstalled the profile. I think I may know why? Because I didn’t make the two files read-only? Would that cause certain buttons to not function?
-
Why don’t you just try again as it was told, make two files read-only this time?
-
Just did and still not working right. I have all axis working but all of stick and half of throttle buttons are not working as advertised. I’ve posted in Muds profile thread for assistance. Sounds like someone else is having the same issue as me.
Sent from my iPad using Tapatalk
-
Sounds like DeviceSorting.txt has wrong sort.
-
How do I fix that?
Sent from my iPad using Tapatalk
-
I’m not sure what I’m doing wrong, but I load file in correct place. I setup my axis and then exit and make my axis assignments file read only. I then load the script as instructed. Run BMS and test. All axis works, but I’m missing lots of button assignments like MSL step switch, all buttons on stick, and half of switches on throttle. The switches on throttle panel work as advertised.
I go to the controller page and test and there are no assigned functions for these buttons and switches, however I can’t assign the correct functions because they are not present in the list.
Here’s what I see:
Sent from my iPad using Tapatalk
Sent from my iPad using Tapatalk
-
Open BMS-Manual.pdf and press Ctrl+F to search for “DeviceSorting”.
“Thrustmaster Combined” must be at 1st line of the file.
Also make sure you select “Thrustmaster Combined” as a Primary Device(Search this word in BMS-Manual too if you are not familiar with the term).After you fix DeviceSorting and PrimaryDevice, Click any button…Trigger, TMS, Pinky etc and check what will show up at here.
-
-
The way i started with BMS was do all the stuff myself as you learn about the SIM you can tell whats important and necessary to have it bound to the HOTAS system.
-
I mapped all axis and used blank config in Falcon and blank TARGET profile aswell. Rebinded the Joystick buttons to the “Stick” section in BMS ( I had same problem as you with the button numbers, so i just redo the binding )
-
Launched up TE with unlimited fuel and just learn how to fly and get used to the new stick.
-
At point when i was able to do basic maneuvering i started to read Training manuals and went from Ramp start ; Navigation etc. etc. During this time i began to map key combinations to the keyboard and HOTAS which i knew i would use alot ( since there is really much to learn i am still at this point right now ). You have 32 DX keys ( 19 on stick ). The way i am doin it is to use DX keys for all buttons that can be pressed/held. For 2way; 3way switches and rest i use keyboard combinations like ctrl+alt+key or ctrl+alt+shift+key etc. so i have free unmodified ( or easy combinations like shift+key ; ctrl+key; alt+key ) keyboard buttons which i can map them later for quick use so there is no reason to put down both hands from HOTAS (example: whole ICP panel for which i bound unmodified/unshifted key arrows and numpad).
Because of this i know where is what, for things that are used only once on ramp or rarely i use the mouse.
My head was spinning too the first time i got my HOTAS i was totaly lost.
After all of that i must say it is really easy to actually do it just by goin step by step, you will understand how things work, for me next step will be meesing around with layers in TARGET.Hope it somehow helps you to chose your own path, remeber to be patient and do a backup of your configs in case of messing up ( i did mess up few times and had old backup key file ).
Rzax
-
-
I would like to do option two, but I can’t seem to find a guide or ‘how to’ on the topic. Most of this stuff is all over my head. Is there any literature that can help me understand this?
Yes you need to have the code you want to use and the TARGET user/script manuals handy. The TARGET manuals will tell you exactly how to do things.
-
Thank you all! It was the devicesorting.txt that was the issue. It still had my previous hotas on there as well as rudder pedals. I removed the old stick, moved like instructed and presto! Everything works like magic. Thanks for the great help!
-
I use Warthog throttle and Cougar SSC and was disappointed I could not use the Coolie Hat; however, once I discovered how to program the base switches for different functions for both on and off positions and how to use shifted layer on the throttle, all using DX buttons without Target, I found I had a surplus of available program options for the throttle despite no Coolie Hat. The Keyfile Manual is a valuable resource.