• Dear visitors,

    The email issue has been finally solved.
    Thank you for your patience and happy browsing.

    Team ACM.

SOLVED AI Problem

luchian

Administrator
Staff member
Disable New AI - record - re-enable

Cached grids and payload files help speed up loading, but more than often just a general headache... :lol:
Yes, for me too. It took me a while to understand what the hell is AI doing :lol:.
I don't really do "drives", so I left AI behavior off all the time after finding out.

I'm left with one final problem tho:
My start/finish TV cam is simply skipped when I watch replays. It goes from the last corner TV-cam to the first corner TV-cam, without switching to start/finish TV-cam at all. I checked the IN/OUT points 3 times already, cannot understand where the issue is :ninja:.

NVM: solved it by splitting the start/finish cam, to go from 0.95 to 1, and then from 0 to 0.03.
When did this become a thing? I remember the cams in the beginning being able to figure it out alone.
 
Last edited:

Johnr777

Moderator
Yes, for me too. It took me a while to understand what the hell is AI doing :lol:.
I don't really do "drives", so I left AI behavior off all the time after finding out.

I'm left with one final problem tho:
My start/finish TV cam is simply skipped when I watch replays. It goes from the last corner TV-cam to the first corner TV-cam, without switching to start/finish TV-cam at all. I checked the IN/OUT points 3 times already, cannot understand where the issue is :ninja:.

NVM: solved it by splitting the start/finish cam, to go from 0.95 to 1, and then from 0 to 0.03.
When did this become a thing? I remember the cams in the beginning being able to figure it out alone.
Always, since it can’t go past 1.0

The trick is indeed to duplicate camera and use 2 in-out values
 

luchian

Administrator
Staff member
Yes, it cannot go over 1. But I seem to remember it was automatically switching from e.g. 0.9 to 0.1. Or maybe I am just fabricating memories :lol:. In any case, thanks for the replies.
 

Rob Pawn

Active Member
hallo, does anyone of you have a idea whats goin wrong with my record attemps?

i turned off "New AI Behavior" completely.
I can not turn off "general patch settings" cause game will not start without it.
surfaces.ini is prepared - only pits and road surface is set to valid.

I recorded AI line for Drift and Kart Layout, without issues.

Now comes the problem when i try to record the Spline for the race layout.
1st, AI spline was kinda broken cause of fucked up sidelines, cause of connected roads to the main racetrack.
Then i thought, ok, just export only the race road to record the AI line. (like picture shows)
After recording 2 laps, it does not created anything in AI folder.

Then i thought, ok, lets create sidelines (side_l/r.csv) and load it with shift while starting in hotlap mode.
Now it creates a fast_lane.ai but its only 1kb big and not workin at all.

Does it crash while exiting the game? Track is long but by far smaller then nordschleife.

Any ideas?

Screenshot 2024-01-02 083601.png
 

Johnr777

Moderator
Did you wait long enough? Large tracks usually take a while to finish creating the file.

I also ensure once I cross the finish line, I close the AI app, then exit the game.
 

Rob Pawn

Active Member
thx for reply. Yes, after exiting the game i did nothing until game window was closed. Its goin pretty fast tho.
does not take longer then for the small drift layout.
I will try to close the app before press exit, next.

What do you mean by once crossing the finish line?
I start hotlap, press record, drive 1st lap, then 2nd lap for the actuall line and stop before i cross the finish line.
 

Rob Pawn

Active Member
complete 2nd! facepalm
makes somehow sense. otherwise i get the first lap ai.line only *facepalm* :D
i dunno, i remember the YT tutorial told me to stop before passing finish line, if i remember correctly...

but anyway, this is not the issue. IT STILL DO NOT WORKS.
For all other layouts it worked even with just 1 lap finished.
 

fughettaboutit

aka leBluem
this tiny gap btw those 2 meshes can already break ai line, ac (edit: might) thinking the surface is not continuous
upload_2024-1-4_15-31-29.png


upload_2024-1-4_15-33-48.png


and why no intermediate time gates?
AC_TIME_1_L/R and AC_TIME_2_L/R

and one AC_HOTLAP_0 is enough, you cannot spawn more than 1 car there anyway
 
Last edited:

Rob Pawn

Active Member
thx a lot for this advices.

i have trouble with blender which all of a sudden moves planes randomly for a couple of micro millimeters.
last big change i had to move everything down in hightlevel.
which probably caused more plane movement then usual.

Section times? who needs this? Or is it helpful for recording?
But yeah, i can place some in each Village respectivly in the four 90° direction change corners...

I did not knew about hotlap spawner - i decided last week to create some more. good to know!

i will try tomorrow. thx so much for your time!
 

Rob Pawn

Active Member
Alright. STILL NOT WORKIN! :ROFLMAO:

The Track is now 1 Object with gapless Vertice Connection.
AC is not creating fast_lane.ai.candidate.

It seems that AC is crashing while exiting the game after record...
When i start AC afterwards again, the opened or closed apps, like AI tool, Weather App, or Comfy map are resetted to the point before i took changes to start recording.
(i start with closed AI tool - open AI tool to record - exit game - Restart game and the AI tool is not open!)

Otherwise, whats about PIT Surface?
Its contained in a seperate kn5 file then the track it self.
Pit-Surface is just a plane underneath a basic road (is valid track=1) and not connected in anyway to the track.
IS THIS A PROBLEM TOO?
And i see that the road which leads to pit, has a gap to the track as well...

Screenshot 2024-01-06 104224.png
 

fughettaboutit

aka leBluem
pits should not be a problem, when recording fastlane, but maybe when recording pit-lane

and after joininginto one object, the complete mesh still can have gaps...
 

Rob Pawn

Active Member
after merge vertices with <m> <b>, i verified by loop select with <ctrl> key. 100% there is no gap.
iam close to just give up :banghead:
 
Top