srce

Have you authenticated navigraph with a new code under options > 3rd party? This apparently needs to be done again for new releases. Before doing that, only the Standard map is available on the ENROUTE page. Afterwards, all work for me on the ground.

I can see all options in the menu. Perhaps you should attach a screenshot.

The text in red at the top is the clue... Go back outside (ctrl-c) and click on the engine covers and pitot covers.

In the take-off performance calculator in the OIS, can the minimum climb gradient be calculated and displayed?

Additional situations were requested on the Dev Stream, so here's a few ideas: - Fuel leak - Icing causing pitot tube / static port blockage giving inaccurate speed / altitude - Radome damage from hail in cumulonimbus - damaging weather radar / pitot tubes / comms antennas etc - Lightning causing electrical system failure - Jammed flaps - Runaway trim - Landing gear failure - Hydraulics failure - For bird strike, could optionally have visible cockpit windscreen damage, making it harder to land visually - For depressurization, model oxygen masks in cabin - add a few audible screams when they come down 🙂 - When there's an engine fire, shouldn't we see loss of thrust / EGT change and maybe some smoke? - Green laser attack on final (turn the screen green) - Volcanic ash, when in specific parts of the world - Emergency evacuation - with slides! - Passenger taking more than 100ml of liquid on the flight 🤔 - Something dull relating to baggage having to be unloaded as PAX don't turn up And rather than just being manually triggered, would be nice if they could either be random, according to user-defined conditions (E.g failure just before V1 so have to consider a rejected take-off), or for something like icing based on weather conditions.

The load on generators don't seem to vary as other generators are switched off. E.g. GEN 1B is always at 40%, regardless of whether 1A is ON or OFF. Shouldn't the load increase when 1A is OFF? Similarly, switching the APU on doesn't change it: v1.0.6 / MSFS 2024 SU1

What should we expect when using GPS Jamming situation? I got a few 'pull up' audible warnings, but there didn't seem to be any impact on IRS deviation (under Position > IRS) or GNSS accuracy (under Position > GNSS).

Another problem is that the pax numbers and cargo weights don't go down as GSX is deboarding.

I'm not sure you should press both. If you only press Load with GSX, then you will see the passenger numbers / GWCG rise as the passengers board. If you press both, it immediately jumps to final numbers. It seems ZFWCG will stay at 0% until refueling is requested, then a value appears (It seems that refueling isn't always automatically requested - not sure why.) Note, the ZFW/FUEL LOAD entries on the Loadsheet OIS page will remain empty - so you need to get them from the OFP or AOC/ACARS loadsheet for the INIT FMS page. The manual doesn't mention the Load with GSX button. edit: Although having said that, I tried it again a couple of times, and sometimes the number of pax starts increasing - then goes back to 1/367 and stays there, even though GSX eventually says boarding complete. edit: Looks like GSX has had a few more updates over the weekend, so will give that a try.

No oil? Try refilling in OIS maintenance page.

Do you have the APU running?

Yep, saw that earlier with v1.0.5 after only using GSX to load.

Post a screenshot maybe? What do the engine indicators show?

Looks fixed in 1.0.5, for me.

See:

Are you using GSX? It might have broken your gear on push back.

In the pic below, the MORA appears to be inconsistent between the captain's and f/o's NSs. Captain's side has range of 320nm, and is showing 1000, whereas F/O's range is 40nm and showing 1800. Shouldn't the captain's side show 1800 as well? edit: Oops - should be in 2024 forum.

ANF not drawn correctly on F/O's ND. Ok on Captain's side. - v1.0.4 on '24 SU1.

Sounds like a WASM crash: See for what to report.

Any idea why FMA is BRK MED rather than BTV, when I have a BTV EXIT point set? v1.0.4 on '24 SU1

The closest airports page doesn't always display correctly. v1.0.4 in '24 SU1. Was seeing the same in both FMS 1 and FMS 2. Can't clarify under what conditions it stops working though, unfortunately.

Aircraft: A350--1000 Simulator: FS2024 SU1 Navdata Method: NAVIGRAPH WASM Error: Avionics route broadcast in.... 0xc0000005 Specs: CPU i9 13900KS, GPU 4090 and RAM 64GB At the gate, bat and ext pwr on, load from simbrief, start gsx boarding, extinguish overhead lights and do fire test, then systems freeze.

v1.0.3 / SU1 / wasm cache cleared - buttons freezing after trying to run fire test. Has happened a couple of times.

Tuning the radios from the 2024 EFB doesn't always work either.

I notice there's also a tyres damaged message. On the OIS under maintainance you can replace tyres, but that doesn't help.