Most of the commonly reported issues and questions are answered in the Frequently Asked Questions (FAQ) option under the Support menu of this website.
*** PLEASE NOTE ***
Your forum account is not the same as the account used in the shop. They are completely separate accounts.
Your forum account is not the same as the account used in the shop. They are completely separate accounts.
1st December: A new version of the GoFlight Interface Tool for MSFS is now available.
12th November: A new version of the GoFlight Interface Tool for X-Plane is now available.
6th June: A new version of Virtual Flight Sim Hardware is now available (huge update)
21st November: A new version of the GoFlight Interface Tool for FSX/FSXSE/P3D is now available.
Xplane 11 zibo mcppro
Does anyone know if that should be considered normal ? Zibo and goflight mcp. Check the screen and the actual mcp.
Im using pollypot soft. As is. With one of the setup for zibo that is available for download.
Im using pollypot soft. As is. With one of the setup for zibo that is available for download.
Comments
S
No not normal at all. I have had the 1 knot difference but I just tried to reproduce it and everything worked perfectly. When it happens to me again, I'll take a bit more notice and try and track it down. In terms of all the lights, it's definitely not normal. I do have some issues when changing modes. The previous mode light stays illuminated as well as the new modes light.
The V/S window should be blank when zeros.
I've attached a latest copy of the profile that I have. Remove your old one and import the new and see how you go.
David
Since the version of Zibo 3.36 and 3.37. There are some buttons of the MCP Pro hardware that do not sync with the panel of the aircraft.
you press VOR LOC or APP or VNAV, LANAV ... etc and they do not light up on the plane. but it's random
the opposite works very well
Do you notice the same problems ?
Thanks
GoFlightInterfaceTool_SetupX-Plane_2_0_15_2 -w10 - XP11.36
edit i dont see : i loadt latest copy of the profile and i try with him
1. On the MCP-Pro tab in GIT, change Write delay to 20ms (this syncs the lights and displays perfectly for me. Anything higher doesn't sync properly) and change Cmd delay to 100 (anything lower causes hardware lockups for me).
2. In detective, I increased all the Sleep values by a factor of 4 under each bespoke command in David's code. The initial "Start" bespoke variable, I think, was causing my crashes and I now have that set to 480ms. I've quadroupled all the other sleep values (except IAS up and down) to play on the safe side and haven't noticed any bad side effects.
Like I say, trouble free ever since and I haven't had the IAS mismatch of 1 kt since. I know everyone's hardware/setup is different, but hopefully it'll work for you too.
Russ
modification 1 ok
modification 2 nok
I have not managed to know what to change in detective as you a photo ?
except that now GIT is buged what is so the initial values of Write delay and of that I I give them
thanks
yes the picture and your details will help me but I'm afraid to make mistakes while it works not too bad it should not be worse.
I would also like the guys from Pollypot to give their opinion on these problems
thanks a lot
Roland