Presets not loading correctly, UI bug / docs or SDK sample error?

[WombiiActual]

Loading the FS 2024 SDK sample for the DA62 mod using presets, the preset that is loaded in the plane configuration screen shows AIRCRAFT.UI_MANUFACTURER AIRCRAFT.UI_MODEL instead of the name. It does however load the correct cabin/gear/engine/instrumentation info below it. edit: see below. It actually doesn’t show the extra info either.

Is the SDK sample wrong or is the UI coded wrong? Which section should the bug report be in?

When creating a custom livery + attachment + preset package for a default aircraft, the new presets also show AIRCRAFT.UI_MANUFACTURER AIRCRAFT.UI_MODEL, but they also fail to list the cabin/gear/engine/instrumentation info, even when copying a preset from the default model in the VFS.
What are the requirements to show this info correctly in an addon mod package?

Edit: test project sent to privatecontent. Adds 4 presets to default C152.

Edit: After trying again, the DA62 mod sample is also not showing the extra info like cabin/gear/engine/additional.

Edit 3: I was able to add the manufacturer name and model name by adding the following to the preset aircraft.cfg file, but it absolutely refuses to show the extra UI info regardless of which additional fields I add to the file.
ui_manufacturer = “@asobo-aircraft-c152,TT:AIRCRAFT.UI_MANUFACTURER”
ui_type = “@asobo-aircraft-c152,TT:AIRCRAFT.UI_MODEL” ;

I feel the UI should be able to pull this info even if the preset is added in an addon package.

[EzRyder]

i made some of this work adding presets by hard coding the ui_manufacturer and ui_type in the preset aircraft.cfg
i would assume aliasing the correct localization block should also work?

not sure this is correct or if it helps but … here is how i got some of that working within a preset

[WombiiActual]

I made a powershell script to copy one preset from each modular default plane into an addon package to test this further.

@EzRyder Thank you for the hints on the discord. Adding the lines for manufacturer and type manually either as text or aliasing the localization strings (@packagename,string) works to fix the title lines, but the info panel seems to be bugged depending on the aircraft.

@Boris Thank you for tagging it to bug-logged, but I’m not sure which part of it is logged as a bug and if any of it is considered working as intended. The following is a summary of the individual issues I’ve found here, and if you let me know which ones are working as intended or have been logged, I can make separate bug reports for them.

1: selection UI does not bring up the correct manufacturer and model name of a preset in a separate addon for an aircraft that uses localization strings in the common aircraft.cfg. See point 2 on how to fix it.

2: SDK DA62-mod sample does not use localization string aliasing (@packagename,string) to show this is necessary. For example "@asobo-aircraft-c172sp-as1000,TT:AIRCRAFT.UI_INSTRUMENTATION_GARMIN_G1000".

3: Selection UI does sometimes not bring up the info panel at all (cabin/gear/engine/instrumentation/additional information).

4: NOTE: Point 3 above might be aircraft specific, like the C152, B36, A330, while the DA62 and X Cub seems to work.

5: The info panel does not load if the addon package is loaded from devmode, only in community folder. This makes it more difficult to troubleshoot and is not documented.

5: Selection UI does not load the Cabin or Gear info for presets from a separate addon package.

6: It is not documented (as far as I can tell) where the selection UI pulls all the info panel info from, which makes it difficult to troubleshoot.

7: Selection UI does not load all info in the statistics panel for presets from a separate addon package.

8: It is not documented (as far as I can tell) where the selection UI pulls all the statistic panel info from, which makes it difficult to troubleshoot

[Boris]

Sorry for not being clearer.
I have indeed logged all of this in a ticket.

I’ll keep you updated.

Regards,
Boris