C++ changes are not reflected in existing Blueprint properties after compiling with Rider

Development Getting Started & Setup
, , , ,
1

I’m using Unreal Engine 5.7 with Rider 2026.2.1, and my project is opened directly in .uproject mode.

I’m currently not using Live Coding. When I create a new C++ class, I normally use Rider’s Unreal integration / UnrealLink to trigger a build, because the new C++ class sometimes does not appear in the Content Browser’s C++ Classes section until the project has been compiled.

However, I noticed a different issue when working with a Character Blueprint.

For example, suppose I create a camera component in my C++ Character class and set its relative location in the constructor:

Camera->SetRelativeLocation(FVector(0, 0, 100));

Then I compile the project from Rider and change it to:

Camera->SetRelativeLocation(FVector(0, 0, 150));

The C++ code definitely compiles successfully, but the existing Blueprint derived from this C++ class still shows the old camera location (Z = 100).

Restarting Unreal Editor does not seem to change it either.

However, if I manually change the transform in the Blueprint, or use Restore to Default, the new C++ value (Z = 150) can appear.

Interestingly, if I have a move (such as “Create a new Cam Component”) from the same C++ class after compiling, it correctly refresh the new component.

So I’m wondering:

Is this expected Unreal Engine behavior?

Does an existing Blueprint store its own serialized/default property values, so changes made in the parent C++ constructor are not automatically propagated to the existing Blueprint?

Or could this be related to Rider’s UnrealLink/RiderLink integration or the fact that I’m not using Live Coding?

Environment:

  • Unreal Engine 5.7
  • Rider 2026.2.1
  • Project opened in .uproject mode
  • Using UnrealLink / RiderLink
  • Live Coding disabled

Any explanation of how Unreal handles C++ constructor defaults, CDOs, and existing Blueprint defaults would be greatly appreciated.

2

I’m having a similar issue, and it is specifically with camera component.

(5.8.1)

No matter what i do, my blueprint can’t see any of the camera information I created. The boom is gone, the camera component is gone, it’s all gone. ‘Poof’.

It’s declared in the code correctly everywhere. It’s almost as if I have to rebuild the blueprint from scratch just to get the camera component to exist for it.

Unfortunately for me I have tons and tons of blueprint specifically built systems that I am slowly moving to c++; so rebuilding that blueprint from scratch doesn’t help me at all but hinders me.

I’ve tried unparenting and reparenting, nada.

Something hinky with camera components is going on is all I can figure.

edit:

welp in order to try and fix why UE can’t see things correctly I’m once again back to compiling, this time 4205 files. (just the project itself, not the full engine, that would take 50 years.)

It’s mind boggling to me how I barely have written 20 files yet the compilation of the project keeps magically getting larger and larger.