Some strange behavior after build.

wukakuki · May 17, 2017, 7:32am

I don’t know how to reproduce the issue. but it really exits. After I package my project. Some values in UMG are lost its default value. Even the value from the widget that set “Is Variable” will be null (I print the result of “is valid” and output is false). I don’t know if there is anyone who face the same issue as me and knowing how to reproduce the issue. Please tell me. I create a test widget in an empty project. however, it seems that this issue appears randomly and hard to reproduce.

anonymous_user_d2b909bf · May 17, 2017, 1:58pm

Hello Wukakuki,

I have a couple of questions for you about this issue to help me investigate further.

Have you had this issue occur in engine versions beside the 4.16 preview?
Can you provide a screenshot of the issue you are experiencing?

Thanks!

wukakuki · May 18, 2017, 7:44am

this issue only occur in 4.16p3
I print a value in UMG

. “props slot 0” is a user widget object that set as “is variable”. And play in editor as standalone game. The output

138342-screen+shot+2017-05-18+at+3.34.29+pm.png

. However, after package, the output

138343-screen+shot+2017-05-18+at+3.39.45+pm.png

. So, I think the default value is lost. Not only this value, but also other bool, int, etc value.

anonymous_user_d2b909bf · May 18, 2017, 3:19pm

I have reproduced this issue and logged a report for it here

You can track the report’s status as the issue is reviewed by our development staff. Please be aware that this issue may not be prioritized or fixed soon.

wukakuki · May 22, 2017, 1:54am

So, I can’t check blueprint is valid or not at runtime. But how about the value? I check the value with the code

. this is a float value. In editor, it prints

138660-screen+shot+2017-05-22+at+9.46.23+am.png

. However, after package, the output is

138671-screen+shot+2017-05-22+at+9.50.43+am.png

. So, do you mean, I can’t get the value at runtime?

anonymous_user_d2b909bf · May 22, 2017, 1:59pm

This issue may be due to a different cause then the one I have already logged. Could you make a new post about this specific issue with steps to reproduce this issue?

wukakuki · May 22, 2017, 2:44pm

Please… the issue that you logged has been marked as “By Design”. But I think it’s the same. These two issues appear together and can be described as “lost its default value”. And I think the issue is not “By Design”, the reference is null (value is “0”) after package.

wukakuki · May 22, 2017, 3:12pm

I noticed what’s wrong. The steps to reproduce you logged is totally wrong. It’s not the issue I mean. I will make a new post. Thanks.