Yes - of course it's Pete's latest, and yes I've read John's aircraft-specific tutorial, and it doesn't answer the questions I have which concern Profiles, shortened name substrings, and multiple-button/ketpress assignments when bringing in a GPS, hardware naming, plus a couple of other subjects. I also don't use CH Products, WideFS, GPSOut, PFC equipment, GoFlight.My 'problem', Jahman, is plowing through sixty-one pages of User Manual, plus another fifty-four in the Advanced Guide, plus the other pdf's that come with it (did I mention Linda?) - and then trying to glean what I've missed or not grasped in the other three or four privately-written ones which bear no relevance.Come to think of it - you said "That's odd"... but tell me, why did those folks feel the need to write and share FSUIPC tutorials...?PS - I've also sent you a pm. Perhaps we can chat or Skype offline about this later. I'd be quite interested to find out how far you've gone with it. Maybe steal some ideas!Cheers,

Edited February 6, 201214 yr by Paul J

Yes - of course it's Pete's latest, and yes I've read John's aircraft-specific tutorial, and it doesn't answer the questions I have which concern Profiles, shortened name substrings, and multiple-button/ketpress assignments when bringing in a GPS, hardware naming, plus a couple of other subjects. I also don't use CH Products, WideFS, GPSOut, PFC equipment, GoFlight.

I would suggest mastering the axis assignment/calibration, switches and buttons first, then when you got that working move on to the more complex stuff.

I also don't use CH Products

Most of John Cook's tutorial applies to non CH hardware as well (ecept perhaps configuring a reverse zone on the throttles).

My 'problem', Jahman, is plowing through sixty-one pages of User Manual, plus another fifty-four in the Advanced Guide, plus the other pdf's that come with it (did I mention Linda?)

A good recipe for indigesttion! Stick to John Cook's guide, then move to the FSUIPC User Manuals for greater detail "as needed" (except a fast first read to skim of the documentation and get an idea of what's in there).

then trying to glean what I've missed or not grasped in the other three or four privately-written ones which bear no relevance

Ah, Tutorial Confusion! I would suggest you only read John Cook's Tutorial (I've read the other ones as well and find John's to be the clearest, most effective, so I only recommend that one tutorial), and once you got the basics going (axis, switches and buttons, only then move on to the FSUIPC User Manuals.

PS - I've also sent you a pm

PM replied!Cheers,- jahman.

Edited February 6, 201214 yr by jahman

So saving settings in separate .cfg files doesnt work for some reason.

Just want to mention that those "saved" cfg files are abbreviated files. Only select settings are saved. I won't be at my FSX computer for awhile, so I can't specify which those are. I don't think, however, that those "Realism" settings are saved in them. (But, then again, I've never looked or that section because I never change those. So I could be wrong about that.) I do know, however, that the "saved" CFGs are significantly shorter than the normal FSX.cfg file.Rich

Edited February 6, 201214 yr by RSorochak

This is what changes the (for want of a better name) 'settings_test.cfg' contained after I made a few changes.It can be inserted into the sim after the aircraft/saved scenario is loaded and started.[GRAPHICS]TEXTURE_MAX_LOAD=1024NUM_LIGHTS=8AIRCRAFT_SHADOWS=0AIRCRAFT_REFLECTIONS=1COCKPIT_HIGH_LOD=1LANDING_LIGHTS=0AC_SELF_SHADOW=0EFFECTS_QUALITY=2GROUND_SHADOWS=0[sCENERY]LENSFLARE=0DAWN_DUSK_SMOOTHING=1IMAGE_COMPLEXITY=4[DISPLAY]BLOOM_EFFECTS=0SKINNED_ANIMATIONS=1TEXTURE_BANDWIDTH_MULT=157UPPER_FRAMERATE_LIMIT=0[PANELS]QUICKTIPS=0PANEL_OPACITY=100[TERRAIN]LOD_RADIUS=3.500000MESH_COMPLEXITY=75MESH_RESOLUTION=23TEXTURE_RESOLUTION=28AUTOGEN_DENSITY=3DETAIL_TEXTURE=1WATER_EFFECTS=6[WEATHER]CLOUD_DRAW_DISTANCE=3DETAILED_CLOUDS=1CLOUD_COVERAGE_DENSITY=8THERMAL_VISUALS=0DownloadWindsAloft=0DisableTurbulence=0[TrafficManager]AirlineDensity=0GADensity=0FreewayDensity=17ShipsAndFerriesDensity=0LeisureBoatsDensity=0IFROnly=0AIRPORT_SCENERY_DENSITY=2

Edited February 6, 201214 yr by Paul J

Rich, the reason for using the "Save" feature is so that those pesky scenery slider and realism settings can be saved.. The saved FSX cfg files are indeed shorted, but in other setting areas.

I would suggest mastering the axis assignment/calibration, switches and buttons first, then when you got that working move on to the more complex stuff.

Individually they are no-brainers, Jahman. It's how they treated when multiple control systems are spread over differing aircraft and profiles.. For example - if, 1)... say twenty keys are assigned for gps control, and you want these available for all aircraft.. does one have to assign these to all of the separate profiles - or can one assign them, leaving the "use Profiles" box unchecked, thus (perhaps) creating a 'default' assignment which will then be seen by all profiles? 2). In one of the docs I remember reading that the assignment wasn't 'fixed' until the "OK" key was pressed. Does this mean, then, that each of those twenty keypresses have to be done individually, i.e. open FSUIPC, assign say, button_4 on the Numeric Keypad (Nexxtech USB) to 'GPS NEAREST BUTTON', confirm it, hit OK, go back into the sim - and then back to FSUIPC and repeat the whole process over again? :(

Most of John Cook's tutorial applies to non CH hardware as well (ecept perhaps configuring a reverse zone on the throttles).

The first line states:-"This guide describes using FSUIPC to setup the CH USB Yoke, CH Pedals and CH Throttle Quadrant."... and John's guide doesn't answer those questions above, nor anything about profiles.I just have to plod on, I guess, make changes, do a 'compare' on the previous .ini and the new .ini file, checking and translating the numbers as I go. Batch files made everything so easy.... :lol:Thanks for your input, Jahman.

Paul,If you want to drive FSUIPC beyond the basics, you need to start looking at the fsuipc.cfg file in the FSX/Modules folder.Although the FSUIPC learning curve is rather steep at first, the steep part is surprisingly... short!For example re: profiles, try your hanad at assigning a single key to apply to all aircraft vs. a single aircraft. Then look at how the FSUIPC.cfg file changes and you will have the exact answer you are looking for, and your understanding will be deeper and more solid than you could have gleaned from even the best written user manual :("Trust me", once you have all your controls assigned and working to your satisfaction via FSUPC, you will never look back. Also the convenience of backing-up all your control assignments by simply copying a single file is tremendous.Cheers,- jahman.

Edited February 7, 201214 yr by jahman

"start looking at the fsuipc.cfg file in the FSX/Modules folder."I do this already, Jahman. I have the Single_Piston and the Twin_Piston finished, pretty much, and am now working with Twin_Jet, with the Maddog and Citation. Once solidified, the next step is to reduce the duplication into single 'default' key, buttons and axes sections which will give a smaller overall file size. Gotta go right now, but will be back later. Thanks for the response.

Edited February 7, 201214 yr by Paul J

Does anyone have any suggestions or recommendations?

Steph, How are you making out with your issues? Any luck?Rich

Edited February 7, 201214 yr by RSorochak

Note that it is possible to create multiple desktop program shortcuts to fsx.exe in order to start fsx with different fsx.cfg files (you would want ot give each one a unique name) using the /CFG: swtich. It's also possible to get fsuipc4 to load different fsuipc4.ini files, though it is sort of a kludge also via multiple shortcuts.scott s..

Aaah... you mean, like this, Scott?https://www.dropbox....onfigs?h=bc888e.. and called from something like this...@ECHO OFFCLS:MENUSET PATHC=C:\Users\pj\AppData\Roaming\Microsoft\FSX\SET PATHF=F:\Flight Simulator XECHO.ECHO.ECHO.ECHO 1 - Single PistonECHO 2 - Twin PistonECHO 3 - OnlineECHO 4 - HelicopterECHO 5 - Twin_JetECHO 6 - MaddogECHO 7 - LancasterECHO 8 - OriginalECHO x - EXITECHO.ECHO ....................................................ECHO.SET /P M=Type 1, 2, 3, 4, 5, 6, 7, or x to EXIT, then press ENTER:IF %M%==1 GOTO SINGLE_PISTONIF %M%==2 GOTO TWIN_PISTONIF %M%==3 GOTO ONLINEIF %M%==4 GOTO HELICOPTERIF %M%==5 GOTO TWIN_JETIF %M%==6 GOTO MADDOGIF %M%==7 GOTO LANCASTERIF %M%==8 GOTO ORIGINALIF %M%==x GOTO END@ECHO OFF:SINGLE_PISTONC:CD "%PATHC%"del fsx.cfgcopy .\Configs\Single_Piston.cfg fsx.cfg /Y 2>&1 1> NUL:F:CD "%PATHF%"start .\fsx.exeECHO.ECHO Hit the 'Enter' key when FSX has completely closed...PAUSE 2>&1 1> NUL:C:CD "%PATHC%"copy .\fsx.cfg .\Configs\Single_Piston.cfg /Y 2>&1 1> NUL:CLSGOTO MENU:TWIN_PISTONC:CD "%PATHC%"del fsx.cfgcopy .\Configs\Twin_Piston.cfg fsx.cfg /Y 2>&1 1> NUL:F:CD "%PATHF%"start .\fsx.exeREM start .\FPS_Limiter.exe /r:D3D9.dll /f:90 /x:OFF /l:OFF "%PATHF%"\fsx.exeECHO.ECHO Hit the 'Enter' key when FSX has completely closed...PAUSE 2>&1 1> NUL:C:CD "%PATHC%"copy .\fsx.cfg .\Configs\Twin_Piston.cfg /Y 2>&1 1> NUL:CLSGOTO MENU:TWIN_JETC:CD "%PATHC%"del fsx.cfgcopy .\Configs\Twin_Jet.cfg fsx.cfg /Y 2>&1 1> NUL:F:CD "%PATHF%"start .\fsx.exeECHO.ECHO Hit the 'Enter' key when FSX has completely closed...PAUSE 2>&1 1> NUL:C:CD "%PATHC%"copy .\fsx.cfg .Configs\Twin_Jet.cfg /Y 2>&1 1> NUL:CLSGOTO MENU:MADDOGC:CD "%PATHC%"del fsx.cfgcopy .\Configs\Maddog.cfg fsx.cfg /Y 2>&1 1> NUL:F:CD "%PATHF%"\MADDOG2008\start maddog_lm.exeECHO.ECHO Hit the 'Enter' key when FSX has completely closed...PAUSE 2>&1 1> NUL:C:CD "%PATHC%"copy .\fsx.cfg .Configs\Maddog.cfg /Y 2>&1 1> NUL:CLSGOTO MENUand so on....:Eofexit

The problem with this DOS script is that it looks 'like a DOS script'; there's no nice GUI, and it's a pain whenever a difference in the aircraft's controls pops up - such as an A2A B-7, or a B-707 with four jet engines. I use four or five separate home-built controllers, and each lever, button and switched needs to be configured, and a new control xml created, and there are buttons, too, which aren't available through the Settings->Controls interface. And it goes along with a different fsx.cfg.A better way, if you've been following this - is the use of FSUIPC: It will get away from six or seven separate files, and I can also see the possibility of calling different settings.cfg files, too, not from within FSUIPC (not that smart), but from a gui app which I found this morning.. http://www.autohotkey.com/. This is a lot like Visual Basic scripting, but with a lot of the hard work done for you. There's a forum, too with some bright ideas. So - early days yet, but as anyone who has a homebuilt cockpit knows - the hard work is in the research and planning.

I can also see the possibility of calling different settings.cfg files, too, not from within FSUIPC (not that smart),

Actually I would imagine it would be fairly easy to do this via a LUA script run under FSUIPC.Chhers,- jahman.

Im hoping someone can help me with an fsx scenery setting grumble.I have several add on sceneries such as Horizons VFR photo gen x, Aerosoft Gibraltar, Hong Kong, Heathrow, UK2000 Airports, plus i have FS Global mesh add on. In the accompanying documentation they all suggest changes to autogen display settings, texture settings, traffic and a plethora of other settings too numerous to list, in order to run properly, but none of the setting changes are the same for each add on.In addition to this, the type of aircraft i fly, whether it be a default aircraft, Abacus or PMDG usually needs some changes to the settings to look its best or to improve the fps depending on which scenery im using.Is there any way of saving specific settings that apply to the particular add on im using, so that i could select it easily but then change to another scenery/aircraft if i wanted and not have to set everything up again? Im guessing that the .cfg files have something to do with it and i have in the past saved different .cfgs but when i reload them the settings arent as i thought i had saved them.I found a forum link to an Orbx GUI called 'Fsxgo', but i dont know if it would solve my problem or not as im not sure all the setting changes suggested in my scenery add ons are covered by the scope of 'Fsxgo'.Does anyone have any suggestions or recommendations? The other problem i have is that i like to fly with the realism settings high, no auto mixture etc but my husband needs a more 'basic' setup. Is there any way of having both of our user preferences saved somewhere so that we dont have to keep changing the settings each time we swap seats?Hope someone out there can give me some advice as to the easy way to save different setups so that i can select them at will without having to change them every time i want to fly from somewhere different.Thanks in anticipationSteph

Hi Steph,I'm using FsxGo for different scenery settings : Orbx, Aerosoft Antarctica, IFR,VFR,... and I let it startup FTXCentral, AntarcticaX Scenery Tool , before it start's FSX

Yes - FSX Go would do a great job of this, too. The deeper one gets into FSX the more obvious and overlooked tools seem to be available! I got it when it first came out, looked at it, put it aside - but it might be a good solution for me too. Certainly Steph can use it: just create a "Steph_1" , 2 and 3 profiles.. this would work just fine.Jahman's long and steady support of FSUIPC has solved one half of the FSX multiple-controller configuration issue, and if FSX Go can use differing settings configs, and then launch TrackIR, ASE and then FSX - I'm sold completely.Great suggestion, Patrick - thanks for the post and your interest!Last - point - to other folks following this long and pedantic (sorry) thread - how do you handle the issue of the various FSX settings combinations, and how do you manage controller configuration when going between say, an A2A B-17, or the NGX, and then a Duke, and then a P-40?