Gibfender's X55 Profile
-
Yeah, I thought the same thing, but it’s my first HOTAS, so I’m not sure how the range knob is supposed to work. Again, for me it works with TGP, so that means that Falcon recognises the rotary. I’m starting to think that it simply shouldn’t change the range of FCR or other displays, because if it works correctly with TGP, and I set it directly from Falcon’s menu, then there’s no reson why it should not work for other purposes.
Can someone please clarify the function of the range knob?
Range Knob only works with the TGP for me. I am using a tablet to change the range of the FCR and other displays.
-
Oh, ok. So it’s not supposed to change the range. It looks like it’s working as intended, then.
-
Oh, ok. So it’s not supposed to change the range. It looks like it’s working as intended, then.
It does change the FCR range in AA mode.
Check in your install folder, Docs, Falcon BMS manuals, -> BMS-DASH-1 and look up the throttle configuration. There you will see what the range knob is used for.
EDIT : all the functions are not listed in the Dash-1. Basically :
- in AA, when FCR is SOI : change FCR range
- in AG, when FCR is SOI : change radar gain
- when TGP is SOI (AA or AG) : change TGP zoom.
I dont recall what it does when HSD is SOI, but I advise you to have the HSD range coupled with the FCR range. You can do that with OSB-2 on the HSD page (DCPL - CPL)
-
It does change the FCR range in AA mode.
Check in your install folder, Docs, Falcon BMS manuals, -> BMS-DASH-1 and look up the throttle configuration. There you will see what the range knob is used for.
EDIT : all the functions are not listed in the Dash-1. Basically :
- in AA, when FCR is SOI : change FCR range
- in AG, when FCR is SOI : change radar gain
- when TGP is SOI (AA or AG) : change TGP zoom.
I dont recall what it does when HSD is SOI, but I advise you to have the HSD range coupled with the FCR range. You can do that with OSB-2 on the HSD page (DCPL - CPL)
For me only TGP zoom is working. It’s strange, don’t you think? Because it obviously means that Falcon detects the rotary, but for some reason it’s not working in any other mode. Do you have any idea why this happens?
-
Actually, no, it dont know.
I dont use a rotary for my range Knob, only two keyboard press (My only problem with the Warthog, BTW). But there is a lot of Cougar owners over here that might be able to help.
-
Yeah, I thought the same thing, but it’s my first HOTAS, so I’m not sure how the range knob is supposed to work. Again, for me it works with TGP, so that means that Falcon recognises the rotary. I’m starting to think that it simply shouldn’t change the range of FCR or other displays, because if it works correctly with TGP, and I set it directly from Falcon’s menu, then there’s no reson why it should not work for other purposes.
Can someone please clarify the function of the range knob?
Thanks for this info, I’m struggling with this also. I’m using my own profile but couldn’t get range to work. I’ll try with TGP also. I will add my findings later
-
Ok, I was wrong.
Manual Range Knob does NOT change FCR range, ever. So it seems your Range Knob is working just fine !
For changing range (or antenna horizontal aperture, BTW) with HOTAS controls, drive the cursor to the edge of the display.
The name “Range Knob” is coming from earlier F-16 versions, when this knob also allowed to change the range for a gun sight display (IIRC, it was named LCOS). This gun mode is obsolete now.
That means there might be a bug with the “Manual Range Up” & “Down” that I am using to emulate my range knob, though
-
Ok, I was wrong.
Manual Range Knob does NOT change FCR range, ever. So it seems your Range Knob is working just fine !
For changing range (or antenna horizontal aperture, BTW) with HOTAS controls, drive the cursor to the edge of the display.
The name “Range Knob” is coming from earlier F-16 versions, when this knob also allowed to change the range for a gun sight display (IIRC, it was named LCOS). This gun mode is obsolete now.
That means there might be a bug with the “Manual Range Up” & “Down” that I am using to emulate my range knob, though
Ok, thanks for the explanation. I was already slewing the cursor to the top and bottom edges to change the range with HOTAS. I’ve known about this for years, when I was still slewing the cursor with the keyboard.
-
Looks like a good profile. Want to throw up a version that uses twist-rudder for those of us that cannot into hotas programming?
Many of your choices look a lot like my DCS Warthog setup, aside from which toggle switches on the throttle do what, so it should be easy to learn.
The biggest problem I have with other profiles is the use of the mouse nipple, which doesn’t work right on my Rhino, and I’m not going to send it in for replacement for such an inconsequential problem, when it’d mean weeks without my beloved stick.
-
Mine mouse nipple on X-55 doesn’t work as intended. Seems it works better when pressed.
I had similar problem with range knob. And also came to same conclusions. Ive decided to bind manual range changing to that rotary since this seems to be comfortable and quicker than slewing cursor to the edge.
I think I have made one interesting binding on the throttle - meybe someone will be happy with this idea: for one of the toggles Ive made a combo: hit Q, 0,5 second later hit 1. So with one move of my left thumb I get the picture from AWACS. On the same toggle but in up position I made a similar macro: Q and then 2. Usefull for quick declaring in combat. I use it a lot and find this very comfortable.
-
What are my options if I do not have rudder pedals? Since all of my buttons are messed up. None of them show up correctly when I load the profile.
-
What are my options if I do not have rudder pedals? Since all of my buttons are messed up. None of them show up correctly when I load the profile.
Are you using the HUD software? Try reinstalling the x55 driver. Make sure it’s the up to date one. I had this problem yesterday and once I reinstalled the driver, it all worked fine.
-
Yeah I have the HUD software. I just reseted my drivers. No luck.
-
Yeah have all the newest profiles and software. I just don’t damn get this.
-
Yeah have all the newest profiles and software. I just don’t damn get this.
I’m not sure exactly what your symptoms are - do you have a different order of joystick devices? With dx bindings you’re going to run into trouble.
-
Hi there -
I’m looking for a little bit of help installing this.
I’ve placed the files in what I think are their correct locations and selected the profile in the Rhino software. My problem is in-game. I can’t get the profile to work. How do I disable the default game settings, and get the installed Rhino profile to work?
e.g. I launch the game, but cannot control the aircraft.
Thanks,
Kart -
Make sure the X55 is selected under controller in the setup menu
-
Just got my x55 the other day. Tried using the profile (yes i loaded the profile in mad catz config) with the matching keyfile. I’m having issues with the throttle and stick sharing commands. For example in bms stick shows buttons 0-17, throttle shows buttons 33-63 (all hats save pov are registering as button presses) and i get a lot of commands being shared across multiple buttons (1 example is dms is assigned to a hat on both the stick and the throttle).
My current plan is to just enter all the commands in the keyfile manually assigning dxshifting/buttons. Unless you guys have a better solution.
-
PM me your email adddress. I’ll send you my profile and keyfile and you can give that a try. I just flew earlier this morning with no problems.
-
Thanks again chaos for sending that profile. Couple observations about the x55.
-
when working with the saitek/madcatz software I have experienced the “throttle ghosting.” I think this is more a problem with the software than the stick itself as I haven’t seen any ghosting since setting up the stick with pure dx controls in the bms keyfile. My guess is that the ghosting problem is twofold. First, the software turns the buttons into key-presses which are generally active in any window and windows doesn’t seem to like a lot of errant key-presses. Second, it is really easy to inadvertently leave a button set to hold a key without letting it go. Try holding a couple keyboard keys down and see how well windows behaves
-
I don’t have mfds or rudder pedals. Both Chaos’ and Gibfender’s profiles didn’t work for me out of the box. I’m pretty sure this is because BMS mapped my x55 to the same DX buttons as your rudder pedals and mfds. This showed some interesting behavior as I found my throttle and stick sending the same bms commands using different buttons compounded by further conflicts with the software mappings. What did seem to work in the end was to delete all the joystick entries in the keyfile and then use Chaos’ profile. I never did get Gibfender’s to work since it was more a DX keyfile map than a saitek software one.
In the end I took both maps and modified to fit my own needs with almost exclusive keyfile dx bindings/shifting. Only exception is the stupid slider on the throttle. What a retarded idea they had. It looks and feels like a slider but behaves like a button with no option to change. BMS doesn’t even see it as a dx button, so you are forced to map it using the buggy software. I currently have it set to turn the jammer on and off.
-