X55 keyfile -BMS -Full DX Programmed
-
This post is deleted! -
Version 5.1 keyfile updated with a minor fixes, though 5.0 worked allright it is better update to 5.1
DX Code line SimTriggerFirstDetent/ manual laser the fifth argument was missing, set to 0.
DX Code line Trim …fifth arguments set to 0/2/4/6 … changed to correct value 0.@Lynzoid. Why Viewcontrol ?? No TIR ?? I have special key for that too
-
This post is deleted! -
Yup, waiting for my TIR.
-
This post is deleted! -
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. -
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!