1 Like
The green âselectâ node is not re executed because it is connected only once, storing its value in the variable.
The variable then has multiple connections to pass on its value. it sends the same data every time because it does not execute a green node more than once.
Your right in that that does work⌠but when itâs comparing them in âcheckAlreadyExistâ why does it not see it already exists⌠i feel like im covering up another problem but it works
would storing the value in CheckAlready exists have the value be the same at the time of comparison?
It works now with the links connected to the variable?
Well you passed a different thing to the check than into the location array, because you got random data multiple times before. Thatâs what the video explains about how pure nodes work. A very confusing and unfortunate design in the blueprint system.
it seems to work such as this like you suggested
but im still confused how checkAlready exists doesnât realize it already has a copy
i appreciate your effort here to help me see, and iâll be marking your answer as the correct one but i want to leave this open a moment until i figure out how A dosent equal A
Maybe that helps with the confusion
By executing the green node through 3 connections you grab a random vector, then another random vector, then another. After the check the second and third connections are just a different vector.
I connect it once then store it immediately. The stored value does not change because that node executes once through the white line (execution pin). Anything that is a blue node or a variable node executes once. The green ones like âSelectâ, âRandom âŚâ they execute again and again for every connection. Confusing it is.
so when it compares it its different but by the time it goes to add it its got different information because by then the main loop is already starting on the next evaluation
Right vector should always be right vector⌠so my assumption is its started on the next one by the time it stores it because of the pure nodes
Itâs not a time problem. Everything here happens on the same frame. The issue was that you tried to retrieve a value from a green node which task was to generate a random value on every request (every line connected to it)
Every request (3 times in one frame) there was a 50/50 to return forward or right.
Gotcha⌠so the probability isnât locked in so it draws a new one which has a chance of being the same thing, this whole time i was assuming you were talking about the forward vectors⌠so my fault entirely it never occurred to me the select random was also a pure node
1 Like
thatâs it 
1 Like
Thank you so much honestly for beating me with a stick so iâd see it
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.