TUTORIAL Build your FIRST track - BASIC GUIDE

[Xuacu]

Super! Thank you very much!

basically yes, but you can have values above, where 1.1 is like 110%

using that in [HINT... makes them push more, where 0.5 is hold back by half!

Thank you!

Looking for morte info about hints I found this in the forum:

Hi! In the data folder (under your main track folder) is a file called ai_hints.ini. Open that up in a text editor. You can add hints to help the AI deal with things like that. e.g.

;the left hand bend (you can put anything here. It's just a comment)
[HINT_0]
START=0.08
END=0.10
VALUE=0.595

;the drop
[HINT_1]
START=0.227
END=0.247
VALUE=0.35

;the kink. Don't back off too much!
[HINT_2]
START=0.297
END=0.32
VALUE=1.35

So START and END are the start and end points for the hint. 0 is when you cross the start of the AI spline and 1 is the end of the spline (1 lap). So 0.3 is 30% through the lap. You can find these values easily using the AI line helper app (https://www.racedepartment.com/downloads/ai-line-helper.16016/). It tells you the number as you drive the lap. Just plug these numbers in where they fit.

VALUE = This is the value of how much the ai should push in comparison with default. e.g. 0.9 = back off a little, 0.5 = back off quite a bit and drive more slowly, 1 = drive normally (you wouldn't use this as this is the default value), 1.4 = drive wrecklessly

Hope this helps. There are other tweaks possible in the AI_HINTS.INI file but I don't know enough about them to advise. The above use is the most common.

set road to valid, all others to invalid
View attachment 5451

when recording the new ai line, everything else but your road-mesh in your surfaces.ini should be set to IS_VALID_TRACK=0

if you dont do this, ac will assume it can drive anywhere, also in the pits, if you use your normal "surfaces.ini" with pits set to valid

another thing that should fix this (i dont know for sure)
would be recording side_r.csv and side_l.csvwith ai-line helper and using those with the "holding-shift at ac-start" method

 

[Xuacu]

basically yes, but you can have values above, where 1.1 is like 110%

using that in [HINT... makes them push more, where 0.5 is hold back by half!

I have solved the problem with these parameters:

; 01
[HINT_0]
START=0.0
END=0.055
VALUE=0.9

[HINT_0]
START=0.95
END=1.0
VALUE=0.9

Thank you very much!

 

[Xuacu]

I have solved the problem with these parameters:

; 01
[HINT_0]
START=0.0
END=0.055
VALUE=0.9

[HINT_0]
START=0.95
END=1.0
VALUE=0.9

Thank you very much!

I have realized that I have the nomenclature wrong, but it still works, it may be that one of the two sectors is not applying it

It is currently named like that: [HINT_0] [HINT_0]
and it should be like that I think: [HINT_0] [HINT_1]

 

[Xuacu]

duplicated messsage

 

[heryy21]

Hi guys, i am making a track and i wonder how i could make a similar starting counter device like in this video from 0:17, can anyone help me?

 

[Johnr777]

Hi guys, i am making a track and i wonder how i could make a similar starting counter device like in this video from 0:17, can anyone help me?

You would need some basic LUA knowledge to accomplish that. Maybe best to find the track and see how it was done?

 

[quetillo]

Hello people, I have a rallycross circuit, with 2 surface, road and gravel, I try to create the AI and the CSV, without result, I have tried everything and nothing

 

[fughettaboutit]

Hello people, I have a rallycross circuit, with 2 surface, road and gravel, I try to create the AI and the CSV, without result, I have tried everything and nothing

is the sand part declared as
IS_VALID=1
in surfaces.ini?

 

[Johnr777]

rename the gravel to road and try recording the CSV again

 

[Johnr777]

is the sand part declared as
IS_VALID=1
in surfaces.ini?

Might be hardcoded / namecoded for the game to think its not a valid surface

 

[quetillo]

The gravel surface is like this IS_VALID TRACK=1 if I put it like this.
IS_VALID_TRACK=0 I get the message. I record again and it comes out like this, but it only appears in the area where gravel is assigned, it becomes small. And I don't know if it is from ai_hints or from where. I have the 2 side_l and r.csv

 

[Johnr777]

Issue is the mesh name…. Use 1ROAD to record the csv and change it back after

 

[quetillo]

Issue is the mesh name…. Use 1ROAD to record the csv and change it back after

Now I have the problem that the cars remain stopped, they accelerate but do not advance, they told me that this is already from the car's ai

 

[Johnr777]

Now I have the problem that the cars remain stopped, they accelerate but do not advance, they told me that this is already from the car's ai

open the fastlane.ai in kseditor and resave

 

[quetillo]

but actually it is not the AI but the side_r.csv
side_l.csv. which is the red limiting line, because the ai is fine.

 

[Johnr777]

but actually it is not the AI but the side_r.csv
side_l.csv. which is the red limiting line, because the ai is fine.

You just said the AI cars dont move.

 

[quetillo]

You just said the AI cars dont move.

That's right, the AI cars accelerate but do not come out, I was looking for information and they say that it is by touching the rpm of the car.

I've been watching videos of generating the AI and each video is different, regarding pit_lane or fasty_lane. Looking for videos on how to join the 2 csv. something confusing if you start watching videos and each one is in a different way

 

[Johnr777]

That means the AI line is corrupt, because maybe you changed the 1SAND to 1ROAD, or whatever...

To fix, you import the AI line in kseditor and resave.

To make side CSV, you use the app AI LINE HELPER

 

[ClipsDlamini]

Hey Luchian, I was wondering if you are still active on the forums? I have a few questions I would like some solution based answers to.

 

[fughettaboutit]

Lucian is still here. There should be no question others would not be able to answer...I mean just go ahead and ask...