Dynamic registrations - problems still exist post-beta

Black Square

@lilycrose By "doesn't work", do you mean that it isn't showing up, or that it's doing what you're seeing in this particular topic? Have you enabled it with the "Force MSFS 2024 Registration" setting in the tablet interface?

@AlphaEcho I'm just trying to understand the totality of the situation before I bring it to Asobo. It is difficult enough to obtain recognition of a problem from them, let alone providing a convincing argument to investigate and fix, so I try to be very concise when describing issue to them. I've had good luck with providing my best guesses for them to explore, such as you will find below.

@jmarkows Sound like everything is working as intended there. None of the Baron paint schemes make use of the winglet registrations. Thanks for checking on things, though. I expect everything to be working well on PC now, but there seems to be some kind of HTML/CSS rendering issue with XBOX, because the only way to see what we're looking at here is for the "structure" of the HTML "page" that the registrations are rendered onto to be different than what we're seeing on PC. I haven't seen any evidence of this in other gauges, so I suspect whatever fix they finally applied for the dynamic registrations may have missed the CSS file that defines this structure. I suspect that what you're seeing on XBOX is exactly what you would see on PC if you deleted the CSS file, in other words.

jmarkows

I traced the panel.cfg file to the Registration folder and found the .css file. I renamed it .css.old and then loaded back into the sim. This is the result, same as what it looks like above. Deformed on the left side, nothing on the right.

Are there also no winglets or tail numbering on the Duke, as well? Just the fuselage?

EDIT: here it is again with the .css re-enabled

jmarkows

I repeated the same test with the TBM and I see similar to the Duke above, not quite the overly large version posted above

Black Square

@jmarkows I had a hunch you might do that Hm. Similar, but not identical. Maybe the font size is not being picked up, and the CSS doesn't properly constrain the container size, so the bounding box grows the font size until it pushes the other registrations out of frame? Since you're already in the Registration folder, you could try deleting this section from bksq_bonanza_registration.js.

        var sidesize = url.searchParams.get("ss");
        if (sidesize) {
            this.sidesize = parseFloat(sidesize);
        }
        var tailsize = url.searchParams.get("ts");
        if (tailsize) {
            this.tailsize = parseFloat(tailsize);
        }
        var wingsize = url.searchParams.get("ws");
        if (wingsize) {
            this.wingsize = parseFloat(wingsize);
        }

I'm not sure this is entirely useful testing, but you can see why I went here as a possible explanation for what we are seeing.

lilycrose

@Black-Square No registration shows on the exterior of the aircraft until I enable it in your EFB. Is that what you are looking for?

Addendum: The hours do not increment either. When I land and check the HOBBS it shows the updated hours, but when I restart the sim the hours have reverted to 0. I have to assume the state saving isn't updating either, but I can't swear to that.

As a reminder, this is the normally aspirated Baron on a PC.

jmarkows

@Black-Square said in Dynamic registrations - problems still exist post-beta:

@jmarkows I had a hunch you might do that Hm. Similar, but not identical. Maybe the font size is not being picked up, and the CSS doesn't properly constrain the container size, so the bounding box grows the font size until it pushes the other registrations out of frame? Since you're already in the Registration folder, you could try deleting this section from bksq_bonanza_registration.js.
        var sidesize = url.searchParams.get("ss");
        if (sidesize) {
            this.sidesize = parseFloat(sidesize);
        }
        var tailsize = url.searchParams.get("ts");
        if (tailsize) {
            this.tailsize = parseFloat(tailsize);
        }
        var wingsize = url.searchParams.get("ws");
        if (wingsize) {
            this.wingsize = parseFloat(wingsize);
        }
I'm not sure this is entirely useful testing, but you can see why I went here as a possible explanation for what we are seeing.

I took out

        var sidesize = url.searchParams.get("ss");
        if (sidesize) {
            this.sidesize = parseFloat(sidesize);
        }
        var tailsize = url.searchParams.get("ts");
        if (tailsize) {
            this.tailsize = parseFloat(tailsize);
        }

from the TBM registration file and this was the result. I had the .css filed enabled originally, but even after disabling it it looks like this.

Waffler11

I, too, have been struggling with this mightily. Some of you may know that custom dynamic registrations are sort of my calling card as I utilize it in many, if not most, of my liveries. I keep looking for a way to fix this nagging issue.

I think I've narrowed it down to being a compatibility issue with 2020 aircraft in 2024. In short, I've had no problems with dynamic registrations in aircraft using the native 2024 folder structure, especially the modular format. Any 2020 aircraft or 2024 aircraft using the legacy (2020) folder structure either does not have working dynamic registration or is limited to just the default font and color (that is, black).

It might be that our hands are unfortunately tied with any 2020 aircraft being stuck with default dynamic registration and work around that or, again, we ask Asobo to look into this and hopefully fix it.

lilycrose

So, the dynamic registration still isn't working, but I use the tablet to set it and I'm okay with that. I also figured out, the state saving and hours issue is FS24, not BlackSquare. If I can get the program to shut down normally it saves the hours, etc, but most of the time it hangs and I have to shut it down through Steam, so no data is saved.
I assume nothing is written to the state.cfg file until FS24 shuts down, is that correct? It would be nice if it wrote when I exited back to the main menu, then I could copy the stage.cfg out and back in before the next flight. Not elegant, but it would work.

AlphaEcho

Hi. Just wanted to mention the problem with the dynamic registrations is still present with the native 2024 Starship (Xbox).

I also bought the Bonanza and Baron last night and they too have the same registration issue (partial, zoomed in reg no.).

I have quite a large collection of a/c now (shhhhh) - I’ve only noticed a similar reg issue with the A2A Aerostar……but the Comanche has no dynamic registrations problem at all.

It would be really good to hear how this is going to be fixed. I’m guessing it’s a sim issue, although believed SU4 would fix this problem.

Thanks. Mike.

ploodovic

@AlphaEcho I’m seeing the exact same thing on Xbox. The above theory, that it was caused by 2020 planes in 2024, wasn’t the whole truth.

Black Square

@AlphaEcho I'm glad to hear that you're enjoying the new planes, but this blemish really bothers me. The reason you only see it with A2A and myself is that we both use our own custom registration systems, which have caused problems in MSFS 2024, because it would appear that Asobo made some hard-coded changes to registrations. They had to fix it for PC to begin with (which took until SU4), and now we're going to pressure them as much as we can for this fix in SU5. I'm sure it will come up again, but I will let you know when I have anything to share from them.

AlphaEcho

Many thanks for the update.

A related query that you may think is/isn’t relevant or a problem - on Xbox, when I enter a registration on the aircraft selection screen, it seems as though that registration should only be applied to that specific livery. However, if I add a registration to, for example, a Starship, then that same registration is applied to every plane in the game (for those planes that allow custom regs).

This seems wrong to me (ie: for GA I like to add the reg of the plane I learned to fly in but want different regs for airliners etc). I can’t determine whether this is the intended behaviour but surely Asobo didn’t design this so users had to change the registration every time they launched a flight with a different plane?

Regards.

ploodovic

@AlphaEcho That is by design. It was the same in 2020; you enter a tail number and it gets assigned to all planes and liveries.

You’re right that the UI makes it look like the setting would be for only that plane, or livery, but it’s universal.

AlphaEcho

Oh OK, thanks. Would be much better if you could assign unique registrations to each livery (as you say, the UI definitely gives this impression). Odd, because before you change the number to one of your choice, all the original reg numbers are different livery to livery (from memory).

Cheers.