Deleted Account

Yes 🙂

Heya! WASM not compiling actually never was an issue, we just initially thought it was, but it wasn't. Now, the frames shouldn't be that much worse as on the PMDG, in fact for me, they are nearly identical. I posted my screenshots earlier in this thread. However for the next update there are some more performance improvements, hopefully it'll get better for you as well then 🙂

Heya 🙂 We will look into adding support for configs to stay after updates; for now it hasnt been a feature as it might lead to problems in the update process. Thank you for putting in the suggestion 🙂

As said above, the SimBrief request pending issue seems to be an issue on the WASM API, and we reported this to Asobo. They have confirmed the issue and will come back to us with more information to resolve this. There unfortunatley really isn't any more we can do. I know this is frustrating, especially because it works in other planes, but this is where we currently stand.

Yes, thats exactly the one I mean 🙂 When the diamond goes up to the top of the meter the airplane should normally automatically decrease its descent rate to catch it again; you can also just do a manual level off if you want to to help the aircraft a bit with it 🙂

Heya again! No, I unfortunately can't reproduce this. Which version of iniManager are you using? Anything older than 2.10 by chance? If it is 2.10 it'll say so in the options, if there is no version in the options page, it something older. In that case, please update the Manager.

Heya 😄 I`ll add it to our internal wishlist, no promises though obviously 🙂

Heya 🙂 My personal tip would be to keep an eye on the pink diamond and if you're too far above the profile pull the speedbrakes. Especially with the speedrestriction at 10000ft the A310 can sometimes be slow to slow down; speedbrakes always help there. You can also check your current altitude vs the profile on the PROG page.

Currently not planned unfortunately, no 😕

SimBrief request pending issue seems to be an issue on the WASM API, and we reported this to Asobo. They have confirmed the issue and will come back to us with more information to resolve this. This is where we stand with this.

Ah, sure enough I was able to reproduce it now. The issue with this is, that it only happens with Multiplayer aircraft that don't have our scenery. I don't know if there is actually anything we can do against it, but I'll forward it to our scenery team and see if they can 🙂

Heya! These buildings are not there on my end. Please make sure you don't have any other NFFN scenery installed or any leftover sceneries in your community folder 🙂 Please report back after you've checked, if you still have the issue, thanks 🙂

Heya 🙂 Could you please show me the settings page of your iniManager and while you are there press the Scan Now button again to see if that fixes the issue? 🙂

Heya 🙂 Thanks for pointing this out, I´ll put it on the list for the next patch to fix 🙂

Not planned currently due to performance reasons.

SU12 as in Sim Update 12 😄 Should be around Mid March.

From where is this retro livery? From the iniManager or from some 3rd party?

Heya! Nope, 3.02 was just fixing a small mistake we did in 3.01 🙂 This will be something for the next version.

No worries at all, take care 🙂

Heya! Sorry it took me so long to get back to you. I unfortunately can't reproduce this issue. Could you please try with an empty community folder (except LAX) and try again? Thanks 🙂

Heya 🙂 Super sorry that it took me so long to get back to you 😕 Good news is I can replicate this issue! I'll put it on our internal list for fixes in a future patch, thanks for reporting ^-^

Heya! Can you tell me which taxiway you are trying to take when this invisible wall introduces itself?

Sorry the turn around on this was a bit longer. I just completed a rather laggy arrival into KLAX from KDEN; my poor laptop was fighting hard at your settings 😄 Unfortunately I'm afraid I was not able to reproduce the issue even with the same settings 😞 Do the jetway eventually load in when you are at the airport for a prolonged amount of time by chance?

I actually don't think it makes a difference. The TOD marker should always be there; looks like this: (white hockey stick between SMASH and SALYY) Did you have a discontinuity in your flightplan by chance?

Can confirm this is fixed in the next update coming (hopefully) with SU12 🙂