Question about some variable hidden in the editor (bCanEverTick & Mobility on SK)

Development Pipeline & Plugins
, ,
1

Hello !

We have two small questions about some variable visibility in the Editor:

  • FTickFunction::bCanEverTick is not visible in the editor
  • Same question on why the Mobility selector is not visible on SkinnedMeshComponent and descendent

For context, we made a performance pass on a lot of blueprints, using a tool in C++ to change the mobility of every components as well as completely removed the tick from most of them. However we’ve had some exceptions, where the component needed to be movable and have a tick (because we need to have physics on them), but we couldn’t do it in the editor, we had to modify the engine to display those values.

But before submitting this change on our repo, we want to ask if there is a specific reason to hide them ?

2

Hi there,

You are most likely safe to make these changes on your repo.

The mobility selector’s category is hidden at the UPrimitiveComponent level. Typically this will be overridden in derived classes when it is applicable. Since it has not been overridden in the skinned mesh component (and others) it’s possible that it was intentional but it could also just be an oversight.

As for bCanEverTick. I think this was hidden in blueprint to keep things unambiguous. Since blueprints have another method of toggling this by implementing the tick event (or not).

- Louis