City-Racing

About this game

Latest news

• Announcements·24 Jul 2026Official

  Cars that crashed off the edge of the map at high speed would fall forever

  Fixed:Cars that crashed off the edge of the map at high speed would fall forever — they now automatically reset back to the last checkpoint you passed.Fixed a bug where a crashed car resting on its side or upside-down could get stuck with the camera flickering/glitching instead of recovering. Flipped cars now reliably right themselves and return to the track within a few seconds.Fixed a potential build-stability issue in the city traffic system that could have caused compile failures in future builds.Technical changelog (for you)Player recovery system (CRCarInfo.cs)New: player car falling below the map (Y
  Read full article on Community Announcements (LesGo)

• Patch Notes·26 Jun 2026Official

  Repair Stations

  added more repair stations around all the race tracks, also re-posisioned the other stations, to the waypoint path for the AI Cars. Like the long race track also of AI cars would get damaged and not make it to the next repair station, so I added more stations aroound all the race tracks.
  Read full article on Community Announcements (LesGo)

• Announcements·13 May 2026Official

  Now we also needed to tighten the IsCarAhead

  Looking at the current implementation, awareness has two problems that cause clumping:1.The "in-path" test is too wide — a 35° forward cone within 35 m means any traffic car roughly in front (even one or two lanes over) triggers a slow-down. So, when a pack of city cars is around, the AI brakes for cars it could just drive past.2.The cap fires even when there's a clearly open overtake lane — so the AI matches the slow car's speed (~36 km/h) instead of swinging into the free lane and blasting past.Fix: tighten the geometry to "in my lane" only, and don't apply the speed cap if an adjacent lane is open (let the lane-selection logic do the dodging instead). I'll also raise the default headroom, so the AI keeps enough momentum to actually pass.Now we rewrite ScanForTrafficCars to (1) only consider cars in our actual lane (lateral check), and (2) skip the speed cap if there's a free adjacent lane. Also we tighten IsCarAhead's TrafficCar add-on so it doesn't over-trigger every frame.Now we also needed to tighten the IsCarAhead traffic-car add-on so it only triggers when the car is genuinely close-in-lane (not a 60° cone for any TrafficCar within 0.6 * laneWidth of the lane center which over-fires):   What was wrong1.The old "in path" test was a 35° forward cone within 35 m, so the AI saw traffic cars one or two lanes over and treated them as obstacles → constant brake.2.Even when a clear overtake lane existed, the speed cap still fired (otherSpeedKmh + 6 km/h), so the AI matched the slow city car's speed (~36 km/h) instead of swinging around → the clumping you described.3.IsCarAhead's TrafficCar add-on also used a 60° cone, so every lane-selection tick the AI thought it had a car ahead.Fix (in CRAILearningSystem.cs)ScanForTrafficCars was rewritten with two key rules:·Lane-tight geometry: a traffic car only counts as "in my lane" if its lateral offset (using Vector3.Dot(myRight, toOther)) is within ±laneWidth/2 AND forward distance is within trafficFollowDistance (now 9 m,...
  Read full article on Community Announcements (LesGo)

• Announcements·4 May 2026Official

  added a real lane‑offset field and use it when building the per‑car waypoints

  Let me explain the issue clearly:Why the cars still drive in the center: The field perfectCenteringDistance is not a lane offset — it's just the tolerance the learning system uses to score whether a pass through a waypoint counts as "perfect" (within X meters of the waypoint). Setting it to 5 just makes the scorer more forgiving; it doesn't move the car off the road centerline.The AI follows whatever positions are stored in the per-car waypoints container, and CreatePerCarWaypointsContainer() clones waypoints with src.transform.position — i.e., dead center of the road. To put cars in the right lane I need to add a real lane offset that shifts each cloned waypoint perpendicular to the road direction.TrafficCar interaction: The methods tc.GetSpeed() / tc.IsHazard() exist and the scan logic is fine. The reason it can look "broken" today is that AI cars are driving on the centerline, so they sit on top of TrafficCars (overlapping/clipping) instead of approaching them in a forward cone — ScanForTrafficCars requires the traffic car to be ahead within a forward cone, so head‑on/centerline overlap makes the awareness misfire. Fixing the lane offset fixes the awareness too.I added a real lane‑offset field and use it when building the per‑car waypoints, and add a clarifying tooltip on perfectCenteringDistance so it isn't confused for a steering offset.No errors. Here's a summary of the fix:What was wrong·perfectCenteringDistance is a scoring tolerance for the learning system (how many meters from the waypoint counts as a "perfect" pass). It never fed into steering, so changing it from 3 → 5 didn't move the car off the centerline.·CreatePerCarWaypointsContainer() cloned each waypoint at src.transform.position — i.e., the road centerline — so the AI dutifully chased the centerline.·The TrafficCar awareness (ScanForTrafficCars → tc.GetSpeed()/tc.IsHazard()) is wired up correctly. Its forward‑cone test was just being undermined by the AI sitting on top of TrafficCars on the cente...
  Read full article on Community Announcements (LesGo)

• Announcements·24 Apr 2026Official

  breakdown of the three big upgrades

  🏎️ Recap: What We Just Did to CRAILearningSystem.csHere's a breakdown of the three big upgrades and why each one makes the AI noticeably better.---1. 🗑️ Killed the global minWaypointSpeed / maxWaypointSpeedBefore: Every car on every track was hard-clamped between two magic numbers (e.g. 30–250 km/h) in the inspector. A Formula car and a city sedan got the same ceiling, and a tight roundabout had the same floor as a freeway.After: Bounds are derived per-waypoint from baseSpeed (the designer-tuned value cloned into the per-car / dynamic container):·Sharp corners: ceiling shrinks toward 0.85 × baseSpeed·Straights: ceiling opens up to 1.4 × baseSpeed·Floor: 0.4 × baseSpeedWhy it's better: The dynamic per-car waypoints are now the single source of truth for "how fast is reasonable here." No more babysitting two sliders per scene/car combo, and a hairpin literally can't be clamped at the same number as the back straight.---2. 🧠 Predictive Backward Braking — the actual cornering fixThis is the big one. The complaint was "cars at 100 mph just plow to the middle of the road and never make the turn." That happens because the AI was only braking at the corner, not before it.New method: PropagateCornerBrakingBackward(currentWP) — runs every frame after ApplyLearnedSpeedsAhead().It walks cornerLookAhead waypoints out (default 8) and, for every adjacent pair, enforces a physical braking budget:prevWP.targetSpeed ≤ aheadWP.targetSpeed + (distance × maxBrakingPerMeter)…and sharper corners shrink that per-meter budget, so steeper turns force earlier brake points.Crucially, the lower ceiling is written back into learningData\.optimalSpeed — so the car remembers the new brake point next lap instead of re-discovering it by overshooting again.Why it's better:·A 90° corner learned at 50 km/h now automatically drags the previous 1–8 waypoints down to a deceleration curve the car can physically achieve.·High-speed cars finally make the turn instead of understeering across the centerline.·I...
  Read full article on Community Announcements (LesGo)