Here is a picture of a search attempting to find a variable called “Start Loc”:
You can clearly see that the variable is being used in the middle of the picture.
If I create a new referance to “Start Loc” (I.e. drag from variable list a put into the graph, selecting ‘get’) you can now find “Start Loc” in the search:
Image links seem to be temperamental, here are direct links:
Using “Find Referances” on the invisible getter gives a near search string which is:
Nodes(VariableReference(MemberName=+"Start Loc" && MemberGuid(A=-284182496 && B=1130834749 && C=232342691 && D=-213515062) ))
Whereas “Find Referances” on the variable in the editor variable list (left hand side of BP editor) gives:
Nodes(VariableReference(MemberName=+"Start Loc" && MemberGuid(A=-1577340200 && B=1289802846 && C=-227196020 && D=-649442317)))
Whats the reason for these GUID’s missmatching? This doesn’t extend to new getters as proven by the second picture. For some reason the older getters have a different MemberGUID but they still point to the same variable.
This is the same across the blueprint:
Find referances on the variable in the variable list:
Find referances on the getter in the picture:
Find referances with a new getter created from the variable list (i.e. drag → get):
Could this be todo with the code being copy+pasted? The code still runs fine, so internally the blueprint parser has no trouble finding which variable to get from the getter in the first picture. I vaguely remember writing this code in a different class, then moving it over into this one.
This is incredably infuriating. Whenever I search for referances to a variable, i.e. to see if it’s in use and to replace it’s use etc., the search function simply doesn’t give the correct results. Please note that “Start Loc” in the picture and the new “Start Loc” created both refer to the same variable in the same class.
This problem seems to have been happening a lot and it’s making refactoring near impossible. I’m glad I’ve finally been able to capture the exact problem though, hopefully this can get fixed soon.