Skip to content

feat(api): expose simGetClockRate RPC (salvage credit @davidtr99 #4612)#9807

Open
Bartok9 wants to merge 1 commit into
microsoft:mainfrom
Bartok9:aerial/salvage-sim-clock-rate-4612-20260723
Open

feat(api): expose simGetClockRate RPC (salvage credit @davidtr99 #4612)#9807
Bartok9 wants to merge 1 commit into
microsoft:mainfrom
Bartok9:aerial/salvage-sim-clock-rate-4612-20260723

Conversation

@Bartok9

@Bartok9 Bartok9 commented Jul 23, 2026

Copy link
Copy Markdown

Summary

Salvage of #@davidtr99's useful clock-rate RPC (#4612), rebased onto current main.

Exposes simGetClockRate on the RPC server/client (true sim/wall scale via ClockFactory::getTrueScaleWrtWallClock) plus a matching Python VehicleClient.simGetClockRate. Naming uses the sim* prefix to match neighboring pause/continue APIs while preserving the original idea and credit.

Credit

Original work: @davidtr99 in #4612 (opened 2022; VERY OLD / quiet — §15a salvage).

Motivation

Scripts that change ClockSpeed have no first-class way to read back true scale vs wall time from the running sim.

Verification

  • C++ bind + client method compile-path aligned with existing simIsPaused pattern.
  • Python client mirrors other thin RPC wrappers.
  • No simulator behavior change beyond additive RPC.

AI-assisted; human-reviewed.

Claim: bartok
Operator: bartok
Campaign: aerial-drone

Add simGetClockRate on C++ RPC client/server and Python VehicleClient,
crediting @davidtr99 microsoft#4612. Returns ClockFactory true scale vs wall clock.

Signed-off-by: Bartok9 <danielrpike9@gmail.com>
@Bartok9
Bartok9 force-pushed the aerial/salvage-sim-clock-rate-4612-20260723 branch from bf567d9 to c675e22 Compare July 23, 2026 09:23
@Bartok9 Bartok9 changed the title salvage: expose sim clock rate API (credit @davidtr99 #4612) feat(api): expose simGetClockRate RPC (salvage credit @davidtr99 #4612) Jul 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant