Found a Bug with Arrays and Array Length (Blueprint)

anonymous_user_e4d2f3d4 · February 19, 2017, 9:08am

i made the normal button from the Example Content so it can also be pushed by Blocks but i got it so the animation stays and than i looked and found the bug (see Picture) and wanted to report it here or get help to fix it

anonymous_user_e729f54e · February 20, 2017, 4:04pm

Hello ,

I was not able to reproduce this issue on our end. I have a few questions for you that will help narrow down what issue it is that you are experiencing.

Quick questions:

Can you reproduce this issue in a clean project?
If so, could you provide a detailed list of steps to reproduce this issue on our end?
Could you provide screen shots of any other blueprints/settings that may be involved with this issue?

ctzn_no7 · February 22, 2017, 6:09pm

I can confirm similar issue when using Local Variable arrays inside function.
Array index will start from 1 unless you resize the array to 0 before adding any data to them.

anonymous_user_e729f54e · February 24, 2017, 3:42pm

Hello ,

I was unable to reproduce this issue on our end with the information provided. Could you answer the questions that I asked of ?

ctzn_no7 · February 24, 2017, 7:31pm

I was unable to reproduce this with new projects too, however it is still present in my main project.

Without resize, the array starts from 1 (see DrawDebugString on the right)

and with resize it starts from 0.

I did double check that there are no default values set for those arrays.
Best guess it has something to do with BP array variable changes in 4.15

edit: I might add, this project was updated from 4.13.2 to 4.15.

I tried reproducing it with clean 4.13 project then updating it to 4.15 without luck

anonymous_user_e729f54e · March 6, 2017, 4:17pm

If you move the asset with this issue to a clean project, does this issue still occur?

anonymous_user_e729f54e · March 9, 2017, 6:58pm

Hello ,

We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will follow up.

Thanks,