Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
Is the device recognized in Windows (try the command "joy.cpl" to see any connected controllers) ?
What do you see in DCS when you open control settings ? Is the Stick/Throttle being recognized here (each column present, regardless of the mappings) ?
I found the two sets of software for the X55 Rhino (windows 7/8, and windows 10) at http://www.saitek.com/uk/down/drivers.php
So it has: "Pro Flight X55 RHINO (Win 10 only)" version with driver and software links for 32 and 64 bit.
What I found was when I tried to click the 64 bit drivers and software links to download them, Windows edge popped open a box asking which app I wanted to open it with (Chrome, Edge, or old Internet Explorer. If I select Chrome or Edge, it appears to just open a junk page. If I select the old Internet Explorer, it opened a window that appeared to be a straight link to a download. So using Internet Explorer, I was able to download both the "Pro Flight X55 RHINO (Win 10 only)" Software and Driver files.
I ran the software installer, and it opened up and installed as "Madkatz" files, but it did open in what is the generally recognized program if you were to try to use their garbage SST programming software.
So what I'm saying is the files are there, it just appears they are in some type of old FTP type of link that Chrome and Edge are long past understanding or even attempting to process, but did work as apparently W10 still has some sort of old Internet Explorer creeping around in it's software. And using that old Internet Explorer seems to be the ticket for what appears to be an old FTP type of site. FTP servers are still used somewhat, but in general it's understand that those older types of files and the whole structure of it was rife with security issues, which is why I think Chrome and Edge won't cooperate with those links.
I also noticed that using Edge, when I right click on the download links and the popup window that has things the things like "copy link", "print", etc, it has a selection that says "Open link in new Internet Explorer mode tab", and it does the same thing, opens a window with immediate links to let you save the files. So it appears the Microsoft is leaving a sort of older protocol in place, buried a little, but still available if you need to get at things like old FTP server links.
Can you see the device in windows gaming devices control panel?
I managed to download drivers as Hootman suggested through Internet Explorer and I see in DCS World Settings the columns with Saitek X55 stick and thruster and I do have rudder peddles but they are not connected. when I try and bind the wheel break setting ( in Axis commands) to my pinkie switch ( on the stick ) it won't bind. Both sticks are plugged straight in to separate USB ports, so power issue is not the problem. I am great full for all the help; I have spent hours of head scratching. Ray
So also you need to understand this about Saitek/Logitech HOTAS and sticks with pinky switches, which is generally used in conjunction with their "three modes".
In general, as best I recall, the pinky switches are not recognized by the vast majority of gaming programs as valid selections. You can google around and read up on that. if you look around you will also find a "solution" that the pinky switch can be recognized if you open the windows "setup usb game controllers" X55 properties settings where you can see and test all the buttons, sliders and triggers on the HOTAS. If you leave that settings window open in windows, the pinky switch will then be recognized in DCS.
I know this because I am/have been debating using the pinky switch as an added "modifier" switch. I just checked again, and when the windows HOTAS properties window described above is left open, DCS recognizes the pinky switch, for my X52 it is shown as JOY_BTN6, the same thing it is recognized as in the windows properties box.
The same holds true for the rotating selector on the X52 and I assume the X55, the selector that allows you to switch into the three modes in the Saitek SST software. The purpose of that is to expand by 3 times the amount of programmable combinations. Those show as JOY_BTN24, JOY_BTN25, and JOY_BTN26. But again, only if you leave the HOTAS properties window open in windows.
So it is possible to use those, the only benefit I am debating is if I want to add the pinky switch as a "modifier" in DCS which would then allow a whole new slew of assignments.
But to use those, you would have to have the HOTAS properties open in windows while you are both assigning and flying. If you assign them, and don't have that open later when flying, any assignments using that pinky switch won't work.
The pinky switch and rotating mode knob are unique to SST software, so games just don't recognize them. Why they work with the windows HOTAS properties windows open is something a smarter person than me would have to explain.
I'm debating using the pinky switch as a modifier. I use VoiceAttack, and have the majority of keystrokes programmed in DCS so I can use that. While I tried to stick to somewhat of a logical setup with the keystrokes modifiers, in the end it's not THAT important to me as I'm not going to be manually using those. Without VoiceAttack flight sims with tons of key combos are basically worthless to me, I'm not doing all that keystroking. Right now the majority of things I have left to program are mainly the radios and some rheostats, things like that, and those will probably be programmed using the pinky switch as a modifier. It's no great pain to leave the windows HOTAS properties open during flight, since I already have to start up TrackIR and VoiceAttack.
Hope this info helps you understand and progress a little further. Since you mention being a bit new to this, I highly suggest at some point you look into VoiceAttack as an option. It's only $10, and I think it is probably the best bargain utility ever released for PC gaming. I never (or very rarely) take my hands off the HOTAS. I even set up scripts, such as a voice command "set night lighting", that executes every setting I want, from setting the external and internal lighting to where I want, to adjusting the level of the NVS level. And scripts can be used for anything to combine actions using a single voice command. I also have a voice command "Jettison all stores", that selects all the stores locations and presses the eject button. If you try to do that manually, that's about 6 or 7 different key combinations or cockpit mouse clicks, including having to look down at the panel. I concentrate on what I'm doing or looking at, say my command and it's done.
There simply isn't enough combinations on a HOTAS in my opinion to set everything I want to set up, so VoiceAttack is the goto. It initially takes a lot of time setting up the VA profile, but many times you can find VA profiles offered by other people. I think there are VA profiles on the DCS site "files" section, don't think there's one for the AH-64 there yet, but I like creating my own anyway. And you can print out a HTML document of all the voice commands and keybindings that go with them. Just a suggestion, it will greatly reduce your workload, and less workload = more fun, right?