本文へ移動
cccskills
無料GitHub で公開

check-ue5-limitations

Tells you what CARLA on UE 5.5 (branch ue5-dev) cannot do that UE 5.8 (ue58-dev) can, so you do not attempt an unsupported workflow there — no Autoware integration, no ROS 2 middleware choice (FastDDS only), no DLSS or ray-traced-lens camera, no OFPA large-map mount so Town12/13/15 load black, and a few missing World/Actor methods. Also states what is identical, so the ue58 skills can be used directly for everything else. Use when working against a 5.5 checkout, when a ue58 skill's step has no counterpart, or when deciding whether a feature request is possible on 5.5 at all.

インストール方法を見る

含まれるファイル(5)

  • SKILL.md6.8 KB
  • references/gaps.md6.1 KB
  • scripts/check_env.sh2.2 KB
  • scripts/env.sh3.2 KB
  • scripts/gaps.sh8.2 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

What UE 5.5 cannot do

Paths. scripts/… and references/… below are relative to the directory holding this SKILL.md. Your working directory is the user's project, not that directory, so prefix them with its absolute path or the command is not found.

5.5 and 5.8 are the same CARLA line, not parallel products. PythonAPI/carla/src/Sensor.cpp is byte-identical between the branches, Actor.cpp differs by 2 lines and World.cpp by 22. 5.8 is the later revision — the one released as CARLA 1.0 — so treat 5.5 as an earlier point release. It still declares 0.10.0, which is also what every ue58 build reported before that release, so the version string does not separate the two: the branch does.

The practical consequence: the ue58 skills are the procedures for 5.5 too, minus the five gaps below. There is no ue5 mirror of each skill because there is almost nothing to mirror.

Instructions

Progress:
- [ ] Step 1: bash scripts/check_env.sh
- [ ] Step 2: list  — the gaps, and which ue58 skill each one breaks
- [ ] Step 3: check — confirm against the tree in front of you
- [ ] Step 4: then use the ue58 skill, minus the MISSING lines
source scripts/env.sh

bash scripts/gaps.sh list      # needs no checkout
bash scripts/gaps.sh check     # this tree's gap markers
bash scripts/gaps.sh diff      # measured, if a ue58 tree is also present

The five gaps

GapWhat is absent on 5.5What it breaks
ROS 2 middlewareros2/middleware/ (RMW abstraction, QosProfile.h, ActiveMiddleware) and the CARLA_CYCLONEDDS_* / CARLA_ZENOH_C_* optionsFastDDS only — --rmw cyclonedds / --rmw zenoh do not exist ([[run-carla-ue58-server]]); [[add-ros-publisher]]'s QosProfile.h step does not apply
Autowareboth publishers, the control subscriber, AutowareSteeringCompensation.h, sensor.other.autoware_gnss, sensor.other.vehicle_status[[run-autoware-ue58]] has no 5.5 counterpart
DLSS + ray-traced lensenable_dlss, dlss_screen_percentage, SceneCaptureCamera_RayTracedLens.cpp, CARLA_DLSS_SDK_PATHsensor.camera.rt_lens does not exist; [[create-sensor]]'s DLSS attributes are 5.8-only
OFPA large-map mountMountExternalPackageRoots in Carla.cppTown12 / Town13 / Town15 load with an empty World Partition and a black screen. 5.8 absorbed this patch upstream; on 5.5 it is still a manual fix
A few API additionsWorld.get_ego_spawn_points, World.set_publish_tf / get_publish_tf, World.spawn_custom_mesh, Actor.enable_constant_acceleration / disable_constant_accelerationthose calls raise AttributeError; the rest of the python-api group applies unchanged

What is identical — every ue58 finding transfers

CMake-only build (no Makefile, Util/Tools not Util/BuildTools); all six package targets; the MapsToCook default including uncookable Town15, so an out-of-the-box package build fails on 5.5 too; the single-dash -ros2 flag; the actor factories and their PropParameters.json / WalkerParameters.json / VehicleParameters.json registration; the entire CarlaTools header set.

The known defects are shared too, which means the ue58 notes apply verbatim: RecastBuilder missing from Util/DockerUtils/dist (map-import navmesh silently produces nothing), Environment.sh not setting CARLA_BUILD_TOOLS_FOLDER (so Import.sh invokes /Import.py and exits 2), and the #if 0 // @CARLAUE5 wheel block that stops GenerateNewVehicleBlueprint producing a drivable vehicle.

Examples

Example 1: "run Autoware against my 5.5 build"

list — gap 2. Not possible: none of the publishers, the subscriber or the two sensors exist. Say so; do not adapt [[run-autoware-ue58]]'s steps, they have nothing to bind to.

Example 2: "start the server with cyclonedds"

Gap 1. 5.5 has no middleware abstraction, so FastDDS is the only transport. -ros2 itself works.

Example 3: "load Town12 and it's black"

Gap 4, and it is the expected outcome on 5.5, not a broken install. The mount patch is absent, so the World Partition comes up empty. Either apply the patch or use a non-partitioned town.

Example 4: "is this checkout 5.5 or 5.8?"

check. It classifies by markers rather than by branch name — ros2/middleware, the Autoware publishers, MountExternalPackageRoots — and reports the engine branch the tree names for itself (ue5-dev-carla vs ue58-dev-carla).

