Blueprint Integer Selection with increment afterwards cause Ensure condition failed: DestinationExpression->AssociatedVarProperty

anonymous_user_727e15ba · March 29, 2017, 5:32pm

Well im not sure if this a Failure of mine or a bug so i wanted to ask before creating a bug report.

The problem is if i do this:

then i’ll get following Failure next time i package(output.log)/compile UE4(Visual Studio Debugging Session)/ restart project (output.log)

Ensure condition failed: DestinationExpression->AssociatedVarProperty [File:\Engine\Source\Editor\KismetCompiler\Private\KismetCompilerVMBackend.cpp] [Line: 1318]

also the packaging will fail.

Solution for me (for now) is to check the EControllerHand with Equal for Left and use Branch for incrementing.

greetings

anonymous_user_727e15ba · March 29, 2017, 5:56pm

Well i forgot to tell: I’m using the SteamVR Plugin… which servers the EControllerHand

anonymous_user_2b03d27c · April 5, 2017, 3:59pm

Hey C4r731-

The ensure message is not a bug, but rather an indication of a potential problem in the future. If you’re already found a way to work around the ensure that works for you, I would continue with that method.

Cheers

anonymous_user_727e15ba · April 6, 2017, 9:33am

Hey ,

thx for your Post and thx for the additional info… but while a got this message i could not package my project… after the workaround packaging was ok… anyhow, my workaround so far is to branch (left or right) and call a function… probably overkill for just small things but it works for me :D…

greetings,

C4r731

Everynone · August 28, 2020, 9:05pm

Just run into this in 4.25.3:

Do not - Set by Ref - when using the Select node.

Hax-Dev · May 31, 2024, 3:05am

Hello,

I just want to say THANK YOU SO MUCH for your reply. This helped me solve my issue that I was having with packaging. Sure enough, I was using a select node and inputting it into a “Set by ref” node in one of my blueprints. I even remember thinking it was SO smart to add instead of doing individual set nodes for each variable. So much for that.

I wonder if this is a bug? Either way, I thank you for the solution. I was searching for hours until I found your post.