Yeh same with my mcp2 and the vr software its really hit and miss detecting,  glad i got it working by turning the mcp2 on 5 seconds after starting p3d,  for some reason this works when no other way works,  scots solution did not work for me unfortunately,  love to know whats changed probably a windows system issue

All

Please report your Win10 version and build number (using System Information).

Not home but will advise in 24 hours,  im on the very latest,  win 10 pro

Hi Scot

 

Win 10 details as below

Item    Value    
OS Name    Microsoft Windows 10 Pro    
Version    10.0.17763 Build 17763

Scot

 

I did use your modification but it did not work but perhaps it is some how contributing to my workaround, IE running linda, running P3D4 then in 5 seconds switching on the MCP, within 3 seconds the MCP2 flashes and says select your aircraft and fly now, from that point it works in P3D and with Linda

Thanks Wayne

Can you turn on all the debugging as above and send me your FSUIPC5.log after running your workaround?

Hey Scot

 

Just sent it via email

 

Regards

Wayne

Thank you Wayne for the log. It shows the original correct FSUIPC connection to the MCP. This indicates that the new switch is not active.

Please check that you have made this change to FSUIPC5.INI [General] section:

 VRIDisableCMDRST=Yes

This needs to be done before starting P3D. It took me several attempts to lock this change in.

Then run 2 tests saving the FSUIPC5.LOG for each.

1. clean start of P3D without worry around.
2. use workaround.

then email me both logs.

PS ALSO EDIT LINDA COMMON.LUA TO COMMENT OUT THE CMDRST INSTRUCTION. SEE ABOVE

 

Edited February 3, 20197 yr by ScotFlieger

1 hour ago, suchw said:

Win 10 details as below

Item    Value    
OS Name    Microsoft Windows 10 Pro    
Version    10.0.17763 Build 17763

That is interesting. My system is only at 17134. Can others experiencing the problem report their Win10 build version?

just sent you the log files and also confirmed that I have already disabled that command line in the common.lua

The latest FSUIPC5.log still shows the CMDRST being sent as though the VRIDisableCMDRST=Yes is not working.

Your system is recorded as Windows 10 Pro 64 Bit reported as Build Windows 10 Pro 64 Bit reported as Build 17763, Release ID: 1809 (OS 10.0). This is the same build as I am using so mine has updated automatically in the past week. That defeats my latest hypothesis.

Edited February 3, 20197 yr by ScotFlieger

My system is Windows 10 Pro, version 1809 installed om the 25/01/19

 

OS build 17763.292

Edited February 2, 20197 yr by Mantamuzza
added additonal information

Hi Andrew,

Sorry for very late respond but i lost track of the tread since you merged it.

My windows version (i got this from the system information) is : Windows 10 Pro 64 Bit Build 17134.523, 1803, 26-05-2018.

I have sent you the log files, but i am not sure if i have set the two dashes correctly in front of the com.write line. I can not find "outline 153" because there are no line numbers in the .txt. I saw a lot of com.write lines.

anyway, maybe you can check out if i have choosen the right line from the logfiles i have sent you.

Your support is great, you just never give up don't you? Thanks

Ben

Edited February 3, 20197 yr by Bentree_

Hi Ben

Thank you for the latest logs. The change to fsuipc5.ini is not set correctly. Close all programs and try again. Insert 

VRIDisableCMDRST=Yes

into the [General] section. 

Also the change to common.lua should be made to LINE 153 (-- com.write(dev, "CMDRST", 8 ) adding 2 dashes) - not outline 153.

I don't want to give up because LINDA should be working for all VRI users.

 

O.k. i will try again, but can you please tell me how to find Line 153?

I can set the cursor on top and count down until 153 but then i did not finish on a com.write line 🙂

Regards,

Ben