All Activity

I didn t have time to run engines,so I have not autosave

I can confirm the iniManager makes absolutely no difference - im suspecting this is a MSFS2024 online services / connection issue. Its completely random .... It happens during climb out, sometimes during cruise. Temporary connectivity issues while using wireless internet might be the culprit. @IniSteve can you try recreate this, perhaps the team can try purposely disrupt their internet connection while flying the aircraft, see if they can reproduce this. The joys of online gaming! I cant begin to describe how much of my time I have wasted trying to troubleshoot this issue - could you please at least give this a try and report back... im begging you @iniBuilds!

Thanks. This is logged and will be fixed in a future update.

Can't speak on behalf of other devs, but we did not find a solution that wouldn't compromise another function, so we chose to let the user have full control over their setup.

Thanks. Do you happen to have an Autosave from before the crash?

If i am being honest. I don't think this is an Inibuilds issue. I actually think this is on Navigraphs end. I am having the same issues with the PMDG aircraft where the navdata is not updating. I actually have to log out of Navigraph in the airplanes and then sign back in and then everything is updated. It's weird. I never had that issue until the last AIRAC update over New Years.

Between iniBuilds, FSL, and Fenix, only FSL has it tied to a key bind in the sim. How come only one dev does it? It's kind of inconvenient to need a 3rd party app to program one function to my hardware when everything else can be bound in the sim. Thanks.

Ini manager

WSSS airport simbrief WSSSLGAV Flightplan,navigraph airac 2601 aircraft A340 EIS 1 Passenger version 1.07 Simulator FS2024 specs 11700K,RAM 32GB,AMD 6900XT

You profile was co-located and active on a piracy server which is against our rules, so we've suspended your participation in the discord. Despite that, you can still receive support for legitimately owned products via the direct support portal.

Getting back on topic, @Diegolas__Are you able to provide a brief example of the last interaction you had wiht the aircraft pre-crash and do you happen to have an autosave from before then?

I didn't know that could be reported like that. I'm coming to the forum, firstly because I want to, since I'm a customer and that's what forums are supposed to be for. If it bothers you, I couldn't care less. And yes, I flew with it in 2020 without problems; my problem is with the 20204, and with your nonsense, you didn't even bother to ask which simulator it happened in. You're the one who's not contributing anything with that stupid comment. I ask that you don't reply to any future posts I might write.

Appreciate the assist here but please let's keep this topic and forum on the whole a civil place. It's 100% fair to be frustrated anytime this happens and no one should assume every user is keeping up to date with the findings from these events. And yes, an autosave and any debug console information that can be provided will assist greatly in finding out if this is a repeatable crash or a one-off caused by a memory error in the sim.

It's an LVAR (a "local variable" that you can use to disable/enable different functions) There is no key binding in the sim for pedal disc but you can use a 3rd party control program (FSUIPC, SPAD, MobiFlight, etc...) to assign functions using the above variable. We will look into if we can create a native solution in the future.

And yet you've failed to provide any debug or troubleshooting information to help iniBuilds sort the issue. Many people, myself included are flying the A350 just fine, including long-haul flights 9-12+ hours so, if you're experiencing issues with this plane still, then it's likely something on your end - either your hardware or another addon interacting with MSFS and causing a WASM crash. Maybe try to provide some relevant data to iniBuilds, and maybe even provide an autosave and perhaps they can reproduce and fix your issue before you come to the forums and whine that it's not working for you without providing any meaningful, helpful, or constructive information.

Hello IniSteven my user name is daddysgirl123

What is that? Doesn't look like a key binding in the sim.

Hi Kanye, what is your discord profile name?

Hi. It should be this LVAR - `L:INI_TILLER_DISC`

afaik the EDW A359 are equipped with the new "long winglets". 😉 so maybe is it possible to correct it from your side, that the textures appear on the long winglets as it is irl? 🙂 Thanks!

I will pass this on to the team. Thanks

Ah, interesting update. I don't believe that to be the case but this also means there me be a spike in the weather refresh that is causing this to happen. Are you able to do a 8-9 hour flight over the weekend or in a manner where you can actively monitor and quickly respond to the sim to see if this occurs again? (I know what Im asking so no stress if you can 😉 )

Hi. Looking into this it seems the wrong winglet type is coded in the livery config file. I will forward this tot he team for correction into the master livery file but if you don't want to wait you can copy the following file here - [YOUR INIMANAGER FOLDER]\inibuilds-aircraft-a350-900-edw-ihc\Config\Edelweiss\ **note: IHF will be the other livery folder This should restore the "short winglets" Alternatively, you can just delete the config file and set all the options manually in the OIS. We'll consider adding them, but it will depend on painter availability in between other projects. LiveryConfig.cfg

Thanks for the explanation. Quick clarification: I’m not using the default MSFS Live Weather—I’m using Active Sky exclusively. Does the SAT spike/live-weather bug you mentioned still apply when weather is injected by Active Sky?

Could you guys possibly incorporate a key binding for the pedal disc button for the Airbuses? I have the IIDB steering tiller and I'm able to bind the pedal disc button with the FSL Airbus using the "Toggle Water Rudder" binding. Thanks.