X55 keyfile -BMS -Full DX Programmed
-
Hello Snelle and thanks for an amazing keyfile job.
Q: as i understand with patch applied the nipple will move ‘sim’ cursor, not ‘radar/mfd’ cursor. or am i wrong. and if it’s sim’s one - now do i ‘click’?Your mini stick/nipple is now recognized as x/y axis, you can assign this axis in BMS controller setup. A screenshot of the BMS controller setup pages, also showing x/y setup mini stick, should have been in the package but did not make it to v5.0. I corrected this by adding the screensnhot to the package, so just redownload for an example.
The mini stick in the v 5.0 is intended to be stup as shown to move the radar cursor.Perhaps someone can provide me of a screenshot of BMS controller page in English? , of course with similar setup as shown in the example in package.
-
Ok, i see, thanks! Yes i will provide the screenshot as soon i finish reinstall of bms. Great work!
Oh, the pinkyshift - is it both sim pinkyshift AND hotasshift? Thanks -
Ok, i see, thanks! Yes i will provide the screenshot as soon i finish reinstall of bms. Great work!
Oh, the pinkyshift - is it both sim pinkyshift AND hotasshift? ThanksThe provided keyfile give you acces to DX shifted functions in BMS via the
pinkyshift
So not both as I´ve not programmed anything on the HOTAS -SST except for an AB toggle on the SLD. -
Ok, super keyfile! Only thing i omitted is trim yaw knob. One slight accidental touch and plane is trimmed.
But, i am postponing 4.33 due to poor performance. Sticking to 4.32u7.
Will the keyfile work unmodified (5.0)?
Thanks
ps. sorry for no screenshots. my win is localized and those dx names came out all garbled (non-us win7 does that). -
Ok, super keyfile! Only thing i omitted is trim yaw knob. One slight accidental touch and plane is trimmed.
But, i am postponing 4.33 due to poor performance. Sticking to 4.32u7.
Will the keyfile work unmodified (5.0)?
Thanks
ps. sorry for no screenshots. my win is localized and those dx names came out all garbled (non-us win7 does that).There are some differences between 4.32 and 4.33 and they are all documented in //DOC keyfiles section. To take the shortcut I took the DX part of my 5.0 4.33 and copied it into an original Kolbe 1.6 Full BMS 4.32.
edit: removed link for this keyfile, available per request.
-
Many thanks for personalised keyfile Downloaded.
Just flew first proper mission on 4.33 (yes, fps are lower but turns out it’s still well playable) using your setup (minus yaw trim knob).
Wonderful! -
Many thanks for personalised keyfile Downloaded.
Just flew first proper mission on 4.33 (yes, fps are lower but turns out it’s still well playable) using your setup (minus yaw trim knob).
Wonderful!As in RL cross checking the plane is manditory. Leaving the yaw trim out will make you feel miserable once in a while, especially when trying to balance a damaged plane.;)
-
Yes, but there’s no ‘dead center’ on this knob. How am i supposed to know the ‘zero’? Mark the knob with a marker?
-
In the flight control section of the advanced control page you can set the deadzone for the yaw trim control. I have it set to “medium” so that having the knob anywhere close to the middle of its range provides no yaw trim. The knob should have a small line cut into its top. When that line is pointing to 12-o-clock (straight up when looking at the throttle) you should be in neutral and have no yaw trim.
-
Great idea. Done.
snelle, i believe you got an error in your 5.0.
It’s either firstdetent or seconddetent (i am not near sim pc atm). There’s ‘0’ missing after -2 and before 0x0. I inserted the missing 0 and now gun works again.
I also made unshifted trim hat control the view, and shifted - trim. One question - what 0/2/4/6 mean after -1 -2 in it’s dx lines? I found out, that putting 0 for hats (even hats that are just dx buttons) won’t work. -
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!