Marketplace package name: STING S4, TL3000 and FSR500
Context: flight
Bug description:
For all MSFS 2020 airplanes installed in MSFS 2024, streaming or direct in community not matter what you set in the registration Vpainting this ugly and really annoying Yellow BOLD with outlined black text registration keeps showing.
As you can see in the picture below, the registration is coming YELLOW despite the Vpainting being configured as font_color=black.
Guys, my most of customers are incredible annoyed by this, it damages the looks of the airplane, problems with registrations of airplanes have been reported by me and other 3rd party developers since November last year.
Repro steps:
Just load any MSFS 2020 aircraft, to repeat just load the Sting S4 FSReborn livery.
I know it’s a workaround, but have you considered keeping your own registration.html/css/js under a suitable VFS path containing your company name or some other suitable namespace, and pointing your VLivery entries at that?
Remember we cannot upload custom msfs 2020 packages exclusively for msfs 2024.
So if i do what you suggest, I have to do it for Microsoft marketplace 2020, which means in msfs 2024 you end up putting html, js and css code of registration that is done for msfs 2020.
Simply put, i could end up with a worse scenario where with future SUs versions coherent totally breaks.
This is a core bug imo, and needs addressing. Same thing with the pilots views from external for msfs 2020 aircraft.
Customers are really tired of these issues because they are visually irritating, this morning again I woke with customers raising tickets and complaints about missing pilots (even on SU1) and the registration issues.
This is driving customers away, if my customers disappears, so does the percentage fees we provide to Microsoft from our sales.
We needs stuff corrected to ensure the promised compatibility for msfs 2020 planes is there, I am sure Asobo and others can sense my frustration lately on my recent posts, but is not like I didn’t reported these issues with plenty of time and they are affecting now us as 3rd party vendors, badly… and all i see is stuff will remain as they are until SU2 or maybe SU3… meanwhile I am on the front line taking the hits from people complaining about the same things over and over again.
We know the frustration and are actively working on resolving these bugs - but as you know there are still issues in the sim that have higher priority than wrong font/color or missing pilots.
I realize this would be additional work, but would it be possible for you to have a page on your website that lists the issues found in 2024 with each of your aircraft, clearly stating that these are BC issues that are being worked on by Asobo? Maybe that would help moving the front line towards us rather than you.
I understand the registration issue affects all of your aircraft - what about the missing pilots?
Yes pilots is also affecting all MSFS 2020 airplanes, it is weird because for me is working and yet as you can see from my discord post this morning, this customer is having the issue:
I asked if he was on SU1 and he is, it seems the problem kicks when the users are trying to set a different gender for the pilots (my default is female pilot, male co-pilot).
Thanks for your understanding, and we 3rd party devs also understand there are many things your team is working on, however please consider the vast amount of developers reporting problems with their current 2020 airplanes running inside MSFS 2024, which were assigned automatically to customers by Microsoft and people just encounter problems with them from day one.
The effect is, it creates an overall impression that MSFS 2024 is totally broken (when we all know this is not the case), but these users just want to load the products they own and have a good experience, they don’t understand it is a MSFS 2020 airplane, they don’t understand what is backwards compatible mode, they just want to fly, and the reality is they encounter quirks after quirks for the last 4 months that remain unresolved.
It is important people can see MSFS 2024 for the strong platforms it is, it is also important to understand MSFS 2024 native products will take a while to become to realisation and hit the market, most 3rd party developers are just trying to convert their stuff and struggling with the SDK because, well it is massively different. Unless you were a 1st party developer like Inibuilds, and others who been working with 2024 for a long time behind the scenes, well you are pretty much clueless about how to do a MSFS 2024 airplane at this point.
This means the majority of the products currently being used by the customer base are either the airplanes shipped with MSFS 2024 or MSFS 2020 airplanes ported from MSFS 2020, which are plagued with these visual difficulties that is irritating them. This is causing rejection towards MSFS 2024, because they can load MSFS 2020 and have things working.
There is not that much that needs to be fixed on this regards to bring back the overall impression that MSFS 2024 is way more advanced than its predecessor, you only need to address 3 things really:
Liveries selections and glitches for MSFS 2020 airplanes.
Registration glitches for MSFS 2020 airplanes.
Pilots views for MSFS 2020 airplanes.
With just those 3, people will start feeling much more at ease, this coming from feedback from all our support tickets and questions we receive.
I appreciate a lot your offer to be put in the front line like this, but I don’t think it would be fair for the platform and the team behind you. I don’t want to be that guy that is just pointing fingers at Asobo / Microsoft for problems, specially when I know how hard everyone is working.
This would create a more toxic environment in the community, and my objective is to avoid that at all cost, instead I prefer posting the bugs here, and see that you guys have marked the reports as “logged”, “in progress” and eventually “fixed”.
When users ask me about these issues, I just point them at the bug reports, where it shows not only progress and indication you guys are actually working the issues, but also how you guys interact with us, how friendly you guys are and how hard you guys are working.
This presents a better picture for the community who in return becomes more appreciative of all the team at Microsoft and Asobo for their efforts, they also can see how much FSReborn and Asobo interact in a proactive and positive manner, which once again helps the entire community to become more appreciative of the work we both do for the platform and how much we love this hobby.
Thanks for taking the time to answer me, if you could perhaps in your next schedule meetings bring to the attention to the team those 3 key points and see if they could be prioritised in order to provide a better stability point of view for the customer base it would be great.
I know these things will not make it now for SU1, as a software engineer I understand totally the life cycle of things, I am trying with my feedback (which as you know me know, is always honest, polite and as positive as possible) to help you guys understand how are things here in the front line, it is an attempt to ensure the future of MSFS 2024 becomes much more brighter and get people very happy by the time SU2 hits the public.
As you know liveries ordering (for 2020 aircraft) is already resolved on our end - but the fix needs to make it to the user (not in SU1 RC so either in SU2 or earlier if an SU1 Patch has to be published).
I believe there is still an issue with how these are presented in the selector - needs to be fixed for SU2 or earlier.
Registration: we need to investigate - hopefully it can be fixed for SU2 or earlier.
Pilots view: it was supposed to be improved or even fixed, but maybe we missed something here (such as the user changing the gender as you described!) - we will investigate and report back.
As as side note, we fully agree with your analysis of the situation and are trying to move forward on several fronts (stability, performance and - of course - backwards compatibility).
Hi @EPellissier the blue looks okey to me, and users have the option to set a “clear canopy” in the FSReborn EFB, which is located in the left side pocket. So this is not a big deal.
I would recommend you to Change the canopy to clear version (Left pocket, EFB–>Settings), so you can debug the pilots easier.
Yes the registration is not using the correct font vs MSFS 2020… note this is the same case in the interior registrations.
So, to answer Eric’s question, although I’m sure he already knows, it looks like you’re relying on the default font. IOW, you did not provide a font with your plane.
Sadly, if they chose to change default fonts between sims, well, they shot themselves in the foot attempting to make MSFS2020 compatible with 2024. Hopefully that’s not the case, and, if they wanted to add a new/more fonts, they did that on top of using the same default font. It’s not completely undoable, but, it forces yet another MSFS2020 compatibility rule to use the old default font unless otherwise specified for 2020 planes code to run for 2020 planes. Of course, I’m not saying anything new here.
To answer your question, who knows? It might be ignoring scale and bold because a font isn’t specified, and the css needs to be fixed on their end. There are a lot of reasons that could be causing what’s going on.
