Summary
The editor behavior of the Scene Graph components can cause the project to soft lock. It is resolvable, but it’s mainly caused by the inconsistent and unintuitive initial value UX. I already outlined several problems about it in the following thread, but it hasn’t received any further attention yet.
FORT-901741 - Scene Graph - Editor behavior that easily becomes the source of bugs
Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
UI/Tools
Steps to Reproduce
Create an enum that you intend to extend during development and a single value.
my_enum := enum<open> {
FirstValue
}
Create a component that has an editable field with such enum as its type and very importantly, do not provide a new default value.
my_component := class<final_super>(component) {
@editable
MyEnum: my_enum
}
Add the component to an entity in the scene.
Expected Result
The value isn’t initialized with a default value in code, so should the editor not automatically set it to FirstValue, but instead display “set to value” button.
Observed Result
The editor automatically set it to the first enumeration case, which makes it impossible to override / set-manually in this particular case. Validating the project will yield an error of an uninitialized field. The expected behavior is not that the error message goes away, but that the editor UX is updated to display the proper “set to value” button to mirror the fact that the value hasn’t been set to any default in code.
Platform(s)
UEFN (v37.00)