I assume its just an oversight, not really a bug but it could be considered one.
I set up all my meshes so that XX_01 is the smallest and XX_63 would be the biggest mesh in the list.
I tested this in 4.7.2 in a blank project and I am not seeing the results shown in the video above. I have a few questions for you that will help narrow down the issue that you are experiencing.
Quick questions:
Can you reproduce this issue in a clean 4.7.2 project with no starter content?
If so, could you provide a detailed set up steps to reproduce this issue on our end?
Are you using a project that was upgraded from an older version of the engine?
Sorry about the delay, but when I heard 4.7.3. would arrive soon I wanted to wait with the test untill it was available.
This video (unlisted for public) not only proves that 4.7.3 has the bug I showcased before, but like previous versions starts the indexing again at _10 instead of _01.
After watching the video that you posted I was looking into the issue further (with intent to reopen) I found that I had pulled up a similar issue, and that the issue that you have mentioned is still not resolved. In short this is a known issue and you can find any follow up information at the original post. My apologies for the mix up. I will be sure to bump the community interest for this issue. Thank you for your information and time.
Thank you for the update. I went ahead and double checked on this issue for you. It appears that you are correct the status for this issue has not been changed to resolved as of this time.
I went ahead and double checked on this issue for you and it appears that this issue’s status has not yet been updated to fixed as of yet. However, I will be sure to update this community interest for this issue. Thank you for your time and information.