Control traffic lights in a running CARLA simulation. Change their color, switch them off, hold a fixed state, adjust phase durations, or restore normal cycling, targeting individual lights, junctions, nearby lights, or the whole map.
Adjust how autopilot vehicles behave in CARLA, including speed, following distance, traffic light responses, and lane changes. Apply settings across traffic or to individual vehicles, and configure seeds and synchronization for repeatable traffic runs.
Explore roads, lanes, and junctions in a CARLA simulation map through text reports and visual overlays. Locate places described in everyday language, inspect nearby lane details, and trace a path forward or backward along a lane.
Record a running CARLA simulation to a .log file for later replay or inspection. Capture object creation, movement, and traffic-light states, optionally include controls and velocities, and verify that the recording contains simulation frames.
Control street, building, and vehicle light sources in CARLA. Switch groups on or off, adjust their color and brightness, and enable automatic nighttime lighting to prepare illuminated city scenes or blackouts.
Create and edit CARLA driving routes by placing waypoints and scenario triggers in the simulator. Inspect routes visually, review summary tables, check XML structure and trigger positions, and convert older route files to the 2.x format.
Read and change a running CARLA server’s timing, physics substeps, and rendering settings. Switch between client-controlled steps and automatic progression, keep Traffic Manager synchronization aligned, and read back the settings to verify each change.
Inspect data published by a ROS 2-enabled CARLA server using Docker, without installing ROS 2 locally. Check topic contents and rates, run a sensor-equipped vehicle demo, and view lidar data and supported map markers in RViz2.
Run CARLA routes with a driving agent through ScenarioRunner, including scenarios available only in route mode. Inspect route contents, execute one or all routes, and obtain reports on completion, collisions, traffic lights, and other criteria.
Import FBX 3D models into CARLA as props that can be placed through its Python API. Handles category tags, measured dimensions, asset registration, and spawn checks for individual files or folders of models.
Builds CARLA's ue4-dev branch on Linux, producing the Unreal Engine 4.26 editor, server modules, and an installed Python client package. Fetches required content, optionally compiles native ROS 2 support, and verifies the build against a source-built server.
Drives a CARLA vehicle to a specific destination using navigation agents that plan routes, avoid obstacles, and obey traffic lights. Can also plan and draw a route between two points without moving the vehicle.
Run Scenic traffic scenarios on a CARLA server. First test whether a valid scene can be generated, then simulate with limits on runs and steps, record the outcome, and restore the world's asynchronous setting afterward.
Creates a Python agent skeleton for CARLA Leaderboard and checks its sensor configuration offline against the installed version’s rules. Covers version-specific initialization, driving logic, and ROS1 or ROS2 agent integration.
Launches a CARLA RPC server a carla.Client can connect to, working out for itself what you pointed it at — a downloaded/extracted release, a package cooked inside a checkout, or a source checkout run through the UE4 editor — headless or windowed, and shuts it down cleanly. ROS2=1 starts it with the native ROS 2 interface active (--ros2, --rmw=fastdds/cyclonedds/zenoh, --ros-domain-id). Use when the user asks to "run/start the CARLA server", "boot CARLA headless", "launch CARLA with a window", "run the CARLA I downloaded", "start CARLA with ROS2 enabled", or "serve a packaged CARLA build".
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Create, migrate, improve, or debug detailed vehicle assets for CARLA using Blender and Unreal, including reference-based geometry, materials, wheels, physics, lights, and runtime validation. Use for vehicle asset authoring rather than ordinary traffic spawning or map decoration.
The English summary is being prepared. Showing the original description.
Gets a custom map into CARLA on UE 5.8 — the four distinct routes and which one to pick — via Util/Tools/Import.py for FBX+OpenDRIVE assets into a source build, CARLA_MAPS_TO_COOK to ship a map inside a package, or client.generate_opendrive_world() for an OpenDRIVE-only map at runtime with no build at all. Covers where imported assets land, why an imported map cannot be loaded from a package by name, and the four capabilities the UE4 skill has that ue58 lacks — standalone asset packages, their installer, semantic-material tagging, and a pedestrian navmesh that is generated but silently skipped. Use when the user asks to "import a map", "add a custom map", "load my .xodr", "package my own town", or "create a standalone map package".
The English summary is being prepared. Showing the original description.
Imports FBX meshes into CARLA on UE 5.8 as spawnable props — drives the editor headlessly to import the mesh, derives the prop size from its measured bounds, and registers it in PropParameters.json so it appears in the blueprint library as static.prop.<name>. Handles the FBX unit-scale problem, verifies the result against a running server, and can revert cleanly. Use when the user asks to "import a prop", "add a custom mesh/object to CARLA", "make my model spawnable", or a prop imports but never shows up in the blueprint library.
The English summary is being prepared. Showing the original description.
Imports a pedestrian into CARLA on UE 5.8 as a spawnable, animating walker — imports the skinned FBX bound to CARLA's shared pedestrian skeleton, duplicates a donor walker blueprint and repoints it at the new mesh, and registers it in WalkerParameters.json as walker.pedestrian.<id>. Can also export a shipped walker to FBX, which is how you obtain a rig-conforming mesh to start from. Use when the user asks to "import a walker/pedestrian", "add a custom character", "clone a walker", or has a walker that spawns but stands still.
The English summary is being prepared. Showing the original description.
Cooks and packages a shippable CARLA server from a UE 5.8 ue58-dev checkout via the CMake `package` targets (shipping/development/debug/test), scoping the cook with CARLA_MAPS_TO_COOK, and inspects an existing package for the failures a green build hides — stale pak/ucas mismatch, missing staged OpenDrive/TM road data, missing post-process profiles, and Town15's uncookable content. Use when the user asks to "package CARLA UE5", "cook a map", "build a shipping server", "make a distributable CARLA", or a package builds but renders black / has no maps.
The English summary is being prepared. Showing the original description.
Runs the Autoware autonomous-driving stack against CARLA on UE 5.8 over CARLA's native ROS 2 interface — no bridge process. Reports the DDS contract (rt/vehicle/status/* out, rt/control/command/* in), the Autoware-only sensor blueprints, generates the lanelet2 + point-cloud map artifacts Autoware needs instead of an .xodr, and drives the two shipped modes (classical NDT stack, or the camera-only VAD end-to-end model). Use when the user asks to "run Autoware on CARLA", "connect an AV stack", "drive the ego from Autoware", "generate a lanelet2 map", or asks which topics CARLA exchanges with Autoware.
The English summary is being prepared. Showing the original description.
Starts a CARLA UE 5.8 server from a ue58-dev tree — the editor binary in -game mode (the working headless server), the packaged shipping build, or the full editor — with offscreen/nullrhi rendering, custom RPC and streaming ports, and native ROS 2 via the single-dash -ros2 flag. Probes a running server, and stops one cleanly despite the 15-character process-name truncation. Use when the user asks to "run/start CARLA UE5", "launch a ue58 server", "run headless", "publish ROS 2 topics from UE5", or a client cannot reach the simulator.
The English summary is being prepared. Showing the original description.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)