In developer settings of the editor, we cannot edit an InstancedStruct property (“GameData”) that has an EditCondition meta tag, but we can edit a TArray<InstancedStruct> property (“GameDatas”).
If we change default value of bEnabled to true in code, both “GameData” and “GameDatas” can be edited as expected.
This issue has appeared just after upgrading from UE 5.4.x to 5.5.4.
Steps to Reproduce
1- Create a new UDeveloperSettings subclass in your MyGame project, add to .h file something like this:
`#pragma once
// Minimal include “CoreMinimal.h”
// Parent include “Engine/DeveloperSettings.h”
// UE include “StructUtils/InstancedStruct.h”
// Generated include “MyGameEditorDeveloperSettings.generated.h”
UCLASS(Config = “EditorPerProjectUserSettings”, meta = (DisplayName = “My Dev Settings”))
class MYGAME_API UMyGameEditorDeveloperSettings final : public UDeveloperSettings
{
GENERATED_BODY()
UPROPERTY(EditAnywhere)
bool bEnabled = false;
};`2- Compile-launch editor, open Editor Preferences, find “My Dev Settings” and click on Enabled checkbox, “GameData” isn’t enabled for edition, “GameDatas” is enabled for edition.
I was able to reproduce the issue locally in UE 5.5 and newer versions, including the latest 5.6 Preview and Main (CL 42589677). This behavior does not occur in UE 5.4, so it appears to be a regression.
I’ve shared the issue with the internal engine team and created a JIRA report. The issue will soon be visible on the public Unreal issue tracker at:
Please note that Epic ultimately determines whether the issue will be made publicly accessible, and the process may take a few days. The tracking link might not work immediately.
As a temporary workaround, you may want to avoid using the EditCondition meta tag on single FInstancedStruct properties inside UDeveloperSettings.
I’ll go ahead and close this case for now, but feel free to reply if you have anything else to add.