Arty57

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

I have no issues starting or completing a flight with this error. What is the blocker for you? -A

FWIW I have used the default pilot side for the last 30 days or so. Always was able to light up and use the WINWING MCDU and SAP .70 but…I would also experience periodic freezes of the WINWING screen necessitating unplugging and replugging (power cycle powered USB hub) to unfreeze the MCDU. This occurred randomly every 30 min or less. Tonight after reading of your experience with using .71 SAP with the co-pilot side I was able to complete a 3 hour flight without any MCDU freezing or lockups. Only one flight so far but I am encouraged. YMMV. TANSTAAFL. Blue skies, -B

Thank you for your concise and honest response. I look forward to seeing what version 1.0.4 brings. Blue skies, -A

The freezing I am referring to is when using the WINWINGS MDCU hardware. I have been patient as have others, but it’s time for an update from the developer. Early on shortly after release the forum had multiple posts from iniBuild staff suggesting that the fix would be soon forthcoming. Now, some 40 days after initial release updates concerning this critical bug remain few and far between. Please provide an estimate for when a resolution can be expected. Thank you, -A

That’s what I thought. Asobo plane, is it not?