Jump to content

Archived

This topic is now archived and is closed to further replies.

wingclip

FSX Control Assignments

Recommended Posts

Hi Folks, Does anyone know which file I must backup/save that encompasses all my joystick control assignments to the FSX commands? For reasons of my own, I want to be able to save all my present joystick commands that I have assigned in FSX, (Deluxe Gold w/Acceleration Pack), so that I can reset the entire FSX controls back to its default setup. I see a file labeled "Controls.dll" and suspect that if I save that file I will be able to reinstall it and regain my present joystick assignments but I'm not sure. So does anyone know if that's the one, or is it some other file, (or combination of files)? Thanks

Share this post


Link to post
Share on other sites
Guest jahman

I would highly recommend you de-assign all your controls in FSX and use FSUIPC instead. You will never look back! Cheers, - jahman.

Share this post


Link to post
Share on other sites

Thanks but A: As I said I need to know for my own reasons and it's not because I'm being secretive. I just don't want to bore anyone with the details that would do nothing but confuse the issue. And B: I already have the FSUIPC payware version and it was, in my opinion, a complete waste of money.The guy that designed it is a genius in his field, but he absolutely sucks at making a user manual. I've made manuals for many years on how to use comples CNC equipment and machinery and rule #1; when you write a user manual, you do not include how and why the function works. That is a typical mistake with most user manual written by the people who made their own software. They don't understand that most people don't understand the processes that it took to make the software nor do they care. They simply want to know how to use it. I'm sure that my lack of excitement over FSUIPC may be coming through but you have to understand where I'm coming from. I have written dozens of user/how-to manuals in the 38 of my 55 years and I know something about the subject. The other problem this designer had was his obvious disdain for using pictures!? When one picture can speak paragraphs of words I have to wonder what the hell he was thinking! You SHOULD ALWAYS use pictures when it is possible. It almost seemed that he wanted it to be as complicated as possible and his manual certainly did that. In fact, he has several manuals that he's included with his payware, (at the tune of almost $40.00 bucks!), and yet he failed incredibly with conveying how to press a button on your joystick and make it activate a function on a particular plane like maybe pressing the 'waypoint' button on the GPS for instance. He gave NO EXAMPLES that were usable to the majority of us who DID NOT spend $5,000.00 on some flight sim controls but in fact, own the flight controls that fall in the $40.00 to $300.00 area. So no, I'm afraid I see FSUIPC in a completely different light. Then add to it the fact that the designer's idea of his so-called "support" is nothing more than a lot of pedantic sarcasm and you're left with a big waste of time and money. The Freeware version isn't worth the time to download either. Anyone considering this program needs to make sure that they kiss the &@($* of the designer, (it wasn't hard for me to forget his name), before they ask him for support. Even then, I doubt he'd say anything useful. I'm laughing right now because I just realized that I went off on this rant the moment I read the letters "FSUIPC" :) Please believe when I say that I am not in any way sore at you and in fact, I appreciate your attempt to help. This, (buying FSUIPC), is just something that has bothered me since day one. I never could get him to answer that question of how to make a simple command like the one I described. I just read his replies to similar questions, (I'm not the only one, you see), and then figured out that I wasted my money. So thank you for the suggestion but it's not going to help, (even if I did like FSUIPC). :) Rich

Share this post


Link to post
Share on other sites
Guest firehawk44
Hi Folks, Does anyone know which file I must backup/save that encompasses all my joystick control assignments to the FSX commands? For reasons of my own, I want to be able to save all my present joystick commands that I have assigned in FSX, (Deluxe Gold w/Acceleration Pack), so that I can reset the entire FSX controls back to its default setup. I see a file labeled "Controls.dll" and suspect that if I save that file I will be able to reinstall it and regain my present joystick assignments but I'm not sure. So does anyone know if that's the one, or is it some other file, (or combination of files)? Thanks
Look for the file 'standard.xml' in your main fsx directory. Best regards,Jim

Share this post


Link to post
Share on other sites
Look for the file 'standard.xml' in your main fsx directory. Best regards,Jim
Thank You Jim!! I found that file so I'm going for it.

Share this post


