Can't assign Curve Table as variable!

[AirmassStudios]

Hi, can’t think of a method to reference a curve table in blueprint editor. “Evaluate Curve Table Row” node accepts input (Curve Table Object Reference) but there simply isn’t such variable type, nor can I import my curve tables as named objects. What to do? I’m collecting weather preset curves in curve tables, and without ability to switch one table to another, I’d imagine I’d have to basically repeat same long row of evaluations, based on weather and hardcoded curve tables.

By all accounts, no curve table reference type looks like a bug or undone work in UE (5.7.3)

[MajorT]

Hey @AirmassStudios

Yes, that is intended.

Instead you should use the CurveTableRowHandle.

A row handle generally is a CurveTable asset and a RowName mapped together.

To evaluate a row, you need to break the struct first.

[AirmassStudios]

Thanks, but I don’t quite understand. My curve tables are bunch of weather preset variables set by weather type - i.e. “rainy day”, “sunny day”, etc. There’s actually quite a bunch of rows, from cloudCoverage to exponentialFogDensity to rainSpawnRate to whatever, over 24 hours.

What I’m trying to do is assign curve table to set weather type, i.e. CT_Sunny, CT_rainy, and then grab named rows out of it and find value at time.

I kind of don’t get how I would do it based on rows themselves, because entire curve tables are different (I need to switch out curve tables per daily weather).

[MajorT]

The CurveTable itself is not marked as BlueprintType, therefore you can’t use the CurveTable asset directly.

Instead you could switch over to DataRegistries (one per weather preset) or migrate your code into DataTables/DataAssets

[AirmassStudios]

This would destroy bunch of handy bezier Curves I have to make things happen smoothly at runtime (more or less, I’m using slight time compression).

I GUESS I could - rather than have a curve table per weather, have curve table per variable, so I’d have something like DT_CloudCoverage and named rows are “Sunny”, “Rainy”, etc - since they’re literal text (row name) fed into evaluation node, I can change/switch on them much easier.

But that would make it pretty annoying to actually build weather data.

[MajorT]

I don’t see how using DataRegistries would “destroy” anything.
They’re essentially like you’re CurveTables but on a global scale.

Meaning you can have one Registry per WeatherPreset.

Get a list of all RegistryId’s (the items) and evaluate them like a float curve table.

Whereas the RegistryType would be e.g., “sunny”, “rainy”, etc