Get available levels; Getters and Setters for types on actors & static meshes by jasonashton · Pull Request #364 · tempo-sim/Tempo

jasonashton · 2026-01-14T21:55:08Z

No description provided.

jasonashton · 2026-01-15T13:23:28Z

TempoCore/Source/TempoCore/Private/TempoCoreServiceSubsystem.cpp

 	ResponseContinuation.ExecuteIfBound(Response, grpc::Status_OK);
 }

+void UTempoCoreServiceSubsystem::GetAvailableLevels(const GetAvailableLevelsRequest& Request, const TResponseDelegate<AvailableLevelsResponse>& ResponseContinuation) const


This really just gets any assets at a path. Not sure if we should add more filtering to truly get all levels or make it a more generic RPC

I mean I think this RPC would be very useful but it shouldn't have a name specific to levels. We could have both and they could share a helper. Is it possible to find only levels? Does the umap extension help?

I can make it a more generic RPC, it does look like there's a way to filter by levels and add a more specific RPC, or we can filter client side maybe by .umap

I think two RPCs, one for levels and one for all non-level assets would be best. I don't really think of levels as "assets"

jasonashton · 2026-01-15T13:27:13Z

TempoSensors/Source/TempoLabels/Private/TempoActorLabeler.cpp

 		UnLabelActor(*ActorItr);
 	}
-	
+


jasonashton · 2026-01-15T13:27:58Z

TempoSensors/Source/TempoLabels/Public/Labels.proto

+
+message SetActorTypeSemanticIdRequest {
+  string actor_type = 1;    // e.g., "CBP_QuantumCharacter_C" (class name)
+  int32 semantic_id = 2;    // 0-255 to set, -1 to revert to DataTable default


Not sure reseting to datatable default is the right move here

jasonashton · 2026-01-15T13:30:56Z

TempoWorld/Source/TempoWorld/Public/WorldState.proto

  bool include_hidden_components = 5;
 }

+// Request actors near a world position (instead of near a named actor)


comment in () not necessary

pete-tempo

I'm generally fine with this, but just throwing out a couple of alternatives to consider:

Do we need runtime overrides? We can't decide our label schema at edit time?
Could we instead drive the data table from a json file that users can edit? You could set it up to re-read it and relabel everything at runtime.
I believe the data table is only read once right now. So do you need override maps, or should we just edit the maps we loaded from the data table?

pete-tempo · 2026-01-16T12:59:42Z

TempoSensors/Source/TempoLabels/Public/Labels.proto

+
 service LabelService {
  rpc GetInstanceToSemanticIdMap(TempoScripting.Empty) returns (InstanceToSemanticIdMap);
+  rpc GetAllActorLabels(GetAllActorLabelsRequest) returns (GetAllActorLabelsResponse);


Does this make GetInstanceToSemanticIdMap unnecessary? If so we can remove that

pete-tempo · 2026-01-16T13:04:36Z

TempoSensors/Source/TempoLabels/Public/Labels.proto

+message StaticMeshTypeInfo {
+  string mesh_path = 1;          // Full asset path
+  string display_name = 2;       // Short name extracted from path
+  int32 instance_count = 3;      // Number of components using this mesh


Maybe update the comment to reflect "active" or "current" components. Component "instances" maybe? To differentiate between component classes

jasonashton · 2026-01-18T21:12:07Z

I'm generally fine with this, but just throwing out a couple of alternatives to consider:

Do we need runtime overrides? We can't decide our label schema at edit time?

Could we instead drive the data table from a json file that users can edit? You could set it up to re-read it and relabel everything at runtime.

I believe the data table is only read once right now. So do you need override maps, or should we just edit the maps we loaded from the data table?

My goal is to be able to ship a few pre-built levels that we can insert meshes and actors into, and generally avoid having to go into unreal and edit it as much as possible. It'd be much easier to set up a base environment and be able to set up scenarios, different layouts, etc. without re-packaging the level.

Also part of this is that end users can decide their own labels depending on their needs

jasonashton · 2026-01-18T21:14:32Z

Could we instead drive the data table from a json file that users can edit? You could set it up to re-read it and relabel everything at runtime.

I looked into editing the table directly and I do think it makes sense to keep parity with the json data table, but it's stored as a uasset, do you have any ideas about this?

pete-tempo · 2026-01-18T22:11:02Z

Could we instead drive the data table from a json file that users can edit? You could set it up to re-read it and relabel everything at runtime.

I looked into editing the table directly and I do think it makes sense to keep parity with the json data table, but it's stored as a uasset, do you have any ideas about this?

Yeah you can fill a data table from a json. I don't know if it works at runtime. https://dev.epicgames.com/documentation/en-us/unreal-engine/BlueprintAPI/EditorScripting/DataTable/FillDataTablefromJSONFile

pete-tempo · 2026-01-23T12:02:27Z

TempoSensors/Source/TempoLabels/Private/TempoActorLabeler.cpp

 	{
 		// We've labeled this Actor before. Make sure all the components are labeled.
-		LabelAllComponents(Actor, *ActorIdPair);
+		// Copy to avoid dangling reference if LabeledObjects is modified during labeling.


LabeledObjects would have to be modified between the if and the next line right? Is that possible? I thought it was all on the same thread?

jasonashton had a problem deploying to fork-pr-environment January 14, 2026 21:55 — with GitHub Actions Failure

jasonashton commented Jan 15, 2026

View reviewed changes

TempoSensors/Source/TempoLabels/Private/TempoActorLabeler.cpp

UnLabelActor(*ActorItr);

}

Copy link
Copy Markdown

Contributor Author

jasonashton Jan 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove

jasonashton commented Jan 15, 2026

View reviewed changes

jasonashton temporarily deployed to fork-pr-environment January 15, 2026 15:27 — with GitHub Actions Inactive

pete-tempo reviewed Jan 16, 2026

View reviewed changes

jasonashton temporarily deployed to fork-pr-environment January 21, 2026 15:29 — with GitHub Actions Inactive

pete-tempo reviewed Jan 23, 2026

View reviewed changes

jasonashton added 3 commits January 29, 2026 13:01

First attempt at actor re-labeling

7d57182

Add Set Component Semantic Id

6d6cf9a

Change class id for actor types, not individual actors

5142ba1

jasonashton added 8 commits January 29, 2026 13:01

Add Actors Near Position RPC

e55efee

add rpc to get available levels

6b553a8

Get and Set static mesh semantic IDs

7ef9a6a

cleanup

fe0da5e

Runtime pointer fix

110515f

low memory package option

4506865

Evict frame when falling behind

e91a1c7

Pass FInstanceSemanticIdPair by value to prevent segfault

8702754

jasonashton force-pushed the jashton/get-set-static-types branch from 442486b to 8702754 Compare January 30, 2026 17:13

jasonashton temporarily deployed to fork-pr-environment January 30, 2026 17:13 — with GitHub Actions Inactive

jasonashton deployed to fork-pr-environment January 30, 2026 17:13 — with GitHub Actions Active

jasonashton temporarily deployed to fork-pr-environment January 30, 2026 17:13 — with GitHub Actions Inactive

Conversation

jasonashton commented Jan 14, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

pete-tempo left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

jasonashton commented Jan 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jasonashton commented Jan 18, 2026

Uh oh!

pete-tempo commented Jan 18, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

jasonashton commented Jan 18, 2026 •

edited

Loading