37 minutes ago, Vitold69 said:

We have time to test new PMDG tablet and Horizon 789 meanwhile.

Yep. I've got plenty to occupy my time until block 2 arrives.

On 10/19/2023 at 8:37 PM, Aamir said:

Ultimately, criticism is fine. It is what it is, I can't do much about that - it is simply a byproduct of choosing to do what we're doing. You could have had IAEs around a year ago, but with 0 actual simulation behind it. Just a skinned CFM with "interpreted" display data and a bunch of nonsense running behind the displays. But hey, it would have worked, I guess.

It was our choice and our decision to build both the IAEs and CFMs to be better. Much better. We set our targets on stuff that is new and innovative. That is what our company is about - but pushing the boundaries come at cost. Both financial, and opportunity. Trust me, I stand here today sometimes wishing we did, in fact, just skin the IAEs and call it a day, followed by quickly throwing out the A321 and A319 and simply just moving on. It would have been cheaper by a factor of 10, and I'd reckon most wouldn't have noticed. But I would have. And it's not our ethos. As a consumer I believe in putting my dollars behind a company whose products I admire, but also whose ethos aligns with what I'm looking to get out of my dollars. So, that may open the door to criticism, because of how long it took to do. I think that's fair, and it does mean some customers completely disagree with it, and no longer want to spend their money with us - but we're always going to end up pushing for quality and depth over timelines, because there's no joy in what we do otherwise. 

Aamir, I think it's sometimes pointless engaging on these sort of discussions because ultimately anger in the sim community is soon forgotten and the community generally is fickle. Nobody will not buy the next Fenix product no matter how long it takes. Until then though it's impossible for you to fight against the energy and vitriol that the community can inflict upon developers.

When I read on this forum I realise that there are a large amount of people who are deeply interested in aviation but actually very few understand or have some knowledge about it. That's however because most are not engineers or real pilots. That isn't their fault but the consequence is their expectations are varied and founded in that misunderstanding.

At the end of the day you're trying to replicate a living and breathing thing that has been designed by teams of engineers within a multi-billion $ company, and even that environment is fluid as aircraft are always changing. Hardware and software wise, the first A320's built in the 90's are vastly different to an A320 built yesterday, most people really don't understand that. It's ridiculously complex when you throw in engine variants or the sub-configs used by various airlines.

As you say, you could trick the ECAM to show EPR values, roll in the IAE model and you're done. However even with the model alone, will everyone recognise that the flap extension at config FULL is around 5 degrees different for IAE vs CFM, what about the aerodynamics impact? The majority won't recognise these intricacies but this is why even a variant of the same aircraft takes so much time.

I guess what I'm trying to say is I don't think you need to answer the door in terms of criticism. It is impossible that you could ever truly appease everyone. 

Edited October 30, 20232 yr by G MIDY

7 hours ago, 737_800 said:

It is what it is. It will be there when ready. I personally don't care about that, as long as they deliver a good product in the end. What makes me happy instead of deadlines, are updates of new features or screenshot over the process.

No biggie means I don't mind if it is delayed. I was just passing on the latest from Discord as many users don't use it. 

Enjoying her whilst waiting in anticipation… perhaps Santa will use Fifi instead of Rudolph this year :).

I for one APPRECIATE the updates here, I just don’t use Discord enough. Ta!

C

Edited December 6, 20232 yr by cavaricooper

Any news from our Discord fellows? Will FIFi pull Santa’s Sleigh using IAE’s this year?

Happy Xmas!

C

Only news was they were rely heavily on detail maps and built V2 around them however they do not seem to function properly on some exports and sometimes, scarily, on the users side. The issue started on one of the SDK updates and they need fixes from it for several features but also need the old one to export a working model. They are having to significantly roll back on several months of work as Asobo don't seem to be addressing the issue. A bug report was sent out several months ago to them. Still meeting Intial objectives but the fix is likely just be a few lines of code somewhere in the MSFS shaders which is something they can not change. They are working around it.

Asobo / MS are already looking into more money from 2024's version. This might not even be fixed, who knows.

8 minutes ago, carlanthony24 said:

Only news was they were rely heavily on detail maps and built V2 around them however they do not seem to function properly on some exports and sometimes, scarily, on the users side. The issue started on one of the SDK updates and they need fixes from it for several features but also need the old one to export a working model. They are having to significantly roll back on several months of work as Asobo don't seem to be addressing the issue. A bug report was sent out several months ago to them. Still meeting Intial objectives but the fix is likely just be a few lines of code somewhere in the MSFS shaders which is something they can not change. They are working around it.

Don't know how much reliance they can get from MS when their product don't make them money on the Marketplace. Why a new model in the first place when nothing was wrong with the first one, what the whole new engine model relied on the new one (Model)? Obvious many customers want answers with vague dialogue.

Edited December 21, 20232 yr by JBDB-MD80

11 minutes ago, carlanthony24 said:

Only news was they were rely heavily on detail maps and built V2 around them however they do not seem to function properly on some exports and sometimes, scarily, on the users side. The issue started on one of the SDK updates and they need fixes from it for several features but also need the old one to export a working model. They are having to significantly roll back on several months of work as Asobo don't seem to be addressing the issue. A bug report was sent out several months ago to them. Still meeting Intial objectives but the fix is likely just be a few lines of code somewhere in the MSFS shaders which is something they can not change. They are working around it.

There's a more recent "Fenix block 2 delayed [31 October 23]" thread where this is specifically discussed, and Aamir's response on them proceeding ahead by working around the shader issue:

So if the visual model upgrades are not being held up, hopefully they'll be able to push out Block 2 soon, but maybe not until very early 2024.

16 minutes ago, JBDB-MD80 said:

Don't know how much reliance they can get from MS when their product don't make them money on the Marketplace. Why a new model in the first place when nothing was wrong with the first one, what the whole new engine model relied on the new one (Model)? Obvious many customers want answers with vague dialogue.

You may think nothing was wrong but things were wrong and was acknowledged by the devs when people submitted tickets. We have the answers they are vocal about it in Discord even on here when Aamir replies so you saying its vague, struggling to see how. Many are happy to wait its the minority which are the same few trolls and people who have no understanding how these things happen asking every day. E.G one guy constantly complaining about the Ice not working again but does not read what is actually said. Surprised he has not been banned or even muted like they were on the FSLabs forum.

Edited December 21, 20232 yr by carlanthony24