Roders

Thanks - might be worth mentioning that you have to reinstall the affected airports and then quit iniManager via the control panel. I now have my config options! Appreciate the help!

@IniJamir For me this is only affecting airports installed after the iniManager 2.5.0 update - airports I had installed prior to the update still have config options available to choose from.

Hi there, I can confirm this does not work on my end. Still no configuration options for any airports after trying all the suggested fixes. Best, Roderick.

Just to be clear which "WASM" problem are you talking about, as the term gets thrown around quite a bit? 1. Orange screens "WASM" crash 2. Aircraft freezing (no warning, plane veers off course and runs out of fuel/crash into ground)

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, I just resubmitted.

Hi There, I sent an order transfer request on the 16th of Jan, I have not recieved a notification that it was rejected nor any info at all from anyone at iniBuilds... The aircraft is not available for me to download in the iniManager. The automatic reply said it would take maximum 72 hours before approval/rejection.

Thanks for the response! Once my transfer request has been approved I’ll be using the iniManager version to test further. The only reason I mentioned this is because I’ve had no issues with the A350, although that was a few months ago in MSFS 2020. I know the underlying code is identical, but I do wonder whether differences in how the aircraft is packaged or how it interacts with the sim could play a role here. Initially I was suspecting some kind of internet-related issue. Even though my connection itself is very solid, I currently only have access to a wireless connection rather than wired Ethernet. Would it be possible for others in this thread to confirm whether they’re using a wired or wireless connection? @IniSteve would it be worth considering whether a very brief interruption in connectivity could trigger this issue? Something momentary. The freezes only seem to happen on long-haul flights, which is where the chance of a small wireless dropout is higher. Since this appears to be a sim communication issue, it doesn’t seem completely impossible. @iniBuilds I might be clutching at straws here, but it could be worth investigating. It might also help explain why only a small number of users seem to be affected if it correlates with those running the sim on wireless connections. Just a thought, happy to help test or gather more info if useful.

This is still happening to me with the latest 1.0.7 update. Im using default navdata and currently streaming the aircraft from the marketplace (I had same issues with the package downloaded) @iniBuilds is this a known issue? Its been over 3 months and still no official response as to whether this is being investigated. Is there any way this could be a marketplace issue? Is there anything inherently different about an aircraft downloaded from marketplace vs iniManager in the way that it loads or communicates with the sim? @Eddie I'm begging for a response here, or at lease some form of acknowledgement.

Thanks @richboy2307, ill reproduce the same steps over the weekend and report back. Appreciate the help on this!

Hi @richboy2307, Appreciate the help! Sorry about my rubbish attitude there, flightsim can be frustrating. I didnt have the nerve to try reproduce the error when I restarted the flight. Will spawn the aircraft in over the weekend when I have some time and try make the same inputs. For context I didnt modify the flightplan until descent - I had ILS 14 NEGRA 2A arrival preloaded before departing Mumbai and left eh FLPN overnight with auto S/C etc. The crash happened as soon as I tried to enter a waypoint after AMIKI. I selected the waypoint from the FPLN page in the MCDU and then entered TRA into the 'Next Waypoint' field, it then prompted me to chose between two TRA waypoints. I selected the correct one and then pressed insert, which is when the crash happened. I noticed the PFD and ND froze for a couple of seconds and the range selector knob didnt work before finally the screens went orange. I also noticed when using PLAN mode and cycling through the FPLN that after entering ILS 14 NEGRA 2A the MCDU drew a path straight from AMIKI to CI14 for runway 14, which was confusing as surely it should insert a discontinuity. There are AMIKI transitions for RWY 14 but they involve a series of turns and ZHxxx waypoints (you also have to go into VIAS to select it). I usually enter TRA manually as I noticed this is what most ZRH controllers give me whenever I fly in. Perhaps the lack of a 'discontinuity' confused the aircrafts VNAV calc when entering TRA as an intermediary waypoint. What I was expecting was AMIKI - TRA - [DISC] - CI14 but I think the aircraft was trying to solve for AMIKI - TRA - CI14. Unsure, ill see if I can reproduce. Best, Roderick.

Could be, although flying with default AIRAC is tricky on VATSIM. Im wondering if it has anything to do with streaming vs downloading.... Im eagerly waiting for the inistore release - something tells me MSFS marketplace download hosting is quite rubbish, might lead to issues. I was streaming the A340 up until eysterday when I downloaded it, first flight and I get the system freeze (different to WASM crash).

@iniBuilds this is getting a little ridiculous now. Details below. I changed approach to RWY 14 at LSZH (NEGRA 2A). The crash happened when I tried to enter the waypoint TRA after AMIKI. This is basic stuff iniBuilds - the fact that the aircraft cant handle this is a joke. Aircraft: A340 EIS 2 + Passenger Simulator: FS2024 SU4 Navdata Method: NAVIGRAPH OFP: VABBLSZH_PDF_1768099299.pdf WASM Error: "WASM: Error during FMGS_gauge_update execution. Error code : 0xc0000005" Specs: i7-9700K, RTX2080 and 32GB RAM. Autosave File: 1768124718.bin

