This is the text array within the UMG Blueprint Editor:
https://puu.sh/xxfzp/6d9dca49fb.png
This is the array when accessed trough blueprint(bottom to top):
https://puu.sh/xxfzW/08fbb4abd0.png
This is not the first version of 4.17 this have happened in.
Try loop over that array on your Construction Event. Chances are you change it during runtime or Conditionaly Skip some entrys before printing them. I also noticed the order is in place just with a few skips and that one Entry does not match up “View Distance” and “View Distance Quality”.
Double check that. I did not notice any out of order Entries in Arrays or skips in 4.17
This is the only place where I touch the array in the blueprint(inherits from default class):
It’s inside an UMG widget blueprint. I looped over and tested to get the text on certain indexes, both in the “pre construct” and on “construct”. Now after restarting the editor the array thinks it’s just one index long and I look in the log which tells me that there is nothing at these indexes. It thinks the array is one item long.
PIE: Error: Blueprint Runtime Error:
Attempted to access index 3 from array
OptionNames of length 1! from
function:
‘ExecuteUbergraph_BP_OptionsMenu’ from
node: Print String in graph:
EventGraph in object: BP_OptionsMenu
with description: Attempted to access
index 3 from array OptionNames of
length 1!
[Video showing the setup][2]
if you do a refference search make sure to uncheck “Find in current BP Only” your option Names can be modified outside of this Widget BP. If you create a copy of that variable and read it from there the error should not occour at all.
Thats indeed very strange but if it can´t be reproduced (tried on my Engine) its unlikely that me or the Staff can find a fix for it since the cause is unknown. In your case I would try to make a new FName array and try it with that (give it another name just to be sure). For now I assume your default Object got corrupted somehow and its a one off bug.
If it still happens I would suggest sharing your project with Staff only to look over it. (got to wait for a reply from them in that case)
I did now, nothing else is referencing it. It’s literally the last thing I’ve done on the project. If something else is accessing this text array, then someone is hacking my computer and have added code into the project without me knowing… Which I highly doubt.
That getter for the “Options Names” is the only single place in the project it’s being used other than in the default variable assignment.
Just to be on the safe side, I tried to loop over it trough the character blueprint. It still only give me back a single item…
Well I changed it to a string array, which now worked. But the issue still persists with the text array.
I have same issue,
seems, TextArray can only ForEachLoop 5 times at runtime, but editor mode works.
I changed to string array works.