Apologies for the late reply, but work and a complete melt-down of my PC resulted in a somewhat harried week. Anyway..... The above is actually what the AI does when it adapts, only difference is that it starts at 80. (Or at least it did. Haven't had time to pick the new one apart yet) In my case, it usually jumps from 80 to 90-92 in the first race, 97-98 after the second and so on. The problem though is two-fold; First it starts in the wrong place. If the AI can go from 80 to 120 it should start at 100 to minimize the distance it has to travel. Though this only applies if your level is actually above 100, and let's not forget that a lot of less experienced racers could very well be discouraged if it took them 10 races to get something that even resembled a race. So I can live with that one (even if I still find it annoying ) The second problem comes after it has actually found your level. It then has to truly adapt in order to get good racing, otherwise it doesn't work. To illustrate, let's say that my level for a particular combo is 108. After six races the index-file runs 80-92-98-102-105-108 (completely fictitious numbers, just play along) Now, if you're thinking that the AI has now adapted to you, you'd be wrong unless you happen to be obscenely consistent even when there is traffic around. If you try to race that index with a full grid you will at some point have to slow down to e.g. level 107 because another car is blocking a corner. And since the adaptive AI is made to consistently follow your lap-times it also has to drop down, but the next available level for it is only 105. Which means that for the next lap you'll be blitzing through the field. And then the AI will speed up again, repeat ad nauseum. And if you happen to beat you own level, the AI will then have to insert yet another level into the index. The AI will eventually get there on its own, it just takes a wee while. Make no mistake, the AI doesn't just use one entry in the index, it uses all of them if it has to. If you're reasonably consistent, it normally only needs two or three, but if there are large gaps in the index, you're going to get some decidedly weird races. And to muddy the waters even further, the starting point of 80 only applies if the index-file is empty. Once there is data in it, any new combo will start at what I suspect is the average of the entire index-file. Or in other words, if you've been running NSUs on all the tracks at an average of 105, if you switch over to say GTR3s it'll start at 105 as well, despite you not having any data for that particular combo. And of course.......All of the above are null and void since my training method doesn't work with the new AI. As I said earlier, I haven't had time to completely pick it apart yet, but from the experimentation that I've managed to do you can no longer just quit out after one race and get an AI entry. I think (read: wild-ass guess) that it's because they've corrected what was actually a bug. I doubt the AI was ever supposed to take the first lap into account, since that would mean a lot of short races would mean a lot of non-flying laps in there dragging the average down. So the good news is that they've fixed that. The bad news is that it'll take 2 laps on manual AI level, and probably 3 laps on adaptive to get it to write anything. Now, this is all very preliminary and assuming I can find the time, I'll sit down with the AI over the week-end and see if I can't figure out a new way to 'cheat' us into better adapting AI. But right now I'd say the fastest way would be to run a 2-lap race with fixed AI at your approximate level for that combo, and then run 3-lap races with adaptive until it has...well, adapted. I also suspect that since most people have a level that is more based on the car than the track (i.e. people usually run at one level with NSUs and another with GTR3s no matter what the track is), you're probably better off training one class at a time and then do some manual cut'n'paste or use @pixeljetstream s program to insert the data into a fresh index-file. If you're 108 with NSUs and 95 with GTR3s, and you do the NSUs first, the GTR3s will then have to adapt from 108. On the other hand, if you're capable of doing 108 with the NSUs fairly consistently on all tracks, you can get the data inserted, copy the file, and start over with a GTR3 one starting at 95 and repeat as needed. Hopefully I'll have something a little clearer after the week-end.