Link to post
Share on other sites
Guest jahman
Thanks but A: As I said I need to know for my own reasons and it's not because I'm being secretive. I just don't want to bore anyone with the details that would do nothing but confuse the issue. And B: I already have the FSUIPC payware version and it was, in my opinion, a complete waste of money.The guy that designed it is a genius in his field, but he absolutely sucks at making a user manual. I've made manuals for many years on how to use comples CNC equipment and machinery and rule #1; when you write a user manual, you do not include how and why the function works. That is a typical mistake with most user manual written by the people who made their own software. They don't understand that most people don't understand the processes that it took to make the software nor do they care. They simply want to know how to use it. I'm sure that my lack of excitement over FSUIPC may be coming through but you have to understand where I'm coming from. I have written dozens of user/how-to manuals in the 38 of my 55 years and I know something about the subject. The other problem this designer had was his obvious disdain for using pictures!? When one picture can speak paragraphs of words I have to wonder what the hell he was thinking! You SHOULD ALWAYS use pictures when it is possible. It almost seemed that he wanted it to be as complicated as possible and his manual certainly did that. In fact, he has several manuals that he's included with his payware, (at the tune of almost $40.00 bucks!), and yet he failed incredibly with conveying how to press a button on your joystick and make it activate a function on a particular plane like maybe pressing the 'waypoint' button on the GPS for instance. He gave NO EXAMPLES that were usable to the majority of us who DID NOT spend $5,000.00 on some flight sim controls but in fact, own the flight controls that fall in the $40.00 to $300.00 area. So no, I'm afraid I see FSUIPC in a completely different light. Then add to it the fact that the designer's idea of his so-called "support" is nothing more than a lot of pedantic sarcasm and you're left with a big waste of time and money. The Freeware version isn't worth the time to download either. Anyone considering this program needs to make sure that they kiss the &@($* of the designer, (it wasn't hard for me to forget his name), before they ask him for support. Even then, I doubt he'd say anything useful. I'm laughing right now because I just realized that I went off on this rant the moment I read the letters "FSUIPC" :) Please believe when I say that I am not in any way sore at you and in fact, I appreciate your attempt to help. This, (buying FSUIPC), is just something that has bothered me since day one. I never could get him to answer that question of how to make a simple command like the one I described. I just read his replies to similar questions, (I'm not the only one, you see), and then figured out that I wasted my money. So thank you for the suggestion but it's not going to help, (even if I did like FSUIPC). :) Rich
I understand what you're saying, and that's why it's wise to have a different party document software (a specialist at that, if at all possible). But once you get into FSUIPC (meaning the specific jargon) it really is a terriffic tool for FSX. If you'd like I can help you out with FSUIPC to get you going. Cheers, - jahman.

Share this post


Link to post
Share on other sites

