Longitude Tail Number Issue (still unresolved)

Are you using Developer Mode or made changes in it?

No

Have you disabled/removed all your mods and addons? If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the Community Support section.

Yes

Which aircraft are you reporting an issue about? (Please also add the proper tag for it)

Longitude

Which aircraft version are you experiencing this issue on? (You can find this listed in the Content Manager under the Aircraft Name)

Most Current Version

Brief description of the issue:

The same issue from last year where the tail number doesn’t show on the longitude is still happening. The only solution I found on the forums was “it’s fixed”. That’s not a solution for the rest of us that don’t have it fixed so I’m creating a new thread for this bug until it’s actually fixed for everyone.

Provide Screenshot(s)/video(s) of the issue encountered:

Detailed steps to reproduce the issue encountered:

No steps needed. The issue is always there.

Build Version # when you first started experiencing this issue:

Unknown

Hi @SeppsX ,
Could you either describe the problem or post a link to the previous post that says its fixed? - Thanks!

Personal Comments and Observations

Is this a custom livery?

Here is the topic that has been closed as “fixed-on-live”:

I fly the Longitude with a custom livery, and am seeing my chosen tail number.

No, as seen in the screenshot, that is the default livery. As said in the post, my community content folder is empty.

Thank you, yes this is the post, its the first one that comes up when I search Longitude missing tail number.

Thank you for the reply, but that does not help my situation at all. I am aware the problem is fixed for a lot of people hence why the first post was marked “fixed”. However I wanted to create this topic for the rest of us who still have this bug.

Hi, of course, the description of the problem can be found in text box with the title “Brief description of the issue” and the screenshot provided adequately shows what the problem is. The other person that replied to you linked the correct post about this problem being resolved last year if you want to look at that as well, thank you!

TBM930 also

TBM has his own report that is bug-logged: