All Activity

Hi, I will push this issue to the team, thank you.

Darn, I will push this issue to the team, I am sorry for the inconvenience at this time. If it is any consolation, YBBN is one of the less intensive sceneries as all of the configuration options are low impact, but I do understand the frustration of not being able to fully control the product you paid for.

I even uninstalled and then reinstalled iniManager. No change - still no configuration options.

Hi @IniJamir, Did the fix for this issue get pushed in the 1.2.1 version for XBOX?

Hi, Sorry this is still happening, I'll push this to the team and see what I can find out, sorry for the delay.

Thank you for the suggestions. I deleted the contents of the "Cache" folder in the iniManager folder in Roaming (there wasn't one in Local) and then relaunched iniManager, which resulted in no change. Then I deleted those same contents again and uninstalled and then reinstalled the scenery and then relaunched iniManager... No change - there are still no configuration options in the scenery page. Any other suggestions?

Hi, No need to worry, we've sent the update to Microsoft. Thank you 🙂

The update has been sent to Microsoft

I'll pass this along to the team.

Hi, Sorry you are having this issue, please try clearing your cache folders found in %appdata% > Local and Roaming. You can also try uninstalling and reinstalling the scenery. Hopefully this helps.

Dear all, Thank you once again for updates to the A340 and A350. I would like to know what is going on with the state of these aircraft. Between them, there have been over 30 updates and yet they still contain so many basic errors, the vast majority of which have been reported since the initial release. We are not talking obscure areas, but rather basic functionality. For example, the F-PLN page, and various PERF pages of the FMS, and corresponding ND symbology on both aircraft are so full of bugs and errors that it seems they have simply have not been tested properly. On every single flight one can find a large array of these bugs and errors. I won't go into details of them here as it is not the place to do in the forums, I have made these reports elsewhere as discussed below. This post is merely an enquiry into what is going on in general terms. Personally, I have given hours and hours of my own free time providing detailed bug reports, and I know that some other users have done the same. It is extremely disheartening to see very little done with these reports and really makes one question why bother making them. The answer, of course, being that we are happy to give up our free time to try and help improve the product for the benefit of all users. However, it is deeply discouraging to repeatedly report issues and see no fruition. That these issues were not noticed in the first place also makes one wonder what is going on with testing. Great hype is made of new features being added to the aircraft, for example, the HUD for the A350. However to focus in on this feature, it is totally unusable, again due to it being full of so many errors for such a small feature. It just seems like it is always one step forward and two steps back, even a small feature like the HUD cannot be implemented without it being so full of bugs that will need addressing in the future, in addition to the large amount that remain unfixed since release. It just feels like the list is becoming insurmountable. Surely, if you will forgive the suggestion, thoroughly testing new features so they aren't released in this state and adding to the already long list of bugs would be a better way forward. I have often found in my professional life that getting tasks done properly the first time, even if it takes a little time, always saves time and produces better results in the long run. There are also blindingly obvious regressions with each update. For example, the latest (1.2.1) update on the A350, pressing Ctrl to type in the MCDU using our physical keyboards results in the views changing when numbers are typed. It seems the exclusion for MSFS controls when using the physical keyboard to type has disappeared. How is this not noticed in testing, and how is an update allowed to release with such an obvious regressions? The above paragraphs are not meant to be in any way exhaustive in their description of the issues present, as I have previously stated, this is not the place for that. They are merely offered to exemplify the situation regarding these aircraft. These aircraft are not inexpensive products, they are marketed and priced in a manner that demands a higher standard than what is offered and it would be great to get to the bottom of why this is the case. I sincerely hope that this post is not taken the wrong way. It is not meant to be in any way 'bashing' or hateful, or even angry, and I truly appreciate all iniBuilds do for the flight sim community, particularly with the vast amount of high quality scenery that is released. I would simply be interested to hear an explanation of what is going on, why there are still so many issues, whether there is anything I can do to help, etc. It is meant like all my bug reports, merely to try and get these aircraft up the standard that they deserve, after all, there is so much potential in them. As always, many thanks for the team's continued hard work in all that they do. I truly mean this. I must reiterate that despite what may come across as a negative post, it is not intended in any way to criticise or be hateful towards anybody. Its purpose, like all my posts on these forums, is purely to help make iniBuilds products be as good as they possibly can be. Many thanks again, dectenor2

I'll also add that we should be able to remove static aircraft. I have AIG and BATC for that, so it's just needless clutter for me.

@BoeingSpeedbird Has 1.2.1 been pushed out to the Xbox Marketplace yet though?

Yea the broken engine fan blades need to be a hot fix like yesterday, hard to understand why this is not an urgent matter and has been allowed to linger for over a month....

Update here 1.2.1, but spinning fan blades still broken. Disappointed.

Still not sorted on latest update 1.2.1

Still broken :c

[UPDATE] I don't know why but i've set a custom path, and choose the custom path instead of the basic FS24 community folder and it works now update succesfull

Hello guys I was unable to update from 1.2.0 to 1.2.1 so i tried to uninstall/reinstall Now i'm strucked...I can't install the 24 version, when click install and choose the path nothing happen I've tried to restart inimanager 2.5.0 as administrator => NOK Curiously it works fine for the 20 version... Anyone else ? Any solution for this bug ?

As the title says, not sure if the testers can repo

Noticed this aswell. There's no taxiway markings whatsoever next to the runway 22 threshold

One other user confirms the same: https://discord.com/channels/535246634448191499/1466882084818653368/1466901105182118100

I agree, it took them months to fix the a350 tonality even after commenting on a post a while back and receiving no response, if i'm going to be completley honest the only way to get a response is on their discord, that is the only way. The forums have to be the absolute worst, no response or a fragmented response. And with that ^ since they use cockpit videos for reference for whatever when it comes to the flight model, I find it hilarious they got it wrong in the first place. And the staff would say "it's company options" or that is how it is supposed to sound when cockpit videos which inibuilds uses tells you everything you need to know, like what? And when the tonality was changed to the proper way for both aircraft, hundred above and minimum was not changed, which is for one silly. And the same with retard. My a340 90-80 callouts still don't work to... No clue with the ai use by the other guy in expressing frustration you don't need ai for that. One's actual words is far better, but inibuilds is known for quantity rather than quality, and this better damn change with the a380. Which means a better flight model (no levitating off the runway bull, and this flight model mod doesn't work because everything is controlled by WASM 😂. The biggest sore with ini flight models at the moment is how bad they feel on takeoff, the pitch is first off sensitive and the pitch rotation is wrong I can't even do a 10 degrees back pressure cause I will tailstrike, so great job inibuilds "our data is so amazing!!! yet you use cockpit videos and can't pick up on sidestick handling on takeoff. I expect better system simulation as well, you have the capabilities, aside from that hope this gets fixed

Did an uninstall of the manager using 'Revo Uninstaller' then clean install then set sim paths. Open the manager. Same results. Will do an uninstall of KLAX and reinstall.

Funny thing is it was working just fine last night (Latest version).