Thank You Jahman, Even though firehawk gave me the answer I needed regarding saving the control file, I will take you up on your offer. I'm capable of building on the foundation of what I learn so I don't think I would need that much help but I may not have considered the more complex needs I might run into. I have the software installed and can get to it when I click on the "Add On" button on the task bar when FSX is open. So that said, here's the scenario: I have an add-on plane that has a number of panel switches which do not respond to any of the usual commands to turn on landing lights and panel lights, and in addition, has a number of switches , (like Night Vision and open or close the cockpit), that are typically not found in the control commands of FSX. I want to turn on the landing lights first and to do that I have to use my mouse and click on the switch in the cockpit. In fact I have to do that throughout the entire cockpit, but anyway; the first question is how do I turn on a switch that is typically keyed to a command within the FSX command layout? The second question is how do I turn on a switch that is NOT typically found within the FSX command layout, (like that Night Vision)? Not that it should matter, but the plane I'm using for the examples is the Iris A-10 Warthog. So can you give me a step by step example of those 2 scenarios? The controller I have for flying anything with 'stick control', (i.e. Heli's, fighters, etc.), is a Logitech G940 control system. It's pretty nice and has the ability to re-define all of its switches via a 'mode switch'. The mode switch has 3 positions and I presently just leave it in mode 1. If I should run out of places to add a function I would then switch to mode 2 and so on. The controller I use for any planes that fly with yolks is different entirely. It is all Saitek equipment made up of 2 throttle quadrants, a yolk and a switch box. The switch box is a FSX only control and not programmable but I have downloaded a program that can work that box if I am using FSUIPC. Anyway, the Saitek info may be irrelevant and I just put it in there in case there was something you may have needed to know. It also has 3 modes and works the same way as the G940 Thanks

Share this post


Link to post
Share on other sites
Guest jahman
Thank You Jahman, Even though firehawk gave me the answer I needed regarding saving the control file, I will take you up on your offer. I'm capable of building on the foundation of what I learn so I don't think I would need that much help but I may not have considered the more complex needs I might run into. I have the software installed and can get to it when I click on the "Add On" button on the task bar when FSX is open. So that said, here's the scenario: I have an add-on plane that has a number of panel switches which do not respond to any of the usual commands to turn on landing lights and panel lights, and in addition, has a number of switches , (like Night Vision and open or close the cockpit), that are typically not found in the control commands of FSX.
Generally speaking the central idea behind FSUIPC is that any switch/button/key assignment that you can make in FSX you can also make in FSUIPC. If you can make the assignment in FSX but after making the assignment the switch/button/key won't work, then making the assignment in FSUIPC will likely also not work. If a particular assignment doesn't work, and we rule out an aircraft add-on malfunction, what we have is likely the aircraft bypasses standard FSX controls. In this case you can still use FSUIPC but it gets more complicated, unless your aircraft is supported by LINDA. LINDA is software written in LUA that, for supported aircraft, mapps all buttons and switches in a VC cockpit to keyboard keys, buttons and switches of any hardware you may have. Check here to see if your aircraft is supported by LINDA, and if it is get LINDA here for free. LINDA was made possible by FSUIPC's support of the LUA object-orinted, interpreted language.
I want to turn on the landing lights first and to do that I have to use my mouse and click on the switch in the cockpit. In fact I have to do that throughout the entire cockpit, but anyway; the first question is how do I turn on a switch that is typically keyed to a command within the FSX command layout?
The short answer is you don't. What you do instead is use FSUIPC to map the "Landing Lights On" (possibly not the actual name, you will have look down the list of messages, and this is tedious but is what FSX shows to FSUIPC so it's not FSUIPC's fault that many message names are sub-optimal by not following the standard noun-verb-adjective sequence that would result in a meaningful sort order) and assign that message to your desired key, button or switch.
The second question is how do I turn on a switch that is NOT typically found within the FSX command layout, (like that Night Vision)?
  1. Request your aircraft be supported by LINDA developpers (feel free to post in your aircraft's support forum for to get others to request the same aircraft,
  2. Use FSUIPC Macros,
  3. Write some LUA code yourself (possibly already done by others in your aircraft's support forum).

In cases 2. and 3. I would suggest you get comfortable with FSUIPC first.

Not that it should matter, but the plane I'm using for the examples is the Iris A-10 Warthog.
Unfortunately not supported by LINDA at this time, but most complex aircraft do tend to respond to standard FSX messages like ñights, gerar, flaps, etc.
So can you give me a step by step example of those 2 scenarios?
The idea behind assigning buttons, keys and switches in FSUIPC is simple:
  1. Open FSUIPC,
  2. Click the proper tab for assigning buttons and switches vs. keyboard keys,
  3. click the button/switch or keyboard key you want to assign so FSUIPC can identify it,
  4. Select the appropriate message you want FSUIPC to send to FSX when that button/switch is clicked or key pressed,
  5. Repeat 2. - 4. for all assignments you want to make,
  6. Click OK.

Note for each particular assignment you make you can tell FSUIPC whether it is a global assignment for all aircraft or restricted to the particular aircraft currently loaded. --> See how far you get and reoprt back with specific questions you may have regarding the many options in these dialog boxes.

The controller I have for flying anything with 'stick control', (i.e. Heli's, fighters, etc.), is a Logitech G940 control system. It's pretty nice and has the ability to re-define all of its switches via a 'mode switch'. The mode switch has 3 positions and I presently just leave it in mode 1. If I should run out of places to add a function I would then switch to mode 2 and so on.
All hardwares pretty much is supported. Note FSUIPC allows you to assign FSX messages to complex switch/key presses involving more than one button/switch as well as to set internal flags that can be tested sow a button/switch/key can send different messages to FSX depending on the state of the(se) flag(s). This programming can get quite complex, so please start simple first until you are comfortable.
The controller I use for any planes that fly with yolks is different entirely. It is all Saitek equipment made up of 2 throttle quadrants, a yolk and a switch box. The switch box is a FSX only control and not programmable but I have downloaded a program that can work that box if I am using FSUIPC. Anyway, the Saitek info may be irrelevant and I just put it in there in case there was something you may have needed to know. It also has 3 modes and works the same way as the G940
  1. FSUIPC doesn't care about the brand or model of your hardware because all it sees is the button or switch being clicked.
  2. I assume you are using the SPAD driver for your Saitek hardware.
  3. Note I have purposedly avoided referring to axis assignments in FSUIPC as this is somewhat more complex, but not difficult once you get the hang of FSUIPC.
  4. Once you get the hang of FSUIPC the documentation (reference manua, really) starts to make sense.

Thanks
You're welcome! Cheers, - jahman.

Share this post


Link to post
Share on other sites

Thank You Jahman, You seem to have a pretty good grasp of FSUIPC. You are apparently not too familiar with the many add-ons that do not respond to FSX commands however. I personally have at least 4, (out of about 20 add-on planes or more), if not more that are, for whatever reason, not sensitive to any FSX commands with the exception of the landing gear. I'll be frank, it seems pointless to me to go through the hassles of FSUIPC if there is no advantage short of being able to apply commands to particular planes. I have read quite a bit of info, (and as much of that manual that I could stand), that contradicts your statement that FSUIPC cannot operate a switch if FSX cannot operate it. I'm going on the blogs where people who had "GoFlight" controls wanted to map their entire system to the FSX flight Sims and add-ons. They wanted to do away with using the mouse and/or keyboard to run all the functions that worked on the plane regardless of whether or not FSX was able to run it too. May I also point out the add-on planes such as the "Tilt Rotor" by Wilco Publishing. They specifically state that you must have FSUIPC to operate the plane, (free version), and they're not the only ones. That's because FSX commands will not work the plane. Aerosoft's F16, Iris's A10, and several Nemeth Helicopters all do not respond to FSX commands yet they are explicitly made for FSX, (Accl pack full version). Now I read where you said something about adding yet another program, (Linda), to this mess and I just have to stop and ask you where the advantage is?! I mean, ok, so FSUIPC will let you customize your action to each individual plane but so will PGP, Logitech Profiler, Saitek Profiler and the freeware AUTOHOTKEY. They are all profilers and I can say that even the most complicated ones are far easier to use than FSUIPC. I bought FSUIPC because I thought that it could operate switches on ANY aircraft, (as advertised I might add), and now you're telling me that it can't even do that!? Thank You for the offer and for your time, (I really truly mean that and am not being sarcastic), but I see no reason why you would think FSUIPC is something that once tried, I would never go back to anything else. Honestly, that's probably true only because of all the time I would have had to eat away setting up FSUIPC and even many months more if I wanted to "customize" my keys to each individual plane. So thank you very much but if FSUIPC can't even do something like work the switches that are not included with the FSX commands then I just have to face the fact that I misunderstood the whole point of having it and threw my money away, (it would not have been the first time). FSUIPC is beginning to look more like an unfinished program to me. I learned all the programming I could take from as far back as 1977 and all those languages are extinct now, (Fortran, Cobalt, and others in the CNC machine industry). I'm sure that someone will likely make FSUIPC just as obsolete within a few more years if they haven't already. I think I'll just wait. :) Thanks again

Share this post


Link to post
Share on other sites
Guest jahman

If you want to learn to use FSUIPC you need to start with the simple stuff, then you can do more complex assignments, but it's not realistic to skip the learning part and jump right in to the advanced features such as macros and LUA progrsmming that, as I explained, let you control absolutely every switch and button in your VC cockpit. Cheers, - jahman.

Share this post


Link to post
Share on other sites

Thanks Jahman, but seriously, I already use a semi-complex programming for button assignments in the profilers I mentioned. Of course, the profilers may be able to mimic a mouse movement and in turn that can lead to moving a VC cockpit switch. But it likely requires the LUA programming to do that as well. I'm involved in a number of projects right now, (not having to do with flight Sims), that already take up much of the time I have. So I am not prepared to apply any more time to LUA programming although the truth is I've always had an interest in trying to learn the "basics" of LUA and SDK's. Thanks for the offer and I actually agree with you that it would be unrealistic of me to expect to grasp LUA overnight. That's pretty much the case with any complex subject. But I also thought that FSUIPC had the whole thing packaged so that with, a good user/how to manual and some examples, would make the whole procedure less time intensive. As I said. I misunderstood the advertisements. The freeware was limited and they advertised it as such so I bought the full version without carefully deciphering what claims were being made in the advertisement. My screw up.Thanks again and I actually may try finding you if and when I complete my present projects, (about a month or so).

Share this post


Link to post
Share on other sites
Guest jahman

Well, you still have LINDA to check-out for any other complex aircraft you may fly. Cheers, - jahman.

Share this post


Link to post
Share on other sites

Thank You janvaane! I justy copied and pasted it all to a word Doc and printed it out. It looks like a pretty good breakdown and as soon as I get a moment I'm going to give it a try.Thanks again.

Share this post


Link to post
Share on other sites
Look for the file 'standard.xml' in your main fsx directory. Best regards,Jim
Hey There Firehawk, I thought you should know that your suggestion didn't work after all :( I just found out myself. I saved the "Standard.XML" file and stored it in a folder on my desktop. I then opened FSX and pressed the button that made the controller section go back to the Default setup. After that I did my various tests with the Logitech Profiler. Then today, I turned off the Logi Profiler and went back into the folder I saved the XML file in. I copied and pasted it back into the FSX section and reopened FSX. The control settings were not back! The settings that were there were the default settings, completely unchanged. I tried various things like restarting FSX under different conditions but nothing worked. I didn't try restarting the computer but I doubt that would have any affect. You sounded sure about it when you replied. If you never tried it yourself or were not certain, maybe you could have indicated that. But it's water under the bridge and I'm printing it here so no one else tries that.

Share this post


Link to post
Share on other sites

the controls are stored here:C:\Users\yourname\AppData\Roaming\Microsoft\FSX\Controlsand then the file: Standard.XMLOpen with Notepad

Share this post


Link to post
Share on other sites
the controls are stored here: C:\Users\yourname\AppData\Roaming\Microsoft\FSX\Controls and then the file: Standard.XML Open with Notepad
Thank You Janvaane! That information was invaluable! When I opened it I was elated to see that it contained every command that was programmed via the keyboard, mouse, and/or the control profiler which included the listing of the brand of controls that I had ever set up in FSX. So first I went through the entire list and highlighted all the controllers that were on that sheet. Because I had used a number of different control systems such as CH Products, and a joystick control set I tried but did not like such as the Saitek X- 52 Pro, (way overrated), I believe that I can go ahead and delete those titles and everything that was represented by them. Of course I would save a copy of the XML before I did that. Now correct me if I'm wrong, but I assume that after I make those changes and save it as an XML file I can then copy and paste information into FSX, (in the main section). Then when I open the "Controls" box in the FSX Settings I should see the remaining controllers and their commands. I'm going to go ahead and save a lot of information before I change it and do some tests because there are a few "blind spots" that I'm not so sure about. Apparently FSX automatically saves all the control information that it finds. Either that, or when I saved the last XML file before I change it all back to default, the result was the file I found in the link that you gave me. Thanks again I can see a lot of advantages to having access to that file. I'm sure that I read someplace in the manual of FSX how to go about finding that file but that was a long time ago.

Share this post


Link to post
Share on other sites
Guest firehawk44
Hey There Firehawk, I thought you should know that your suggestion didn't work after all sad.png I just found out myself. I saved the "Standard.XML" file and stored it in a folder on my desktop. I then opened FSX and pressed the button that made the controller section go back to the Default setup. After that I did my various tests with the Logitech Profiler. Then today, I turned off the Logi Profiler and went back into the folder I saved the XML file in. I copied and pasted it back into the FSX section and reopened FSX. The control settings were not back! The settings that were there were the default settings, completely unchanged. I tried various things like restarting FSX under different conditions but nothing worked. I didn't try restarting the computer but I doubt that would have any affect. You sounded sure about it when you replied. If you never tried it yourself or were not certain, maybe you could have indicated that. But it's water under the bridge and I'm printing it here so no one else tries that.
I apologize for the mistake. I did get the file correct. Just not the location where the working copy is located. If I had done a search for 'standard.xml', I would have found the correct info. Hope it didn't mess you up too bad but few people visit this forum and I know you were looking for a quick answer. I do know there's a standard scenery.cfg and a working config in another folder and should have figured the controls had a working folder too but I personally do not mess around with the controls much. I'll try to do better in the future. Best regards,Jim

Share this post


Link to post
Share on other sites

Say no more Firehawk! In the first pace it is I that needed to reaffirm/confirm any information I get when I ask a question anytime about anything. But that said, the worse case scenario was not that terrible. It would have meant reprogramming16 to 20 commands and I already had them mapped on paper. Doing that via the FSX panel is really very easy and would not have taken long. As it is, I have not yet tested the idea of pasting the XML file back into the FSX main folder and then checking to see if I recovered the commands I had before I went to the Default setting. I'm in the middle of something unrelated but when I get my attention back on it I'm going to have to figure out what is really happening with the XML file for controls. You see, I found that the file contained every one of my past controllers and the mouse and keyboard. In addition, each controller was listed with a 'regular' mode and a 'Slew' mode heading. In fact, there were 52 pages recorded and I'm guessing that the file just keeps getting bigger and bigger unless you delete the controllers you don't want or need anymore. Now if that's a fact, then when I clicked the Default button everything in that file that was not originally in FSX from the start would have to be ignored or a new 'Start Read" Point would have to be established for the defaults to work... I think. I say that because the Controller I had connected is the only one that was placed back to Default commands. What I mean is when I first hooked up my Logitech G940, (back when I got it months ago), I opened FSX without using the Logitech Profiler. This meant that the buttons on the controller, (Joystick and Throttle buttons) as well as some axis trim settings were activating various commands that were mapped the way the controller left the factory. Then I remapped the buttons and set sensitivities using the FSX control Window. Now before I ever had the G940 system, (which is a joystick flight system in case you don't know of it), I had done the exact same thing with my Saitek dual throttle yoke and pedal system. OK, so if you're still with me, after I clicked the Default button when I had the G940 connected, all the commands I had programmed in it went back to their factory commands. However, the Saitek controller's commands did not! Then things get REALLY STRANGE when I opened the 'Standard.XML' file that I presently have in the FSX main folder. It is supposedly the file that was made when I clicked the Default button. But when I went in there to look at it I was amazed to see that there were controllers listed which I have NEVER owned or had connected to this computer. Controllers like Thrust Master, Microsoft sidewinder, Logitech Game Pad, CH Products Pro pedals, and even a 360 XBOX!!!?If you look at yours you may see the same thing and then compare it to the XML in the link, (I guess that's a Data file location or something). I'm not sure what will happen if I paste the XML that is in the link that Janvaane gave me, to the main FSX folder. Will it simply transfer anything that is different from one to the other? These are all rhetorical questions but if you or Janvaane do know what's going on please let me know. Thanks, and please don't worry about the misinformation. I can assure you that I've done that a time or two... or three :)

Share this post


Link to post
Share on other sites

Again:the controls are stored here:C:\Users\yourname\AppData\Roaming\Microsoft\FSX\Controlsand then the file: Standard.XMLOpen with Notepad FSX does not use the standard.xml in the root folder of FSX; it's the standard which comes with FSX and it is copied into the C:\Users\yourname\AppData\Roaming\Microsoft\FSX\Controls - folder where it adds the hardware you've connected. So changes to be made there and NOT in the standard.xml in the rootThrtottle on.Jan

Share this post


Link to post
Share on other sites

Thanks Janvaane, and yes, I found that file and opened it with Notepad. But as I am indicating, there are some factors that I don't understand. Apparently, when I push the Default button, FSX refers to the XML file in the main folder. Actually, I really don't know that either. What it may be doing is referring to some 'default section' of the XML in the location that you gave me for all I know. But I think you can see what I'm confused about. It's that "Default" location and where, or which one, it is that is throwing me. The XML in the main folder must serve some purpose right? And if I want to recover the commands that I had when the Logitech G940 was connected BEFORE I clicked the Default button in the FSX control box, what would I do if not copying and pasting the info from the XML that you showed me to the XML that is in the main folder? You see? That's really my point. To recover the G940's command setting before I clicked that Default button. So I'm probably going to make some trial & error tests and see what happens when I get up the nerve and have the 3 or 4 hours to spend on it all at once :) Unless of course, you understand what I mean and know that answer.

Share this post


Link to post
Share on other sites

×
×
  • Create New...