DumbAI 1.3

change log: New Blue Flag Behavior

- Added TrackContext module : pre-computes a lookup table of radius, direction and track width at session start, sampled every 10m along the full circuit

- Blue flag offset side is now determined by the geometry of the upcoming turn (inside of the corner) instead of a raw getTrackUpcomingTurn sign check

- Offset amplitude is modulated by distance to the next turn : full amplitude beyond 300m, linear ramp-down between 300m and 150m, zero inside 150m

- Overtake safety check : offset is suppressed if the apex margin is below 2.5m, or if a chicane (two consecutive turns in opposite directions less than 100m apart) is detected ahead

- Lateral move is now progressive (ramp at 1.0 unit/s) instead of instantaneous, smoothing the trajectory change for both the outlapped car and the leader

- Ramp start is inhibited when a turn is closer than 150m, preventing abrupt moves at corner entry

- Ramp-down on reset follows the same smooth ramp, with an additional speed reduction if the return move is blocked by a nearby car (TTC-based collision filter)

- Multiple outlapped cars in the same group now share a common offset side, coordinated by the car closest to the leader

- Each car in the train receives a speed allowance incremented by 10 km/h per rank, stretching the train and giving each car room to offset without collision

- Continuous upward re-evaluation : if the track opens up after a chicane, the effective amplitude increases on the same side without recomputing the side

- Leader's setAICaution is now reset cleanly via should_reset_outlap_caution, preventing interference with other apps after the overtake is complete

- Stale victims (retired, in pitlane, yellow flag incident, or reset complete) are pruned from the leader's is_outlapping array each tick

- If TrackContext is not yet ready at session start, behavior falls back gracefully to a lateral position comparison (identical to v1 logic), with a log warning

change log:

- removed BlockTeleport system which was not able to override correctly retirement rules of AC and CSP and was messing end of races and return to Content Manager

- refined YellowFlag system, added option in settings to change Yellow Flag triggering speed threshold

- cosmetic changes in the Race engineer

- cleaning of session restarts and use of global variables

As a consequence, the only way to have proper retirement without retired cars going back on track during races is to activate new AI behavior in CSP settings and un-check "get back to the race after going to pits"

changelog:

- added global teleportation block + controlled teleportation to pits management for stuck cars: teleportation to pits after 30 seconds continuously spent at less than 5 km/h without possibility to get back on track

- added Yellow Flag warnings completing the AC flag system: yellow flags added when AI spent more than 1 second on track at less than 5 km/h

- added messaging using native AC system to display 3 kind of events driven by DumbAI: AI that went to pits , track sector under Yellow Flag + driver concerned by the flag and Driver name that just retired

changelog:

- new feature: human player automatically gets tyre compound and AI computed fuel level from DumbAI default behavior in its setup menu, as a default choice

- corrected a bug where AI would always have full tank at start in no refuel scenarios

- fixed a bug display in race engineer (same time gap displayed for car +1 and car +2)

- fixed cases where AI would put wet tyres at start of dry races

- fixed issue when CSP is not able to generate rain tyres

- fixed issue when car has only one slick tyre compound

- fixed issue in some tracks where AC would overwrite DumbAI behavior at start and make bots go to pits & mess around if start position too before pitlane

Change log:

- new race engineer to keep you updated on which is ahead or behind you, with which tyre compound, time lag and number of pitstop

- fixed pit stop strategies and refined their computation: see post here for details = https://www.gtplanet.net/forum/threads/dumbai.434461/post-14517457

- fixed save procedure that forgot Qualifying option

Change log:

- new UI with tyres names and cleared presentation

- new load/save file system based on .ini format with the possibility to have a default.ini launched at start of the session

- new race strategies: "Mandatory Mixed Compounds without Refuel" & "Mandatory Refuel"

- consolidation of all older race strategies

- addition of a new AI behavior: "Running out of fuel"

- new random alternative race strategies, adapted to each race strategies

- fuel strategy adapted for alternative tyre compounds

- solved issues where DumbAI fuel behavior would be overriden by vanilla AC behavior

- global code optimization

Change log:

Following the last reported bug (AI not leaving pits during qualifying), I went through a complete refactoring & optimization of the code and rewrote entirely the pit triggering and release system.

I made tests with CSP 0.3.0p212 for the following different cars:

• Ferrari 365GTB S3 (Mod from AcLegends 60's)
• McLaren MP4/4 (Mod from MAK Corp)
• Ferrari GTE 2019 (Mod from URD)
• Lotus Exo sp1 (Kunos)
• Ferrari 488 GT3 (Kunos)
• Lambo Huracan GT3 (Kunos)
• Ferrari 250 GTO (Kunos)

on different tracks:

• Lago Maggiore Centre (RT version)
• Spa Active Airspace (Kunos modified by Mascot)
• Monza (Kunos)
• Autosport speedway (ACU updated by LaChub & co.)

Both on race session and week-end session (qualifying & race). I can't garantee I tested every combinations but at least every Kunos or mod track has been tested successfully for both session with at least one old car, one recent and one open wheel either mod or Kunos.

Performance now is:

• less than 0.04 ms per update(dt) for 9 AI opponents, max 4Mo memory
• less than 0.06 ms per update(dt) for 19 AI opponents, max 6.5Mo memory

Change log:
As the title says, a correction for a small but important bug reported by @MarshallPlayz where AI was not able to go out of pits during qualifying

Hi !

Here is a first complete version of DumbAI with a mix of new and older features selected from past versions

New features:
- automatic computing of pit stop strategy of bots at the start of the race (fuel & tyres)

- adaptative pit stop strategy during race according to tyre wear, fuel consumption and damages, taking into account fuel and tyre multipliers

Features from older version:

- blue flag behavior for outlapped and outlapping bots

- possibility to change default tyre compound for bots

- 1 example of race rule implementation: mandatory pitstop to change tyre compounds once during the race

- 1 example of the possibility to take into account qualifying results in the race strategy (starting with harder compounds when bad qualifying)

- qualifying behavior: runs of 3-4 laps with adapted fuel level and adapted choice for tyre compounds for qualifying , controlled random launch of each car on track at the start of the session

Other changes:

• UI refreshed
• Code refactored
• Log refreshed

Needs CSP 0.3.0.212 preview to work without bugs , with extended physics allowed

Change log:
As the title says, a correction for a small but important bug reported by @Philip00: where the value given in the UI for max speed limit when outlapped was not forwarded to the bot. Thank you Philip !