Aamir

Do me a favor and DM me the ticket number, I'll look into this personally for you.

Did you turn on automatic crash reporting?

Okay, first recommendation I have - uninstall the product, reinstall it with defender turned off - it can sometimes just outright delete files and do some generally odd things. Then add exceptions for the Fenix folders and try again. There's a how-to here: https://kb.fenixsim.com/efb-showing-as-blank The other thing to do is use the Alternative renderer. I'd start there before I mess with Defender.

Do you have an anti-virus or something like that running? Windows defender, even.

A couple of things to try - untick Display Sync and tick "Alternate Renderer" - failing that a set of log files and a support ticket would be the next go-to.

Hey! This sounds like something we got a good chance of solving, but only with your help - these crashes are quite sporadic and getting logs from someone is always valuable in figuring out how to fix it. If possible, could you send your logs in so we can take a look at fixing this for you? Thanks!

In classic Airbus fashion, some stages will give you notice, others may not.

So, this is an interesting one - but we're finding out users that are unable to engage AP are in AoA Prot submode, which stays engaged after it has kicked in, even if you're no longer in that situation - in order to disconnect AoA Prot submode, do the following:

Just bear in mind a common mistake a lot of people make is to set their curves at +20, not -20, so just make sure and double check your sensitivity curve is truly at -20!

For sure, but I'm just curious to see if I can help - but I do need to know what you mean by "weird" - is it too fast? Too jumpy? Too heavy, or too light? Not precise enough? Also an idea of your sensitivity and SDS setting would be great - along with the sort of hardware you're using. I might be able to give you a couple of suggestions.

Pretty much any sort of feel is now possible - you can make it as heavy or as light as you desire. The recommended sensitivities are a good starting point with SDS. Perhaps post the sensivity you're using here and what desired outcome you're looking for and I can see if there's something easy you can do to make it better.

You guys are taking a message way out of context. That only had to do with David's post about liveries - he was waiting for a sign-off from all livery makers that they were happy with the text and screenshots used. It literally has no effect on the software whatsoever, you just can't see what he's responding to because it's a screenshot of a chat. Not an announcement or anything.

That's just for Dave's little extra informational post - not the build itself.

This should be fixed.

This is our new display render tech we developed for V2 - it's in Block 1 in a "hidden" form because we wanted to use it to troubleshoot this stuff with users having issues with old builds and to generally see how it behaves. We will be making this standard with B2 and switched on for all - but, similarly, it appears some people using Frame Gen mods are encountering issues, so there's a conflict there. It's sporadic, but it's there - so the option to use the older renderer will be made available.

It may be quite important to note that visual artists don't work on system stuff. Which is why when we do previews and show one aspect of the airplane, it doesn't mean we haven't done other stuff. It's right in the very post - we will do a systems deep dive next.

To clarify - I meant a full-bore failure system. The normal ops stuff is OK. Getting into circuit breakers and such is a different story.

It's perfectly fine for people to not like discord - but some things to clarify after some of the comments seen on this thread. 1. Discord is NOT AN OFFICIAL SUPPORT PORTAL. It is a community area for discussion, or to chat with the devs if you so wish in an informal way. If you need support, use the ticketing system - this is specific to people saying they would not have purchased the product had they known they would need to use Discord. You don't need to use Discord for anything. Important and large pieces of news, etc - are all also posted on our website. 2. This is NOT an official file/hotfix. It is a file I threw out there with a quick, unofficial hacky fix to stop the pitots from freezing. As indicated in my comments on Discord - the entire thing is unwarrantied. But people kept hammering at us for not being able to use icing, so I provided a solution, unofficially. To date there has NEVER been any software update of any sort that has been exclusively distributed via Discord. This is NOT distributed "officially", it is NOT a patch that we want installed on every customer's PC, because it is untested and put together quickly for people that are deperate to use icing for whatever reason. Hence, it is not pushed via the installer/update system.

Generally, the sort of issue you see occurs with a flap axis - MSFS will overwrite anything we send it - so my suggestion to start with would be to unbind (completely) the flap axis you have set up, both in MSFS and in whatever external program you have - and try again.

What are you using for your pushbacks?

A dev responded to your questions directly in Discord, with some questions and suggestions. If you do not reply to them, I would expect you find limited help.

Or, you know. Make use of one of the three hundred odd failures if you're getting bored.

It will not - we are working around it.

A question - what are you using for pushback?

No, it isn't. It's actually the opposite. If the FDE is garbage, the output is garbage. word not allowed in, word not allowed out. It's easier to develop an FM for a non-fbw aircraft. There is less tuning to do to make it acceptable.