Trying to access a property causes blueprint runtime error
Sorry for double posting, I've already posted my issue here but managed to reproduce it in a project from scratch and think it's really a bug and not something from my code. Here's what I did:
Am I the only one having this issue? I hope you guys can reproduce it and fix it. :)
Thanks in advance.
There is a difference in the behavior between the 4.10 and 4.11 engine version. I have entered a bug report about the error message you received (UE-29768) for further investigation. Rather than having to restart the editor, I found that compiling the blueprint with the reference (in your case the character) will update the blueprint and print the name as expected.
answered Apr 21 '16 at 01:29 PM
Bump. This error persists in 4.22 still and the logged error is still marked unresolved.
In my case, I import new data assets via C++ compilation and consolidate objects to clean up, then fix up references. Due to the compiling via hot reload, blueprint classes that make use of the new, consolidated data assets don't work unless recompiling manually (no compile error beforehand though) or restarting the editor due to "missing properties".
answered Jun 04 '19 at 12:42 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here