I just realized i did not got the 787 (i am premium/deluxe account)?

As in the topic written i just realized that i should have the 787 (Dreamliner) as a delxue/premium customer but for some unknown reasons there is no 787 in my hangar. What do i have to do to get it?

Have you downloaded the premium deluxe content in content manager / marketplace?

I dont remember but in content manager i could not find her. Afaik it has been installed automatically right at the start. But without the 787.
In my “Installed” List i could see her but i can find her in hangar.

UPDATE
And i cannot delete the other community 787 downloads. Why?

Is it possible that i cannot delete 3rd party sw ingame via content manager?

Can delete all according to 787 (inlcuding premium/deluxe content) and then reinstall it? My premium content wont be gone forever then right?

Community addons in the community folder can be removed by removing them from the community folder in file explorer (the sim must not be running)

Do you have any of the other premium deluxe content? Its not an individual download for the 787, its a whole pack containing all of the content.

Asobo related content for 787 is 6 files and round about 0,6GB. Guess the community content cause the problem. Can i delete premium content and get it back again?
All other premium/deluxe content is installed and available.

I think so, yes, but not something I’ve tried.

I found the 787 hidden in a folder named “Ryanair” which is community dlc.

And yes i think it should be no problem to delete and reinstall premium/deluxe content. But for some reasons i am not too sure :wink:

The 787 from Premium Deluxe will not be ‘hidden’ in a folder named Ryanair in your community folder. Built in content goes to the Official folder. If you purchased the premium deluxe version of the sim, you should be able to find that pack in the content manager in the sim (don’t look for individual planes, it’s the entire pack as one).

In my case its hidden. The third party dlc (Ryanair Livery) is the problem-. Dont know how the dev managed to do but he did.

Moved to #community-support:tech-support which is more appropriate