ual763

It looks like you’ve got dual sceneries overlapping, my guy. Remove the default EGLL in the content manager/marketplace. Maybe that will fix your issue.

I am getting the same issue. I believe it is related to the issue I reported here: Anyways, for some reason the 2024 version of the airport has like 90% of the runway/taxiway surfaces covered in this hideous repeating concrete texture. The surfaces covered in this particular texture noticeably degrade the friction model (e.g. slow the aircraft down as you pointed out). This same texture is causing the winter issues I posted about above. INI, please fix this for 2024!! It is clearly a bug.

https://i.postimg.cc/C1qxt2FG/Content-Screenshot-2025-02-18-12-28-34-43.png

Not sure why the rest of my post is missing. Anyways.... Hello, this is a bug for the 2024 version, however there was no designated 2024 support area for this product in the forums so I am posting it here. Anyways, during the winter, with a slight dusting of snow on the ground, the snow textures on the runways/taxiways look absolutely horrible at MKE. Would it be possible to improve these, or if not to just remove them altogether? It really ruins the experience at MKE in the winter, unfortunately.

Hello

Glad you got it figured out

Just to be clear, you clicked the prompt on the INIT page?

I see in your latest photo, the FMC is also prompting you to select the ALIGN IRS prompt.

Well, the PRIMARY GPS Lost message will be on there naturally as an advisory after it being lost before power was applied. It is an advisory and is to be canceled. The AFCS displays will be blank until the pitch trims switches are on and the pitch trim switches won’t stay on until the IRS is aligned. So, this all leads to you not selecting the ALIGN IRS prompt on the INIT-A page of the FMS/CDU.

This would be tremendously helpful in lower light conditions, especially since there is not an ECAM indication for armed spoilers

I think that maybe your FCU lighting switch is turned off. Maybe you have a key bind for lighting that is conflicting. Turn the FCU lighting switch under the AFCS panel clockwise and let us know if this fixes your issue.

Well, your ECAM does not say IRS IN ALIGN, are you sure you actually hit the ALIGN IRS prompt in the CDU?

This version of the FCOM manual also does not mention the panel integral lighting - just the integrated lighting in windows and pb switches. So the question still remains for any who fly this in real life, does the knob also control the integral panel (backlighting) on the FCU?

Yes, it clearly should control display windows and the green bars on the FCU switches (not sure if this is simulated by INI or not). What is not clear from any of the manuals, is if this also controls the integrated panel lighting. One manual just says “integral lighting”, but then another manual (this one) defines integral lighting as the windows and the switch light bars. A real life A300 pilot would have to comment on if this knob also controls the panel integral lighting.

I see your FCU integral lights are also off. In v1.03, the fcu windows are dimmable along with the integral lighting, as per the real plane. Can you try turning the FCU lighting know up amd let us know if the screens come on for you?

Hmmm, I have a stair option on mine in top right of this menu. The only thing I can think of is that maybe the pax version doesn’t have this and that it is only an option in the freighter as that is what I was flying. Are you able to call the default MSFS stairs?

There is an option for left or right stairs in the EFB under the ground connections tab

When the vertical mode of the FMA changes to ALT automatically when capturing an altitude in LVL/CH (thereby illuminating the ALT HLD switch), the ALT HLD switch plays it’s audio sequence even though the user never presses it.

To go along with his, the APU doesn’t produce any noise in external view on ground. However, when switching the APU bleed switch to on, then you can hear APU on ground.

The A300 uses the default MSFS navdata. So, it should happen automatically when you update MSFS. However, while not officially supported, if you have Navigraph, you can always use Navigraph to update MSFS data through their installer, although it may cause a few issues at some places.

I’m fairly positive this may have been an issue with metar sources, not INI. For example, MSFS wasn’t pulling up METARS a few hours ago, either. Maybe it is now.

Yes, but for this particular bug report I’m referring to the fixed red line marking. Sorry, I could have been more clear in my wording, but didn’t have my FCOM available at the time.

In v1.03, the orange Maximum N1 marking moves with the THR LIMIT pointer, rather than being fixed where it should be. Please see attached photos for reference.

Seems that v1.03 got rid of one phantom orange bug but added another. Please see attached photo for reference.