x

Search in
Sort by:

Question Status:

Search help

  • Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both. Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.
  • You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with each other. Examples
    • cat dog --matches anything with cat,dog or both
    • cat +dog --searches for cat +dog where dog is a mandatory term
    • cat -dog -- searches for cat excluding any result containing dog
    • [cats] —will restrict your search to results with topic named "cats"
    • [cats] [dogs] —will restrict your search to results with both topics, "cats", and "dogs"

[BUG] - The type of Target Array is undetermined

Hello!

I have an issue where arrays spontaneously stop compiling in certain Blueprints. In this particular case, I have a type of BTTask_Blueprint that is supposed to do the following: A) Get all actors of type from the world (will cache this instead of using an iterator later down the line) B) For each of these actors, get their tag and compare it with the desired tag. C) If we find the desired tag, set blackboard variables, and finish executing.

There are two paths in the example, one if we already have a current actor (Current POI), and one if we do not, as we don't want to get the same actor twice in a row.

I can't pinpoint exactly when the blueprint stops compiling, but it seems to be when both of the primary actor for each loops are already connected, and one of the secondary string for each loops is connected - after the second secondary loop is added, the blueprint will no longer compile.

After this point, it is impossible to get the blueprint to compile without deleting all of the array nodes - disconnecting the nodes is not sufficient and they must be removed completely.

The errors look like as follows: Error The type of Array is undetermined. Connect something to ForEachLoop to imply a specific type. Error The type of Array Element is undetermined. Connect something to ForEachLoop to imply a specific type. Error The type of Item is undetermined. Connect something to ForEachLoop to imply a specific type. Error The type of Target Array is undetermined. Connect something to ForEachLoop to imply a specific type. Error The type of Target Array is undetermined. Connect something to ForEachLoop to imply a specific type.

Here's an image of the blueprint itself. I've tried setting up a generic version using a normal blueprint, but could not reproduce this specific issue (Note answerhub makes it insanely small, but if you get the image URL and open it up in a new window it should be readable). alt text

The issue is occurring in 4.6. I've googled around and only found one other reference to these error messages, and the post was quite old, without a solution :(

Thanks!

Luke

Product Version: Not Selected
Tags:
more ▼

asked Dec 16 '14 at 11:11 AM in Blueprint Scripting

avatar image

ambershee
603 23 30 52

avatar image sirrus233 Mar 16 '15 at 10:26 AM

Just commenting for visibility. I am also experiencing this bug. The workaround is viable, but obnoxious to have to deal with (thanks for finding it, Roel!)

avatar image Envy123 Apr 16 '15 at 06:32 PM

I'm also experiencing this bug, even though I've done the workaround from Roel.

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

2 answers: sort voted first

I have this problem as well, this is happening when you duplocate or copy/paste for each nodes and hook them up to a different array.

Easy temp solution is to click and drag from an array output and type foreach, recreate all the nodes, and it is fixed.

more ▼

answered Jan 17 '15 at 07:21 PM

avatar image

Roel
2.4k 70 43 142

avatar image Stormsson May 17 '15 at 09:13 PM

Thank you, you solved my situation too

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

Hello, i've had the same problem, and i found that when you copy a foreachloop node (ctrl + c, ctrl + v), can do a bug where you can't compile and for each loops goes in red. maybe beacuse copying it attached to some reference can do this bug. try to delete all the nodes that you remember you have copied,and put it manually one on one from new, it helped for me. Also try to open and compile all you blueprints and structs if you haven't try before.

more ▼

answered Apr 12 '15 at 04:38 PM

avatar image

jackloop
11 2

(comments are locked)
10|2000 characters needed characters left
Viewable by all users
Your answer
toggle preview:

Up to 5 attachments (including images) can be used with a maximum of 5.2 MB each and 5.2 MB total.

Follow this question

Once you sign in you will be able to subscribe for any updates here

Answers to this question