Two problems firing weapons
-
You assume I have not viewed them (but I have- and have done so for nearly 20 years.) but this is not an operational error (unless someone can prove otherwise) but a controller issue.
I’ll say again I’m a veteran of F4 and when used last on 4.1 worked fine. It’s the mapping issue I have trouble resolving.-Pv-
-
4.1??
If it’s a controller issue, why not download a popular and known-working profile for the X-65F? You can rule out a few issues that way.
It’ll also be easier for others with the same setup to help you as you’d be starting from a known point; at this stage, nobody else but yourself knows how you’ve mapped out your HOTAS. -
I tried “fluke” profile over in the controllers thread. His gun fire does not work at all.
-Pv- -
You assume I have not viewed them (but I have- and have done so for nearly 20 years.) but this is not an operational error (unless someone can prove otherwise) but a controller issue.
I’ll say again I’m a veteran of F4 and when used last on 4.1 worked fine. It’s the mapping issue I have trouble resolving.-Pv-
No. I suggest you make a short video…
-
Fluke’s cursors and TMS don’t work also.
-Pv- -
I tried “fluke” profile over in the controllers thread. His gun fire does not work at all.
-Pv-Fluke’s cursors and TMS don’t work also.
-Pv-If it’s a controller issue, why not download a popular and known-working profile for the X-65F?
From a person who is “not active with the hobby” and saying that his profile “might be an ok-starting point”, which part of that registered as popular or known-working to you?
-
I tried the only profile I could find on this forum. If you know of one which is “popular” and “known working” I’ll try it.
-Pv- -
I’m a WH owner, so unfortunately I can’t really help you there. IIRC, the X-65F has been discontinued as well which doesn’t really help.
Just a wild idea here, but can you use a profile for a different Saitek stick? Will that work with the X-65 as well?
-
-
@Cloud:
http://www.72ndvfw.org/forum/m/5688083/viewthread/25194656-x65f-profile-keyfile-for-bms-433
C9
Thanks C9 but that is too confusing.
It doesn’t matter that Saitek doesn’t build or sell the stick anymore. It still works. I’ve been using it in FSX, DCS Warthog, Falcon4 (earlier versions) Evochron Mercenary, Orbiter, X Rebirth and Elite:Dangerous without fault.
It’s only the new bindings in 4.33 which cause me trouble and only two features are not working: TMS in the radar (TMS in the HSD works fine) and the gun fire. The gun FIRES but does not stop when I let go of the trigger.
None of my other games behave this way. When I played BMS 4.12391 with the same controller, everything worked perfect.-Pv-
-
When I paste snakepit’s bindings into the BMS default full key file changing nothing else in the key file, and no key bindings sent from my profiler software (just the DX controller button for the trigger command is sent) I get the same result. The gun fires without stopping as soon as I press and release the fire button.
-Pv- -
Fixed the gun trigger. This was arrived at completely experimentally.
key file = Full
Saitek profileler:
Advanced mode for the fire button
pressed = alt-/
released = /In the BMS full config, the plain forwardslash is not mapped. It appears for single action fire switch controllers like mine, some unused key must be sent to stop the gun fire once started.
On to the problem with the radar TMS. That problem would seem to be more complicated since it works in the other MFD.
-Pv- -
Well there’s your problem… not using DX bindings where possible.
-
When I attempted to use the DX binding provided by “snakepit” http://www.72ndvfw.org/forum/m/5688083/viewthread/25194656-x65f-profile-keyfile-for-bms-433 the results were as reported. The gun fired without stopping until empty.
At this point, the controller mapper has been the only solution which worked after an entire day of experimenting. Still need to fix the radar TMS which I have no ground for success.
-Pv- -
Strange… I suggest you check your SST not working while loading the DX setup at the same time. Open any text editor and press all of the joystick buttons. Also, check your controller panel and see any DX buttons are not keeping depressed while releasing the trigger.
-
I think you should focus on one aspect at a time. You’re using both the Saitek profiler and changing DX keymaps at the same time during your troubleshooting, so it makes it harder to isolate where the issue is. I suggest reverting back to the stock default BMS keyfile and starting a new Saitek profile that is empty and work on one issue at a time. Don’t delete what you already have, because if you correct the issue you can make some small changes and not to have do the entire profile over again.
With a clean slate, open Setup and in the advanced window press a button on the stick, whatever you intend to use for TMS-UP. Make sure the description/caption under the table actually shows that you pressed a button, even if it isn’t mapped to anything yet, it should still say Button 21 or Button 15 or whatever you press. Then go into the Saitek software and assign a key binding for the TMS-Up to the same button you tested before. Go back to the Setup page and verify it mapped correctly. Using the Saitek software to map it should now show the keypress and NOT say Button XX on the setup screen. If this part is working correctly, jump into a flight and test it out. If the problem persists, unload the Saitek profile all together (This is IMPORTANT for troubleshooting at this point), go back into BMS settings, and map the button using the normal procedures of clicking the callback, then pressing the button. Verify it shows correctly as a button being pressed and the callback in the setup screen. If all is working correctly, jump back into a flight and give it a try. If the problem persists at this point, then it is likely not a profile/software issue, it’s a controller or driver issue. If the problem is corrected, it’s probably a Saitek software issue (Which is my guess, I’ve never had anything but trouble with SST x64)
Your best bet to get it how you actually want it to be, is to do DirectX mapping via your keyfile. I saw previously you said it looked complex, but it is a much better solution IF you want to use the Shift Function to get extra commands from the available buttons If you don’t need the extra buttons, then unload your SST profile every time you want to fly, and you can just go through and use the BMS setup page to map your buttons how you want them. It is a tedious process to manually map everything in a text editor, but it isn’t really that complex to do basic mappings. There are plenty of explanations on the forums about how to do it and how it works, it really only takes a few minutes to look at it and figure out what you’re doing, but it can take time to manually find and map all the callbacks. Like I said, if you don’t use the Shift Function, you can easily do this all in Setup rather quickly. If I remember correctly, X65 registers itself with DirectX as two separate controllers, so there should not be any issues with having to adjust the Registry for extra axes or having more than 32 buttons.
Hope that helps a bit, let us know how it’s going. Personally, I think mixing/matching DX profiling and Vendor Mapping Software (SST in this case) is generally a terrible idea. I feel like the people who have published all the profiles with mix/match configurations are the result of people just being lazy and not wanting to take the time to do it fine-grain with DX mappings, so I would generally not trust a profile posted in the forums for anything more than guidance on which keys are mapped to which buttons if it includes the Vendor profile as part of the profile. But that’s just my opinion.
-
Turns out my controller, internal key mapping and controller mapping are working just fine. The TMS Up/Down commands were not being held down long enough. The vids I watched, nor the BMS manuals mention holding the button down for a length of time.
-Pv- -
Turns out my controller, internal key mapping and controller mapping are working just fine. The TMS Up/Down commands were not being held down long enough. The vids I watched, nor the BMS manuals mention holding the button down for a length of time.
-Pv-I don’t hold them down longer than in any other use, for the two cents it’s worth.
-
I never Hold down TMS/UP, DOWN to designate target… Did you mean DMS?
-
TMS = Target Management Switch.
SimDesignate “Same as TMS up”
SimDropTrack “Same as TMS Down”I remember back in BMS 4.1 all I had to do was tap the TMS up and I had a bug track. Now I have to hold it down for about 1 second.
I can live with that though makes it tricky sometimes if the target is moving on the scope.Added:
BMS Key File Editor Manual
Section 7:11 Supported DX Devices (pg 38)Saitek X45, X52, X55, X52pro, X65 (my stick)
Bottom line: Everything is working now. I have no trouble mapping key commands with the Saitek software which is quite flexible and intuitive.
I only need to know what the sim expects and that takes some interpretation and experimenting. Although the DX mapping by editing the key files
is easy for those of you who are familiar with it, I’m just trying to get the sim up and running and if that means I do things the hard way which gets the results
in a few hours as opposed to text editing which might take days of broken key file editing, I’d rather spend more time flying.-Pv-