Also you can’t convince me these are not bots - what are these “support” forums even for? You get better customer support when you call your bank 🤣

@iniBuilds sort this out man the customer neglect and automated responses are complete nonsense, paid 60 bucks for the sim equivalent of a paperweight - serves absolutely no purpose other than to look pretty … it’s unusable… Also @iniBuilds Pablo @iniBuilds Team the usual “please submit a WASM crash report” response is a complete waste of time, there at least a dozen reports submitted here on the forums within the last week and I can’t imagine how many tickets have been opened… this must be rage bait at this point - the same people have submitted multiple detailed accounts of their issues over the course of multiple months and this is the best “support” your team can muster up? Just give us an update - where are we at with these issues, how long until they are fixed… simple communication guys jeez, remember you charge money for this software

The A340 was an easy cash grab for ini - its clear the addon is heavily dependent on the default A330’s framework …. Don’t expect @iniBuilds to fix or improve anything when they can’t even sort the basics out - I can’t even get the thing to work without constant instrument freezes and WASM crashes, it’s been over 3 month since release! I provided them with endless crash reports and detailed forum posts… absolute silence… @iniBuilds now might be a good time to let us know what is going on in the office? Having a quick break are we… seems your customers are doing your jobs for you making the necessary bug reports and cross referencing systems logic with the real aircraft… but you still can’t be bothered to follow up - add some courtesy to your New Year’s resolution list !

Same for me - iniBuilds please refund, otherwise Ill have to force a chargeback and file a dispute with my credit card company… I have been unable to use this addon properly since I bought it over 3 months ago… just because we are flight simmers doesn’t mean you can treat us like absolute trash! No normal consumer would stand for this

Yeah I am getting the same in SU3 - if the same is happening in SU4 im not sure what I can do to fix this. I started another thread and attached my .bin file.

Sytems freeze randomly, could be 30 mins into the flight, or 10 hours. When the issue happens the waypoint diamonds on the ND are frozen but the actual flight path moves as the aircraft continues flying. Additionally, the chrono clock freezes along with most other flight instruments, strangely the DME values are still updating. Aircraft: A340-300 1.0.1 Simulator: FS2024 SU3 Navdata Method: NAVIGRAPH OFP/routing: PDF attached, routing: LIV1C VASUR UZ21 ITROL UQ25 RUDAS UT941 IBRIT UM998 ONRON/N0462F380 UM998 TIDOU/N0454F400 UM998 CSO UM2 CIRTA DCT ETOIL DCT OMEDA DCT TORTU DCT ERTEV DCT CANNE Z651 KELIP KELIP3G Specs: i7-9700K, RTX 2080, 32GB RAM Autosave File: Bin file attached @iniBuilds Are you really seeing improvements in SU4? Could you please provide some progress on the dev side - does your team have any insight for us? I have not been able to use this aircraft for almost 3 weeks now - just really struggling to make sense of the purchase if I am completely honest. Best, Roderick. FAORLSZH_PDF_1760830137.pdf 1760867410.bin

Just had the same thing in SU3, so frustrating man. @iniBuilds Do you guys have any hints as to what this might be? Just a bit of info would be great, with the recent update and general praise for the aircraft a lot of us feel abandoned here. Console errors/warnings near the time of the system freeze are below, I have also attached a .bin file. 1760867410.bin

I get the same in SU3, exactly as you describe but my log shows WASM issues… try with navdata off for now… I can’t see this being fixed for a few months

Any confirmation that this has been seen or logged would be appreciated - I spent many hours testing and filling out the report as requested. You’d think ini were paying me a salary for the amount of time I have spent on this. I appreciate you are all very busy but some acknowledgement would be great.

Yeah my WASM crashes were happening c. 30-60 mins after departure, so a bit earlier, but also only with latest Navigraph AIRAC. Might be worth changing the title of this topic to better reflect the Navdata issue. Hoepfully ini see this. Because its a market place release, update could take weeks or even months - might have to shelf this aircraft as flying on Vatsim without updated AIRAC data is a bit tricky. Shame as the A343 is by far my favourite AC out there.

@iniBuilds I just tested the exact same flight with default sim navdata and there were no issues - to double check I ended the flight and restarted it with updated Navigraph Airac data and the BAM, the same WASM errors and issues. I confirmd in another thread that other users with this problem are experiencing the same behavior. I am renaming the title of this thread accordingly.

I am having the same issue, however I realised that the only flight I was able to complete was my first flight when I forgot to download updated Airac. @Mantock @Freitas138 @pappa_razzi @Jure are all of you flying with Navigraph AIRAC installed? Try with default sim... I dont have time to check this myself as I already spent my entire weekend trying to sort this out (great use of my time btw thanks iniBuilds).