modwright 0.1.0

package/knowledge/cyberpunk2077/vehicles.control.yaml

@@ -0,0 +1,475 @@
+game: cyberpunk2077
+topic: vehicles.control
+title: How the player controls a vehicle - remote control, the mount, vehicle classes, cameras,
+  weapons, destruction, and how Let There Be Flight adds lift
+facts:
+  - id: cp2077.vehicles.control.remote-control-native
+    claim: VehicleObject has a native SetVehicleRemoteControlled(enable, shouldUnseatPassengers,
+      shouldModifyInteractionState), with ToggleVehicleRemoteControlCamera(),
+      IsVehicleRemoteControlled() and SetIsHackable(enable) beside it. In script the perk, range and
+      not-mounted conditions belong to the quickhack that offers it, not to the call; whether the
+      native checks anything itself is unread (ModWright research calls it with no perk).
+    status: inferred
+    source: codeberg adamsmasher/cyberpunk@a2e6bb3 core/gameplay/vehicles.swift:68, :144, :146, :148;
+      core/components/scriptComponents/vehicleComponentPS.swift:1004-1018
+    tags:
+      - vehicle
+      - remote-control
+      - quickhack
+      - native
+  - id: cp2077.vehicles.control.remote-control-quickhack-flow
+    claim: The vanilla vehicle takeover quickhack (DeviceAction.TakeControlVehicleClassHack) builds a
+      TriggerVehicleRemoteControlEvent with all three flags true, releases any vehicle already
+      remote-controlled, and passes the event to TakeOverControlSystem.ReleaseControl, which ends
+      any camera or device control first; VehicleComponent.OnTriggerVehicleRemoteControlEvent then
+      calls SetVehicleRemoteControlled. It is offered only with the perk
+      Intelligence_Right_Milestone_1, V not mounted, the vehicle within
+      player.vehicleQuickHacks.maxRange, not already remote-controlled, and IsHackable().
+    status: inferred
+    source: codeberg adamsmasher/cyberpunk@a2e6bb3
+      core/components/scriptComponents/vehicleComponentPS.swift:1004-1018, :1060-1068;
+      core/systems/takeOverControlSystem.swift:183-225;
+      core/components/scriptComponents/vehicleComponent.swift:1608-1613
+    tags:
+      - vehicle
+      - remote-control
+      - quickhack
+      - takeovercontrolsystem
+  - id: cp2077.vehicles.control.remote-control-v-stays-standing
+    claim: "Under vehicle remote control V is not mounted: she stays where she hacked from, her weapon
+      is unequipped by the upper-body state while PlayerStateMachine.EntityIDVehicleRemoteControlled
+      is set, the HUD's signal meter is 1 - distance(V, vehicle) / maxRange, and a hit on an
+      unmounted V ends the remote control."
+    status: inferred
+    source: codeberg adamsmasher/cyberpunk@a2e6bb3
+      cyberpunk/player/psm/upperBodyTransitions.swift:1789-1792;
+      cyberpunk/UI/vehicles/remote_control_driving_hud.swift:30-104;
+      cyberpunk/player/player.swift:3265-3272
+    tags:
+      - vehicle
+      - remote-control
+      - player-state-machine
+      - release
+  - id: cp2077.vehicles.control.remote-control-input-context
+    claim: A remote-controlled vehicle switches V's input context to VehicleRemoteControlDriverContext.
+      In it ToggleVehCamera (on release) toggles the native remote camera and Exit (on press) calls
+      SetVehicleRemoteControlled(false, false, true); entering it adds the "RemoteControl" save
+      lock. Enabling through the context requires the vehicle's IsHackable(); disabling does not.
+      Steering and throttle routing are native.
+    status: inferred
+    source: codeberg adamsmasher/cyberpunk@a2e6bb3
+      cyberpunk/player/psm/inputContextTransitions.swift:1-39, :723-729, :1394-1423
+    tags:
+      - vehicle
+      - remote-control
+      - input-context
+      - save-lock
+  - id: cp2077.vehicles.control.remote-control-ends
+    claim: "Every script path that ends vehicle remote control calls SetVehicleRemoteControlled(false,
+      false, true): the Exit key, a hit on an unmounted V, and another take-control request. The
+      native also ends it on distance and reports that through
+      VehicleRemoteControlEvent.isDistanceDisconnect."
+    status: inferred
+    source: codeberg adamsmasher/cyberpunk@a2e6bb3
+      cyberpunk/player/psm/inputContextTransitions.swift:1394-1423;
+      cyberpunk/player/player.swift:3265-3272; orphans.swift:37280-37289
+    tags:
+      - vehicle
+      - remote-control
+      - release
+      - distance-disconnect
+  - id: cp2077.vehicles.control.vehicle-types-and-classes
+    claim: gamedataVehicleType is Bike 0, Car 1, Panzer 2. The script classes are CarObject and
+      BikeObject under WheeledObject, TankObject (empty script body) and AVObject (thruster effects
+      only); all extend VehicleObject. gamedataVehicleModel includes Basilisk 2 and Octant 17.
+    status: inferred
+    source: codeberg adamsmasher/cyberpunk@a2e6bb3 orphans.swift:5296-5302, :5313, :5328, :25080,
+      :26860, :36822; core/gameplay/vehicles.swift:2, :1356-1365
+    tags:
+      - vehicle
+      - vehicle-type
+      - tank
+      - av
+      - octant
+  - id: cp2077.vehicles.control.av-never-driven-by-player
+    claim: "No script path lets the player drive an AV: VehicleComponent.IsDriver returns false for any
+      AVObject, and AVs move by AI spline commands (AIVehicleOnSplineCommand) and scenes. A vehicle
+      meant to be driven should not be an AV-class record."
+    status: inferred
+    source: codeberg adamsmasher/cyberpunk@a2e6bb3
+      core/components/scriptComponents/vehicleComponent.swift:295-314; orphans.swift:47211-47250
+    tags:
+      - vehicle
+      - av
+      - driver
+  - id: cp2077.vehicles.control.tank-drive-model-hover
+    claim: "TankDriveModelData_Record (Vehicle_Record.TankDriveModelData()) carries
+      TankSpringsLocalPositions, TankSpringVerticalOffset, TankSpringStiffness, TankSpringDamping,
+      TankSpringDistance, TankSpringRadius, TankGravityMul, TankMaxSpeed, TankAcceleration,
+      TankDeceleration and TankTurningSpeed: a spring-supported drive model with a gravity
+      multiplier, the Basilisk's hover. It holds a ride height; nothing in it climbs."
+    status: inferred
+    source: codeberg adamsmasher/cyberpunk@a2e6bb3 orphans.swift:20924, :63836-63884
+    tags:
+      - vehicle
+      - tank
+      - basilisk
+      - drive-model
+      - hover
+  - id: cp2077.vehicles.control.tank-player-driven
+    claim: "The player drives a TankObject: VehicleTankDriverContext is entered in the Driving state for
+      a TankObject, PanzerHUDGameController runs, and mounting a tank's driver seat takes V's hit
+      shapes off and puts the tank on the targeting system's ignore list, so turrets and AI aim at
+      the tank."
+    status: inferred
+    source: codeberg adamsmasher/cyberpunk@a2e6bb3
+      cyberpunk/player/psm/inputContextTransitions.swift:1497-1528;
+      cyberpunk/UI/hud/custom/hud_panzer.swift:182-243;
+      core/components/scriptComponents/vehicleComponent.swift:1450-1453, :2930-2968;
+      cyberpunk/devices/securityTurret/securityTurret.swift:397-399
+    tags:
+      - vehicle
+      - tank
+      - basilisk
+      - targeting
+  - id: cp2077.vehicles.control.destruction-kills-mounted-v
+    claim: A destroyed vehicle's KillPassengers applies BaseStatusEffect.ForceKill to every mounted
+      child, the player included unless she has the Invulnerable god mode. A vehicle with the
+      Immortal god mode has its damage level capped at 2, so it does not reach the destroyed state
+      on its own. A remote-controlled vehicle's destruction cannot reach V this way, because V is
+      not mounted.
+    status: inferred
+    source: codeberg adamsmasher/cyberpunk@a2e6bb3
+      core/components/scriptComponents/vehicleComponent.swift:2667-2695, :2698-2711, :3957-3959
+    tags:
+      - vehicle
+      - death
+      - killpassengers
+      - immortal
+      - death-guard
+  - id: cp2077.vehicles.control.vehicle-weapons-need-driver-combat
+    claim: "Vehicle_Record.Weapons() lists VehicleWeapon_Records (slot, item, yaw and pitch limits,
+      cycle time, range, projectiles). The player fires them from the PSM state
+      DriverCombatMountedWeapons, entered from Drive when the record's DriverCombat type is
+      MountedWeapons and player.vehicle.canEnterDriverCombat is set - a mounted-driver state.
+      TankTurretComponent is a scripted alternative: it listens for ShootTertiary and fires an
+      Attack_GameEffect from a slot."
+    status: inferred
+    source: codeberg adamsmasher/cyberpunk@a2e6bb3 orphans.swift:21062, :65155-65192;
+      cyberpunk/player/psm/vehicleTransition.swift:12-14, :1335-1368, :2578-2662;
+      cyberpunk/vehicles/tankTurret.swift:2-63
+    tags:
+      - vehicle
+      - weapons
+      - driver-combat
+      - turret
+  - id: cp2077.vehicles.control.ltbf-lift-is-added-force
+    claim: "Let There Be Flight lifts a vehicle by adding force and torque, not by writing its
+      transform: a native system registers an update in the Vehicle bucket at
+      PhysicsExecuteAsyncQueries (the source's comments call UpdateTransformPrePhysics too early and
+      UpdateTransformPostPhysics too late), and per flying vehicle calls ForceEnablePhysics(), runs
+      the script update, then adds the result to vehicle->physicsData->force and ->torque for the
+      engine to integrate."
+    status: inferred
+    source: github jackhumbert/let_there_be_flight@6d7c1b7 src/red4ext/FlightSystem.cpp:88-131;
+      src/red4ext/Flight/Component.cpp:57-83
+    tags:
+      - vehicle
+      - flight
+      - lift
+      - red4ext
+      - ltbf
+  - id: cp2077.vehicles.control.ltbf-anti-gravity-drone-mode
+    claim: Let There Be Flight's Drone mode applies body-frame lift, surge and sway as force and pitch,
+      roll and yaw as torque, with a brake damping term and no gravity term; its Anti-Gravity Drone
+      mode adds world up (in the vehicle frame) times 9.81 times gravityFactor, cancelling gravity
+      so the vehicle holds where it is with no input.
+    status: inferred
+    source: github jackhumbert/let_there_be_flight@6d7c1b7
+      src/redscript/Flight/FlightModeDrone.reds:94-117;
+      src/redscript/Flight/FlightModeDroneAntiGravity.reds:16-19
+    tags:
+      - vehicle
+      - flight
+      - drone-mode
+      - ltbf
+  - id: cp2077.vehicles.control.ltbf-unmounted-input-path
+    claim: With no player mounted, Let There Be Flight takes a flying vehicle's surge from the vehicle's
+      own acceleration and deceleration and its yaw from turnX (the path its FlightEnable quickhack
+      flies an NPC car on); lift, pitch, roll and sway have no source on that path.
+    status: inferred
+    source: github jackhumbert/let_there_be_flight@6d7c1b7
+      src/redscript/Flight/FlightComponent.reds:640-672; src/redscript/Quickhacks/Actions.reds:8-27
+    tags:
+      - vehicle
+      - flight
+      - input
+      - ltbf
+  - id: cp2077.vehicles.control.physicsdata-layout-not-upstream
+    claim: vehicle::BaseObject's physicsData pointer (0x2D0) and the vehicle::PhysicsData layout (force
+      0x00, torque 0x0C, velocity 0x18, size 0x1E0) are declared only in Let There Be Flight's
+      RED4ext.SDK fork; upstream's vehicleBaseObject.hpp declares neither, and the two disagree by
+      four bytes on the drive inputs (upstream acceleration 0x264 and deceleration 0x268; the fork's
+      script offsets 0x268 and 0x26C behind an input block at 0x264). A plugin that writes vehicle
+      forces must re-derive both at the running game version.
+    status: inferred
+    source: github jackhumbert/RED4ext.SDK@b5ea591
+      include/RED4ext/Scripting/Natives/vehiclePhysicsData.hpp:69-105,
+      vehicleBaseObject.hpp:469-511; github wopss/RED4ext.SDK@ad72777
+      include/RED4ext/Scripting/Natives/vehicleBaseObject.hpp:38-42; github
+      jackhumbert/let_there_be_flight@6d7c1b7 src/redscript/Extensions/VehicleObject.reds:92-127
+    tags:
+      - vehicle
+      - red4ext
+      - layout
+      - version-fragile
+  - id: cp2077.vehicles.control.remote-control-from-script-on-a-spawned-car
+    claim: "A script can put a vanilla car under remote control with no perk and no quickhack: on a
+      Car-type vehicle spawned through DynamicEntitySystem, SetVehicleRemoteControlled(true, true,
+      true) makes IsVehicleRemoteControlled true, sets the player blackboard's remote-controlled
+      vehicle to it and V's upper-body state to 4 while she stays unmounted, and shows vanilla's own
+      remote-control HUD (the signal-strength bar and the neural-link icon). The car drives on V's
+      keys. The camera stays at V until ToggleVehicleRemoteControlCamera(), which gives a chase
+      camera that tracks the car; Exit hands control back to V."
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - vehicle
+      - remote-control
+      - camera
+      - hud
+      - drone
+    related:
+      - cp2077.vehicles.control.remote-control-native
+      - cp2077.vehicles.control.remote-control-v-stays-standing
+      - cp2077.vehicles.control.remote-control-input-context
+    detail: "Driven far from V, the view went to a loading icon and a black screen for a couple of
+      seconds: the world streams around V, not the camera. The test spawn fell back to
+      Vehicle.v_standard2_thorton_galena_nomad_player."
+  - id: cp2077.vehicles.control.remote-control-on-an-av-crashes
+    claim: "Vehicle.av_zetatech_octant, the base game's vehicle record with the Octant model, is type
+      Car in TweakDB but spawns as a vehicleAVBaseObject, reads hackable false, and holds its height
+      (no drop after the spawn). Calling SetIsHackable(true) and SetVehicleRemoteControlled(true,
+      true, true) on it from the CET thread crashed the game: an access violation reading 0x468 in
+      fn_4E98F8 (exe+0x4E9902, a method called on a null object, this+0x468)."
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - vehicle
+      - av
+      - remote-control
+      - crash
+      - drone
+    related:
+      - cp2077.vehicles.control.av-never-driven-by-player
+      - cp2077.vehicles.control.remote-control-native
+    detail: "Which object is null is unread: fn_4E98F8 reads this+0x468 and then a flag at +0x1FC of
+      what it finds, and its caller fn_25F95B4 is on the native's path. So a vanilla AV is not a
+      shortcut to a remote-controlled drone; such a drone stays a copied car- or tank-class
+      template. The tank drive model is Vehicle.v_militech_basilisk_inline5 at runtime (the source
+      tweak's inline numbering gives inline3)."
+  - id: cp2077.vehicles.control.remote-control-takes-a-tank-and-its-hover-height-is-the-spring-distance
+    claim: "Remote control takes a tank. On a spawned Vehicle.v_militech_basilisk
+      (vehicleTankBaseObject, hackable false), SetVehicleRemoteControlled(true, true, true) works as
+      on a car: vanilla's remote-control HUD with the maker's logo, the chase camera from the
+      toggle, and V's keys drive it on its spring hover. The hover height follows the drive model's
+      tankSpringDistance, read when the tank spawns. Changing the flat on a live tank does nothing,
+      and a respawn picks it up. Measured against the spawn point (vanilla 2.1 m springs): 1.06 m,
+      then 3.16 m at 4.2, and 7.48 m at 8.4, level (pitch 1.0, roll 0.0) and stable at speed."
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - vehicle
+      - tank
+      - remote-control
+      - hover
+      - drone
+    related:
+      - cp2077.vehicles.control.tank-drive-model-hover
+      - cp2077.vehicles.control.remote-control-from-script-on-a-spawned-car
+      - cp2077.vehicles.control.remote-control-on-an-av-crashes
+    detail: "Spawned under an overhang at 4x, the tank came up pitched 26 and rolled -43 until it was
+      driven into the open. That spawn also landed on V and hurt her as remote control switched on:
+      the first rc-on returned true and read remote=false a moment later, which is vanilla ending
+      remote control on a hit to an unmounted V
+      (cp2077.vehicles.control.remote-control-v-stays-standing; observed in game: \"The tank spawned
+      on Vs head, doing damage at the moment of taking control\"). A second rc-on held. The spawn
+      was then moved to put the tank 12 m ahead. The drive model's runtime name is
+      Vehicle.v_militech_basilisk_inline5, shared by every Basilisk, so an edit reaches them all;
+      the tests reset it between runs. No ledge or slope was tried (a city street)."
+  - id: cp2077.vehicles.control.a-light-small-tank-hull-runs-away-under-remote-control
+    claim: A tank of the mod's own on a small, light hull ran away under remote control. It was the
+      Basilisk's template with the Octant's hull boxes scaled 0.55 (mass 2363,
+      maxDepenetrationVelocity -1) and a drive model scaled down in mass, stiffness and damping but
+      not in its attitude gains. It landed on its end partly inside the ground; switching remote
+      control on flung it tens of metres at runaway speed through the surroundings, and the game
+      then crashed in an engine buffer overflow.
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - vehicle
+      - tank
+      - physics
+      - remote-control
+      - drone
+      - crash
+    related:
+      - cp2077.vehicles.control.remote-control-takes-a-tank-and-its-hover-height-is-the-spring-distance
+    detail: "The first run blamed the unlimited depenetration velocity and the light mass. A second run
+      showed the landing on its end was neither: at the Basilisk's mass with the depenetration
+      capped the hull still read pitch 89.4 at rest, and the cause was the hull's body frame
+      (cp2077.vehicles.control.chassis-body-frame-is-the-vehicle-frame). That the runaway itself
+      came from the springs pushing along the nose is inferred."
+  - id: cp2077.vehicles.control.chassis-body-frame-is-the-vehicle-frame
+    claim: A vehicle takes its frame from its chassis hull's physics body. The Octant AV's hull
+      (av_zetatech_octant__ext01_body_01.phys) has a body localToModel of a half turn about (0, 1,
+      1) (Y and Z swapped, mapped to the bone `base`), where the Basilisk's hull body is the model
+      frame (identity, no bone). On the Basilisk's template the Octant's boxes left the vehicle
+      resting at pitch 89.4 at either mass, looking level in the Basilisk's own meshes and on its
+      end in the Wyvern's. Baking the body frame into the boxes and the centre of mass, with
+      localToModel set to identity, made it spawn at pitch 0.0 and hover.
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - vehicle
+      - physics
+      - phys
+      - chassis
+      - drone
+    related:
+      - cp2077.vehicles.control.a-light-small-tank-hull-runs-away-under-remote-control
+    detail: Whether the engine honours localToModel for the rendered rig and ignores it for the
+      vehicle's transform, or the reverse, is not read; the rule that works is a chassis hull whose
+      body frame is the model frame. A ModWright new-custom-vehicle scaffold should check it.
+  - id: cp2077.vehicles.control.a-drone-sized-tank-drives-under-remote-control
+    claim: A tank of the mod's own on a drone-sized hull (1.5 x 1.45 x 0.75 m, the Basilisk's mass,
+      drive model and gains, nine springs inside the hull at 4.2) drives under native remote
+      control. Switched on, it rose to about 3.2 m over its spawn point and held level (pitch within
+      0.5) when still. It was flown smoothly for 107 m until the signal dropped at vanilla's range
+      (player.vehicleQuickHacks.maxRange 100), and it was left parked, level and undamaged.
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - vehicle
+      - tank
+      - remote-control
+      - hover
+      - drone
+    related:
+      - cp2077.vehicles.control.remote-control-takes-a-tank-and-its-hover-height-is-the-spring-distance
+      - cp2077.vehicles.control.remote-control-ends
+    detail: It "moves like a much larger object than it is" (as observed in game), it once sank into the
+      ground and was pushed back up by a car, and the Basilisk's hover glow was left standing at the
+      spawn point. The Basilisk's chase camera (boom 13.5 / 16 / 19.5 m aimed 5.75 m up,
+      airFlowDistortion true) framed it from far away and shook; the shake stopped once a session
+      edit set a 5 / 6 / 7.5 m boom and the airflow distortion off, both at once, so which one cured
+      it is not separated.
+  - id: cp2077.vehicles.control.remote-control-range-flat-not-live
+    claim: "Setting player.vehicleQuickHacks.maxRange in a session (TweakDB SetFlat to 300, read back as
+      300) did not let remote control take a vehicle 112 m away: SetVehicleRemoteControlled(true,
+      true, true) returned with IsVehicleRemoteControlled true, and the next reads had it false."
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - vehicle
+      - remote-control
+      - range
+      - tweakdb
+    related:
+      - cp2077.vehicles.control.remote-control-ends
+      - cp2077.vehicles.control.remote-control-quickhack-flow
+    detail: Whether the native reads the range once, reads another value, or whether a deployed tweak of
+      the flat works, is not established.
+  - id: cp2077.vehicles.control.remote-camera-toggle-without-remote-control-freezes-the-look
+    claim: ToggleVehicleRemoteControlCamera() on a vehicle that is not remote-controlled sets
+      PlayerStateMachine.IsVehicleRemoteControlCameraTPP true and leaves V able to walk but not turn
+      with the mouse; a second toggle frees her.
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - vehicle
+      - remote-control
+      - camera
+      - player-state-machine
+    related:
+      - cp2077.vehicles.control.remote-control-input-context
+  - id: cp2077.vehicles.control.remote-camera-choice-outlives-the-vehicle
+    claim: "The remote-control camera choice (PlayerStateMachine.IsVehicleRemoteControlCameraTPP)
+      outlives the remote control and the vehicle: it stayed true after the Exit key, a despawn and
+      a respawn, and the next SetVehicleRemoteControlled(true, ...) came up in the chase camera with
+      no toggle. A toggle then turns it off."
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - vehicle
+      - remote-control
+      - camera
+      - player-state-machine
+    related:
+      - cp2077.vehicles.control.remote-camera-toggle-without-remote-control-freezes-the-look
+  - id: cp2077.vehicles.control.a-released-tank-drops
+    claim: A tank hovers on its springs only while it is driven. Released from remote control by the
+      Exit key, the drone-sized tank fell from its hover to the ground at once.
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - vehicle
+      - tank
+      - hover
+      - remote-control
+      - release
+    related:
+      - cp2077.vehicles.control.remote-control-ends
+      - cp2077.vehicles.control.tank-drive-model-hover
+  - id: cp2077.vehicles.control.a-drone-sized-tank-tunes-no-further
+    claim: >-
+      A drone-sized tank is stable only at the Basilisk's tuning ratios. The light drone (2363 kg,
+      every mass-proportional term scaled by 2363 / 54431.1) hovered and drove with a slight wobble
+      on turns. Every session change away from that made it worse: - the attitude damping tankCTOD
+      x1.5 jerked less; - x3 spun; - all three tankCTO* gains x4 spun; - the "agile" set
+      (tankAcceleration x2, tankDeceleration x2.5,
+        tankTurningSpeed x1.5) spun it on its own.
+      The same agile set made the dense drone (54431 kg), steady at its defaults, jerk at idle.
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - vehicle
+      - tank
+      - physics
+      - tuning
+      - drone
+    related:
+      - cp2077.vehicles.control.a-drone-sized-tank-drives-under-remote-control
+    detail: "Which agile flat destabilises is not separated. Neither is why the gains do not scale
+      freely: a controller stepped at a fixed rate would explain it, and that is inferred. The
+      tankCTO* gains are evidently not normalized by mass inside the engine, since x4 on the light
+      drone spins while the dense drone carries 23 times the gain."
+  - id: cp2077.vehicles.control.chase-camera-boom-has-a-floor
+    claim: The remote-control chase camera follows the tppCameraPresets' boomLength from the Basilisk's
+      13.5-19.5 m down to about 2-3 m, then no closer. Booms of 2 / 3 / 4.5 m were "still too far",
+      1.2 / 1.8 / 2.7 m "a little closer", and 0.72 / 1.08 / 1.62 m "unchanged". Session edits of
+      the preset flats reached the camera.
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - vehicle
+      - camera
+      - remote-control
+      - tweakdb
+    related:
+      - cp2077.vehicles.control.a-drone-sized-tank-drives-under-remote-control
+    detail: "What sets the floor is not read. The candidate is the vehicle's bounds: the Basilisk's
+      bodycar mesh is chunk-masked but still in the entity. Also unread are the camera's collision
+      and a minimum distance in the camera code."