Dynamic registrations - problems still exist post-beta

lilycrose

I'm flying the Baron Professional on 2024 at the moment on a PC, and my dynamic registration doesn't work, so I don't think it's limited to the Xbox or the TBM.

AlphaEcho

@Black-Square The 2024 native TBM definitely does exhibit this behaviour. It’s irrelevant if it works for the person you quoted. Surely it’s best to seek confirmation from those having the problem?

Meant to add - a member above has kindly included a screenshot of the TBM exhibiting the partial zoomed-in reg.

jmarkows

For another confusing data point, I just loaded through every Black Square product I own in MSFS 2024 on PC. With the Dynamic Registration option enabled on the tablet, the results were:

Bonanza v1.1: works, displayed on the fuselage in the approximate location and size the example in the manual shows
Baron v1.1: works as the Baron, but not displayed on any winglets. Not sure if it's enabled on the included liveries
Duke v1.2: same as the Baron
Starship v1.2: works, displayed on each engine nacelle
TBM v1.4: works, printed on the vertical stabilizer

I tried N8289A for a full-sized registry and N43DH for a shorter one (in case the winglets were size-limited). This is with 2024 v1.6.33.0 (post-SU4 hotfix) and the release branch, I was never in the 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.