Having an extra semicolon on the line before declaring a UPROPERTY will cause UHT to miss parsing the following UPROPERTY. This is expected, but an error is usually given when this is the case. This error is not thrown when the declaration happens in a USTRUCT however although the missing UPROPERTY problem still occurs.
Regression?: No
This happened in 4.11.2 and 4.12.5 as well
USTRUCT()
struct FMyStruct
{
GENERATED_USTRUCT_BODY()
UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "MyStruct")
int32 MyInt = 10;;
UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "MyStruct")
int32 MyOtherInt = 20;
};
3. Compile the code
Result: The code compiles successfully, resulting in the second UPROPERTY not being picked up by UHT due to the error that should've been caught
Expected: The compile should fail, giving an error letting the user know that the extra semicolon will block UHT from seeing the second UPROPERTY
i have this problem UE4CC-Windows-58DC12AF4B97F057BD108FBFF569B2E9_0000
I am not able to find world outliner how to enable it?
Undefined sysmbol: typeinfo for AActor when cross-compile linux dedicated server on windows
How can i modify the param name in EQS node
Delay nodes occasionally don't fire the "Completed" output in a nativized build
How to achieve HLSL Multiple Render Target in Material blueprints?
Why does the REMOVE method of map container remove elements have memory leaks?
When I open UE4 4.24.3 it appears that. Does anyone know how to solve?
There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-37859 in the post.