iniSteven

As per the real aircraft, the IAS and MACH modes on the MCP are Pitch modes - they will pitch the aircraft to hold a selected IAS or MACH speed while the throttles are operated manually to adjust climb/descent rate. Again as per the real aircraft, AT mode can only hold an IAS dialed into the window, and TM mode can only hold the Mach value calculated by the PMS. If you want to hold a specific mach value, you have to do it via entering the corresponding IAS in AT mode.

Mach is a pitch mode, not an autothrottle mode. You can only hold a mach speed in cruise with the autothrottle by using "TM" mode through the PMS. The standard AT mode can only hold an indicated airspeed.

Hi Florian, the lights are all working on our end (and various screenshots posted on our discord also confirm that this is not a universal issue) so this is most likely caused by a conflicting addon on your end. I would start by loading the A350 with a clean community folder and seeing if the issue persists.

Hi, in my testing on a 5080 VRAM usage at detailed sceneries was around 12-13gb. What are you seeing on your system?

Please don't report bugs that occur when loading an autosave from a previous version. As the previous version had an error causing DES mode to activate prematurely, it's likely the descent flag had already been triggered and this was baked into the save. We did multiple full flights in 1.2.4 testing both the cruise step descent behavior and the final descent behavior.

Hi, this is what I have from art: We have confirmed the wing livery model provided in our paintkit is working as intended. Please make sure you are using the livery template project provided in the paintkit as it already contains the necessary models to create a livery. Open the xml inside the project with the latest version of the sdk and follow the instructions inside the readme to make your livery. If you are unsure on how to use this template project please refer to the sdk documentation. There is no need to use a model from one of our custom liveries Please make sure as well that your "A343_WINGREG_ALBD.PNG" is a transparent png file and not an opaque one

Having this many simconnect events (one for each pixel the mouse moves) is going to be a huge problem. Simconnect has trouble handling even double-click events like the Autopilot Disconnect, so I doubt this would even work. Plus, having this many events would significantly increase the chances of Simconnect crashing/hanging entirely.

The OIS is a JS gauge - all the rest are core avionics and are part of the WASM package.

It's not possible at this time. Popped out WASM gauges cannot receive mouse click or scroll events, so it is impossible to make them clickable.

It means that it's not something we even can plan because it's not a decision we can make.

Hi, this is incorrect. 1: The winwing MCDU *is* compatible with the A340, which is the only aircraft that uses these grouped instruments. Given the feedback we have received we do not plan to continue using this method for future releases. That said, the graphical display of the instruments has nothing to do with compatibility with Winwing peripherals. Regarding the disconnection issue, we are in contact with Winwing to solve this as many of us on the testing team use these peripherals and want them to work. 2: The A320, A321, and A330 are Microsoft products built by us under contract. As such, the scope and featureset of these aircrafts is determined by Microsoft.

Of course, anytime! Hope you've been enjoying the plane 🙂

Hi Dectenor, We know of this behavior, it is an exception that can happen when there is a mandatory level off segment during the approach. But it's not as simple as simply increasing the descent rate, because we are simulating the CDA function of the A350. As you know, the A350 descent profile is calculated backward from 50ft AGL up to TOD, and as part of this calculation the aircraft seeks to remove all level-off segments and achieve VAPP and configured for Landing at 1000ft AGL. It's important to remember that our goal isn't to make a VNAV system that hits every restriction, we're attempting to make a VNAV system that behaves like the real aircraft. Airbus pilots will tell you that the real aircraft VNAV system isn't perfect, it doesn't always hit every restriction, and can sometimes have odd behavior as well. As mentioned before we are working on improvements to the LNAV and VNAV systems to better reflect the real aircraft behavior, but in the meantime you sometimes have to give the aircraft a little extra guidance, as sometimes happens in reality as well 🙂

Hi, the issue is that your vent extraction is on manual override. This should be closed in flight, but the manual override opens it, which is why you cannot reduce your cabin altitude.

Thanks, forwarded to the scenery team who will take a look 🙂

Hi, I think the issue is that the runway at Queenstown is only 5,800' long and surrounded by mountains. I don't think an A350 is capable of taking off in such a situation! 🙂

Hi, has this happened multiple times or just once? Could you take a screenshot of what you input so we can test the same values? I've just done a calculation to test and it seems to work, so I'm curious if it's related to a specific input. -Steven

Hi Bert, can you confirm that you have Photogrammetry on in your Data/Online settings?

It is unreasonable to expect someone to answer a question within 24 hours on a holiday. We have families too 🙂 The Default MSFS2024 airbuses have weather radar but not terrain radar. You can see here:

There's Terrain and Weather radar in the A300, A340, and A350 as mentioned on the product pages. I am confused as to why that is considered unclear or inconsistent. I apologize for not getting to this topic sooner, that said though I think expecting an answer within 24 hours on December 24th is a bit unreasonable. We are all humans here on the other side of the screen after all 🙂

Hi, I don't think there's anything we can do on our end to fix the issue here, as we can only define start and endpoints for taxiways and runways. All logic regarding routing is handled by BATC's AI.

Hi, you would need to recenter the rudder in order to re-engage the autopilot. I would suggest unbinding any keybinds attached to control movements if you don't need them, they will only cause problems. -Steven

Hi, are you on 2020 or 2024? The 1.0.3 update was for 2024 only.

Hi, the current version of Innsbruck for MSFS2024 is v1.0.3, the changelog for that version is here: v1.0.3 Reconfigured LOJO heliport; removed trees/clutter, added lights and replaced fence and markings.,, Replaced low resolution airside vehicles,, Helipad 03 spawns inside of building, Runway centreline not straight, Trees and ground poly bleed through POI_Stadium, Adjusted alignment of dark patches on main apron, Most airside 3d manhole covers replaced with HD decals, Removed fence at stadium

Disabling it from the content manager is all you should need to do.