LukeFF

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.

Thank you for this!

Alright, thanks. 👍

I noticed that some of the parked vehicles are the horrible, low-res ones from 2020 that don't even have fully rendered wheels. Certainly, we can do better than that. 🙂

Agreed - it's bizarre why these aren't already there.

Alright, this is what I got, @richboy2307. FPS were again pretty good en route, started dropping into the 30s in the Brussels area but remained relatively steady. It was when we started dropping into the 20s and then once again into the teens - all the way down to 12 - when we started our approach into Luton (screenshot attached). I attempted to remedy this by dropping my graphics detail down to the Medium preset, but that did very little. There's just something really bad about the terrain rendering in this part of the globe, because, again, I'm just running the autogen EGLL airport - not the ini EGLL one or the Asobo handcrafted one - and the only other 3rd party scenery I have enabled in this area is ini Stanstead. The handcrafted one from Asobo is turned off.

PW Freighter - when pushing the TO Config Test button, I often receive an "Oil Temp Low" message, even though the temps for both engines are in the green. In this case, it was for the left engine, which was at about 67 degrees, while the right-hand engine was about 80 degrees.

When Microsoft fixes it.

Yes, my system specs are: 9800X3D 64 GB RAM 4070 Ti Super EDDP scenery was Digital Design, not the default one. The only other London-area scenery I have enabled right now is the ini Stanstead one. EGLL AFAIK is the autogen one, not the one included by Asobo for the more expensive bundles. I will give this flight another try this weekend and see if the issue reproduces.

Flew tonight in the PW freighter, Leipzig to Luton (ini version). Flight started out just fine, no issues, FPS hovering about 60, TLOD 100. However, flying at FL340, the frame rates dropped, and dropped, and dropped so much that by the time we were on final approach to Luton we were down to 12(!!!) FPS. No point any more at that point to continue the flight, even with an autolanding, because once we landed I had no way to control where the plane was going. The only thing I can think of that would have contributed to the terrible FPS drop was opening and closing the default EFB, but other than that, nothing out of the ordinary.

PW freighter: the emergency exit lights switch is in the On position whenever starting a new flight.

Yes, you need to uninstall and then reinstall that app to fix the problem.

Next to the loudspeaker knob on both sides of the cockpit, there is a 3-position switch that controls the lighting of the console. Around the time the new radio stack was released, a bug was introduced where this light is now on by default. I'll try to take a screenshot later on. Regarding the heading knob, yes, it was my misunderstanding.

When requesting winds, the resulting output is still borked like it is/was in 2020