Forgive me if this topic has been covered before, I did search, but could not find exactly what I'm looking for after trying numerous search parameters. Also, if it has, and you want to make that comment, please don't just give a snide "That's been covered before." Fine, give the url for it. (OK, obviously one of my pet peeves on a number of forums.OK, what I'm after. All this time I've thought I've been saving my settings in various permutations for different planes, with and without VoXATC, and various for ORBX FTX. Tonight I find that no, most of what I thought I was saving is not in the various setting .cfg files. In retrospect maybe I should have realized this as I now see that the settings panel has a left side labeled "Display Settings," and a right panel labeled "Other Settings," and all the save/load buttons are in the left panel. The savings I most wanted saved are all in the right panel. (For instance sound or ATC settings for when using VoXATC, or the joystick settings for different aircraft, and they are NOT saved in the .cfg file. What a waste!So, the question: Is there a way to save ALL settings (in one or more files) that would represent ALL the data from BOTH panels? If so, how, what are the files involved, and where can they be found - in a Win7 OS? I want my control settings different for different aircraft. I need different settings for VoXACT and not using VoX. How can I accomplish this?Many thanks.

Yes, there is, WR, but it involves the creation of a .bat menu file which will call one of any number of saved flights i.e. I created/saved a flight called, simply, "IFR", and it opens at CYYJ, not too much in the way of traffic, LOD=3.5, but with heavy, dense cloud, and almost zero-zero visibility. There's another called "VFR", with much more traffic, 'nice' clouds, LOD 5.5, at KORS - just right for low and slow. A third one launches the Maddog Load Manager, with the flight launching at Gate B8 at KSEA, and so on. I (now) save the controls with the purchased version of Pete Dowson's superb FSUIPC facility, which will recognise the aircraft (or the type of aircraft) that you have loaded, and will automatically assign the correct buttons / keypresses / sticks and calibration to that particular flight. I have two other bat files: one chooses between using EZCA or not,: the second launches Ken Salter's "Alacrity", to shut down a bunch of services and background programs, and then launching TrackIR: and lastly double-clicking on the Menu bat file to select which scenario I want to use.Originally it was somewhat different, and setup to choose particular aircraft.cfg, plus it's own 'controls.xml' file, but FSUIPC now does the controls, and that allows one to create a complete, selectable and predictable startup flight, with everything in place.If you're interested - pm me and we'll work through a 'how-to'.

Yes, there is, WR, but it involves the creation of a .bat menu file which will call one of any number of saved flights i.e. I created/saved a flight called, simply, "IFR", and it opens at CYYJ, not too much in the way of traffic, LOD=3.5, but with heavy, dense cloud, and almost zero-zero visibility. There's another called "VFR", with much more traffic, 'nice' clouds, LOD 5.5, at KORS - just right for low and slow. A third one launches the Maddog Load Manager, with the flight launching at Gate B8 at KSEA, and so on. I (now) save the controls with the purchased version of Pete Dowson's superb FSUIPC facility, which will recognise the aircraft (or the type of aircraft) that you have loaded, and will automatically assign the correct buttons / keypresses / sticks and calibration to that particular flight. I have two other bat files: one chooses between using EZCA or not,: the second launches Ken Salter's "Alacrity", to shut down a bunch of services and background programs, and then launching TrackIR: and lastly double-clicking on the Menu bat file to select which scenario I want to use.Originally it was somewhat different, and setup to choose particular aircraft.cfg, plus it's own 'controls.xml' file, but FSUIPC now does the controls, and that allows one to create a complete, selectable and predictable startup flight, with everything in place.If you're interested - pm me and we'll work through a 'how-to'.

Hi Paul J. - Thanks for responding. I'm not totally sure of everything you are saying but it sounds to me like your .bat file launches flights, and maybe other programs that you want along with them, and FSUIPC that saves the control settings for specific aircraft. But what then saves other settings in the "other settings" section such as voice sound on/off, ATC window on/off, using Directx10 or not, etc.?As to FSUIPC it appears to me that there is about a 50/50 split in these forums as to whether using FSUIPC, FSX settings, or the control program that comes with your input device is the best way to go. I have a registered version of FSUIPC, so guess I could try that, on the other hand I've got some Saitek stuff coming in next week, so will probably wait to see if their software offers me some functionality that I would otherwise lose, such as what they call their mode switch. I thing there software also may save aircraft specific settings, not clear on the yet.So I'm still left mainly with the "Other settings" question.Again, thanks.

DX10 is either checked or not checked within your "Settings-->Display", Wing, and will remain that way utill you un-check it. Same with the ATC window and voice (sound settings) on or off.."other settings" are saved when you save a flight. So - I want to make a VFR flight as a stock flight. I select my fav airport - say KORS, Cessna 172, parked in the open hangar, nice weather, battery off, mixture pulled, all other switches off - i.e. 'Cold 'n' Dark. I save it as the default flight, naming it "C172 - VFR". I then copy that fsx.cfg, renaming it as "vfr.cfg". Right so far?Next I do the same thing, but this time it's at CYYJ - Victoria, Cold 'n' Dark, and with the BN-2 Islander, but I modify the weather here to have two or three layers of 8/8ths overcast cumulus, with two or three visibility layers, say at ground level 1/8 mile, at 1500' - 1/4 mile, then 3/4 mile upwards to 6000'. That will be solid grey/white within a few seconds of leaving the ground. I save this as "BN2 - IFR", marking it (also) as the default flight. Close the sim, copy and rename the fsx.cfg as "ifr.cfg". I do the same with the Dodo Bell 206 and the Maddog. Now we have four cfg files, plus the original fsx.cfg.All controls for each of the four different aircraft are managed using FSUIPC profiles, with any single-engined aircraft using "single_piston", the twins using "twin_piston", the Maddog using "twin-jet", and so on. The aircraft type will be recognised by FSUIPC immediately, and all controls will be ready to use, calibrated exactly as you saved them with that last flight. (This is an outstanding application, and I have no idea why I didn't begin using it ten years ago! It just takes a bit of study, as the manuals are overly complex, but well worth the time and effort once it's in use.)The dos menu will launch whichever one I want, and everything presented will be set as I saved it. Nothing to change, apart from maybe a different airport or aircraft. It deletes the existing fsx.cfg, then copies the vfr.cfg as fsx.cfg. Same with the ifr or the Dodo cfg's. I keep backups of these and the original.Here's the menu.bat for anyone that wants to play:http://dl.dropbox.com/u/52676345/fsx.batand here's the EZCA on or off bat file:http://dl.dropbox.com/u/52676345/TrackIR%20-%20EZCA.batHave fun!

Thanks again Paul J. I think I get it now. The fundamental thing I was not aware of was that the "other settings" were essential being saved in the fsx.cfg rather than an individual settings .cfg file.So one last question. Are "other settings" saved to the fsx.cfg file when:1. You save a flight as a default flight2. Anytime you save a flight3. Each time you make a change and exit settings. I.e., this is where FSX remembers what other settings you've made so you can open and close the program and retain the last settings.Thanks.

Yes, yes and yes!The default flight saves a number of extra parameters which are read when the next flight or session is started - that's why it's essential that the default flight is a clean one. I.e. nothing running or loaded.When you change your traffic, for e.g. - that change will get passed on to the next flight or session, as each time you close a session the changes that you made are stored - either in the exe.xml, the dll.xml, the scenery.xml or the fsx.cfg. If we start by not loading EZCA - that change will also be remembered. There may be another but I don't remember off the top of my head. (Getting too old). :(