Crash after changing blueprint function variable type from int to float and reloading editor

I’ve been able to reliably reproduce this with my current environment. I have a blueprint function library called “ActorUtils” that contains a method called “IsWithinRange”. This method originally took in an int as the range, but is now being converted to use float.

So I click on the “Is Within Range” function input node and change the variable type of “Range” to float. I then click compile, then click save (have done those two in reverse order as well, same result). I then click simulate or play to start the game and it functions correctly.

After this point I close the editor and relaunch it immediately. I Upon launch I click play or simulate and I receive a crash dialog. Since attachments are limited to two, I will add a comment below with the associated crash log and dialogue screenshot.

If instead of running simulation or play upon relaunch of the editor, I open the blueprint again and click compile then a crash dialogue is produced as well.

Here are the crash dialog and logs.

[link text][2]

Another bit of info that may help. When I am undoing these changes, the only way I can get it to successfully compile the blueprint again is to change the type of “range” back to int then save and then delete the >= comparison node and re-add it. If I simply change the data type back without removing and readding the >= node then it will crash on compile.

Hello,

Thank you for your report. We were not able to investigate this on the engine version you reported, but there have been many version changes to UE4 since this question was first posted. With a new version of the Engine comes new fixes and it is possible that this issue has changed or may no longer occur. Due to timetable of when this issue was first posted, we are marking this post as resolved for tracking purposes.

If you are still experiencing the issue you reported in the current engine version, then please respond to this message with additional information and we will investigate as soon as possible. If you are experiencing a similar, but different issue at this time, please submit a new report for it.

Thank you