The code atm: UFUNCTION(BlueprintCallable, Category = "SQLite") static void UpdateTileID_Row( int32 TileQ, int32 TileR, int32 TileS, TOptional<float> VecX, TOptional<float> VecY, TOptional<float> VecZ, A…

So, I’ve done some testing and mucking around and it turns out you can use TOptionals with callable Blueprints, it’s just unecessarily hacky and long winded. The solution is either a nested private function or sentinel variables. Here’s the blueprint and the returned setclause statement in yellow, …

[image] Scatter: #include "Optional.h" according to the Documentation it’s #include "Misc/Optional.h"

Well that fixed the file unknown error… :+1: However the main error still remains - it doesn’t like the TOptionals (or at least, how I’ve used them).

Does the error remain if you remove UFUNCTION()? if it doesn’t, it’s most probably caused by Blueprints not supporting TOptionals. [EDIT] Just did some testing, it’s only showing an error if I mark the function as UFUNCTION(). So yeah, Blueprints doesn’t support TOptional.

Serious? That’s pretty limiting… Appreciate your effort @Extrone

Epic Developer Community Forums

UE doesn't like my TOptionals...

Development Programming & Scripting

CPP, question, unreal-engine

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled