All Activity

I was able to find information corroborating your statement here within the Safety Airbus Website as I agree with this being the case as it's something I've been told before, what I had logged was regarding Deselecting SLS, I still am working on keyboard clarity when addressing multiple issues in one post; https://safetyfirst.airbus.com/lets-use-xls/?airbus-iframe=true&airbus-post=2048

Did you already start your engines before pushback?

GlassOut fixed the ini pop-out clustering. This is going to replace the std MSFS pop-out.

I think the brake temperature is behaving quite realistically in the current version (1.26). It is quite normal to have a BRAKES HOT ECAM after landing/parking. It's a heavy aircraft and those brakes have to absorb a lot of energy, which will eventually turn into heat. It could well take 5-10 minutes after landing before they reach their highest temperature. Also make sure you use the correct technique when braking: You should avoid multiple brake applications and instead prefer one smooth brake application to bring the speed down.

Hi, First of all, the A350 does not have a FINAL, APP NAV or FINAL APP modes. Please do not implement these. Unlike in the older Airbuses, FLS is installed by default in the A350 and it is used for RNP approaches with LNAV/VNAV and LNAV minimas. It can also create an "ILS-like" indication for some LOC and VOR approaches. As Adrian said, when you press the DESELECT SLS button, it should give you the FLS indication so that you can fly an RNP approach with LNAV/VNAV or LNAV minima. Now it seems to give you the vertical guidance of the APP DES mode, which is only meant for the RNP AR approaches. In the current version, it looks like the FLS is only available for those RNP approach procedures, which do not have a LPV SBAS approach associated with them. This is how it looks like at the moment. This approach (EDDH RNP 23) has LPV, LNAV/VNAV and LNAV approaches in the same procedure. The default is LPV (flown with SLS). When you press the DESELECT SLS button, it brings up the vertical guidance of the APP DES mode (in the screenshot). This is the FLS indication (the double diamonds) you should get after pressing the DESELECT SLS button:

I've seen it requested elsewhere but the focus of replies has been relating to liveries being added... For those that want to paint their own (for themselves or a VA that won't be covered by an "official" paint), we're kionda stuck at the moment as the "paintkits" available on flightsim.to don't match the 2024 version of the aircraft. Can we please get a paintkit to allow people to bring more to the party with this aircraft, even if it's just PSDs with the wireframe (something for Blender would be appreciated however!).

Logged for the team

Logged for the team

Should be an option if implemented. Even on modern aircraft like the Airbus most US operators display all temperatures in Celsius except the cabin temp which is usually shown in Fahrenheit.

I think that regardless of whether you import the waypoints including SIDs/STARs or without that, when you import waypoints into the INS from the PFB, that the last waypoint loaded should always be the destination airport and not the final waypoint in the flight plan. Once you hit that waypoint there is still valuable information to be gained from the distance and time to the destination that are displayed, and I am quite certain that all crews of L1011s fitted with INSes would have done the same. You can do it yourself manually, of course, but then that defeats the purpose of using the autoimport.

Everything is working fine with GSX until it comes time to push. When the operator asks to release break the plane run into the terminal. I usually pump the parking break until it stops. When it happens in the beginning of the push it's certain it will happend at the end, when I pause the sim and restart coault. At GSX they say it's from IniBuild side!

SimBrief fuel imports still seem to be resulting in a displayed 400 lb imbalance. See attached screenshots. The SimBrief OFP has a total fuel amount of 120.0k lbs which is shown in the PFD. However, once loaded, the fuel totalizer only shows 119.6k lbs, and when I add up the fuel shown on the individual tank gauges, I only see a little over 116k lbs of fuel on board.

See attached screenshot. This was after running unattended at cruise for nearly 4 hours with all crossfeeds open and all pumps on. I am not using the PFD fuel balance helper (which also appears to not be working correctly, but that's a topic for a different post). In my screenshot I've turned all pumps off but the tank 3 and 2R pumps to even out first the small imbalance in 2R and then I will try to burn tank 3 down.

I'll bring this up to the team if there is any update

Hi, the landing telemetry simply takes the vertical speed sim variable at the moment of touchdown - IAS, TAS, and G/S have no impact on the recorded vertical speed. Secondly, it should be expected that you will have a higher landing rate at high density altitudes. Because you are moving faster over the ground, you will also need to descend at a higher V/S in order to maintain the same geometric descent. Best, Steven

I'll look into this as well as pass it along to the team, thanks.

Feedback regarding the Brakes and Heating Behavior has been passed along to the team.

Out of curiosity, we're exploring some possible culprits - but the next time you load your sim could you check your console and search "it will use" and send us the screenshot of any console entries? Like this? Also can you specify if you frequently get crashes/freezes or not?

cheers!

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.