Report bugs in OCP4787 for P3D here
Re: Report bugs in OCP4787 for P3D here
martin:
Do you use a MCPv2 or MCPv3 module?
Do you use a MCPv2 or MCPv3 module?
Re: Report bugs in OCP4787 for P3D here
Hi,
I use a MCPv3
Martin.
I use a MCPv3
Martin.
Re: Report bugs in OCP4787 for P3D here
Roar, I ordered and paid for this version but I have not received the email with the link to the software. Can you advise please?
Thanks
Keith
Thanks
Keith
Re: Report bugs in OCP4787 for P3D here
Hope you got it now. Sorry for the delay.drayton_k wrote:Roar, I ordered and paid for this version but I have not received the email with the link to the software. Can you advise please?
Re: Report bugs in OCP4787 for P3D here
Roar,
I am getting "Not a Valid Integer value" error and socket errors 10061. P3d V4 and SIOC are allowed through the firewall. I'm using version 6.0 B8 of SIOC. Any ideas?
EDIT, turning off the firewall does not fix the socket errors
I am getting "Not a Valid Integer value" error and socket errors 10061. P3d V4 and SIOC are allowed through the firewall. I'm using version 6.0 B8 of SIOC. Any ideas?
EDIT, turning off the firewall does not fix the socket errors
- Attachments
-
- Screen Shot 246.JPG (155.08 KiB) Viewed 5346 times
Re: Report bugs in OCP4787 for P3D here
drayton_k:
The Socker Error can be a timing issue. I am investigating this now and believe that on some systems the SIOC server needs more time to start up and get ready for QW_Client call.
I will send you a new update that gives SIOC a little more time to settle down before the client is sending a call.
The Socker Error can be a timing issue. I am investigating this now and believe that on some systems the SIOC server needs more time to start up and get ready for QW_Client call.
I will send you a new update that gives SIOC a little more time to settle down before the client is sending a call.
Re: Report bugs in OCP4787 for P3D here
martin wrote:Hi,
I use a MCPv3
Martin.
The AT button issue you reported has been identified as a bug and is now solved. I send you a new update for test.
The issue with the rotary switches needs more information.
Can you open IOCPConsole and set LOG On and trace what is going on when you turn one of the "faulty rotaries"
DO the test with the new update and send me your findings.
Re: Report bugs in OCP4787 for P3D here
Hi Roar,
The problem with the speed button is solved for the problem with the erratic inputs I opened het IOCP console and i made on every Rotary small turns they still are erratic (i made a screenshot) also when i shut down P3Dv4 there is a error message called Asynchronous socket error 10053.
For the screenshot see my email.
Martin.
The problem with the speed button is solved for the problem with the erratic inputs I opened het IOCP console and i made on every Rotary small turns they still are erratic (i made a screenshot) also when i shut down P3Dv4 there is a error message called Asynchronous socket error 10053.
For the screenshot see my email.
Martin.
Re: Report bugs in OCP4787 for P3D here
Looking at your IOCPConsole tells me that something is faulty with your SIOC programs, as I can not see the variable names in the variable name column. If this has anything to do with your problems I really do not know.i made on every Rotary small turns they still are erratic (i made a screenshot)
This also indicates to me that there is some SIOC problems.Asynchronous socket error 10053
AS you state that PMDG drivers work OK, it seems strange that SIOC should be "faulty".
Anyway, I suggest you do an uninstall and new install of SIOC.
Also make sure your AntiVirus program has exclusions for SIOC and P3Dv4 folders.
Check that you have SIOCv6.0.
Check that you have the latest QW B787 update.
Re: Report bugs in OCP4787 for P3D here
Roar,mvr1918 wrote:drayton_k:
The Socker Error can be a timing issue. I am investigating this now and believe that on some systems the SIOC server needs more time to start up and get ready for QW_Client call.
I will send you a new update that gives SIOC a little more time to settle down before the client is sending a call.
Sorry no this does not help. The same issue Im afraid.
- Attachments
-
- Screen Shot 248.JPG (105.06 KiB) Viewed 5344 times
-
- Screen Shot 247.JPG (12.11 KiB) Viewed 5344 times