All Activity

Hello, I don't own the scenery personally as it's by Fly X Simulations so any sort of support would best be aimed through their email alongside in here: flyxsim@gmail.com You can email them as well for more direct support. Thank you for understanding.

I'll pass this along to our team, thank you.

There is a bug with the Noise Cancelling feature, if it's turned on the cockpit switches don't make any sounds, which I don't think should be happening :) Also on a side note, it would be nice if it could be activated through a clickspot in the cockpit and not in the EFB settings, it could be faster this way. 2026-07-26 17-15-10.mp4

Hi, ill ask our team about this and see what i find

Hi, On occasion for some users the first load will result in an initial WASM Crash, not sure why but for some users this happens and then never again, some users never get it at startup. If you continue to have issues please follow the thread format at the top of the thread as any out of place messages are subject to deletion. Let us know if you continue to have problems and we'd be more than happy to help. Thank you.

Nothing as of yet but the team are aware of the issue. Thank you.

We have in the past few months as users have been able to submit WASM Crash logs to our Master Thread for their corresponding aircrafts and as such we've been able to ingest, investigate, and mitigate if not out right eliminate WASM issues where we can. Over this time period crash reports have gone down in volume in regards to those that post on our forums at least; and we remain committed to stomping out these issues for our users. Thank you all for understanding

I will have to ask for a refun.... first flight... first try... 70$

Any news on that issue, Inibuilds? We would really appreciate if the plane got back in the state it was advertised and we bought it as such - and if we won´t have to wait weeks and month for it to happen. Thanks again and have a nice sunday.

Disgusting, they should release a fix as soon as they know about it, not wait till the A380 releases, we are paying customers with a product that does not work, consumer protection would have a field day.

Have you made any significant progress?

We are always working towards a solution for both issues, everyone's feedback in here doesn't go unheard. Thank you all.

yeah, im pretty sure he mentioned it in the one with fselite. Im not 100 on that tho. it could have been wishful hearing.

Hi, Can you please attach reference so that I can send to the team, thank you.

See this was something I suspected and I wasn't to sure on it so I didn't want to commit to saying that. Next time I will just stick with my gut lol. I appreciate this confirmation :)

You can try clearing the scenery index here Steps to Clear Scenery Indexes Press the Windows Key + R to open the Run dialog box. Type %localappdata% and press Enter. Navigate to the folder path for MSFS 2024: Packages\Microsoft.FlightSimulator\LocalCache\SceneryIndexes (or Microsoft Limitless\LocalCache\SceneryIndexes depending on your specific installation). Select all files inside the SceneryIndexes folder and delete them (leave the main folder itself intact). Launch Microsoft Flight Simulator 2024 again. Let me know if this helps, thank you.

Hi, We usually post openings on social media and on occasion in the discord, you can see listings here

As with most companies it's closed internal testing and is not open to application as far as we know. Just be weary, you can come off as only wanting to for early access.

Yes, I am. When I fly it again I'll try to remember to do that.

for more context, I did an uninstall and reinstall of the airport and started on the 28R runway. I thought that fixed it as I taxied around where took the above pics. I did a flight into ORD shortly after and landed on 27C and the floaters were there again on that side of the airport. I have to think there is some other FSDT or Asobo files causing this that didn't delete properly? Is there a way to check? Asobo says disabled as does FSDT in their installed.

Uneven taxiway surface between K3 and K2. Can this be fixed please bin like this since release. I know it has bin reported and not sure why this is still not fixed yet

Same for me also

Hey- I wanted to see if there was anywhere I could sign up to be a beta Tester for the A380/any future releases? Thanks

You dont see Rnp in youre FMS since a RNP approach is a rnav based approach. RNP is basicly a rnav approach but with extra performance monitoring and alerting. RNP allows for much tighter, scalable accuracy (down to 0.1 NM or less). So that is why there are no "RNP" on youre arrival page, for the rest im unknown on how good the planes flies therse approaches.

The autopilot doesnt follow the glideslope if the localiser isnt caputured yet. So you will need loc* or loc for the gs to be capsured. other wise it will just stay level.