Flounder's X52 Pro Keyfile/DX Profile for BMS 4.33
-
Looks OK as far as I can tell.
Everything was working OK before? You don’t recall making any change to the keyfile or setup? Adding any new devices (rudders, mfds)?
-
“…Everything was working OK before? You don’t recall making any change to the keyfile or setup? Adding any new devices (rudders, mfds)?” - I did not do these maneuvers, only the latest NVIDIA drivers. Previously, Your files did not cause any problems.
-
“…Everything was working OK before? You don’t recall making any change to the keyfile or setup? Adding any new devices (rudders, mfds)?” - I did not do these maneuvers, only the latest NVIDIA drivers. Previously, Your files did not cause any problems.
Really not sure what the issue could be. I don’t think it has anything to do with your BMS install (which you said you’ve reinstalled anyhow) or video drives. It could, I guess, have something to do with the Saitek/Logitech drivers, but I think that is pretty unlikely.
Only thing I would suggest is to remove the Flounder key file in BMS and the Flounder pr0 file from the Saitek folder, re-download them and update the key file and pr0 file from scratch. If you’ve already done that, I’m at a loss.
-
You were not wrong with Maestro, but I made your suggestion earlier. I will check your files in 4.33 U5, it is installed on the second disk. Good day. On the second disk, your Maestro files do not cause any problems, probably in the registry with x52 Pro drivers something is wrong, I suppose that remains of Logitech drivers. Thanks powerful for your express interest!:yo:
-
Mr.Agave, I installed the latest X52 Pro Logitech drivers in USB 3.0, reinstalling Falcon and your files “come to life” - VICTORIA. Thanks:drink::yo:!!!
-
Mr.Agave, I installed the latest X52 Pro Logitech drivers in USB 3.0, reinstalling Falcon and your files “come to life” - VICTORIA. Thanks:drink::yo:!!!
However, failure, “Do not praise the day before sunset.” As I mentioned it was good, now after pressing and releasing Pinkie, this button stays in the active position, it means that all functions only work in displacement, tragedy. Think about the problem, I’ve already exhausted all my ideas.:yield:
-
However, failure, “Do not praise the day before sunset.” As I mentioned it was good, now after pressing and releasing Pinkie, this button stays in the active position, it means that all functions only work in displacement, tragedy. Think about the problem, I’ve already exhausted all my ideas.:yield:
If you press ‘pinky’ again, does it go back the unshifted state? If so, see this post: https://www.benchmarksims.org/forum/showthread.php?18522-X52-Pro-DX-Profile&p=270540&viewfull=1#post270540
If pressing ‘pinky’ goes to the shift state and you cannot un-shift (either by releasing or by another press), check to be sure that the pinky command exists on that button as BOTH as shifted layer command AND as an un-shifted layer command. In this keyfile it should be on button 5 and (virtual) button 261:
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -2 “========= HOTAS UNSHIFTED =========”
SimTriggerFirstDetent 0 -1 -2 0 0x0 -1
SimPickle 1 -1 -2 0 0x0 -1
RecenterTrackIR 2 -1 -2 0 0x0 -1
SimMissileStep 3 -1 -2 0 0x0 -1
PrettyScreenShot 4 -1 -2 0 0x0 -1
SimHotasPinkyShift 5 -1 -2 0 0x0 -1
AFBrakesToggle 6 -1 -2 0 0x0 -1
SimToggleMissileCage 7 -1 -2 0 0x0 -1……
#==================================================================================
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -2 “========= HOTAS SHIFTED =========”
SimWheelBrakes 256 -1 -2 0 0x0 -1
SimEmergencyJettison 257 -1 -2 0 0x0 123
ReloadTrackIR 258 -1 -2 0 0x0 -1
SimCATSwitch 259 -1 -2 0 0x0 115
AFResetTrim 260 -1 -2 0 0x0 -1
SimHotasPinkyShift 261 -1 -2 0 0x0 -1
SimCBEOSB_6L 262 -1 -2 0 0x0 126
SimCBEOSB_8L 263 -1 -2 0 0x0 126……
One command ‘shifts’ the pinky, the other command ‘unshifts’ the pinky. It must be the same command on the same button and is normally 256 “button numbers” apart.
-
If you press “pinky” again, will you undo the state “unshifted”? No, he remains in the Shift state:;;
However, in this HD profile this problem does not exist, but was set in sst / DX: -
If you press “pinky” again, will you undo the state “unshifted”? No, he remains in the Shift state:;;
However, in this HD profile this problem does not exist, but was set in sst / DX:Ok.
Still need to validate these lines …. are they the same in your keyfile?
If pressing ‘pinky’ goes to the shift state and you cannot un-shift (either by releasing or by another press), check to be sure that the pinky command exists on that button as BOTH as shifted layer command AND as an un-shifted layer command. In this keyfile it should be on button 5 and (virtual) button 261:
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -2 “========= HOTAS UNSHIFTED =========”
SimTriggerFirstDetent 0 -1 -2 0 0x0 -1
SimPickle 1 -1 -2 0 0x0 -1
RecenterTrackIR 2 -1 -2 0 0x0 -1
SimMissileStep 3 -1 -2 0 0x0 -1
PrettyScreenShot 4 -1 -2 0 0x0 -1
SimHotasPinkyShift 5 -1 -2 0 0x0 -1
AFBrakesToggle 6 -1 -2 0 0x0 -1
SimToggleMissileCage 7 -1 -2 0 0x0 -1……
#================================================= =================================
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -2 “========= HOTAS SHIFTED =========”
SimWheelBrakes 256 -1 -2 0 0x0 -1
SimEmergencyJettison 257 -1 -2 0 0x0 123
ReloadTrackIR 258 -1 -2 0 0x0 -1
SimCATSwitch 259 -1 -2 0 0x0 115
AFResetTrim 260 -1 -2 0 0x0 -1
SimHotasPinkyShift 261 -1 -2 0 0x0 -1
SimCBEOSB_6L 262 -1 -2 0 0x0 126
SimCBEOSB_8L 263 -1 -2 0 0x0 126……
-
Ok.
Still need to validate these lines …. are they the same in your keyfile?
-
-
Hmmm. Looks right.
No idea.
Well, I will look further I have to, because your profile suits me best. Is it possible that I turned off something in “Services”? Thank you for your interest, Good beer should be. I checked “Services”, they are fine
-
Agawe I found, the culprit is a great program “Alternative Launcher”. After removing “A.L.” Pinky Shift works flawlessly - strange, but true.:drink::spy:
-
Agawe I found, the culprit is a great program “Alternative Launcher”. After removing “A.L.” Pinky Shift works flawlessly - strange, but true.:drink::spy:
Good news. Computers are so fickle. I hate 'em. :roll:
-
Good news. Computers are so fickle. I hate 'em. :roll:
Hehehehehe … the computer is not guilty here, just “AL” mixes something in DX with Pinky Shift. Because until I enter the HOTAS setting, it is good and does not create a problem, it changes the theaters’ way. Chihirobelmo has made the corrected version, now I have no problem with Pinky Shift in the profile “Flounder X52 Pro v5 - Full”:drink::blah:
-
I’m totally new to BMS Falcon and I thought I would try out this profile for my X-52 Pro. However at least some of the throttle buttons do not seem to work. For example the wheel scroll buttons do not change the radar range. Any idea what I could be doing wrong?
-
@ corvus5624 profile works correctly, you set it::yo:
-
So … it turns out I had the controller set to the X52 HOTAS instead of the keyboard … The config above is working now. Except somehow even if I set the Pitch Axis Deadzone and Roll Axis Deadzone so the joysticks Y and X axes respectively, these axes seem to be inactive. I.e. no response in-game and no response in the config dialog. These axes are kind of important I’m kind of in a jam here.
-
In my case it worked with the latest Saitek drivers, now I have the latest Logitech and there is no problem either:nerd:
-
I have the latest drivers btw. The problem is in setting the “Pitch Axis Deadzone” and “Roll Axis Deadzone” axes. I want to set these to the Y-axis and X-axis respectively. However when I set the Y-axis to pitch, the little axis indicator bar (which should be half blue/half grey with a centered stick) is completely grey. Now if I want to set it back to keyboard, the program does not do that, it just stays at Y-axis no matter what I select from the dropdown box. If I assign the Y-axis to the Pitch Trim, then the axis is recognized. So the joystick is working properly in BMS, it is just the Pitch and Roll axes that are giving me trouble.
Also the axes settings in the “Advanced - Flight Controls” tab are not saved. Even if I save my profile, after a restart the flight controls are all set to keyboard. Maybe I should do a reinstall …