Number ordering within Content Browser

The number ordering within the content browser is chaotic.

10 comes before 01 but after 1.

This issue becomes much more of an issue when working with large number of numbered assets.


As a further level of “WTF”, when you view these assets from a drop-down list they order in a different way (and how I would expect everything to order within UE)…


Howdy FoxB,

Thank you for reporting this issue. I have been able to recreate this issue in our internal build with ease. I have entered JIRA report # 7347 into our bug database so that it may be addressed in a future release.

Thanks and have a great day!