In P3Dv4 with the PMDG 737 I have the problem that all the buttons and encoders do not work for the MCPv3 and EFISv2.
However, they are displayed and working in the SIOC console.
7 Segment, LED and toggle switches (FD, AT ARM) work fine with the PMDG.
I have the latest FSUIPC version for P3D v4.3 installed.
The trick to get the MCP running by removing some USB devices does not work in this case.
Encoder and button problem in P3Dv4.3[SOLVED]
Re: Encoder and button problem in P3Dv4.3
which version of OC4BAv4 are you running?
Re: Encoder and button problem in P3Dv4.3
I currently have the 4.4.0.0
I have already sent an update request, as described here in the forum.
I have already sent an update request, as described here in the forum.
Re: Encoder and button problem in P3Dv4.3
Even after the update no change. Led's, 7 segment and toggle switch work. Encoder and button not. Changes in the PMDG are displayed in the OC MCP.
I changed the USB port, changed from USB 2.0 to USB 3.0.
Unfortunately, no success.
I changed the USB port, changed from USB 2.0 to USB 3.0.
Unfortunately, no success.
Re: Encoder and button problem in P3Dv4.3
Either your MCP is faulty or you do not have, the latest PMDG 737NGX version.
Re: Encoder and button problem in P3Dv4.3
Thank you for your answer.
In the IO Console I see that all keys and encoders in SIOC are recognized. The green fields appear when the associated buttons are pressed.
The MCP can not be so. And the PMDG is up to date, v1.20.8465. FSUIPC5.DLL is version 5.132.
I am not alone with the problem. In some German forums there are MCP issues related to P3D v4.2 and v4.1.
In the IO Console I see that all keys and encoders in SIOC are recognized. The green fields appear when the associated buttons are pressed.
The MCP can not be so. And the PMDG is up to date, v1.20.8465. FSUIPC5.DLL is version 5.132.
I am not alone with the problem. In some German forums there are MCP issues related to P3D v4.2 and v4.1.
Re: Encoder and button problem in P3Dv4.3
If you are using the latest SIOC v6, try to revert back to SIOC v5.1 to see if that makes any changes.
Try also to disable FSUIPC ( it is not used by OC4BAv4).
All P3Dv4.1,4.2 and v4.3 works have all been working OK with OC4BAv4.
Try also to disable FSUIPC ( it is not used by OC4BAv4).
All P3Dv4.1,4.2 and v4.3 works have all been working OK with OC4BAv4.
Re: Encoder and button problem in P3Dv4.3
Unfortunately, nothing has changed.
SIOC version is 5.xx. OC4BAv4 is from 27 January 2018.
MCP and EFIS are recognized by the PC. In the SIOC monitor all LEDs and switches/buttons are recognized and displayed when pressed. All LEDs and 7 segment displays can be switched. The MCP is therefore definitely not defective.
When I press a switch on the MCP (F/D, A/T,Disengage) these are taken over by the PMDG and also displayed in the MCP panel. Encoders and buttons are not taken over by the PMDG.
But if I turn in the panel MCP of the Pmdg values or press buttons, this is also transferred to the hardware and the corresponding numerical values or LEDs are displayed correctly.
The MCP can read the Pmdg MCP but only write partially.
Here are some screenshots that may help you troubleshoot.
SIOC version is 5.xx. OC4BAv4 is from 27 January 2018.
MCP and EFIS are recognized by the PC. In the SIOC monitor all LEDs and switches/buttons are recognized and displayed when pressed. All LEDs and 7 segment displays can be switched. The MCP is therefore definitely not defective.
When I press a switch on the MCP (F/D, A/T,Disengage) these are taken over by the PMDG and also displayed in the MCP panel. Encoders and buttons are not taken over by the PMDG.
But if I turn in the panel MCP of the Pmdg values or press buttons, this is also transferred to the hardware and the corresponding numerical values or LEDs are displayed correctly.
The MCP can read the Pmdg MCP but only write partially.
Here are some screenshots that may help you troubleshoot.
Re: Encoder and button problem in P3Dv4.3
Just to recap:
What is the Windows version number?
Is it only MCP or both MCP and EFIS that have the issue?
Have they ever worked in any older OC4BA and/or Windows settings?
When did you bought your OC modules?
Do you have the modules connected to a powered USB hub or directly to a PC/USB?
Is the Power saving option for the USB disabled?
What is the number you get in SIOC Monitor for one of the non-functioning buttons and the name of the button?
Send me the text of both SIOC.ini and PMDG737.ini
When you monitor a variable connected to one of the faulty buttons in SIOC/IOCPConsole, do you see any reactions when activating the button?
If I can't find out the issue after your feedback, I can connect via TeamViewer to have a look.
What is the Windows version number?
Is it only MCP or both MCP and EFIS that have the issue?
Have they ever worked in any older OC4BA and/or Windows settings?
When did you bought your OC modules?
Do you have the modules connected to a powered USB hub or directly to a PC/USB?
Is the Power saving option for the USB disabled?
What is the number you get in SIOC Monitor for one of the non-functioning buttons and the name of the button?
Send me the text of both SIOC.ini and PMDG737.ini
When you monitor a variable connected to one of the faulty buttons in SIOC/IOCPConsole, do you see any reactions when activating the button?
If I can't find out the issue after your feedback, I can connect via TeamViewer to have a look.
Re: Encoder and button problem in P3Dv4.3
Thanks again for your quick reply and your effort. Great service.
- The Windows version number is 1803 Build 17134.165
- The problem occurs in MCP and EFIS
-Yes, it worked perfectly until some time ago. With the original installation, without having to correct anything by hand.
After a big Windows update all USB assignments were changed, all joysticks and boadnar cards had to be reconfigured. I believe that the MCP problems also arose at this time.
-MCP and EFIS are about 2 years old
-I tried both, also in USB 2.0 and 3.0. No difference. Currently both are connected to an active 2.0 hub
-Power saving for USB is disabled
Pmdg 737.ini:
sioc.ini:
"When you monitor a variable connected to one of the faulty buttons in SIOC/IOCPConsole, do you see any reactions when activating the button?"
Yes, when turning the encoders or pressing a button, the associated fields in the monitor turn green and white when released.
What is the number you get in SIOC Monitor for one of the non-functioning buttons and the name of the button?
I'm sorry, I don't understand what you mean.
As already written, everything works perfectly in Sioc. All switches, buttons and LEDs are recognized and displayed correctly. However, not all data from Sioc seem to arrive in the Pmdg.
- The Windows version number is 1803 Build 17134.165
- The problem occurs in MCP and EFIS
-Yes, it worked perfectly until some time ago. With the original installation, without having to correct anything by hand.
After a big Windows update all USB assignments were changed, all joysticks and boadnar cards had to be reconfigured. I believe that the MCP problems also arose at this time.
-MCP and EFIS are about 2 years old
-I tried both, also in USB 2.0 and 3.0. No difference. Currently both are connected to an active 2.0 hub
-Power saving for USB is disabled
Pmdg 737.ini:
Code: Select all
[SIOC]
IOCP_port=8092
IOCP_timeout=4000
Minimized=No
toggle_delay=20
[IOCARDS MODULE]
IOCard_disable=No
IOCard_LPT=No
[FSUIPC MODULE]
FSUipcdisable=No
FSUipcRefresh=60
[IOCP CLIENTS MODULES]
IOCPini_delay=3000
IOCPclient0_disable=no
IOCPclient0_host=localhost
IOCPclient0_port=8099
IOCPclient1_disable=yes
IOCPclient1_host=localhost
IOCPclient1_port=8092
[SOUND MODULE]
Sound_disable=Yes
Volume=100
[*]
[PMDG B737]
CONFIG_FILE=OCP4NGX_v4.5.ssi
MASTER=15,15,1,25
MASTER=7,7,1,27
Code: Select all
[SIOC]
IOCP_port=8092
IOCP_timeout=4000
Minimized=Yes
toggle_delay=20
[IOCARDS MODULE]
IOCard_disable=No
IOCard_LPT=No
[FSUIPC MODULE]
FSUipcdisable=No
FSUipcRefresh=60
[IOCP CLIENTS MODULES]
IOCPini_delay=3000
IOCPclient0_disable=no
IOCPclient0_host=localhost
IOCPclient0_port=8099
IOCPclient1_disable=yes
IOCPclient1_host=localhost
IOCPclient1_port=8092
[SOUND MODULE]
Sound_disable=Yes
Volume=100
[*]Yes, when turning the encoders or pressing a button, the associated fields in the monitor turn green and white when released.
What is the number you get in SIOC Monitor for one of the non-functioning buttons and the name of the button?
I'm sorry, I don't understand what you mean.
As already written, everything works perfectly in Sioc. All switches, buttons and LEDs are recognized and displayed correctly. However, not all data from Sioc seem to arrive in the Pmdg.