JoyNames Problem

[danewatson]

Due to Windows 10 Version 1709 I had to reset my PC during the installation of Version 1703, then I had to reinstall everything all over again. Everything is working great but I am stumped by by FSUIPC.ini file indicating <<MISSING JOYSTICK>> and also the second and third two lines  that are in my saved FSUIPC.ini file get removed when I load FSX. I have attached my ini and my log files for review.

LINE 2 MISSING - 0=Radio Switch Device

LINE 3 MISSING - 0.GUID={B7441AB0-BD61-11E6-8009-444553540000})

 

[JoyNames]

AutoAssignLetters=No

C=Controller (Gamepad F310) << MISSING JOYSTICK >>

C.GUID={A628CE50-0254-11E7-8001-444553540000}

J=Logitech Extreme 3D << MISSING JOYSTICK >>

J.GUID={F7DD4480-BD9C-11E6-8001-444553540000}

R=T-Rudder << MISSING JOYSTICK >>

R.GUID={D17FC700-30DC-11E7-8001-444553540000}

1=Controller (Gamepad F310)

1.GUID={18ECDE50-CD6F-11E7-8002-444553540000}

2=Logitech Extreme 3D

2.GUID={23DBF0D0-CD6F-11E7-8003-444553540000}

3=T-Rudder

3.GUID={EFC4ACB0-CD6E-11E7-8001-444553540000}

FSUIPC4.ini

FSUIPC4.log

[Pete Dowson]

7 hours ago, danewatson said:

Everything is working great but I am stumped by by FSUIPC.ini file indicating <<MISSING JOYSTICK>> and also the second and third two lines  that are in my saved FSUIPC.ini file get removed when I load FSX.

When you change Windows, you get new GUID's and usually new Joystick IDs assigned. Therefore devices previously identified by a specific GIUD and ID will now not be so recognised.

7 hours ago, danewatson said:

I have attached my ini and my log files for review.

You omitted what is probably the most important file, the FSUIPC.JoyScan.csv file. That shows exactly what happens during each stage of FSUIPC's scanning and how it arrived at its results.

Anyway, the end result is that your three device have these GUIDs and IDs, 1-3.

1=Controller (Gamepad F310)
1.GUID={18ECDE50-CD6F-11E7-8002-444553540000}
2=Logitech Extreme 3D
2.GUID={23DBF0D0-CD6F-11E7-8003-444553540000}
3=T-Rudder
3.GUID={EFC4ACB0-CD6E-11E7-8001-444553540000}

whilst your previous assignments were:

C=Controller (Gamepad F310) << MISSING JOYSTICK >>
C.GUID={A628CE50-0254-11E7-8001-444553540000}
J=Logitech Extreme 3D << MISSING JOYSTICK >>
J.GUID={F7DD4480-BD9C-11E6-8001-444553540000}
R=T-Rudder << MISSING JOYSTICK >>
R.GUID={D17FC700-30DC-11E7-8001-444553540000}

You see that all three GUIDs have changed. This is Windows doing, as it re-generates them for the fresh install.

So you need to delete those letter assignments, then make a copy of the new set and put the letters in again so you get

C=Controller (Gamepad F310)
C.GUID={18ECDE50-CD6F-11E7-8002-444553540000}
J=Logitech Extreme 3D
J.GUID={23DBF0D0-CD6F-11E7-8003-444553540000}
R=T-Rudder
R.GUID={EFC4ACB0-CD6E-11E7-8001-444553540000}

That's all.

Pete

 

[danewatson]

7 hours ago, Pete Dowson said:

When you change Windows, you get new GUID's and usually new Joystick IDs assigned. Therefore devices previously identified by a specific GIUD and ID will now not be so recognised.

You omitted what is probably the most important file, the FSUIPC.JoyScan.csv file. That shows exactly what happens during each stage of FSUIPC's scanning and how it arrived at its results.

Anyway, the end result is that your three device have these GUIDs and IDs, 1-3.

1=Controller (Gamepad F310)
1.GUID={18ECDE50-CD6F-11E7-8002-444553540000}
2=Logitech Extreme 3D
2.GUID={23DBF0D0-CD6F-11E7-8003-444553540000}
3=T-Rudder
3.GUID={EFC4ACB0-CD6E-11E7-8001-444553540000}

whilst your previous assignments were:

C=Controller (Gamepad F310) << MISSING JOYSTICK >>
C.GUID={A628CE50-0254-11E7-8001-444553540000}
J=Logitech Extreme 3D << MISSING JOYSTICK >>
J.GUID={F7DD4480-BD9C-11E6-8001-444553540000}
R=T-Rudder << MISSING JOYSTICK >>
R.GUID={D17FC700-30DC-11E7-8001-444553540000}

You see that all three GUIDs have changed. This is Windows doing, as it re-generates them for the fresh install.

So you need to delete those letter assignments, then make a copy of the new set and put the letters in again so you get

C=Controller (Gamepad F310)
C.GUID={18ECDE50-CD6F-11E7-8002-444553540000}
J=Logitech Extreme 3D
J.GUID={23DBF0D0-CD6F-11E7-8003-444553540000}
R=T-Rudder
R.GUID={EFC4ACB0-CD6E-11E7-8001-444553540000}

That's all.

Pete

 

Pete - what can I say but simply THANK YOU YET AGAIN.

I now completely understand the problem - due to my new Windows install and because I thought I was doing the right thing by pasting in my previous FSUIPC4.ini file, the settings did not jive. I made the changes and all is excellent.

Thank you.

PS - I have purchased your FSUIPC5 as I am going to be purchasing P3D v4 next week. Can I copy in my FSUIPC4.ini file and simply change the name to FSUIPC5.ini? Is there anything other file(s) that can or should be copied over?

[Pete Dowson]

3 hours ago, danewatson said:

I have purchased your FSUIPC5 as I am going to be purchasing P3D v4 next week. Can I copy in my FSUIPC4.ini file and simply change the name to FSUIPC5.ini?

Yes, that works fine.

3 hours ago, danewatson said:

Is there anything other file(s) that can or should be copied over?

Only any Macro (.mcro) or Lua (.lua) files you might have in the Modules folder.

One odd thing I note in your INI file. You have "UseProfiles=No" in the [General] section, yet you have

[Profile.Helicopter]
1=WILCO_FSTR
2=BA609 PROTO SIM AIR
3=BA609 EXEC SIM AIR

You do have assignments in these sections:

[Axes.Helicopter]
[Axes.WILCO_FSTR]
[Axes.BA609 PROTO SIM AIR]
[Axes.BA609 EXEC SIM AIR]

If the names in last three match any part of any of our installed aircraft names, then those sections will operate on the old "aircraft specific" system (which was really superseded long ago by Profiles, but still left operational for ongoing compatibility). 

However, the Helicopter section may not match any part of the three aircraft you have listed in its Helicopter Profile.

But back to your question, if you were using Profiles, and had opted for "UseProfiles=Files", you'd need to copy over the Profiles subfolder too.

Pete

 

[danewatson]

5 minutes ago, Pete Dowson said:

Yes, that works fine.

Only any Macro (.mcro) or Lua (.lua) files you might have in the Modules folder.

One odd thing I note in your INI file. You have "UseProfiles=No" in the [General] section, yet you have

[Profile.Helicopter]
1=WILCO_FSTR
2=BA609 PROTO SIM AIR
3=BA609 EXEC SIM AIR

You do have assignments in these sections:

[Axes.Helicopter]
[Axes.WILCO_FSTR]
[Axes.BA609 PROTO SIM AIR]
[Axes.BA609 EXEC SIM AIR]

If the names in last three match any part of any of our installed aircraft names, then those sections will operate on the old "aircraft specific" system (which was really superseded long ago by Profiles, but still left operational for ongoing compatibility). =

However, the Helicopter section may not match any part of the three aircraft you have listed in its Helicopter Profile.

But back to your question, if you were using Profiles, and had opted for "UseProfiles=Files", you'd need to copy over the Profiles subfolder too.

Pete

 

Thanks again Pete.

Re. The Helicopter Profiles, the only one re-installed is 1=WILCO-FSTR, the other two are not yet installed. I will review.

Dane

[Pete Dowson]

10 hours ago, danewatson said:

The Helicopter Profiles, the only one re-installed is 1=WILCO-FSTR

But the Helicopter Profile won't apply to it (unless is has "helicopter" in its name) because you aren't using Profiles ("UseProfiles=No" -- default is "UseProfiles=Yes").

Pete

 

[danewatson]

Thanks Pete, I did fix that.

Deleted all the Helicopter related aircraft and profile and started over from within FSX & FSUIPC. All is now good, now UseProfiles=Yes in the INI file.