A330-200 / A330-300 load with completely empty interior (no cockpit, no cabin) since SU6 — BelugaXL and all other aircraft unaffected

Using the template below will greatly help the team reproduce the issue and ease the process of fixing it. Before posting, search for an existing report. If you are not sure it’s a bug, please first report in User Support Hub.

ISSUE DESCRIPTION

Since Sim Update 6 (1.8.14.0), both the default A330-200 and A330-300 load with the exterior model only. The interior is completely missing — no cockpit, no cabin. Moving the camera inside shows an empty shell.

The aircraft worked normally before SU6. Immediately after the update I initially experienced CTDs/freezes when selecting the A330; it now loads, but entirely hollow.

FREQUENCY OF ISSUE

100% reproducible, every session, both variants

REPRODUCTION STEPS

  1. Start a Free Flight with the A330-200 or A330-300, default livery, any airport.

  2. The aircraft loads with the exterior only; any interior view shows an empty fuselage.

    YOUR SETTINGS

I play exclusively via GeForce NOW (Microsoft Store entitlement). This makes it a clean-room case:

  • No Community folder / no mods possible (Marketplace-only environment)

  • Every GFN session is a fresh instance with all content re-streamed, so local cache corruption is excluded by design

  • Reproduced across multiple sessions on different days

    MEDIA

Can’t replicate - running default A330-300, though on a locally installed instance of MSFS as opposed to GeForce now.

Also not seeing the missing/pink textures on the exterior model that I see in your screenshots.

Thanks for testing. To clarify: I don’t expect this to reproduce on a
standard PC install. My environment is GeForce NOW — fresh cloud instance
every session, no Community folder, Marketplace-only, content re-streamed
each time. The issue is 100% reproducible there across days, on both A330
variants, default livery, while the BelugaXL (same flight deck) and all
other aircraft load fine.

Since SU6 moved some standard-package files into the base installation,
an inconsistency in the cloud-side image or delivery path would produce
exactly this and would be invisible on regular PC installs. There are
also current reports of SU6 asset/LOD issues affecting specific default
aircraft on some platforms but not others.

If any other GeForce NOW (or cloud) users could test the A330-200/300,
that would help isolate this. Thanks.

Thank you for this report. We’ve moved your topic into the User Support Hub.

The Bug Reporting Hub is for posting suspected or confirmed bugs that other users are able to reproduce without duplicating an existing bug report.

Using the template or providing all the relevant information about your bug and sim setup is required in order to provide valuable information, feedback, and replication steps to our test team.

If you are not sure if your issue is a bug or need further input from the community, please use the User Support Hub category. If the community can replicate your issue, first search the Bug category to see if there’s an existing topic. If it already exists, contribute to that report. Duplicate bug reports will be closed.

If you believe it is a new report and no duplicate exists, then create a new bug topic using the provided topic template.

All issues caused by or involving third-party addons/mods should be reported to the third-party developer. Assure that no addons/mods are used when reporting issues in Bug Reports.

This article may be some help:
https://forums.flightsimulator.com/t/how-to-fix-graphical-artifacts-and-pink-texture-issue/592523/1

A330-200/-300 empty interior on GeForce NOW after SU6 — RESOLVED

I wanted to post an update because I finally managed to resolve the A330 issue I had been experiencing on Microsoft Flight Simulator 2024 via GeForce NOW.

My original symptoms after SU6 were:

  • A330-200 and A330-300 loading with the exterior model but no cockpit or cabin at all

  • sometimes CTDs/freezes when loading the aircraft

  • the 707 also frequently crashing while loading

  • in one test, the 707 loaded with pink/pixelated missing textures

  • other aircraft, including the A320neo V2, A300, A310 and BelugaXL, continued to work correctly

Because I use GeForce NOW exclusively, I have no Community folder, no access to local MSFS files, AppData, caches or logs.

The turning point: TouchingCloud

The first major breakthrough was disabling/uninstalling TouchingCloud – Your Wingmen / Air-to-Air Refueling Companion.

This was suggested because there are reports of it conflicting with the 707.

Immediately after removing it, I noticed something beyond the 707 issue: MSFS performance improved dramatically. The UI became much faster and more responsive.

However, the problem was not completely solved. The 707 could now load, but at one point it appeared with heavily corrupted/pink textures, while the A330 was still problematic.

What finally fixed everything

I then removed everything that I had manually set as “Installed” in My Library, leaving Marketplace content to be streamed instead.

After doing this and starting a fresh GeForce NOW session:

  • A330-200 works normally

  • A330-300 works normally

  • cockpit and cabin are fully present

  • 707 works normally

  • the texture corruption is gone

  • performance is significantly better

  • I can still use hundreds of Marketplace liveries without problems

So the number of liveries itself was clearly not the issue.

My current conclusion

The problem appears to have been caused by a Marketplace package / dependency / VFS conflict involving installed content, rather than by a broken A330 build on GeForce NOW.

The removal of the TouchingCloud add-on was the key first step because it immediately improved performance and partially changed the 707 behaviour. Removing all remaining manually installed Marketplace content then completely resolved both the A330 and 707 problems.

I cannot identify which additional installed package was responsible for the A330 issue because I removed them all at once, so this is not a fully isolated root-cause test.

My practical rule from now on when using MSFS 2024 through GeForce NOW is:

Keep Marketplace content streamed whenever possible, and only install an add-on locally in the GFN session when there is a specific reason to do so.

If problems start after installing something, I would now look at Marketplace package conflicts before assuming the aircraft itself or the GeForce NOW datacenter is broken.

Hopefully this helps someone else running MSFS 2024 on GeForce NOW who encounters missing cockpits, pink textures, CTDs or unexplained performance degradation.