UpUpandAway

I can confirm this. Cruising at 14000, 13000 is shown unless you climb just a few feet for the thousands drum to tick over to 14.

I've suffered a CTD on two flights in a row, where the pause at TOD feature was active and the sim had to wait until I'd finished my dinner. After about 45 minutes, I get a DXGI_ERROR_INVALID_CALL (0x887a0001) FS20 crash with my 32GB of RAM almost completely used (usually around 14GB). Today I'm trying the flight for the 3rd time and I've let it stop at TOD again. I noticed that the sim isn't actually paused, the time on the SD keeps running. At the same time, the GPU shoots up at least 5% above what it was. The previous two crashes also showed that the sim time is still running, because it was night in both cases, having started the flight in the afternoon. I think what is happening, is that the GPU (3080ti on DX12) is running out of memory and it ends up using system/shared memory until the system runs out. Now that I've resumed the flight, all appears to be working normally again. Has anyone else noticed this? Didn't the previous implementation of pause at TOD actually pause the sim, i.e. stop time?

I see HB-IHC and -IHF in the iniManager now, thank you! 😃

Would it be possible to update the iniManager livery for Edelweiss to a Swiss registration instead of an Austrian one? For example, HB-IHF which was recently delivered and will start operations next week.

With everything set up for landing at FYWH (elevation 5641'), the LDG ELEVN shows 0 on the SD: As shown in the screenshot, the cabin happily descends below landing elevation. Could this be fixed?

I had this WASM crash when I selected the departure runway in the FMGCS. To reproduce: Load at gate Power on aircraft (Battery, GPU) Import Simbrief OFP using OIS Load company flight plan Select runway (RWY 19 in this case, using DEPARTURE button) Systems freeze Information Aircraft: A350-900 Simulator: FS20 Navdata Method: NAVIGRAPH OFP: Attached Specs: i7-9700K, RTX 3080ti, 32GB RAM WASM: Exception c0000005 in gauge MFD in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-900/panel/inibuilds-A350.wasm FACTEDDM_PDF_1740865389.pdf

Please allow me to bump this topic: Magnetic variation in FACT is 26°W. Syncing the EFB T/O performance loads the magnetic runway heading and the true wind from the METAR. Is the discrepancy dealt with by the EFB, or should I be adding variation to the WIND field? All academic I suppose, but having the variation applied automatically would be cool.

Thanks @richboy2307, after seeing your other post about the LVARs in-sim, I found the same ones you tried, but couldn't get them to work with the AAO demo version. I'll stick to the trigger and moving slightly for the time being. I think the external animation may be out of sync though, the ECAM only indicates REV (along with the associated sound change) when the lever datum reaches the yellow horizontal line just above the R.

Hi @richboy2307, Thanks for the suggestion, I was doing a similar thing with "hold throttle reverse", but I'm assuming in your IDLE REV screenshot where the levers are still at idle, the doors don't actually deploy. I have to move the levers forward quite a bit to enter the yellow reverse zone before the reversers actually deploy. Or I pull them back into the "button" zone and "reduce throttle" repeat to max reverse. When I pull them back to idle in reverse axis mode, they deactivate immediately, so if I want to keep idle reverse, I need to stop above idle somewhere. Is there an LVAR perhaps for idle reverse and max reverse? I could set up the flip lever to set idle reverse, pull back into the button zone to set full reverse and back to idle reverse when the "button" is released.

On a flight from ENSB to ENGM, and the ETAs aren't working: The time is 1541Z, and that is also the time shown at ATSOT on the MCDU, although it is over 400NM behind me. It's supposed to be showing the time I reached ATSOT, but it's showing the present time and keeps updating. The ETA for NORVA. the next waypoint shown on the ND is over an hour away (ETA 1647), though only 120NM away (GS 431kt, should be about 17 minutes). Correct ETA would be 1704. Could this be investigated please?

I turned on the brake fans pulling onto stand and within 3 minutes, the brakes had cooled from over 300°C to ambient 15°C. Could the cooling be applied a little more realistically?

Is there a way to toggle idle reverse, like in the real thing where lifting the triggers does just that? I've set my Bravo up so the (Airbus) reverse levers toggle "hold reverse thrust" - I can then either pull them back ("decrease throttle") which opens the reversers and applies full power, or I can, somewhat unrealistically, move the axes forward and regulate the reverse thrust using the normal axes. The problem is, just lifting the levers keeps the engines in forward idle. In most cases, I just want idle reverse. If this isn't possible in MSFS, I'd happily buy AAO or similar if there's an LVAR for it.

To further illustrate the point, see comparison below, all aircraft roughly pointing at the VOR (CTV 115.70): Fenix A320 iniBuilds A310 iniBuilds A300: The A300 RMI is off by what appears to be the airport's magnetic variation (26°W), despite the CDI on the ND actually being centered on a valid radial.

I've already used Hervé's file, no change unfortunately. Default airport. In my first screenshot, I'm 17.5 nautical miles from the station flying directly towards the airport (visually and according to FMC). Using basic trigonometry, that 26° offset on the RMI would put the station 8.5 NM away from the airport! I'm suspecting it is related to the aircraft dealing with variation or station declination, as I've experienced other variation related issues affecting the FMS: The above issue was fixed for 1.1.1, the VOR bearing/declination issue remains.

Should I report this variation anomaly elsewhere, or is it an acknowledged bug?