LukeFF

With the engine covers on, you can still hear the engines spinning, as if they are open to the wind.

That's up to Microsoft.

Default LOWI confirmed disabled, too.

There are a lot of issues with snow coverage along the perimeter roads and along the approach path, plus I spotted a buffalo wandering the ground as well. 🙂

Hi, I've only tested it with the GE freighter. It seems to be an issue only when the rudder trim is zeroed out (or perhaps it's just really faint).

When it's done.

Take your complaints to MS. They are the ones responsible for updating these aircraft, not iniBuilds.

It appears the rudder trim reset button has no sound right now.

To add: this also seems to extend to the takeoff performance page too.

Tonight I flew a flight where I set the clock back about 12 hours. After importing my flight plan I checked the A300's EFB (not the MSFS one), and the QNH was given as 30.00. However, when I requested a weather report at the same time from the IDC, it said the altimeter was 30.13 (the actual value in the real world at the time of the flight). So,it looks like the A300 EFB is reading the historical QNH but the IDC (and BATC for that matter) is showing the current QNH.

Been noted weeks ago by inii that they can't do anything with a fix from Microsoft.

When using the default "autopilot on" command, the associated switch doesn't make a sound. However, it will make a clicking sound if one uses the mouse cursor to turn it on.

I had an issue tonight where, even though I was tuned into ILS 23L at KIND, the glideslope and localizer never showed up on my PFD, and so I had to make a visual landing approach. I triple-checked I had it tuned correctly, which I did. The scenery is the one from DDT.

Appreciate the help again, thank you. 🙂 I did ultimately find what I needed last night by enabling the behavior debug mode and hovering my mouse cursor over the switch I wanted LVARs for.

I tried that in 2024 but I couldn't get it to work right. Did anything change with dev mode or am I just missing a step?

Perfect, thanks!

Thanks, yes, that did it.

In the A310, there are hand mics on each side of the cockpit, as well as some sort of thick binder that's probably an FCOM in the middle of the pedestal. In the A300 cockpit those items are missing. Would be nice to have them there.

I am having some trouble getting the RUN and STOP buttons to work correctly in AAO for the captain's clock. The code, per the mobiflght page is this: 3 (>L:INIDR_CHRONO_GMT_STATUS) 4 (>L:INIDR_CHRONO_GMT_STATUS) But neither of those work. In AAO, I have them set up like this, but neither respond: 3 (>L:INIDR_CHRONO_GMT_STATUS, Number) 4 (>L:INIDR_CHRONO_GMT_STATUS, Number)

@richboy2307, I didn't see an LVAR in that file for the pedal disconnect button. Could you please tell me what it is?

Thanks! Will check it out.

That's up to Microsoft

I tried programming some scripts today for the exterior light switches but couldn't get them to work. Is there a list of LVARs that can be used with Axis and Ohs for these switches? The mobiflight page just has an incomplete list of LVARs right now.

The little field just to the west of Tivoli Stadium has trees growing through it.