I hear Ben said “Now, we don’t need to protect the pointers, because it’s adding in the constructor, and it’s very likely to fail.”
But I couldn’t understand this.
Would anyone explain this precisely for me 
?
There’s no need to check because It’s assigning a new value to TankAimingComponent.
Is it means
"It’s guaranteed a value exists because it is assigned in native C++ code immediately not in Blueprint lately. " ??
Essentially, yes.
Thank you so much.
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.