Arty57

Thank you Steven for an opportunity to retract my incorrect theory of root cause. I have been more fully informed now and feel far more hopeful for a quick resolution. Blue skies, -A

I believe this will not get addressed in the short or even medium term. Simply put ini’s design decision to group multiple instruments into one popup instead of single popup’s for single instruments. This means that WinCTRL has only one data stream for six or so instruments. Lots of opportunities for collisions and connections to be lost. Single popups mean singular data channels. No Collisions, much less chance of connectivity failures. This is my understanding of the situation based upon months of working to get a resolution for the WinCTRL MCDU screen freezing when used with the iniBuilds a340-300. Identical hardware MCDU, FCU and EFIS and the WinCTRL software, SimApp Pro (any recent version). The Fenix and FSLabs planes both use one popup for one instrument. Both Fenix and FSLabs airbuses perform flawlessly 99% of the time. IniBuilds not so much. The a340-300 is the only ini plane that can talk to external MCDU (FMC/keyboard), unfortunately it keeps losing it’s voice. When that occurs the screen locks up. Notably the keyboard and LSK’s still function and can be witnessed on MCDU in virtual cockpit but the screen locks up. Unplugging and reconnecting fixes it or switching off/on with a switched hub OR changing focus of MCDU from Pilot to co-Pilot in the SimApp Pro software all fix the freeze, until the next one. Very random, sometimes 10 minutes into flight, sometimes 30 but always it will freeze. No matter what your perspective there is no denying it totally kills the immersion of the external hardware. The fact that WinCTRL and/or iniBuilds remain completely silent on this well known bug is telling. Make of it what you will -A

As Pilot061 said, there’re are workarounds but no fix as of yet. Three easy workarounds that are simple to accomplish but are definitely immersion killers: 1.) Unplug your MCDU and plug it back in, screen functionality restored until next time 2.) Using a powered and switchable USB hub, a power cycle (off/on) does the same as #1 3.) in SimApp Pro, select the MCDU and you can switch the MCDU from Pilot’s command (left side) to co-pilot’s command (right side) and back again if needed for the next freeze. This too restores functionality but like in all cases, the freeze returns. IT NEEDS TO BE SAYS SAID: Both the Fenix and FSLabs airbuses when using the same WinCTRL gear, same SAP NEVER freeze up. Never been a problem for them, only the ini a340-300 which is the ONLY ini airbus with a working external physical MCDU. Unfortunately it does not remain working but better than no working external physical MCDU I suppose. -A

The packs have been deprecated and are no longer supported. Lose the packs and all will be as it should be. Blue skies, -B

“The EFB always shows 1.0.7 even though I've uninstalled and reinstalled everything 5 times, deleted the WASM and every other official folder, I can no longer use the aircraft! i checked twice, i deleted every possible folder and installed the 1.0.9 and nothing changed ... the pictures are the state after that all... still 1.0.7” Make sure you 340 is not selected under Free Flght. Put another plane in its place, then download and install the update and you should then be able to install using Library. After that and choosing the 340 for free flght you,should be on V 1..0.9 and your EFB should reflect that fact.

IMPORTANT UPDATE: Version Discrepancy. FYI. Today I installed V 1.0.7 from the Marketplace. This aircraft exhibited the same bug I had previously reported. Details above but the Marketplace V 1.0.7 does exhibit the bugged behavior. Tonight after transferring my MP purchase to my iniBuilds Manager account and installing it, I went to set TO Performance on the Ini Manager plane and no bug is exhibited. This version works as expected performing TO Calculations in LBS. -A

Here you go. Names self explanatory I hope. EDIT most shots to large for here. Same outcome. Attempt TO Perf in LBS, FAIL. TO Perf in KG, Sucess. Easily reproduced SB Flightplan attached. Edit II reduced some screenshots hope these are helpful -A SB Flightplan KPDXKOMA.txt

Ini reports it fixed in this release. It’s not, at least for me. Same symptoms. Same workaround. -A

What I’ve found is there is no need to change your planning. Simply import you SB with LBS flight plan as usual and then on the EFB change it from LBS to KG. Hit calculate and you get V1, VR and V2. Once sent to FMS feel free to put your EFB back on LBS if so inclined. Blue skies, -A

I didn’t realize the 220 was released yet. -A

Howdy. Since updating to Ver 1.0.6 I cannot get a takeoff performance calculation in the EFB. Using stored Simbrief test flights which have never have failed, now every time I push “Calculate” an orange banner appears which states unable to find safe take off data (or something to that effect). This precludes setting appropriate vspeed, flap and trim settings in MCDU. This has never happened before this build. I have uninstalled and reinstalled the plane to no avail. Is anyone else seeing this? TIA, -A

Good day. I have been trying to sort this out ever since initial release (day 1). Originally the WINWING MCDU did not work with the a340. Now after five updates to the a340 and a similar amount to SimApp Pro (SAP) the MCDU works, but not consistently or reliably, at least for me. I am on SAP 1.16.75. I am on a340-300 1.0.5. All WINWING hardware has firmware checked and is current. The symptom of this failure is as follows. Initialize plane at gate on APU. Enable SAP. MCDU and FCU/EFIS come alive and function. Set fuel and weights via EFB and Simbrief. Flight Plan into MCDU via SOP. When everything is set depart as normal. Every flight at some point the MCDU freezes. Screens locked. LSKs and buttons still function as can be seen on virtual cockpit MCDU. Only the physical MCDU is affected and only then the screen. This usually occurs within the first ten minutes of flight, sometimes sooner, sometimes later. When this happens a power cycle of my switched and powered USB3 8 port hub restores functionality of the MCDU and it operates without issue until the next occurrence at which time a power cycle is needed again. Rinse and repeat throughout the entirety of the flight, two, three even five hours. I have never once experienced a flight without an MCDU freeze and most flights are two or more. As I type this I am engaged on a test flight KLAS to KBOS. In the first 30 minutes of this five hour flight I have had two MCDU freezes. The MCDU is the only component in the WINWING chain that is affected. The virtual cockpit MCDU and physical FCU and EFIS continue to work as expected and all functions of those components are available. I have Airbuses from other vendors, Fenix and FSL, that operate the same way (MCDU, FCU/EFIS via SAP) that have dozens of flights each, never once with a lockup or freeze. Only the iniBuilds a340 exhibits this consistent anomalous behavior and failures. A solution is desired and requested. Please assist. -Braun T

Never gonna work in these two birds. Touch screen v LSK key presses. FCU and EFIS do work in the 350 tho. Ini doesn’t make a 380 (yet). Blue skies, -A

Good. That’s how it’s supposed to work. Unfortunately I still experience the freezing. Hopefully ini can provide a universal solution. Blue skies, -A

Title says it all. We are now on version 1.4.0 of the a340 and still the MCDU when using the WINWING gear with SAP freezes routinely. Not a showstopper as a reset of the MCDU (power cycle) restores functionality but it most certainly breaks any sense of immersion and real life flight, which, after all, is the goal of using hardware gear with the aircraft…Immersion and real life flight. If this was a problem for other aircraft using WINWING and SAP, I would have a bit more patience but Fenix and PMDG manage to broadcast data to MCDU’s flawlessly and have done so for many many months now, beta’s and all, so I feel it’s time for iniBuilds to pony up some answers concerning support of WNWING. IniBuilds: When can we expect to see full compatibility and functionality in your software for this gear? Thank you, -A