[Bug] browser indexing starts at 10, not 01

Development Asset Creation
, , ,
1

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.

1570×356 279 KB

Sadly it starts at XX_10, goes to XX_63 and then ends the list with XX_01 to XX_09
Shouldnt the browser start with XX_01 and end with XX_63 ?

2

Hello,

This is a known issue and the issue seems to have been resolved in the 4.7.2 version of the engine. Thank you for your time and your information.

Make it a great day

3

Uhm… I am using 4.7.2 and the problem is still there.

4

Ok, let me rephrase that.

This has not been fully resolved in 4.7.2.
(would have been nice if you didnt instantly discard my report…)

Here is proof of the issue:


It does innitially load the indexing correct (starting at XX_01)
but if you change folders and move back, it starts at XX_10 again.

Thank you.

5

Hello,

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:

  1. Can you reproduce this issue in a clean 4.7.2 project with no starter content?
  2. If so, could you provide a detailed set up steps to reproduce this issue on our end?
  3. Are you using a project that was upgraded from an older version of the engine?
6

Hello Rudy,

  1. Will try, but that will have to wait untill tomorrow. (real life stuff)
  2. I will record my findings for easy-to-follow steps if it does happen.
  3. yes, currently using a project that was started at 4.3 and has been updated to every new version release up untill 4.7.2.
7

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.

8

Hello,

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.

Original post:

Make it a great day

9

Hello rudy, just a small FYI. this happens again in 4.9.2

10

Hello,

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.

Make it a great day

11

Hey Rudy…
Its still there/back in 4.10 :confused:

12

Can confirm, just had it with some meshes.

13

Hello Kashaar,

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.

Make it a great day