When changing a Blueprint variable's value and playing in viewport the value sometimes gets reverted

Development Programming & Scripting Blueprint
, , , ,
1

Hi, I’ve noticed this in Blueprints in “<”, “>” comparisons with floats and other cases. What happens is that if you change a float there and you don’t compile, many times, but not always, if you play in viewport and go back to check the Blueprint, the value is the old one.

2

Have you already noticed this?

3

Hey Albert Espin -

I have tried to duplicate this problem and have been unsuccessful, do you have a particular instance where this is happening more than any other?

4

Well, it simply happens pretty often if I change the value of a float inside a float sum, a comparison, a SetTimer time value or many other places inside functions.

Try typing a float value in cases like those, play in editor, and then change it and play back without compiling. At least in my case, it will lead to a no-change some of the times.

I’m using 4.1.1. It’s not a very problematic issue, but it would be better if it could be solved.

5

Hi Albert Espin -

To Clarify you are PIE, then change the float value then stopping PIE but not compiling the blueprint before you stop PIE.

Thanks I want to make sure I can reproduce this exactly.

Eric Ketchum

6

Not exactly, step by step it’s like this: in a blueprint set a float value (for example in a < comparison), start PIE, stop PIE, change the float value, start PIE again without compiling the blueprint: the change sometimes won’t have taken effect.

7

No, I’m not closing the blueprint at any point, just doing what explained above. Are you in 4.1.1? Have you tried it some times? It happens very often, maybe a half of the times for me, but not always.

8

Are you closing the blueprint before you starting the PIE again and then reopen it? I have tried to reproduce and I am not seeing it happen. This behavior seems like it is working as intended though. The editor really wants to pull information from compiled script and unless saved when you close the PIE and the engine is creating a check point (notice how you cannot undo past closing a PIE session) it will pull information from saved content browser data and not temporary editing data, like an open blueprint.

Eric Ketchum

9

Hi Albert Espin -

I wanted to check in with you, I was never able to reproduce this issue in house, but are you still having this issue in the new build, or did 4.2 seem to fix it?

Thank You

Eric Ketchum

I am marking this answered, but if this problem has persisted or returns feel free to reopen.