Systems

I have had multiple crashes in the last weeks on around a third of my flights, with versions .4, .5 and .6. They look like wasm crashes (nothing responsive anymore), but with wasm crashes, the plane normally remains controllable with primary flight controls, in this case the flight controls are also frozen. The crashes happen out of nowhere, while not doing anything to the plane. Aircraft: EIS 2 + Passenger, if i remember correctly the eis1 was also affected once. Liveries are multiple liveries from the ini manager, they are current. Simulator: FS2024 Navdata Method: NAVIGRAPH Specs: AMD Ryzen 5 5600X, 32gb of ram, RTX3060VR 16GB Aut…

Hello, when spawning the A340 (any variant) the plane spawns in floating (gear up) and with the WASM already crashed. I've tried deleting the WASM folder and reinstalling the plane entirely several times. I am on the latest SU 4 beta Below are some pictures:

This blue field can't be filled

Found a bug on the Autopilot panel, I am not able to switch Vertical Switch any higher than 200 ft Per min , then it scrolls automatically back to zero, It will however step climb when ALT is pushed in. Otherwise a fantastic aircraft

I find that the autothrottle takes too long to engage on takeoff. I set it to 250kts, and the speed climbs past 250kts to 280kts before it kicks in and drops back to 250kts.

Hi, I figured that various Vars regarding the MCDU (FMS) stay at 0 (zero) even when values are entered in the MCDU. The following are affected: (L:INI_V1, Number) (L:INI_V2, Number) (L:INI_VR, Number) (L:INI_FMS_MDA, Number) These Vars are needed for script writing and addons for the excellent A340-300! Could you confirm and maybe fix this? Thanks and keep up the good work!

Hello, Since v1.0.5, the addon is not usuable. i'm getting random WASM crash at every flight. I'm not the only one. We need an Hot Fix. Thank you.

Hello Inibuilds Team, I saw that none of the WASM crash issues were stated in the V1.0.6 Changelog. Did you have a look on the numerous wasm problems it has ? R/W change / Coordinates / DIR TO / SEC FPLN etc etc...

Hello ini Team, @Eddie, @iniSteven, I have no idea what you are doing. Please, tell us what is the version of the FMS you try to implement? With 1.02 you downgraded the IRS INIT to HONEYWELL P3. Now you implement an OFFSET version of HONEYWELL P4. Some of my reports are based on the assumption you do P3, but if it’s now P4… So, what is it now? left P3 / right P4

Hi, so the offset stuff seems to be buggy. Whatever wayoint I chose from the list either for start or end, it keeps selecting a completely different one. So as you can see, it randomly selected "LEGRO" although i chose "PIKIL". Same for the end. Ive tried to select for example JANJO and it keeps chosing between one of the coordinates...

I conducted a flight and had to select an alternate which is far away from the original destination. As a result the alternate fuel was 10.2t. In the MCDU however I was not able to enter that number. I would get the error "ENTRY OUT OF RANGE" despite the aircraft calculating 11t for the alternate.

I noticed that on the Engine ECAM Page the N2 Vibration for Engine 1 seems to have an incorrect value assigned. The value is shown correctly on the cruise page. This should be a minor task for a developer to fix.

Today I wanted to enter some along track waypoints for my etops entry points and encountered two issues: For one i could not enter them from the coorinate waypoints that I had imported, but had to enter it from the last non-oceanic waypoint. I tried to enter it as 47N015W/+93 an as 4715N/+93, which both was met with a message "invalid navaid". What worked is entering it from Etiki as Etiki/+353. It then was inserted distance whise at the correct place, but somehow the waypoint, in this case PD03, is laterally offset from the original track. This should definitely not happen with along track waypoints.

It is easy to repeat this error 1. Start a free flight game from a runway, and fly the aircraft off the ground. 2. Press ESC on the keyboard and select "Restart" 3. After the game restarted, the WASM crash occurred. Aircraft: A340 EIS 1 Passenger Simulator: FS2024 SU4 1.6.31.0 Navdata Method: MSFS OFP: No OFP free fly WASM Error: [inibuilds-A340.wasm] Error: Unable to open directory [inibuilds-A340.wasm] \work\autosaves\ WASM: Module vfs://inibuilds-aircraft-a340/SimObjects/Airplanes/inibuilds-a340/attachments/inibuilds/Function_A343_Interior/panel/inibuilds-A340.wasm is now dirty Specs: CPU i9 1…

So the scenario was simple. I had my oceanic entry point and i was pasting the coordinates and this happened.

When i spawn at the gate I can´t get in the plane. I tried the keyboard combinations but nothing works.

Hi everyone! I tried the EIS1 variant yesterday and today, but had issues. Everything was configured right in the MCDU and so on. Inflight, I couldn´t get my speed back to managed, don´t know why, had to land manually. Today I tried again and had a strange behavior before the flight even started. Look at the screenshot. Any ideas? The ICE2 variant is strangely completely fine and works as it should. Look at the EFIS. It responded, so I think WASM was running and the WASM module was running ok. (I looked it up) Edit: I downloaded the aircraft via the store and installed it on my drive. Now its working. May be an issue with streaming.

Hi - I'm noticing when I pop out the instruments, they are included in a single window, as opposed to each having its own window. Is there any way to adjust it so that they are in separate windows? Even if the CPT PFD + ND were grouped together, that would be great. Loving the plane so far. Thanks!

I don't understand why the MCDU don't load my flight. Simbrief is loaded.

After being accepted by OBBB I received the notification of current ATC unit. When I close it however, the current ATC unit is not displayed on the DCDU. I am on version 1.0.5. Shouldn't there be the text?: CURRENT ATC: OBBB BAHRAIN RDR

This will now be a longer post, as the F-PLN has many issues. Maybe I will do follow on post in future. 1. at LSK1R show only 5 dashes ----- and move 1 column right 2. removed 3. Line 1 is missing TIME 0000 4. LSK1R is missing the airport refference altitude rounded to tenth 5. for the leg length the unit NM does only appear at line 2 6. all dashes have to be large font 7. the color and size of the / is always defined by the following text or numbers (just a general remark) 8. LSK1L is missing the label for the SID name 9. The CA leg is indicated wrong. Already mentioned in the A350 topics. An CA leg is somehow a…

Are these approaches modelled in the A340? Cheers

EFB - MY FLIGHT - IMPORT FROM SIMBRIEF. ERROR: Instance was null. Any suggestions?

RJTT LDA22Y: MX22 is the hardcoded MAP of that approach. Now the systems displays several items wrong. 1. There is no RWY-Waypoint coded in the NAVDATABASE for that approach, because the MAP is prior the Runway. So DON'T display a RWY-Waypoint in the F-PLN !! 2. The blue track line has to start at MX22, because that's the MAP ! So the INTCPT Heading of 208° has to be drawn blue from MX22, resulting in a different INCTP position with the CF leg (178°) to UTIBO. 3. If the GA is not displayed, then there is just blank between MX22 and RWY. NO green line. 4. The WPT-name "INTCPT" has to be drawn green (also the diamond) on ND. 5. That is not rela…

FIX Info doesn't accept a WPT entry. It looks like it just accepts Airports. That's wrong!