X55 keyfile -BMS -Full DX Programmed
-
Got it!
Oh, snelle, one more thing - on my particular system the saitek profile you include is slightly unreliable. What i did - slightly longer ‘B’ keypress for slider (about 0.250 for both pos). Now my airbrake works every time. Guess it’s system/os dependent.This is why one better stays away from these profilers, though this suprises me as it is a very simple profile with 0,1 sec time hold for a single keypress. Normally the length of the keypress should be irrelevant for such, even set to 0 with quantonize it should function as normal.
-
Yup, but on my system i had missing AB toggles, ruining my landings, before i decided that i had enough. I even thought i had a faulty slider at some point.
Oh, and i had numerous BSODs (oh, windows, i’ve been ‘missing’ you and your ‘things’) re: saitek215.sys driver, before updating to latest driver/software. Now it’s not BSODing anymore.
As long as i remember using sticks (tm, ch, now saitek) there were always problems with drivers/ctds/bsods (spontaneous stick disconnect with tm, jitter with ch).
But i feel that X55 is THE flight system for falcon, no contest.
Thanks again! -
Ok, my cougar MFDs are here. Snelle, is your key file TM MFD friendly? Sorry for clogging up the thread.
-
This post is deleted! -
Ok. Will do. at this moment i am fighting with mfd’s wanting to be first 2 dx devices no matter what i do…
-
Ok. Will do. at this moment i am fighting with mfd’s wanting to be first 2 dx devices no matter what i do…
I was afraid of that, you can renumber X-55 as #3 and #4.
DX support for Cougar needs to be added.
Also another note on the BMS keyfiles: it has DX stuff implemented that needs to be stripped and replaced with X-55.
-
-
-
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.