![]() Compiler parses/converts the files into binary code.Foxy calls the Compiler with the name of the joystick file.Use Foxy to create your joystick and macro files.So to summarizes, the simple flow of data to use the emulation features of the HOTAS Cougar goes as follows: These joystick files can be pretty tricky to create so using a wonderful software, like Foxy, makes it that much easier. I will only say that Foxy (the great, beautiful, easy-to-use software that it is) is the main software that people should use to create the joystick files. Of course James could pop in here and say 'what about Foxy?' Well, there is a whole section on Foxy so I won't get into that either. There is plenty of information about the programming the joystick here, so I won't get into it, but just keep in mind that whenever you download (or upload - depending on how you look at the whole system) a joystick file to the HOTAS Cougar for emulation, it is the compiler that does all the work. It is called from either Foxy or the CCP. It is hidden in the background, and if all goes well, should never been shown to the user. The Compiler is my favorite part of the whole project and it's the software that is the least displayed to the user. So, this new application (to convert text files to binary files) was started and deemed to be called 'The Compiler'. The joystick sends the exact same signals to the PC as the keyboard would if it was producing the 'a' character. In other words, instead of the keyboard producing the 'a' character, the joystick does. Emulation means that the joystick can 'emulate' the key presses from the keyboard. I can understand if people do not understand what emulation means. This firmware, among other things, does all of the emulation for key presses and macros. Mark made most of the firmware (code that runs inside the microprocessor). About this same time, we needed an application to convert normal text files into binary code that the HOTAS microprocessor could understand. Slowly, I added more and more functionality to the F22Loader and made it more user friendly. Why was it called "F22"? Simply because it was based on it's predecessor, the F22 by Thrustmaster. Why was it called "Loader"? Because at that time we mainly used it to download preset files to the HOTAS. Of course at that time, we called it the F22Loader. And there we had the very first version of the HOTAS CPP. I started developing a very simple application that could communicate with the HOTAS through the very standard drivers that we had. So, they called in the big guns… me! (toot toot - that's the sound of me tooting my own horn). At that time, Mark and the rest of the hardware team was ready to include some software. I started at Guillemot in July of 2000, but only started on the HOTAS project in October or November of that same year. I am Software Engineer at Guillemot Corporation. But before we get into it all, I would like the first article to give you some history about myself, and what I did for the HOTAS. So, this section will be devoted to all the many things that you can do with the CCP that are maybe not so obvious from the documentation. Increase/Decrease the curving affect of any axis.Here is just a small list of configurations that is possible to do with the CCP: And when I say control, I mean CONTROL! The CCP is like your cockpit to your fighter jet. It is the main application that it used to control your Thrustmaster HOTAS Cougar. what the heck is a CCP? (maybe not in those words) Well let me tell you. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |