JoyNames Conflict/Issues

[Sea2Sky]

I'm troubleshooting an issue I've been having with some conflicts/issues between FSUIPC v5 and P3D v4.

Initially, I had it configured appropriately so that all my flight sim hardware was working between FSUIPC5, and P3D. During my Flight Sim build, there were some newly added hardware, and USB re-connections to a  newly installed 7 port powered USB hub attached next to my flight dash. I'm also a registered user of FSUIPC v5.

The old working version looked like this:

[JoyNames]
AutoAssignLetters=No
1=TRC 32DIGITAL IN 15
1.GUID={62C61340-2D60-11EA-8001-444553540000}
2=JAY Rudder
2.GUID={A7B66F40-1B31-11EA-8001-444553540000}
3=GarSim 530
3.GUID={836103C0-2276-11EA-8001-444553540000}
0=Pro Flight Cessna Yoke
0.GUID={51842490-A618-11E7-8003-444553540000}

My current FSUIPC5.ini configuration under [JoyNames] look like this (auto detected, updated changes):

[JoyNames]
AutoAssignLetters=No
1=vJoy Device
1.GUID={DA0C7E80-36D4-11EA-8004-444553540000}
3=GarSim 530
3.GUID={713A11F0-36D0-11EA-8001-444553540000}
A=<< MISSING JOYSTICK >> << MISSING JOYSTICK >>
2=JAY Rudder
2.GUID={A7B66F40-1B31-11EA-8001-444553540000}

Note: There is a missing joystick listed under 'A', and no device 0 listed in the new JoyNames config.

I've since updated my Saitek Cessna Yoke to a Brunner NG yoke, so that has changed. I've also removed the TRC 32DIGITAL IN 15 switch panel with the Flight Illusion GSA-055 central interface, which should be the vJoy Device. However, I'm not seeing CLSE NG Yoke listed under JoyNames (but is listed in Windows USB Game Controllers). The yoke is working in P3D, so my assumption is that the Brunner software is handling the yoke axis hardware completely.

 

I've manually wiped the [Buttons] configuration in FSUIPC5.ini, then configured 5 buttons on the Brunner yoke in FSUIPC under P3D addons to confirm the device ID's being used by the yoke:

[Buttons]
PollInterval=25
ButtonRepeat=20,10
1=P1,5,C65561,0     -{PAUSE_TOGGLE}-
2=P1,6,C65606,0     -{VIEW}-
3=P1,7,C65567,0     -{VIEW_MODE}-
4=P3,4,C66653,0     -{VIEW_COCKPIT_FORWARD}-
5=P3,3,C67036,0     -{CINEMATOGRAPHER_TOGGLE}-

The yoke is using two separate devices, P1, and P3, but no input from the GNS 530 GPS as the buttons are not recognized under FSUIPC5 buttons and switches tab, but P3 is picked up by the Yoke device.

The old FSUIPC buttons configuration had the following extra buttons mapped when it did work with the GNS 530 hardware:

7=P3,12,K81,40     -{Key press: alt+Q}-
8=P3,0,K83,40     -{Key press: alt+S}-
9=P3,1,K83,40     -{Key press: alt+S}-
10=P3,13,K87,40     -{Key press: alt+W}-
11=P3,2,K89,40     -{Key press: alt+Y}-
12=P3,3,K90,40     -{Key press: alt+Z}-
13=P3,7,K75,40     -{Key press: alt+K}-
14=P3,6,K74,40     -{Key press: alt+J}-
15=P3,5,K118,40     -{Key press: alt+F7}-
16=P3,4,K117,40     -{Key press: alt+F6}-
17=P3,14,K78,40     -{Key press: alt+N}-
18=P3,16,K120,40     -{Key press: alt+F9}-
19=P3,17,K86,40     -{Key press: alt+V}-
20=P3,18,K124,40     -{Key press: alt+F13}-
21=P3,19,K65,40     -{Key press: alt+A}-
22=P3,20,K67,40     -{Key press: alt+C}-
23=P3,21,K113,40     -{Key press: alt+F2}-
24=P3,10,K119,40     -{Key press: alt+F8}-
25=P3,11,K79,40     -{Key press: alt+O}-
26=P3,8,K123,40     -{Key press: alt+F12}-
27=P3,9,K121,40     -{Key press: alt+F10}-
28=P3,15,K122,40     -{Key press: alt+F11}-
29=R3,27,K72,40     -{Key press: alt+H}-
30=R3,26,K73,40     -{Key press: alt+I}-
31=P3,25,K114,40     -{Key press: alt+F3}-
32=P3,24,K115,40     -{Key press: alt+F4}-
33=R3,23,K116,40     -{Key press: alt+F5}-
34=P3,22,K50,25     -{Key press: alt+shft+2}-
35=P3,29,K126,40     -{Key press: alt+F15}-

Onto my current issue;  the Emuteq Garmin 530 GPS hardware now has no buttons mapped or being recognized by FSUIPC buttons and switches input. My Yoke uses a combination of both device 1, and 3 under FSUIPC buttons and switches tab; but the FSUIPC should be using the Garmin 530 as device ID 3. When I activate any knob or button on the Emuteq GNS 530 GPS device, no button commands are being sent to the FSUIPC button and switches tab. The GNS 530 config is mapped to use the appropriate shortcut keys, but not being received anymore by FSUIPC.

I'm not sure if this is related to the issue, but the P3D's calibration menu device ID do not match the  FSUIPC device ID.

0 Mouse Yoke
1 Mouse Look
0 vJoy - Virtual Joystick
1 GarSim 530
2 Jay Rudder
3 CLSE NG Yoke

I'm also attaching the FSUIPC5.JoyScan.csv output for reference as it appears that the yoke and GPS are using conflicting device IDs:

Good?, flags, VID, PID, Name, INIid, REGid, RegEntry, INIguid, REGguid, HIDguid, ValsOK?, ReadsOk?

,,, HIDscanning completed

N, x00, x241D, xFE4E, , -1, -1, 0, {NULL}, {NULL}, {A7B66F40-1B31-11EA-8001-444553540000}, Y, N
N, x00, x1234, xBEAD, , -1, -1, 0, {NULL}, {NULL}, {DA0C7E80-36D4-11EA-8004-444553540000}, Y, N
N, x00, x25BB, x008B, , -1, -1, 0, {NULL}, {NULL}, {713A6010-36D0-11EA-8002-444553540000}, N, N
N, x00, x25BB, x008B, , -1, -1, 0, {NULL}, {NULL}, {713A11F0-36D0-11EA-8001-444553540000}, Y, N
N, x00, x1DD2, x1020, , -1, -1, 0, {NULL}, {NULL}, {A7B66F40-1B31-11EA-8001-444553540000}, Y, N

,,, REGscanning completed

N, x00, x241D, xFE4E, JAY Rudder, -1, 2, 0, {NULL}, {A7B66F40-1B31-11EA-8001-444553540000}, {A7B66F40-1B31-11EA-8001-444553540000}, Y, Y
N, x00, x1234, xBEAD, vJoy Device, -1, 1, 0, {NULL}, {DA0C7E80-36D4-11EA-8004-444553540000}, {DA0C7E80-36D4-11EA-8004-444553540000}, Y, Y
N, x00, x25BB, x008B, CLSE NG Yoke, -1, 0, 1, {NULL}, {713A6010-36D0-11EA-8002-444553540000}, {713A6010-36D0-11EA-8002-444553540000}, N, N
N, x00, x25BB, x008B, CLSE NG Yoke, -1, 3, 0, {NULL}, {713A11F0-36D0-11EA-8001-444553540000}, {713A11F0-36D0-11EA-8001-444553540000}, Y, Y
N, x00, x25BB, x008B, CLSE NG Yoke, -1, 0, 0, {NULL}, {836103C0-2276-11EA-8001-444553540000}, {NULL}, N, N
N, x00, x25BB, x008B, CLSE NG Yoke, -1, -1, 2, {NULL}, {DB75AB70-36D4-11EA-8010-444553540000}, {NULL}, N, N
N, x00, x25BB, x008B, CLSE NG Yoke, -1, -1, 3, {NULL}, {DB73AFA0-36D4-11EA-800C-444553540000}, {NULL}, N, N
N, x00, x1DD2, x1020, GarSim 530, -1, 3, 0, {NULL}, {713A11F0-36D0-11EA-8001-444553540000}, {713A11F0-36D0-11EA-8001-444553540000}, Y, Y
N, x00, x1DD2, x1020, GarSim 530, -1, 0, 0, {NULL}, {836103C0-2276-11EA-8001-444553540000}, {NULL}, N, N

,,, User settings imported

N, x00, x241D, xFE4E, JAY Rudder, 2, 2, 0, {A7B66F40-1B31-11EA-8001-444553540000}, {A7B66F40-1B31-11EA-8001-444553540000}, {A7B66F40-1B31-11EA-8001-444553540000}, Y, Y
N, x00, x1234, xBEAD, vJoy Device, 1, 1, 0, {DA0C7E80-36D4-11EA-8004-444553540000}, {DA0C7E80-36D4-11EA-8004-444553540000}, {DA0C7E80-36D4-11EA-8004-444553540000}, Y, Y
N, x00, x25BB, x008B, CLSE NG Yoke, -1, 0, 1, {NULL}, {713A6010-36D0-11EA-8002-444553540000}, {713A6010-36D0-11EA-8002-444553540000}, N, N
N, x00, x25BB, x008B, CLSE NG Yoke, 3, 3, 0, {713A11F0-36D0-11EA-8001-444553540000}, {713A11F0-36D0-11EA-8001-444553540000}, {713A11F0-36D0-11EA-8001-444553540000}, Y, Y
N, x00, x25BB, x008B, CLSE NG Yoke, -1, 0, 0, {NULL}, {836103C0-2276-11EA-8001-444553540000}, {NULL}, N, N
N, x00, x25BB, x008B, CLSE NG Yoke, -1, -1, 2, {NULL}, {DB75AB70-36D4-11EA-8010-444553540000}, {NULL}, N, N
N, x00, x25BB, x008B, CLSE NG Yoke, -1, -1, 3, {NULL}, {DB73AFA0-36D4-11EA-800C-444553540000}, {NULL}, N, N
N, x00, x1DD2, x1020, GarSim 530, 3, 3, 0, {713A11F0-36D0-11EA-8001-444553540000}, {713A11F0-36D0-11EA-8001-444553540000}, {713A11F0-36D0-11EA-8001-444553540000}, Y, Y
N, x00, x1DD2, x1020, GarSim 530, -1, 0, 0, {NULL}, {836103C0-2276-11EA-8001-444553540000}, {NULL}, N, N

,,, Values matched and decided

Y, x1E, x241D, xFE4E, JAY Rudder, 2, 2, 0, {A7B66F40-1B31-11EA-8001-444553540000}, {A7B66F40-1B31-11EA-8001-444553540000}, {A7B66F40-1B31-11EA-8001-444553540000}, Y, Y
Y, x1E, x1234, xBEAD, vJoy Device, 1, 1, 0, {DA0C7E80-36D4-11EA-8004-444553540000}, {DA0C7E80-36D4-11EA-8004-444553540000}, {DA0C7E80-36D4-11EA-8004-444553540000}, Y, Y
N, x12, x25BB, x008B, CLSE NG Yoke, -1, 0, 1, {NULL}, {713A6010-36D0-11EA-8002-444553540000}, {713A6010-36D0-11EA-8002-444553540000}, N, N
Y, x1E, x25BB, x008B, CLSE NG Yoke, 3, 3, 0, {713A11F0-36D0-11EA-8001-444553540000}, {713A11F0-36D0-11EA-8001-444553540000}, {713A11F0-36D0-11EA-8001-444553540000}, Y, Y
N, x11, x25BB, x008B, CLSE NG Yoke, -1, 0, 0, {NULL}, {836103C0-2276-11EA-8001-444553540000}, {NULL}, N, N
N, x01, x25BB, x008B, CLSE NG Yoke, -1, -1, 2, {NULL}, {DB75AB70-36D4-11EA-8010-444553540000}, {NULL}, N, N
N, x01, x25BB, x008B, CLSE NG Yoke, -1, -1, 3, {NULL}, {DB73AFA0-36D4-11EA-800C-444553540000}, {NULL}, N, N
Y, x1E, x1DD2, x1020, GarSim 530, 3, 3, 0, {713A11F0-36D0-11EA-8001-444553540000}, {713A11F0-36D0-11EA-8001-444553540000}, {713A11F0-36D0-11EA-8001-444553540000}, Y, Y
N, x11, x1DD2, x1020, GarSim 530, -1, 0, 0, {NULL}, {836103C0-2276-11EA-8001-444553540000}, {NULL}, N, N

I see a conflict between the two device:

Y, x1E, x25BB, x008B, CLSE NG Yoke, 3, 3, 0, {713A11F0-36D0-11EA-8001-444553540000}, {713A11F0-36D0-11EA-8001-444553540000}, {713A11F0-36D0-11EA-8001-444553540000}, Y, Y
Y, x1E, x1DD2, x1020, GarSim 530, 3, 3, 0, {713A11F0-36D0-11EA-8001-444553540000}, {713A11F0-36D0-11EA-8001-444553540000}, {713A11F0-36D0-11EA-8001-444553540000}, Y, Y

 

Adding logging details as well for registry conflict reference:

       94 ---------------------- Joystick Device Scan -----------------------
       94 Product= JAY Rudder
       94    Vendor=241D, Product=FE4E (Version 0.1)
      110    GUIDs returned for product: VID_241D&PID_FE4E:
      110       GUID= {A7B66F40-1B31-11EA-8001-444553540000}
      110       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X1023,Y1023,Z1023
      110 Product= vJoy - Virtual Joystick
      110    Manufacturer= Shaul Eizikovich
      110    Serial Number= 2.1.9
      110    Vendor=1234, Product=BEAD (Version 2.25)
      110    GUIDs returned for product: VID_1234&PID_BEAD:
      110       GUID= {DA0C7E80-36D4-11EA-8004-444553540000}
      110       Details: Btns=128, POVs=(0, 18000, 27000, 9000), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767
      110 Product= CLSE NG Yoke
      110    Manufacturer= Brunner Elektronik AG
      110    Serial Number= XXX
      110    Vendor=25BB, Product=008B (Version 1.0)
      110    GUIDs returned for product: VID_25BB&PID_008B:
      110       GUID= {713A6010-36D0-11EA-8002-444553540000}
      110       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0
      110       GUID= {713A11F0-36D0-11EA-8001-444553540000}
      110       Details: Btns=6, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X65535,Y65535,Z0
      110 Product= GarSim 530
      110    Manufacturer= www.emuteq.com
      110    Serial Number= xxx
      110    Vendor=1DD2, Product=1020 (Version 1.3)
      125 -------------------------------------------------------------------
      156    WARNING: Joystick ID 0 is duplicated in Registry
      172 Device acquired for use:
      172    Joystick ID = 2 (Registry okay)
      172    2=JAY Rudder
      172    2.GUID={A7B66F40-1B31-11EA-8001-444553540000}
      172 Device acquired for use:
      172    Joystick ID = 1 (Registry okay)
      172    1=vJoy Device
      172    1.GUID={DA0C7E80-36D4-11EA-8004-444553540000}
      172 Device acquired for use:
      172    Joystick ID = 3 (Registry okay)
      172    3=CLSE NG Yoke
      172    3.GUID={713A11F0-36D0-11EA-8001-444553540000}
      172 Device acquired for use:
      172    Joystick ID = 3 (Registry okay)
      172    3=GarSim 530
      172    3.GUID={713A11F0-36D0-11EA-8001-444553540000}

 

How can I reset/flush the devices in FSUIPC/P3D and reregister them? Will I need to manually update particular registries, configs, etc; or can I perform a full registry clean?

Edited March 4, 2020 by Sea2Sky
adding device 0 missing.

[Thomas Richter]

Hi,

first of all please attach a full not altered or incomplete log file as major information are missing. Pleas close P3D before copying the content.

Thomas

[John Dowson]

Yes, your registry entries look a right mess with conflicting/duplicated GUIDs for different devices. It would have been a lot easier to resolve these issues if you had used the 'JoyLetters' facility (please read about this in the User manual), but its to late for this now, although you should activate this once your problems have been solved.

You say:

14 hours ago, Sea2Sky said:

I've also removed the TRC 32DIGITAL IN 15 switch panel with the Flight Illusion GSA-055 central interface, which should be the vJoy Device.

Do you mean that you have added the Flight Illusion GSA-055, as this is now recognised?

I think the best way forward with this is if you could do the following:

1. First, disconnect your new devices (Flight Illusion GSA-055  and Brunner Yoke) and uninstall any software/device drivers for these. Then reboot.
2. Start P3D. load an aircraft and then stop the sim.
3. Attach the newly generated log, ini and JoyScan.csv files - better to attach the complete files rather than copy/paste.

Once that is done, we can use the files to work out what needs to be removed from your registry and ini files.

After that, you can reconnect your devices and install any software needed and then we can take a look at the files again.

John

[Sea2Sky]

Thanks John for clarifying.

I have all my hardware that I need installed and finalized, so I will remove all the software installations for my hardware, and install one by one and examine the generated logs to see if that resolves the issues.

[Sea2Sky]

 I've tried to uninstall/reinstall my hardware control devices but kept running into joystick conflict issues. I replaced a lot of my Saitek controls with more professional simulation hardware, and after going over the controllers in the registry, and old driver removal, I eventually gave up.

I did a fresh reinstall of Windows 10, P3D, hardware controls/drivers, scenery packages, and FSUIPC. I've cleared out all controls within P3D, and am exclusively using FSUIPC. I just finished setting up my hardware in FSUIPC, and everything is looking good (except the individual light switches, as mentioned in a separate post).

One issue that I've noticed which seems to be random is in regards to my Brunner CLSE NG yoke. It has it's own software and support, but does require vJoy to also be installed. Sometimes FSUIPC recognizes half my buttons on the yoke to be from the vJoy device ID, and other times, it's recognized as the CLSE NG Yoke device ID. Is there any known conflicts with vJoy and CLSE NG devices, and how can I keep the buttons consistent to the appropriate ID. The best case working scenario for me is when all the yoke buttons are identified in FSUIPC as the CLSE NG device ID.

I've attached a copy of my FSUIPC.JoyScan.csv file for reference:

Good?, flags, VID, PID, Name, INIid, REGid, RegEntry, INIguid, REGguid, HIDguid, ValsOK?, ReadsOk?

,,, HIDscanning completed

N, x00, x241D, xFE4E, , -1, -1, 0, {NULL}, {NULL}, {52571BC0-6B69-11EA-8005-444553540000}, Y, N
N, x00, x1234, xBEAD, , -1, -1, 0, {NULL}, {NULL}, {0FB96D90-6B69-11EA-8002-444553540000}, Y, N
N, x00, x1DD2, x1020, , -1, -1, 0, {NULL}, {NULL}, {DEC169D0-6B73-11EA-8002-444553540000}, Y, N
N, x00, x25BB, x008B, , -1, -1, 0, {NULL}, {NULL}, {52560A50-6B69-11EA-8003-444553540000}, Y, N

,,, REGscanning completed

N, x00, x241D, xFE4E, JAY Rudder, -1, 2, 0, {NULL}, {52571BC0-6B69-11EA-8005-444553540000}, {52571BC0-6B69-11EA-8005-444553540000}, Y, Y
N, x00, x1234, xBEAD, vJoy Device, -1, 0, 0, {NULL}, {0FB96D90-6B69-11EA-8002-444553540000}, {0FB96D90-6B69-11EA-8002-444553540000}, Y, Y
N, x00, x1DD2, x1020, GarSim 530, -1, 3, 0, {NULL}, {DEC169D0-6B73-11EA-8002-444553540000}, {DEC169D0-6B73-11EA-8002-444553540000}, Y, N
N, x00, x25BB, x008B, CLSE NG Yoke, -1, 1, 0, {NULL}, {52560A50-6B69-11EA-8003-444553540000}, {52560A50-6B69-11EA-8003-444553540000}, Y, Y
N, x00, x25BB, x008B, CLSE NG Yoke, -1, -1, 1, {NULL}, {52565870-6B69-11EA-8004-444553540000}, {NULL}, N, N

,,, User settings imported

N, x00, x241D, xFE4E, JAY Rudder, 2, 2, 0, {52571BC0-6B69-11EA-8005-444553540000}, {52571BC0-6B69-11EA-8005-444553540000}, {52571BC0-6B69-11EA-8005-444553540000}, Y, Y
N, x00, x1234, xBEAD, vJoy Device, 0, 0, 0, {0FB96D90-6B69-11EA-8002-444553540000}, {0FB96D90-6B69-11EA-8002-444553540000}, {0FB96D90-6B69-11EA-8002-444553540000}, Y, Y
N, x00, x1DD2, x1020, GarSim 530, 3, 3, 0, {DEC169D0-6B73-11EA-8002-444553540000}, {DEC169D0-6B73-11EA-8002-444553540000}, {DEC169D0-6B73-11EA-8002-444553540000}, Y, N
N, x00, x25BB, x008B, CLSE NG Yoke, 1, 1, 0, {52560A50-6B69-11EA-8003-444553540000}, {52560A50-6B69-11EA-8003-444553540000}, {52560A50-6B69-11EA-8003-444553540000}, Y, Y
N, x00, x25BB, x008B, CLSE NG Yoke, -1, -1, 1, {NULL}, {52565870-6B69-11EA-8004-444553540000}, {NULL}, N, N

,,, Values matched and decided

Y, x1E, x241D, xFE4E, JAY Rudder, 2, 2, 0, {52571BC0-6B69-11EA-8005-444553540000}, {52571BC0-6B69-11EA-8005-444553540000}, {52571BC0-6B69-11EA-8005-444553540000}, Y, Y
Y, x1E, x1234, xBEAD, vJoy Device, 0, 0, 0, {0FB96D90-6B69-11EA-8002-444553540000}, {0FB96D90-6B69-11EA-8002-444553540000}, {0FB96D90-6B69-11EA-8002-444553540000}, Y, Y
(Y), x16, x1DD2, x1020, GarSim 530, 3, 3, 0, {DEC169D0-6B73-11EA-8002-444553540000}, {DEC169D0-6B73-11EA-8002-444553540000}, {DEC169D0-6B73-11EA-8002-444553540000}, Y, N
Y, x1E, x25BB, x008B, CLSE NG Yoke, 1, 1, 0, {52560A50-6B69-11EA-8003-444553540000}, {52560A50-6B69-11EA-8003-444553540000}, {52560A50-6B69-11EA-8003-444553540000}, Y, Y
N, x11, x25BB, x008B, CLSE NG Yoke, -1, -1, 1, {NULL}, {52565870-6B69-11EA-8004-444553540000}, {NULL}, N, N

 

Here are the JoyNames, Axes and Buttons to reference how vJoy has configured some of the yoke buttons in the past. As you can see under buttons, 1-3 used the vJoy device in FSUIPC, but when FSUIPC loaded the CLSE NG buttons correctly, it would use 6-8, which are the same buttons as vJoy 1-3 (2, 3 were set differently for testing). I've also added JoystickCalibration just to reference the Axes brake configuration, which is working fine.

 

[JoyNames]
AutoAssignLetters=No
0=vJoy Device
0.GUID={0FB96D90-6B69-11EA-8002-444553540000}
1=CLSE NG Yoke
1.GUID={52560A50-6B69-11EA-8003-444553540000}
2=JAY Rudder
2.GUID={52571BC0-6B69-11EA-8005-444553540000}
3=GarSim 530
3.GUID={DEC169D0-6B73-11EA-8002-444553540000}


[JoystickCalibration]
RudderBlendLowest=1
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=Yes
ExcludeMixtureSet=Yes
ExcludePropPitchSet=Yes
SepRevsJetsOnly=No
ApplyHeloTrim=No
UseAxisControlsForNRZ=No
FlapsSetControl=0
FlapDetents=No
ReverserControl=66292
Reverser1Control=66422
Reverser2Control=66425
Reverser3Control=66428
Reverser4Control=66431
MaxThrottleForReverser=256
AileronTrimControl=66731
RudderTrimControl=66732
CowlFlaps1Control=66162
CowlFlaps2Control=66163
CowlFlaps3Control=66164
CowlFlaps4Control=66165
SteeringTillerControl=0
MaxSteerSpeed=60
LeftBrake=14500,16380
RightBrake=14348,16380/16

[Axes]
PollInterval=10
RangeRepeatRate=10
0=1P,0,F,66416,0,0,0	-{ TO SIM: PAN_VIEW }-
1=2X,256,D,7,0,0,0	-{ DIRECT: LeftBrake }-
2=2Y,256,D,8,0,0,0	-{ DIRECT: RightBrake }-

[Buttons]
PollInterval=25
ButtonRepeat=20,10
1=P0,5,C65561,0 	-{PAUSE_TOGGLE}-
2=P0,6,C67036,0 	-{CINEMATOGRAPHER_TOGGLE}-
3=P0,7,C65567,0 	-{VIEW_MODE}-
4=P1,4,C65906,0 	-{PANEL_1}-
5=P1,3,C66482,0 	-{TOGGLE_WATER_RUDDER}-
6=P1,0,C65561,0 	-{PAUSE_TOGGLE}-
7=P1,1,C66653,0 	-{VIEW_COCKPIT_FORWARD}-
8=P1,2,C66654,0 	-{VIEW_VIRTUAL_COCKPIT_FORWARD}-

 

I'm wondering what determines the button mapping to P0, or P1? Would this be fixable to remain consistent with P1 only instead of FSUIPC switching between P0 and P1 randomly? Or is this something more related to the yoke manufacturer as they are using two joystick devices to operate the same buttons?

 

[Pete Dowson]

5 hours ago, Sea2Sky said:

I'm wondering what determines the button mapping to P0, or P1?

Only the [JoyNames] assignment, i.e.

5 hours ago, Sea2Sky said:

0=vJoy Device
0.GUID={0FB96D90-6B69-11EA-8002-444553540000}
1=CLSE NG Yoke
1.GUID={52560A50-6B69-11EA-8003-444553540000}

This next part I don't really understand:

5 hours ago, Sea2Sky said:

Would this be fixable to remain  consistent with P1 only instead of FSUIPC switching between P0 and P1 randomly?

FSUIPC cannot "randomly switch" -- unless Windows is generating different IDs andGUID's each time.  Are you unplugging or disabling the devices randomly? Windows is a bit pernickity with that sort of thing.

Additionally If you want all your assignments on 1 assign to 1 not 0, and vice versa. The actual assignments do not change except by your action in the assignments tabs. Only the device identifications (JoyNames) may change.

If things are likely to change you should be using Joy Letters in any casde. Please see the chapter in the User Guide about that.

Pete

 

 

[Sea2Sky]

I guess my struggle is this: vJoy device 0 *is* device CLSE NG 1, and vice versa. The yoke can use both devices for button mapping in FSUIPC.

When the yoke buttons work correctly, FSUIPC identifies the yoke buttons as device 1. When it does, all buttons are mapped to device 1, and the hat switch works accordingly. The buttons will use P1:0, P1:1, P1:2. When FSUIPC includes vJoy device 0 as part of the yoke button configuration, then I get a mishmash of yoke buttons using both joystick devices, and certain hat switch directions become device 0.

Example: when FSUIPC loads the yoke buttons properly, only CLSE NG device 1 is used for all yoke button mappings, including the hat switch. But sometimes on load, FSUIPC uses both device IDs for button mapping, and then P0:5, P0:6, P0:7 overrides P1:0, P1:1, P1:2.

I'm trying my best to identify the situation I'm seeing in FSUIPC, it would have been better to create a video to explain what I'm speaking about if the above doesn't make sense, which I would be willing to do if necessary.

Next time this issue persists, I will try changing to Joy Letters to see if that resolves the issues.

Thank you for your patience Pete, as this is a bit of an odd issue, and I don't think is normal. All USB inputs are set in a USB extender, and are never removed.

[Pete Dowson]

9 minutes ago, Sea2Sky said:

I guess my struggle is this: vJoy device 0 *is* device CLSE NG 1, and vice versa. The yoke can use both devices for button mapping in FSUIPC.

That's really not relevant here. If they connect as two devices they are treated as two devices.

If you have all the connections you need with only one of them, then only assign to that one. Why have you assignments to both?

11 minutes ago, Sea2Sky said:

When FSUIPC includes vJoy device 0 as part of the yoke button configuration, then I get a mishmash of yoke buttons using both joystick devices, and certain hat switch directions become device 0.

That can only possibly occur if you have assigned to device 0. FSUIPC cannot change the numbers in your assignments!

Are you sure you have controllers actually disabled in P3D? My guess is that you are getting confused by P3D doing auto-assignments when it sees the devices.

Pete

 

[Sea2Sky]

9 minutes ago, Pete Dowson said:

Are you sure you have controllers actually disabled in P3D? My guess is that you are getting confused by P3D doing auto-assignments when it sees the devices

I think you are correct and hit the nail on the head. In the end, I did remove all device button mapping for each device within P3D. But yesterday, I may have missed vJoy device in P3D. As of last night, all assignments were cleared up in P3D, and FSUIPC did use the correct device ID 1. Since everything is working now, I will walk away from this with hopes of it not reoccurring.

Thank you for your help throughout my  post ramblings. :-)

[Pete Dowson]

1 minute ago, Sea2Sky said:

But yesterday, I may have missed vJoy device in P3D. As of last night, all assignments were cleared up in P3D, and FSUIPC did use the correct device ID 1.

There is an option is P3D to disable devices altogether. Best to use that. Otherwise, if ever one of the connections isn't present on starting P3D but is there on a later start, or if a Windows updates changes things, P3D may think it is a new connection and mnake auto-assignments again.

I think the option to disable all controllers is right at the end of the controller assignments options in P3D.

Pete

 

[John Dowson]

I will reoccur unless you disable controllers completely within P3D, as it has a habit or re-assigning. Also, its a good idea to update to use JoyLetters to prevent problems if your Joy Ids get re-assigned (just change  AutoAssignLetters=No to AutoAssignLetters=Yes in the [JoyNames] section of your ini).

...saw Pete just replied:

1 minute ago, Pete Dowson said:

I think the option to disable all controllers is right at the end of the controller assignments options in P3D.

Its at the bottom of the 'Controls - Other' page

John