KSJ

Uninstall / delete from WASM MSFS2024 / Remove liveries from Community / From Marketplace Streaming do new download / open sim check / repeat everything again if still screwed up (took me 3-times) / put liveries back into Community. With closed fist hit yourself in the head for making a Marketplace purchase when you vowed to never do it again. Check announcements regularly for when Ini sets up a transfer routine.

So, just updated to 1.01. Booted the sim and brought up the standard cabin livery. This is what I now have. Am I alone? A hint as to what the heck is going on?

I know from personal knowledge that RW crews have provided Ini with lists of possible inaccurate modeling. Let's give them a chance to work through them towards update 1.

Sounds like a sensitivity setting. Each A/C is different. You may need to setup a custom curve in control settings for the L101.

Agree with Dr_Ed ... spawning on the runway is a real mistake with a complex airplane. There are already pointed out bugs with the aircraft that we are working around with manual setup on the ramp. When you spawn on the runway the A/C may try to start up with these bugs and no corrective action having been taken. Also, I wouldn't rely on the sim to setup a complex A/C to begin with.

Takes a VERY long time to load for the first time. I've seen up to 15-minutes. Sometimes it helps if after you've waited 2-3 minutes, hit ESC and try spawning again.

L1011/Standard/FDs ON, before engine start - Can't Set V2+70 / AOA. Pressing TOGA button on yoke locks out the speed setting knob when showing AOA. Initially the display shows IAS 100. If I change the speed (to say, 217) pressing TOGA button changes it to some seemingly random speed and, again, the knob is non functioning and it cannot be changed. What may I be doing wrong??

I had a post about this entitled "Winwings MCDU Progress" which had some workarounds and replies from users experiencing this issue. For some reason it has disappeared from the Forum. Would be great to have some indication from Inibuilds as to why. There were some very useful sources of information in that post. Go to this Post

The floods on both the main panel and ped are inoperative

Unfortunately, although the buttons function correctly and operations are reflected in the A/C, the MCDU display is not functional. Discussed with WW and waiting for their fix.

You're absolutely right. I see now what the issue is. They did not update their website product support list to reflect the latest changes to Simappro.

Think you missed the point here. All users know that Simappro supports the hardware but Simappro supports only a limited number of aircraft. Here's the list: https://us.winwingsim.com/view/goods-details.html?id=945#catalogue-4 The issue is it doesn't support Inibuilds products. Also, thrid party developers such as Mobiflight historically have produced alternative methods of driving Winwing gear. Mobiflight and others are handicapped due to the unavailability of the list of variables needed to drive the WW MCDU screen. The buttons are working with third parties such as Mobiflight but not the screen. The point I was making is that publication of the variable list would allow us users to have what we need right now. WW has promised the Ini A350 for a long time as an example. But to date no joy. We have no reason to believe the A343 will somehow come to the top of the WW developer's list.

Why are we waiting around for Winwing's developers to do a native project? It's a good idea in the long run but, there's other, quicker, alternatives out there just waiting for you to publish the display lvars. Developers such as Mobiflight and others can come up with profiles at light speed. This would be a much more timely and supportive path for your customers. The new A343 is outstanding. Personally, I now use it as my go to platform. I can use a mobiflight profile for the FCU and EFIS's and for the buttons on the MCDU. What a shame I can't use the whole MCDU because they don't have access to what they need. You guys could do well to put development into the hands of more motivated groups. Silly as it may sound, I know a bunch of "pilots" holding off purchase just because they can't use the mcdu.

Thanks for this workaround which works fine. It's now June 2025 and it's still not fixed. I did note on the A330-300 the pop out does work on the EFB.

Would be nice to have a response from the developer. This is a major defect preventing normal flights. At least give us an update or a projected time of fix.

Made a post that should not have been made. How does one delete it entirely? Or, can't we?