Some bindings fail in packaged builds (UE 5.4.3)

ersenal · 18 Jul 2024, 11:44

Hi there!

I've noticed that some of my properties are not being bound correctly (always the same properties) in packaged builds, even though editor builds seem to be completely fine. The data context is a UNoesisInstance and I set the XAML inside the constructor like so:

UOptionsMenu::UOptionsMenu() {
  BaseXaml = LoadObject<UNoesisXaml>(nullptr, TEXT("/Path/To/My/XAML"));

These properties hold valid initial values and I update them inside NativeConstruct:

void UOptionsMenu::NativeConstruct() {
  Super::NativeConstruct();
  settings = UUserSettings::GetTotSettings();
  
  brightness = settings->Brightness;
  NoesisNotifyPropertyChanged(this, "brightness");

I'm quite confounded as it is, and any help is very much appreciated :)

Editor (Development-Editor):

Packaged (Development-Game):

XAML snippet of a property that can't be bound in packaged builds:

ersenal · 18 Jul 2024, 19:45

This was apparently due to FName shenanigans. I had to set WITH_CASE_PRESERVING_NAME for runtime/packaged builds to make it work. Though, I ultimately decided that I should probably follow UE's naming conventions to reduce the overall friction going forward.

30 Jul 2024, 13:34

This was also discussed this here: viewtopic.php?p=16378

We don't recommend setting WITH_CASE_PRESERVING_NAME to 1, we discovered a few issues with this. Until we find a better solution (we could make changes to our Symbol implementation) we recommend following Unreal convention.

Some bindings fail in packaged builds (UE 5.4.3) Topic is solved

Some bindings fail in packaged builds (UE 5.4.3)

Re: Some bindings fail in packaged builds (UE 5.4.3)

Re: Some bindings fail in packaged builds (UE 5.4.3)

Who is online