Calling events of other bp with input type same as caller bp generates errors on standalone games
Calling an event of another blueprint with an input type that's the same as the type of the calling blueprint generates errors in the log when playing as a standalone game or mobile (preview). It does work when playing in the editor.
The error occurs even when not setting the argument (see first image)!
And it causes the entire calling blueprint to not work anymore.
I discovered it on a new game i'm working on (mobile game):
[2014.08.20-22.13.56:084][ 0]LogBlueprint:Error: [compiler] Error Function 'OnPersonTap_Fail' called from OnPersonTap_Fail should not be called from a Blueprint [2014.08.20-22.13.56:084][ 0]LogBlueprint:Warning: [compiler] Warning [0005.05] Compile of Person_Fail failed. 1 Fatal Issue(s) 0 Warning(s) [in 1 ms]
Then i tried a standalone game of another (much bigger) game i'm working on, gives the same error:
[2014.08.20-22.45.18:121][ 0]LogBlueprint:Error: [compiler] Error Function 'StartDispensing' called from StartDispensing should not be called from a Blueprint [2014.08.20-22.45.18:122][ 0]LogBlueprint:Warning: [compiler] Warning [0026.23] Compile of BallDispenserButton failed. 1 Fatal Issue(s) 0 Warning(s) [in 3 ms]
Any ideas what's going on? Is there a workaround for this?
We have not heard from you in quite some time. I am marking this thread as answered for tracking purposes. If you are still experiencing this error, please comment here to let us know. Thank you.
answered Sep 03 '14 at 05:46 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here