Eddie

Try to force-reset the calibration by toggling the "reverse on axis" a few times. Exit back to the main menu. Select another plane, then A330 again. Load in and set the calibration now. For a full guide (including troubleshooting) on calibration, it's available here:

Hi, Apologies for the radio-silence on this. Seems I missed the post entirely. Nonetheless, a paint-kit is in the works! Due to how things work in FS24, the aircraft is now modular which presents a different way of creating said paintkits, but again, we are working on it. Unfortunately no ETA at the moment. Hoping for sooner than later 🙂 Thank you

Hello, Have you ensured all assists have been turned off and that your turbulence setting is on low(preferably)/medium? That is the usual suspect if any conflicting keybinds aren't the problem.

Hi there, Try following this and installing it again afterwards. Please let me know the result Thank you 🙂

Hi there, @Stormfish Can you confirm whether or not you're still having this issue? @Wasp056 I've hopped in the P2F now, tested both GE & RR and can't seem to reproduce the issue. (See video & image below). May I ask when you installed the simulator? If it was within the first few days, I strongly recommend a complete re-install due to corrupt data in the first few days. You can also try force re-download of the aircraft(s) that are having this issue; How to - force a re-download of streamed packages? - FAQs - iniBuilds Forum Microsoft Flight Simulator 2024 2024.12.22 - 16.45.38.01.mp4

I cannot at this time no. That is something that will be shared closer to release 🙂

Both variants come in the same package with the inclusion of the -900 ULR as a free addition later down the line.

Hello, Please note the trailer is not indicative of the final product. Things are subject to change. But regardless, the team is aware of this. Thank you for the report nonetheless! 🙂

Hi there, The update released earlier today. You can read more here and watch our newest trailer linked in that post as well It will do all the things it should to be "VATSIM-worthy" and more. Pricing information will come closer to release. As mentioned in our dev-post; the planned release is within Q1 2025. 🙂 And we're super excited to get it into everyone's hands soon too!

Hi there, Please refer to this;

Hi Carlos, Yes that is what it means; you'll be able to use this scenery for both simulators. Thank you

Hi there, If any of you are using BeyondATC, please make sure you update to the latest version available and try again. We identified some kind of conflict with the version prior to the latest and it seems it has been resolved now on BATC's end. Thank you 🙂

Hi, The A220 is still a Synaptic Simulations project. This question is better for them regardless of our contribution. Thank you 🙂

Hi, That link is still valid, I suspect your account may be barred from re-joining or this may be some kind of technical issue. Please reach out to direct support, provide your Discord ID and explain the problem there too; https://inibuilds.com/pages/contact Thank you

Hello, Please check again if the option is now available. Let me know if not. Thank you

Hi again @Hifi flyer! Just checking in. Did you end up getting this resolved? 🙂

Hello, Please make sure the iniManager is closed and then try deleting the appdata folder for it: X:\Users\username\AppData\Roaming\iniManager Launch the iniManager in administrator mode after that. If that still doesn't resolve it, it may be worth a complete reinstall. If THAT doesn't solve it, please reach out to direct support https://inibuilds.com/pages/contact Thank you 🙂

Hi, please contact direct support if the issue remains. https://inibuilds.com/pages/contact

- Removed previous thread for showing personal information - Hi, Have you tried again later? Still same issue? If so; please try re-installing the application entirely. Let me know if that resolves it!

Hi there, Please try clearing your scenery indexes; To do that locate your folder by following the path below. (MS Store) \AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SceneryIndexes (Steam) \AppData\Roaming\Microsoft Flight Simulator\SceneryIndexes Then delete the contents inside but leave the folder intact. (The indexes will rebuild on next load of FS) This should solve the issue. Let me know if not.

Hi there, That is a question best suited for Noriega Designs. You can contact Mario over at https://mariosplanes.com/index.php/en/contact-en Thank you!

Clearing your scenery indexes: To do that locate your folder by following the path below. (MS Store) \AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SceneryIndexes (Steam) \AppData\Roaming\Microsoft Flight Simulator\SceneryIndexes Then delete the contents inside but leave the folder intact. (The indexes will rebuild on next load of FS) This should solve the issue.

Please ensure you have no assists enabled as well as the turbulence setting down to, preferably, medium/low/off. Let me know if this resolves the issue 🙂

Hello, Due to the nature of how the aircraft is structured for MSFS2024, older liveries will not work unless specifically converted to the new format. We have updated most of our in-house liveries on the iniManager for this reason. However, older liveries should work with the compatible version that we pushed for MSFS2024. Are you using compatible or premium edition? Thank you

I understand the frustration but we really can't put any "pressure" on MS. Their schedule is entirely up to them depending on what they want to release or update, and now with FS24 brought into the loop, it's almost double the work-load (presumably) of said schedule. I wish we could hit the publish button ourselves but unfortunately it isn't that easy. I am still hopeful it's sooner than later. Thank you