Skip to content

Port ue4-dev vehicle/physics/control API to ue5-dev (Category 5: Vehicle API) #9630

@youtalk

Description

@youtalk

Is your feature request related to a problem? Please describe.

The ue4-dev branch contains vehicle physics, control API additions, and actor component functions that have not been ported to ue5-dev. Part of the broader effort discussed in #9581.

Describe the solution you'd like

Port the following vehicle/API improvements as new implementations targeting ue5-dev:

  • PR #0l feat(vehicle): wheel rotation API and telemetry — wheel pitch rotation API (a14b2d943), server-side wheel rotation (03e71c251), telemetry data exposure (01b1ede51), WheelTelemetryData Python list conversion (3647beaf0), GetVehiclePhysicsControl with physics off (fda970b88), physics disabled wheel check (e7e3987f7), COM height 0.52m for realistic sedan dynamics (bd6860437)
  • PR #0m feat(api): new force/impulse and actor component functions — force/impulse at location (60fdd57e0), actor component getters (0b13c72d6), bone transform retrieval (5d6862c3d), socket name retrieval (3eb9a7626), debug shape clear (00ff27ac3), GeoLocation→Transform conversion (5ca6323f4), custom map path loading (842f44294)

Describe alternatives you've considered

Cherry-picking from ue4-dev was considered but rejected due to UE4→UE5 differences.

Additional context

This is Category 5 of the ue4-dev→ue5-dev porting effort. PRs #0l and #0m are independent and can be reviewed in parallel.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions