Compile Error after engine restart

1 Like

hi
i am using my player character to set enum states of another character.
after the engine has been restarted i get a blueprint compile error when i press play but if i open the BP and click compile everything is fine until i restart the engine.
any ideas please?]

Hi ,

Could you try to reproduce this issue in a new project? Something simple with very little assets that could be posed so we can troubleshoot the issue.

Thanks but not got time to do that right now. this problem has moved down on my todo list. But the problem seems to be that the enumerators Names and Numbering system messes up Iā€™ve found this to have always been the case even back in 4.1 and 4.2. because i have reordered or removed Names in the Enum BP everything messes up for example when using SET BLACKBOARD VALUE AS ENUM 0=FallBack 1=WingMan 2=Search and so on which is correct, in the BP sown above Using the nodes LITERAL ENUM the errors indicate ENUM IS INVALID and that 2=FallBack 1=WingMan 3=Search ill look into it further when i get time.

This issue has been resolved for me with update to 4.4

I still have this problem with 4.4.0 with every ā€œLiteral enum ā€¦ā€ node. Everytime I restart the editor, it shows a compile error

Hi Ghar,

Try downloading the 4.4.1 hotfix, this seem to be what fixed 's issue.

Not resolved for me iā€™ve just started using the Behaviour tree in 4.4.3 with enums and I get a compile error on restarting the editor on all nodes where i use a ā€˜Literal enum xā€™ node to set the key value on a blackboard. If you click the ā€˜compileā€™ button in the blueprints that error, it resolves it and works for the rest of the session. As soon as you restart the editorā€¦compile error.

Only seems to be when your setting a blackboard enum, works fine when setting enums elsewhere.

Also setting the enum value by using a number directly on the ā€˜set value as enumā€™ node works fine.

Hi savagebeasty,

Since this issue is persistent for you in a version later than 4.4.1, could you create a new question for this?

Thanks,
TJ

I get the Same problem as got i have updated to 4.4.3 still the same problem

Hi Hitendra,

Since 's issue was solved by upgrading to 4.4.3, could you post your issue in a new question?

Thanks,
TJ

Canā€™t you just reopen it, itā€™s not fixed in 4.4.3. Honestly Iā€™m not lying, try it :slight_smile:

@ - can you confirm that setting a blackboard enum value as a ā€˜literal enumā€™ works without a compile error after reloading the editor as either Iā€™m mental or thereā€™s something more complicated with this than I initially thought there was.

Are you using the latest build from Github or the latest build from the UE launcher?

Sorry to here you have this frustrating issue. Iā€™ve not had this issue personally since I updated to 4.4 not sure the bug has ever been fixed and may return at any time, surely youā€™d think that staff would have access to information about what bugs have been fixed by whom, when and in which version release, Iā€™m currently on hold with my main project as 4.4.3 introduced to many bugs to be useable new and old ones returned. I read through the 4.4.3 update notes before updating and nowhere did it say or give the impression that it would screw my entire project up. Iā€™ve been working on a new project concept called Bug Wars but itā€™s proving not to be much fun to play.
It may be worth a complete reinstall of UE4 and the launcher, please post here again if you resolve this issue to help others, good luck.

Due to my ever decreasing hard disk space I usually uninstall the existing version of the engine and launcher and redownload/install the new version from fresh, then just point it at my projects folder.

I havnā€™t tried it in a clean new project so Iā€™ll give that a go. To be fair Iā€™m not overly bothered about this as I just use the number instead of the literal enum node, itā€™s just annoying having to open my enum to remember what number corresponds to which enum name :slight_smile:

But at the same time, the names donā€™t work in the behaviour tree either they just show the enum number so Iā€™m getting used to it.

In fact Iā€™d probably be better off just ditching enums and using strings :slight_smile: