Need a "push" to convert to FSUIPC

[conao]

Hi all,

I have a joystick, a yoke, pedals, two different throttles and a couple more hardware that use keymapping to emulate MCP, EFIS, radios and even the FMC. I use these to fly 3 or 4 different aircraft, from a Baron58 to a 737-800. Of course, I'm getting tired of having to change the FSX assignments every time I want to fly a different combination of aircraft and hardware. So, maybe it's time to take the final step and convert everything to FSUIPC...

I've always had a payed copy of FSUIPC, but never really used it for much more than a few tweaks and to enable the add-ons. Regarding assignments, I just use a few keymaps that were missing to fully use my MCP with one of my jets. To be honest, I'm scared to delete all key assingments and axis from FSX and start configuring everything in FSUIPC!

The different options and technique is well described in the manuals, but my question is how to really plan the system as a whole. Do you really start by deleting everything from FSX? Is this really the right scenario for FSUIPC to take control over all my 4 different aircraft and they're specific usage of each hardware? Is there a way to backup FSX assignments, just in case I regret down the way?

As I said, I just need a final push and would appreciate to read your experiences and tips about it.

Thanks,

Marconi

[Pete Dowson]

The different options and technique is well described in the manuals, but my question is how to really plan the system as a whole. Do you really start by deleting everything from FSX? Is this really the right scenario for FSUIPC to take control over all my 4 different aircraft and they're specific usage of each hardware? Is there a way to backup FSX assignments, just in case I regret down the way?

On the latter point, I think your assignments are all saved in any case. You don't actually need to de-assign anything, just disable controllers. One switch, on or off!

On the first part, I'd recommend starting by editing the FSUIPC INI file. Make sure these settings are like this:

In the [General] section:

ShortAircraftNameOk=Substring

UseProfiles=Yes

In the [JoyNames] section:

AutoAssignLetters=Yes

The latter will make FSUIPC use letters (A, B, C, etc) for your attached controls instead of their Windows ID numbers, and this will be safer if you ever unplug them or move them.

Then, you say you have 4 aircraft. If they all need different assignments and calibrations, you would create 4 Profiles -- eventually. but first you should select a good default, typical of your 4, and make a good set of default assignments and calibrations. That's without a Profile. then when you load one of your "special 4" you can create a profile with a suitable name and let it inherit the basic default assignments and calibrations. Only then start tailoring them specifically. Same with each of the other three. Load, assign/create Profie, assign and calibrate differences.

Lastly, close FS and edit the INI file again. Assuming you use assorted variations (different liveries perhaps) of those 4 aircraft, you can go to the [Profile.<name>] sections and abbreviate the aircraft name listed thereunder (i.e. as "1=name") to something which will select all the variations of that aircraft but without including anything you don't want under that profile. The abbreviation can be a bit in the middle of all the names if you like.

That's about it really. Start like that, try it as you go.

Save the FSUIPC INI file as a safeguard. If you want to revert just remove it and re-enable FSX controllers.

Regards

Pete

[conao]

Hi Pete,

Thanks a lot for your comprehensive reply. Sounds like a good idea to start with a basic set of assignments to be used to create the specific Profiles later. I'll give it a try, but I have a few more questions below...

On the latter point, I think your assignments are all saved in any case. You don't actually need to de-assign anything, just disable controllers. One switch, on or off!

Ok, that works fine for the controllers, but how about the keyboard assignments? Let's say I need the key "K" to do something in one aircraft and something else in another. I assume I'd then need to de-assign it in FSX and use the Profiles in FSUIPC to assign it to different functions, right? That was the question... should I simply delete all keyboard assignments in FSX and redo only the really necessary ones in FSUIPC? Won't there be conflicts between FSUIPC and FSX if I don't do so? Or FSUIPC intercept the key strokes first?

Another thing, is it possible to use multiple keyboards (in FSX or FSUIPC). Are the keyboards treated as controllers?

In the [JoyNames] section:

AutoAssignLetters=Yes

The latter will make FSUIPC use letters (A, B, C, etc) for your attached controls instead of their Windows ID numbers, and this will be safer if you ever unplug them or move them.

I hope this one really works because I don't have an "exclusive" FSX PC, which forces me to plug and unplug all devices every time I fly in the "home" PC. My wife would kill me if I didn't do so! :smile: Is this still ok?

Thanks again,

Marconi

[Andydigital]

Pete has gone away on holiday for the weekend, so I will reply.

Another thing, is it possible to use multiple keyboards (in FSX or FSUIPC). Are the keyboards treated as controllers?

No it only works with one keyboard, if you have two plugged in it hasn't got a clue which one is which, but they both will action the commands assigned to them, you just cant assign a different function per keyboard/key.

In the [JoyNames] section:

AutoAssignLetters=Yes

Yes this works perfectly and if you are just starting out with a fresh fsuipc.ini without any existing assignments then its completely transparent to you and just works.

As for your question about keys being assigned in FSUIPC and FSX, well it is always best to remove ANY dual assignments and that includes key assignments, if you don't then unexpected things can happen, or at least both functions will be actioned whatever they maybe.

[conao]

It makes sense, Andy. Thanks a lot!

I guess it's now time for me to try it for myself. I'll probably come back with some more questions after that... ;-)

Regards,

Marconi

[conao]

Hi,

 

So here I am again, one year later and still not using FSUIPC for the assignments.  :-)

 

I guess my main interest was in the key commands, not in the axes, so I abandoned the idea for some time. But now I have LINDA and, oh boy, she's really beautiful!

 

With LINDA I got all my key commands mapped for each aircraft, including my MCP Combo and Switch Panel. Now I'm ready for the axes!

 

Just before I start, just wanted to get a thumbs up from you about my JoyNames section. I enabled the AutoAssignLetters option as per the instructions above, but I notice each controller is shown twice, with letters and numbers assignments. Is this correct or is it old garbage? Should I delete something?

 

[JoyNames]

AutoAssignLetters=Yes

A=Saitek Aviator Stick

A.GUID={01A1B850-1D49-11E2-8001-444553540000}

B=Saitek Pro Flight Yoke

B.GUID={101FDA10-1070-11E1-8002-444553540000}

C=Saitek Pro Flight Rudder Pedals

C.GUID={101FDA10-1070-11E1-8001-444553540000}

0=Saitek Aviator Stick

0.GUID={01A1B850-1D49-11E2-8001-444553540000}

2=Saitek Pro Flight Yoke

2.GUID={101FDA10-1070-11E1-8002-444553540000}

1=Saitek Pro Flight Rudder Pedals

1.GUID={101FDA10-1070-11E1-8001-444553540000}

 

Thanks,

 

Marconi

[Andydigital]

Mine is similar so I assume that is correct.

[conao]

Thanks Andy! I'll start working on the axes then!

 

Marconi

[Pete Dowson]

Just before I start, just wanted to get a thumbs up from you about my JoyNames section. I enabled the AutoAssignLetters option as per the instructions above, but I notice each controller is shown twice, with letters and numbers assignments. Is this correct or is it old garbage? Should I delete something?

 

I'm pretty sure this is actually explained in the chapter on Joystick Letters in the manual, but here goes with more detail.

 

When using the letters in the assignments, FSUIPC needs to relate those to the Joystick IDs, which are numbers, used when talking to the Windows joystick routines. These are found by doing a Registry search for the GUIDs and/or Names. Rather than have FSUIPC do such a search every single time when generally they will be the same (especially during one session), the FSUIPC initialisation does it once when FS is loaded, and only again when entering the FSUIPC options. The results are recorded in the INI file so the numbers can be matched up to the letters via the names and GUIDs 

 

Pete