Punkcat
(Punkcat)
June 8, 2026, 5:54pm
1
Summary
Cannot move a child object from it’s parent to the root of the folder it’s parent is located in, or to another folder. On the second attempt, the “XXX is already assigned to XXX” hover message shows, as if the object had actually been moved.
Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
Assets
Steps to Reproduce
root
├── folder_1
└── folder_2
└── sm_parent
├── sm_child1
└── sm_child2
click and drag sm_child_1 to folder_1
will not move
try again, now hover message will show
repeat test with folder_2, same result
Expected Result
child object should move to folder
Observed Result
child object does not move to foler
Platform(s)
PC
Additional Notes
This was previously possible. The only workaround at the moment is to drag the child object to root then to a folder.
Punkcat
(Punkcat)
June 8, 2026, 6:00pm
2
To clarify: This is in the Outliner.
latunda
(latunda)
June 8, 2026, 7:01pm
5
Does it work after you reopen the project? [UEFN EDITOR] When I detach a child from the parent nothing happens
I don’t know why they didn’t want to create a ticket when I reported it
Punkcat
(Punkcat)
June 8, 2026, 7:05pm
6
Nope, tried resetting without success.
latunda
(latunda)
June 8, 2026, 8:52pm
7
tried to move again or verified the tree structure was updated? it shows the message because it moved but did not reflect in the outliner
Punkcat
(Punkcat)
June 8, 2026, 8:58pm
8
Oh wow, good catch! it is moving but just not showing the update in the Outliner. That kind of actually makes the issue a little worse!
It’s just a visual bug but very annoying. Should be definitely put in Known Issues.
Flak
(Flak)
June 11, 2026, 2:06pm
10
@Punkcat We’re unable to reproduce this here. Could you get a video repro of this so we can figure out what’s going on?
@Flak I already checked-in with them on Discord and validated the issue happening in 41.00, but we were not able to reproduce in newer builds. So consider the case closed.
FORT-1114286 has been ‘Closed’. We’re unable to reproduce this issue.