"Power users" copying between FSUIPC*.ini's suddenly wont work here

[Morten]

Hi Peter

In the good old FSX days I was used to copy from ini to ini right away without any problems according to your guide here:

"POWER USERS note: if you have a lot of investment in your Buttons, Keys, Axes or Joystick Calibrations via FSUIPC version 4 then you will want to retain most, if not all, of that work. This is okay—those parameter sections are identical in FSUIPC5, though many [General] section parameters no longer apply. These won’t be deleted, so to create a tidy file, use an editor to copy just the [Buttons …], [Keys …], [Axes …] and [JoystickCalibrations …] sections over from your FSUIPC4.INI file to your new FSUIPC5.INI file. After that, check they all work and possibly re-assign those which have changed." 

Now with P3Dv4, I found that this simulator totally ignore whatever copied  values I put into the new applicable FSUIPC5.INI file, even though, strictly according to your guide above. Values that were originally based on the “Send direct to FSUIPC calibration” option. 
Moreover, what is really odd in my eyes, is that I copied and pasted from the exact same FSUIPC5.INI version - that is, from my second computer to my current main computer, both having the exact same installed P3Dv4 versions. But still my main computer wont react to ANY of the exact same" joystick" controls in use!! I can actually see all the assigned values inside the ingame FSUIPC GUI..!  

Before doing the copy/paste action, I strictly insured these actions:

1. Completely deleted ALL axis settings inside P3Dv4 on my current main computer.
2. Deleted FSUIPC from my P3Dv4 Modules folder on my current main computer.
3. Installed a completely fresh "untouched" FSUIPC5 version (identical to the version on the second PC) into the P3Dv4 Modules folder on my current main computer.
4. Ran a P3Dv4 session, just so that a FSUIPC5.ini would be created - didn't touch anything during that session / didn't open FSUIPC! 

.....No respond on any of the controls! What the heck am I missing out?!!

Yes, of course I could do another configuration, BUT in this case we are talking about many physical controllers, including a 4-engine quadrant including reversers, mixture/propeller/spoiler pins and pedals with differential brakes,  which would take me HOURS to complete and finetune!

In use: Win.10 Pro 64, P3Dv4.3,  FSUIPC5 vers. 5.14   

Regards,
Morten

[Pete Dowson]

34 minutes ago, Morten said:

Now with P3Dv4, I found that this simulator totally ignore whatever copied  values I put into the new applicable FSUIPC5.INI file

Are you sure you are actually changing that file? Because there's no way FSUIPC will ignore any settings it is able to read!

36 minutes ago, Morten said:

But still my main computer wont react to ANY of the exact same" joystick" controls in use!! I can actually see all the assigned values inside the ingame FSUIPC GUI..!  

Ah, if you are only talking about joystick device assignments, then it is extremely unlikely that both PCs have the same IDs and same GUIDs for the same devices. You need to check your orginal INI'd [Joynames] section and compare with the new one generated, or the one logged in the LOG file. hen you can edit them to be the same. (This is much easier if you had first set FSUIPC to use JoyLetters -- i.e. on the first PC.

The "POWER USERS" note you refer to is referring to changing from P3D3 (or FSX) to P3D4 on the same PC without other changes like removing and reconnecting all devices. No way will two separate PCs generate the same GUIDs for the devices, and they are crucial to the DirectInput access FSUIPC uses.

The same thing would apply with FSX on both PCs. It isn't related to FSX or P3D3 to P3D4.

Pete

 

 

[Morten]

Hi Peter

Thanks for your quick answer!

However I'm a bit confused. Not quite sure what to edit from what...?
Have struggled with this issue now for hours!!

Hereby attached the involved files for clarifying or a quick edit maybe... 

Best,
Morten  

FSUIPC5_From NEW pc.ini

FSUIPC5_From OLD pc.ini

FSUIPC5_Log from NEW pc.log

[Pete Dowson]

6 hours ago, Morten said:

Not quite sure what to edit from what...?

Just the Joynames section!

Here's that section from your old INI (with the oddly placed space lines removed:

[JoyNames]
AutoAssignLetters=Yes
1=USB  ADAPTOR
1.GUID={EE32BE70-6492-11DF-8001-444553540000}
U=<< MISSING JOYSTICK >>
R=<< MISSING JOYSTICK >>
A=Saitek Pro Flight Yoke         
B=USB  ADAPTOR
B.GUID={EE32BE70-6492-11DF-8001-444553540000}
C=Saitek Pro Flight Combat Rudder Pedals
C.GUID={844B0DD0-9238-11E0-8001-444553540000}
2=Saitek Pro Flight Combat Rudder Pedals
2.GUID={844B0DD0-9238-11E0-8001-444553540000}
0=Saitek Pro Flight Yoke
0.GUID={76070770-648E-11DF-800E-444553540000}

The missing U and R lines in both can just be deleted. They must be historical as you have no such assignments. (In fact you have very few assignments, so with all your confusion I would have thought it quickier to start over in any case -- 13 axis assignments and only 3 buttons assigned! From what you were saying I thought it was a mammoth set of assignments and profiles! (Your calibrations would have still been okay).

Anyway, your active devices above are just:

0=Saitek Pro Flight Yoke
0.GUID={76070770-648E-11DF-800E-444553540000}
A=Saitek Pro Flight Yoke         
(with a missing A.GUID line which should be there too!!!)

1=USB  ADAPTOR
1.GUID={EE32BE70-6492-11DF-8001-444553540000}
B=USB  ADAPTOR
B.GUID={EE32BE70-6492-11DF-8001-444553540000}

2=Saitek Pro Flight Combat Rudder Pedals
2.GUID={844B0DD0-9238-11E0-8001-444553540000}
C=Saitek Pro Flight Combat Rudder Pedals
C.GUID={844B0DD0-9238-11E0-8001-444553540000}

Doing the same arrangement from the new INI

0=Saitek Pro Flight Yoke
0.GUID={419D8620-EA3C-11E8-8001-444553540000}
A=Saitek Pro Flight Yoke         

1=USB  ADAPTOR << MISSING JOYSTICK >>
1.GUID={419DAD30-EA3C-11E8-8002-444553540000}
B=<< MISSING JOYSTICK >> << MISSING JOYSTICK >>

2=Saitek Pro Flight Combat Rudder Pedals
2.GUID={A675B770-EA3C-11E8-8001-444553540000}
C=<< MISSING JOYSTICK >> << MISSING JOYSTICK >>

You see that all the GUIDs are different? That is because they are generated new by Windows when it first sees the device! That was your problem. The actual ID numbers (0, 1, 2) are okay. 

So, it is almost correct. You only need to reproduce the 0, 1 and 2 lines and put the A, B and C in. Thus:

0=Saitek Pro Flight Yoke
0.GUID={419D8620-EA3C-11E8-8001-444553540000}
A=Saitek Pro Flight Yoke
A.GUID={419D8620-EA3C-11E8-8001-444553540000}

1=USB  ADAPTOR
1.GUID={419DAD30-EA3C-11E8-8002-444553540000}
B=USB  ADAPTOR
B.GUID={419DAD30-EA3C-11E8-8002-444553540000}

2=Saitek Pro Flight Combat Rudder Pedals
2.GUID={A675B770-EA3C-11E8-8001-444553540000}
C=Saitek Pro Flight Combat Rudder Pedals
C.GUID={A675B770-EA3C-11E8-8001-444553540000}

This business is actually  described in the Joy Letters section of the User Guide.

The Log is useful in that it contains this:

      109 ---------------------- Joystick Device Scan -----------------------
      109 Product= Saitek Pro Flight Yoke
      109    Manufacturer= Saitek
      109    Vendor=06A3, Product=0BAC (Version 2.1)
      109    GUIDs returned for product: VID_06A3&PID_0BAC:
      109       GUID= {419D8620-EA3C-11E8-8001-444553540000}
      109       Details: Btns=23, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U255,V255,X1023,Y1023,Z255
      109 Product= USB  ADAPTOR
      125    Vendor=079D, Product=0201 (Version 2.9)
      125    GUIDs returned for product: VID_079D&PID_0201:
      125       GUID= {419DAD30-EA3C-11E8-8002-444553540000}
      125       Details: Btns=8, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U0,V0,X255,Y255,Z255
      125 Product= Saitek Pro Flight Combat Rudder Pedals
      125    Manufacturer= Saitek
      125    Vendor=06A3, Product=0764 (Version 2.0)
      125    GUIDs returned for product: VID_06A3&PID_0764:
      125       GUID= {A675B770-EA3C-11E8-8001-444553540000}
      125       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U0,V0,X127,Y127,Z0
      125 -------------------------------------------------------------------
      125 Device acquired for use:
      125    Joystick ID = 0 (Registry okay)
      125    0=Saitek Pro Flight Yoke
      125    0.GUID={419D8620-EA3C-11E8-8001-444553540000}
      125 Device acquired for use:
      125    Joystick ID = 1 (Registry okay)
      125    1=USB  ADAPTOR
      125    1.GUID={419DAD30-EA3C-11E8-8002-444553540000}
      125 Device acquired for use:
      125    Joystick ID = 2 (Registry okay)
      125    2=Saitek Pro Flight Combat Rudder Pedals
      125    2.GUID={A675B770-EA3C-11E8-8001-444553540000}
      125 -------------------------------------------------------------------

See the "(Registry okay)" comments there? That means the device ID in the Registry concurs with the numbers assigned in the INI. I bet this Log isn't the first one from the new installation, because I think it is unlikely the IDs were originally the same.  All recent versions of FSUIPC actually fix the ID in the registry if they disagree. That's just a safeguard for folks not using Joy Letters.

Pete

 

 

 

[Morten]

Thanks indeed Peter!!
What would we do without you!

All works fine again, except for them throttles which need a bit fine tuning - no problem anymore as they now are identified and recognised!  

A "mammoth" you say....well yes for little me at least, starting out with facing your elephant of a science manual 😰

Best,
Morten