Example 5: "import a prop on 5.5"

Nothing in gap 1-5 touches it: use [[import-carla-ue58-prop]] directly. Same for walkers, packaging, and running a server.

Troubleshooting

Problem: check says the tree has 5.8 markers Cause: CARLA_UE5_ROOT points at a ue58-dev checkout. Solution: use the ue58 skills directly — none of these gaps apply.

Problem: a ue58 skill's step fails on 5.5 and it is not in the gap list Cause: the list covers structural differences found by diffing the trees; a behavioural difference at runtime would not appear in it. Solution: say the behaviour is unverified on 5.5 — no 5.5 build has ever been run here — and investigate rather than assuming the gap list is exhaustive.

Problem: diff refuses to run Cause: it needs both trees. Solution: export CARLA_UE58_ROOT as well, or use list / check.

Outputs

Nothing is written and nothing is started: all three modes are read-only. list prints the gap catalogue, check reports which markers this tree has, and diff prints a measured comparison of the ROS 2 layer, the CMake options, the Python binding line counts and the declared versions.

Per-gap evidence — file paths, reference counts, and what each gap means for which skill — is in references/gaps.md.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Adds a new ROS 2 message type to CARLA's native ROS 2 interface — the hand-written POD struct under LibCarla/source/carla/ros2/types/msg, its Fast-CDR serialize/deserialize pair, the RIHS01 type hash computed in Docker, the CdrTopicInfo registration and the type-hash test. Use when the user asks to "add a ROS message type", "support sensor_msgs/X in CARLA", "add a carla_msgs type", "why is my type hash warning appearing", or needs a message CARLA does not publish yet. There is no IDL codegen — every step is manual.

日本語の概要は準備中です。原文の説明を表示しています。

carla-simulator/carla-agentic-tools42026年9月12日 更新

Adds a new topic to CARLA's native ROS 2 interface — a publisher (BasePublisher + PublisherImpl, topic suffix, QoS, registration in ROS2::GetOrCreateSensor, a ProcessDataFrom* entry point and its call site in the UE4 plugin) or a subscriber that lets ROS drive an actor. Also covers adding a middleware (RMW) behind IPublisherMiddleware. Use when the user asks to "publish X to ROS from CARLA", "add a ROS topic/publisher/subscriber", "make the obstacle/lane-invasion sensor publish", "add odometry to ROS", or "add another RMW".

日本語の概要は準備中です。原文の説明を表示しています。

carla-simulator/carla-agentic-tools42026年9月12日 更新

Reads and summarises ScenarioRunner output — the criteria pass/fail tables from --output/--file, the machine-readable --json and --junit result files, and the criteria JSON written alongside a --record recording — and runs the metrics module (metrics_manager.py) to compute custom measurements over a recorded run offline, without the simulator. Use when the user asks "did the scenario pass", "why did it fail", "summarise these results", "compare these runs", or wants distance/speed/lane metrics from a recording.

日本語の概要は準備中です。原文の説明を表示しています。

carla-simulator/carla-agentic-tools42026年9月12日 更新

Gets actor and level 3D bounding boxes and projects them into a camera image as 2D boxes — the dataset-annotation workflow. Lists box geometry, draws 3D boxes in the world via debug, or captures one camera frame and writes an annotated PNG plus a JSON of 2D boxes for matching actors. Use when the user asks to "get bounding boxes", "draw boxes around the cars", "project boxes onto the camera", or "generate a detection dataset / annotations".

日本語の概要は準備中です。原文の説明を表示しています。

carla-simulator/carla-agentic-tools42026年9月12日 更新

Builds CARLA (branch ue4-dev, Unreal Engine 4.26) from source on Linux end-to-end — UE4 fork, the Carla server (editor C++ modules), the LibCarla Python client wheel, and content — then verifies them against a from-source server. Optionally builds the native ROS 2 interface in (ROS2=1 → --ros2, Fast-DDS/CycloneDDS/Zenoh), which is compile-time only and cannot be enabled later. Use when the user asks to "build CARLA from source", "compile CARLA ue4-dev", "set up CARLA on Ubuntu (incl. 24.04)", "build CARLA with ROS2 support", or "produce a CARLA server + client wheel". Cooking a distributable Dist/ package is a separate skill (package-carla-ue4); running the build is run-carla-server.

日本語の概要は準備中です。原文の説明を表示しています。

carla-simulator/carla-agentic-tools42026年9月12日 更新

Builds CARLA on Unreal Engine 5.8 from the ue58-dev branch using its CMake build system — configure a preset, then build the carla-unreal / carla-unreal-editor / carla-python-api-install / launch targets — with ROS 2, DLSS, RSS and cook-scope options, and the engine-side build of the CarlaUnreal UE 5.8 fork. There is no Makefile and no Util/BuildTools in this tree, so every UE4 `make` recipe is invalid here. Use when the user asks to "build CARLA UE5", "build ue58-dev", "compile CARLA with cmake", "rebuild the Python API", or hits a CMake configure or target failure.

日本語の概要は準備中です。原文の説明を表示しています。

carla-simulator/carla-agentic-tools42026年9月12日 更新

carla-simulator のスキルをすべて見る

このスキルの問題を報告する