Maverick PRE
-
Hi! What is your joystick? I had the same problem with X52Pro. The problem was the assignment of commands for joystick in BMS using default file “BMS” for HOTAS Joystick. To assign commands for X52Pro I used file “keystroke”. Small Tip - It is best to use for joystick buttons direct commands without Shift, Alt, Ctrl operators, especially for TMS and DMS long/short functions!!!
i am using X52. i will try that
-
Most people that have “dumb” Mavericks are because they are firing when the Maverick is pointed the correct direction but hasn’t established a track within the missile itself. This is a reasonable problem because real Mavericks won’t fire without a track. There would be no chance to hit. Not so with BMS, you can dumb fire them and much wailing and gnashing of teeth comes after.
The key to the whole thing is to verify the track with the flashing (or not) bore cross on the WPN format. Flashing is not locked. Solid is locked. It is a small plus sign that wanders around the display showing the relative look direction of the missile seeker compared with straight ahead. You FCR lock the target in PRE, SOI switches to WPN, missile pointed at the target. Time to shoot? No! Verify the track and a solid (not flashing) bore cross.
is this for moving targets? could you kindly simplify your answer
-
because real Mavericks won’t fire without a track. There would be no chance to hit. Not so with BMS…
FYI Mavericks are always hot. You pickle and a missile will be launched.
-
You can tip the cursor in any direction to see if it moves or not. If it moves, it isn’t locked. When locked, the cursor won’t move.
-
You can tip the cursor in any direction to see if it moves or not. If it moves, it isn’t locked. When locked, the cursor won’t move.
i think it locks with TMS up but mine is not working due to settings with Saitek X52 i will change and try. as far as i remember from older versions it was tracking target. thanks for the reply
-
I had to write an X52 macro to make it work.
For example if you do want to map CTRL + UP, I had to program the keypress like
press routine:
Press (CTRL) delay (0.02s) press (UP)while pressed:
-nothing-release routine:
release (up) delay (0.02s) release (CTRL)It’s the same way with TMS, DMS, CMS. This way, also TMS/DMS/CMS/Comm switch long/short press will work.
TMS up long will not work when using a simple keypress in the saitek software because it will repeat the keypress instead of holding that key (try in the test menu).It took me about a week to figure that out
-
I had to write an X52 macro to make it work.
For example if you do want to map CTRL + UP, I had to program the keypress like
press routine:
Press (CTRL) delay (0.02s) press (UP)while pressed:
-nothing-release routine:
release (up) delay (0.02s) release (CTRL)It’s the same way with TMS, DMS, CMS. This way, also TMS/DMS/CMS/Comm switch long/short press will work.
TMS up long will not work when using a simple keypress in the saitek software because it will repeat the keypress instead of holding that key (try in the test menu).It took me about a week to figure that out
Thanks a lot. at least i have found someone facing same problem with me. i think this problem should be consider in new version release. i dont face this problem when flying with DCS A-10 Warthog
-
Why not simply assign DX buttons and be done with it?
-
Why not simply assign DX buttons and be done with it?
well actually that’s another thought i wanted to try but i am using 3 modes also with clutch which might mess things up
-
assigning DX buttons solve everything except DMS right assign is MFD 2 and i cant reassign to DMS right. does this make difference?
-
Why not simply assign DX buttons and be done with it?
I had some of the buttons doubled (X52 is missing one POV if you don’t have a tracking device and that’s been the way it is when i created the profile) and I didn’t quite get that working, so the macro was my solution… I’m always open for any better solutions since when one macro is running, you can’t start another one at the same time.
So, pressing TMS up and putting the airbrake out at the same time won’t work.
TMS/DMS is on one POV and since my ministick “spikes” from time to time, I’m using that in the shift state, preventing the mapping in DX.
I recently switched over to mapping all the single buttons in DX, but that’s “subject to change”.
I really need to map my radar cursor to the ministick, but didn’t figure out yet how to do it.If you have any good documentation about axis and button mapping in DX- I am always interested in improving myself
-
If I were the owner of an X-52 I would make use of SimHotasPinkyShift as a dual-purpose pinky button and shift. I probably would have a simple SST profile too so I could put the speedbrake on the slider axis or something. Most SST entries would be blank so I got the natural “fall through” DX buttons past the SST layer.
http://www.blu3wolf.com/falconbms/Kolbe/Falcon%20BMS%20Keyfile%20Manual.pdf This is all I ever needed to know about DX mapping in Falcon.
-
I had some of the buttons doubled (X52 is missing one POV if you don’t have a tracking device and that’s been the way it is when i created the profile) and I didn’t quite get that working, so the macro was my solution… I’m always open for any better solutions since when one macro is running, you can’t start another one at the same time.
So, pressing TMS up and putting the airbrake out at the same time won’t work.
TMS/DMS is on one POV and since my ministick “spikes” from time to time, I’m using that in the shift state, preventing the mapping in DX.
I recently switched over to mapping all the single buttons in DX, but that’s “subject to change”.
I really need to map my radar cursor to the ministick, but didn’t figure out yet how to do it.If you have any good documentation about axis and button mapping in DX- I am always interested in improving myself
For ministick you must choose bands in mouse with SST software and separate them by dragging from the lines it should be like first band wil be %33 and second %67 i am using than you can map cursor keymap…
-
Jep, you can map the ministick. But you can’t map it as an axis, only buttons. And it’s jittery on my stick… So I have the bands mapped in the shift state. Otherwise, it will randomly create that keypress. Which took me weeks to figure out and I even exchanged my keyboard until I found that my ministick has some spikes once at a time and then my cursor jumps to somewhere I never told it to be. I mapped the right arrow key to it…
That little switch next to the ministick is the HOTAS pinky switch on my setup.
It’s basically a workaround for bad hardware to be precise.
-
You CAN map it as a pair of axes; thats how I set mine up.
It requires a registry edit however, and it will cost you one other axis (as DX only likes having 8).
So, if you can bear parting with your twist rudder, you can download the registry fix from http://falcon.blu3wolf.com for your specific stick and run it.
After running the edit, assign the newly created axes within BMS as normal.
-
Thanks a lot, man! I tried to convert the x65’s mapping without success because I am missing the registry keys.
I have rudder pedals so loosing the twist axis won’t hurt at all.