Systems

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!

The RJBB24R SOVRI1 Departure is a RNAV SID. In the NAVDATABASE the complete SID has a hardcoded RNP of 0.1 NM. The currently indicated 1.00 is wrong. So you need to read what is in the DB and dispaly it. Please fix that!

1. I expect a right turn at "500" and then to MUMSU - MIMIG - ... The DF leg between "500" and "MUMSU" is hardcoded as right turn in the NAVDATABASE....so you just need to drawwhat is coded. Please correct this ! RJBB24R - SOVRI1 2. You indicate the turn arrow in the F-PLN next to MUMSU. That's wrong! The Leg starts at "500" and the arrow indicate the pilot the turn direction he has to fly. So the arrow has to be displayed at 500 in the FPLN. Yes, the turn is coded in the DF leg and the F-PLN is representing that entry with the WPT MUMSU, but still the arrow has to be indicated next to 500 !! Bellow is a real world example (Yes, a modern Thales, but th…

The already selected RWY has to be green without selection arrow (line 5 in this case)

Hello, After trying V1.0.3/2 and 1.0.4, I can feel a difference of performance of the aircraft. the rate of climb and the overall performance of the 340 in the 1.0.3 were perfect and now in the 1.0.4 it's start to be overpowered at some points at low and heavy weight. At heavy weight the aircraft is still too easy to make lift off. Did you change the A/C performance from an update to an other ? Thank you for your consideration and your updates and futur updates and keep improving this beauty. Best Regards.

When you are below the profile in managed descent the autopilot should target 1000ft/min. Its currently averaging 200ft/min

Strange thing recently happening. Latest MSFS 2024 beta and lates A340 build. Every time I try to load up a flight with EIS1 I get CTD. It loads up fine with EIS2. Cleared WASM and reinstalled the plane. Only CTD with this plane. All other planes working just fine. Strange indeed. Any suggestions?

I do not want to make a long post, just checking if others having as well serious issues with FMS? Last 4-5 days I have tried several flights, deleting WASM folder, using the A340 downloaded and streamed as well, but for online flying the the plane is unusable, least on my PC. - giving a DIR tend to messup the entire flightplan - changing arrival procedure and arrival rwy, delets the remaining of the entire fligh plan - Importing Simbrief flight plan in the EFB gives an error message "instance null" All in all, as long i do not touch the FMS and using the initial flight plan it seems OK, as soon as I want to modify (ATC gives direct or chan…

If I’ve already downloaded the terrain data in the EFB, do I still need to download the terrain data again in the previous iniBuilds Manager?

WX not working in MCDU both SayintentionsAI and Beyond ATC