I was unable to reproduce this issue on our end. I have a few questions for you that will help narrow down what issue it is that you are experiencing.
Quick questions:
What version of the engine are you using?
Can you reproduce this in a clean project?
If so, could you provide a detailed list of steps to reproduce this issue on our end?
Could you provide screen shots of any other blueprints that may be involved with this issue?
Here is my set up for the set that I ran:
This example worked in both PIE and Standalone mode. I am using a widget with a series of text blocks that I am setting in order to display the different bits of text. Could you get this set up a try and let me know if it works for you?
We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will offer further assistance.
Edit: To be clear, it’s happening with every enum I try from this specific blueprint (even when converting to string and printing), however other blueprints are able to display the same enum properly.
Could you please answer the questions that I asked in my original post (except for the engine version of course)? I will need more information in order to narrow down what issue it is that you are experiencing.
I’m having the same issue in 4.7.6 as well. I’m trying to convert an enum to string and when I print it out, instead of giving the literal value stored in the enum, it prints out like ‘enumerator0’. Also everything works perfectly in PIE. The issues occur only in standalone.
I will try it out on a clean project and let you know if it’s coming up with the same result.
Please be sure to answer as many of the original questions as possible. Also please feel free to try the set up that I had and let me know if it works for you.
Alternatively, you can also try a print string check to see if the enum converted to string is equal to an actual string variable holding the same literal value. Prints success in PIE, but failure in Standalone. Here’s a screenshot:
After reading over the steps that you provided I was able to reproduce this issue on our end. I have written up a report ( UE-15811) and I have submitted it to the developers for further consideration. I will provide updates with any pertinent information as it becomes available. Thank you for your time and information.
After looking into this issue it appears that the report that was filed was a duplicate of (UE-13906) and the original issue was resolved in the 4.8 version of the engine. I hope that this information helps.
Hi Rudy, it’s working in PIE and Standalone, but not in packaged if you enable the BP->C++ converter. I have tested this in both 4.11 and 4.12 (master branch). I know the BP->C++ converter is not yet finished, but maybe it helps to report bugs it has at the moment
This sounds like it may be a separate issue. Could you start a new thread and place a link in a reply on this thread (for tracking purposes)? After this I will be more than happy to assist you further.