Summary:
UDMXProtocolSettings’s Attributes and FixtureCategories array properties (both Config-marked TArrays) come out in exactly reversed order after closing and reopening the project, despite DefaultEngine.ini on disk remaining correct and unchanged throughout. InputPortConfigs/OutputPortConfigs (also array Config properties on the same settings object) are unaffected.
Steps to reproduce:
- In Project Settings → Plugins → DMX, note the order of the
Attributesarray (e.g.Colorfirst,Sizelast). - Close and reopen the project.
- Reopen Project Settings → Plugins → DMX and view
Attributesagain.
Expected result: Array order unchanged (Color still first, Size still last), matching what’s saved in DefaultEngine.ini.
Actual result: Array order is exactly reversed (Size now first, Color now last) — confirmed via the DMX settings panel’s own Export function, which serializes the live in-memory object: the exported file shows the reversed order, while DefaultEngine.ini on disk (checked directly) still holds the correct original order.
Additional notes:
- Verified this is a pure order reversal with no data loss — every
Attributesentry (name + keywords) is present and unchanged in content, confirmed via a full diff against the correct saved config. - Restarting the Editor (tried twice) does not resolve the reversed display/live-object state.
- No second/conflicting config file found anywhere in the project or per-user Engine config that could explain a stale override — the reversal appears to happen during the Editor’s own config load/merge for this settings class.
FixtureCategories(also an arrayConfigproperty,TArray<FString>) exhibits the identical exact-reversal behaviour.
Engine version: 5.6.1
Platform: Windows
DMX Backup 2026-09-04 153801.ini (4.7 KB)