X55 keyfile -BMS -Full DX Programmed
-
I know i know Already got a hang of it.
Funny thought: what if i just use ‘+’ sign? say 31+64? Would that be recognised as a sum/total? Is that what you are saying???
-
I know i know Already got a hang of it.
Funny thought: what if i just use ‘+’ sign? say 31+64? Would that be recognised as a sum/total? Is that what you are saying???
No man, just do the math and replace as key files are plain text. Try SimTriggerSecondDetent 0 -1 -2 0 0x0 0 first replace the first 0 with 64, save and check BMS UI if that’s a correct call. If ID swapped then you get SimCursorEnable and then you work with ID swapped version, saves some time.
-
And it’s done! Stumbled upon a bug on the way. Good 1 hour it took. BMS is sensitive to the lenght of keyfile name. I tried x55[snelle etc originalfilename]-pov-2mfds.key and falcon CTD’ed when i tried to load it. I was checking line by line, digit by digit, and then just decided to rename it to ‘my.key’ and it worked.
Oh yea, mfds add to the immersion. -
And it’s done! Stumbled upon a bug on the way. Good 1 hour it took. BMS is sensitive to the lenght of keyfile name. I tried x55[snelle etc originalfilename]-pov-2mfds.key and falcon CTD’ed when i tried to load it. I was checking line by line, digit by digit, and then just decided to rename it to ‘my.key’ and it worked.
Oh yea, mfds add to the immersion.Yes, you obvious overcooked the name, glad it works out.
Could you upload a copy ? Would be nice to make this keyfile part of the collection also available for public sharing. -
-
This post is deleted! -
This post is deleted! -
Thanks Lynzoid for putting up the TM Cougar info, I will do update on first page shortly with these after streamlining.
-
I noticed problems with ACM turning Bore mode into slew mode unintended.
The problem probably is that microstick tends to ‘drift’, and as a result BMS detects movement in the throttle microstick and activates slew mode in ACM.
I read more about this issue here on other brand devices so I assume it is common.
The solution is to use larger deadzone on the cursor x/y in BMS advanced controller. -
Just asking… can current profile be used on U1? (Sorry if I missed the info somewhere!)
-
The profile works fine with U1. When I upgraded my USB IDs changed and instead of using the swapped ID file, I used the regular one. With this I discovered that some of the bindings in the swapped ID file are mixed up.
The shifted scroll wheel to cancel DGFT/MRM mode works perfectly, it didn’t work in the shifted ID file.
Shifting the front throttle rocker switch is bound to COMM IN/OUT as in the diagram. On the shifted ID file I couldn’t get this to work either
The 2 throttle hats now function as indicated in the diagram. In the shifted ID file the upper throttle had pushed forward activated the jammer, pushed backward deactivated the jammer, and pushed up was CMS forward (I think). The lower throttle hat would step through programs and modes. These now work correctly with the lower switch pushing down activating the jammer, pushing forward deactivating the jammer, and up and back running programs.Thanks again Snell for your excellent work. Here is a link to imgur with images of the English-language axis configuration: http://imgur.com/a/TPrYv
-Rabbit
-
Corrected issues with ID swapped version. Thanks for reporting these issues Attackrabbit.
New IDS keyfile in package, downloadable from the main page. Only the IDS version has been revised and nothing else.Interesting to notice that an upgrade to U1 shifts the ID state back to normal.
-
Hi guys……is only a my problem or i cannot obtain the shifted state?..in detail i’m press pinky switch but it not change any shifted function.
Best regards
Gabriele -
Hi guys……is only a my problem or i cannot obtain the shifted state?..in detail i’m press pinky switch but it not change any shifted function.
Best regards
GabrieleIs that all the detail you got? That leaves me assuming you use the standard profile, not trying to get shift readings from UI, etc
Whatever, when you follow the guidelines in documentation you will be ok.!
I.e. unless hardware failure of course. -
Yes i’m follow the guidelines and i’m load v4.00 profile in sst and 5ns in keystroke…and when i press th pinky in controller setup says pinkyswitch…but in the simulator no switch
Inviato dal mio ALE-L21 utilizzando Tapatalk
-
Ok solved!!!..…i’m replace your keystroke with an other “your” fresh keystroke and now it’s all OK…Thanks for your attention and yor profile Snelle!
-
Ok solved!!!..…i’m replace your keystroke with an other “your” fresh keystroke and now it’s all OK…Thanks for your attention and yor profile Snelle!
Any idea which version you were using first? Did you download from first page in this threat?
All key files as of v1.0 had a functional shift, I can rule that out for sure for what it’s worth.
Anyway…. glad you got it to work in the end. -
To access the shifted state, press and hold down the pinkie button for at least 0.5 seconds and then, while still holding the pinkie button, press the next button / switch. The pinky switch is the small circular button at the base of the stick. The larger paddle / trigger shaped button at the base of the stick is used to disengage the autopilot. To use the usual pinky switch functions (e.g. expand FOV for the TGP, activate EXP mode for the FCR), quickly tap the pinky switch for <0.5 seconds. Make sure you don’t have any profiles loaded (aside from Snell’s if desired) in the H.U.D. / SST Saitek software (the menu in your notification area that looks like a green rhino’s head)
-
Snelle, I just wanted to thank you for your hard work and dedication. I’ve struggled with X55 and BMS for some time. Then I found your post, I knew nothing about DX programming but followed the posts and read your instructions. Turned out my joystick throttle was ID swopped, but my rudder pedals (Milan) seems to have taken the first numbers so I used IDS version and renumbered the throttle unit buttons. Works a dream!
My only issue is my mini stick only seems to want to go up and left, probably hardware issue, I’ll see if I can change the cursor control to the current trim hat.
Thanks again!
Worther_1Sent from my Nexus 7 using Tapatalk
-
My only issue is my mini stick only seems to want to go up and left, probably hardware issue, I’ll see if I can change the cursor control to the current trim hat.
No other HUD profile active?
I assume you allready re-installed and recalibrated the X-55, else it is indeed probably hardware related.
EDIT :I wonder if it could be due to registry error of X-55?? If a reg-fix patch can make the cursor alive, is sure could malfunction easily to.
Look at the reg-fix inside and examine your registry if all content made it into the registry.
You have hardware conflict? check device manager.
Perhaps try delete all registry setting of X-55 manually, un-install and then re-install with Administrator privilige, after that apply reg-fix.It that does not help I would program the cursor on the H3 or H4. From the main page you can download an older version 3.0 developed before mouse x/y fix and with mouse programmed on H3.
You could use it as reference.
Good luck!-sorry for editing this answer a few times over.