All Activity

Hi, we'll take a look into this, I'm gonna pre-emptively assume (and I might be wrong so don't quote me just yet) but regarding the autosave I think it only saves anything that has an associate LVAR with it as well as the flightplan data. BTV and Checklist are digital items and the sunvisors just might not be included. I'll ask about this too. Thank you.

I’ve noticed since the everlasting bugs and crashes, the autosave system in the 350s have been extremely useful. However, the majority of the time i need them, I’ve found they save the most necessary bits - time, place, area, avionics etc - but don’t save some other stuff that are just nice not to have to go through and update, those being BTV distance, checklists, sun visor positions, among some random other stuff that’s less important, I think, as I can’t remember them. Additionally, I (may) have found a bug and not sure if it’s actually present in the real aircraft or not: During a flight, the time displayed across multiple screens isn’t always correct (at least not to local time. The UTC time (with seconds, found in the F-PLN section, then the fix info drop-down -> time) is right, but the time displayed across other areas of the ac is out of sync, so I’m not sure if that’s a bug, caused by stopping/starting the sim manually, or something else. Many thanks

Three of my last four flights into KLAX ended with a crash to desktop using MSFS 2024 and KLAX v1.0.2. Everything seems to be going fine then there are three sound cutouts and then the sim crashes. No messages or warnings or anything like that.

To Reproduce: Video (unlisted) is time stamped with moment. WASM crash occurred when inserting the approach data for runway, then STAR, when pressing "Insert" to flightplan: https://www.youtube.com/live/MpOLidphPJA?si=cUIdGiFJrb0lKD2Z&t=5340 Aircraft - A300-600R Premium (Passenger) Simulator: MSFS 2024 1.7.27.0 (latest SU5) Version: 1.1.9 MSFS2024 Marketplace (Installed not Streamed) Navdata: Navigraph Route - EDDF/25C N0446F350 ANEK3F ANEKI Y163 HERBI Y164 MOPAN DCT LUTIX DCT BENOT DCT NEMOS DCT NINTU DCT MEBAK DCT REPSI DCT LERGA DCT MINSO DCT NARAK DCT AGN DCT PIPOR L866 PPN/N0442F370 N976 NEA L14 ADINO DCT ELVAR DCT ALAGU DCT USALU USAL9C LPFR/10 EDDFLPFR_PDF_1779642878.9e825734.pdf Livery - Lufthansa (retro) D-AIAN WASM Error: Unable to retrieve. When I returned to the simulator to retrieve it, it looks like it was already purged. Specs: AMD Ryzen 7 9800X3D / RTX5080 / 64GB Autosave File: Not available for this aircraft.

As I said, it's been noted and passed along...

AGAIN, didn't ask if I need to hear it or not, Airbus or not, I asked why we don't hear them so to make them heard, VOR/ADF/ILS/MARKER.. Those are fitted in the aircrafts, they're there for a reason, please make them work.. If iniBuilds don't want make the audio monitoring work in their fleet, just say so and don't make excuses.

You do not need to listen to the tones as an airbus pilot wether automatically or manually tuned, to be clear. Even in a Cessna with a modern GPS the navaids are automatically identified and pilots do not legally need to listen to the tones when this occurs. I have noted that the tones are not audible through the radio so I will pass that along.

Hello @iniBuilds , I am amazed on what work you have done with the A340, alongside with the updates you push out to improve the A340, such a phenomenal aircraft! I am currently flying this on Xbox and would highly request to add in the Terrain Radar for both EIS1 and EIS2 displays. Also you should also considering to implement the terrain radar to other aircraft, such as the Inibulids A330, A320neo, A321LR, and A350. Just like in the old MSFS2020 days the terrain radar used to work on the Inibuilds A320neo and would be very useful for all your great Airbus aircraft you guys developed. Please reach me out back if you any further updates regarding if you guys are able to push an update for this for all your Airbus aircraft and also the A340. Thank you.

I have already reported this issue to support. Appeared after 1.2.6 update.

I get this message too when taxiing after landing

Dear iniBuilds Development Team, I am writing to report a recurring telemetry calculation issue in the A350 flight report system, specifically when operating at high-altitude airports (e.g., SEQM, elevation ~7,900ft). The Discrepancy: Upon touchdown, the aircraft’s landing performance was physically smooth, with the Radio Altimeter (RA) providing precise and steady closure rates (the 5-4-3-2-1 callouts were perfectly paced, confirming a stable and gentle flare). However, the generated in-built landing report recorded an inflated Sink Rate (-263.60 ft/min) and G-force (1.13G), which contradicts both the smooth tactile feedback and the reliable RA data. Root Cause Analysis: After reviewing the logs, I have identified the probable logic error in your touchdown telemetry script: Velocity Input Confusion: The report recorded a touchdown speed of 142.27 KTS, which is equivalent to the Indicated Airspeed (IAS) at this altitude, rather than the actual Ground Speed (GS) / True Airspeed (TAS) of 166 KTS. Mathematical Amplification: It appears your vertical acceleration/velocity calculation formula uses horizontal speed as a vector component (or denominator). By using the incorrect IAS instead of GS, the formula essentially "compressed" the denominator, leading to an artificial inflation of the Vertical Speed and G-force results. Cross-system Dependency: The internal sound engine and HUD/PFD display mapping seem to be triggered by this corrupted VS value, resulting in an unnaturally "hard" landing sound and visual data that does not reflect the actual physical state of the aircraft. Recommendation: Please ensure the WASM module’s landing telemetry logic is updated to utilize Ground Speed (GS) or True Airspeed (TAS) for all kinematic calculations, instead of relying on uncorrected IAS, especially for high-altitude operations. Thank you for your hard work on this aircraft. I hope this technical breakdown helps in optimizing the flight report system. Best regards,

Yeah, that’s what I do too, but it’s nicer to use the physical keyboard like we can do with the MFD… Especially when the EFB itself says there shouldn’t normally be any conflict...

hi again found the problem ! it s a small scenery near KLAX thats causing interference. have nice flights

Yeah have noticed this. I just use the onscreen keyboard on the OIS that you can pop up to avoid any conflicts.

Hello! I recently purchased the A350 and honestly, I’m really happy with it so far! The aircraft is absolutely beautiful and has always been a dream aircraft for me, so I can already tell I’m going to have a great time flying it. After a few hours of testing, everything seems to work perfectly from what I can see, except for the keyboard input on the OIS / EFB, which does not properly lock the keyboard inputs. For example, with some keys I can still move my joystick assignment or deploy the flaps while typing things into the OIS, even when the message “Aircraft control disabled when inputting text with physical keyboard” is displayed. I searched online and through the Discord, but from what I found it either seems to be a rare issue or people have the opposite problem of being stuck with the keyboard, or something that may have been fixed in previous updates? I already restarted the game after fully configuring the aircraft, but the issue is still there. I’d also prefer not to unbind some keyboard keys since I use them during flight... Thank you very much in advance for your help, and apologies if the solution is actually simple and I somehow missed it...

I noticed that the fuel consumption seems to be very accelerated and inaccurate. Has there been a fix yet for this? Also i noticed that once i turn on one engine. It kind of automatically turns on the other engine. the heat blur turns on for the engine thats is not turned on at all. Not sure if its a visual glitch or it could be contributing to the fuel burn. I also noticed that it only acts this way on the a330 300 not 200

As soon as you have activated 4x in the EFB, you can increase the sim rate further using the assigned keys for sim rate.

??? I aware of that.. but that's for auto tune in case of the VORs but when we manually tune?.. Mind you, the A300 auto tunes too. That's not what I'm asking... in case you don't read properly, or you're making your own suggestions out of others posts? I will write again, can we pilots hear the tones, NOT the avionics, US PILOTS, when pulling the corresponding knob on the ACP, which are there for that reason.. ?

Hi, we did make changes to the runways for the FS2024 version of the scenery and were able to get FSLTL to use the full length of the runway. BATC seemed to be dependent on other factors, but beyond our ability to control. Best, Steven

Hi, in the A340 and A350 there is no need under normal operation to listen to nav radio morse tones in order to identify them. They are automatically identified by the aircraft - when the LS or VOR identifier is shown on the screen, the navaid has been tuned and identified by the avionics.

Hi Mikai, regarding the GPWS sounds, there are actually several different soundsets that are used depending on the airline and specific equipment installed. We have even heard a boeing style "TWENTY-FIVE hundred" call in some recordings. The current recording are the highest quality and cleanest samples we have from an actual aircraft, so for now they are what we will stick with. Best, Steven

I have the sound code open on my laptop right now, funny enough. I’m working on a mod to fix this.

Any news on this? i miss the 108

hi i have the same trouble with lax enhanced scenery.its impossible to take off or land. so much stutters. Among other runway 25 and taxiways too. i ve uninstall the scenery and clean the catch. but no result. no problem with others sceneries. Any help appreciate Thanks in advance Pierre

3 Minutes and 30 seconds THE 2000 .... 500