DumbAIMisc 1.0.2

[ancient_3]

Hey Ancient,

Regarding point number 2 (“some AI drivers returned to the pits again just two laps later”), it appears this is not a bug. I hadn’t realized that those cars were involved in an incident on the straight in Canada. The impact wasn’t severe enough to cause retirement, but it was sufficient to require a pit stop for repairs. I’ll run some further tests, but for now everything looks fine.

As for point number 1 (“this may not be related to the app itself, but I’ve noticed that one AI driver often performs an extremely fast pit stop, while the rest of the field spends the expected amount of time in the pits according to the car.ini settings for tire changes and refueling”), this issue still occurs. However, I don’t think it’s related to the app either.

Do you still need the car/track combination? I can upload it and send it to you via PM if that’s easier.

Best wishes,
Philip

if they spent an amount of time like the tyre changing time , should be OK then :-)

I'm still interested to have just the track name, just to have a look at pits positions in blender and project pitlane.

I started to work on version 1.1 , in which I'll add possibility to save settings and also working on adding a new log system (in DumbAI main window instead of in the lua debug)

Thanks again for the testing, it is motivating to have some feedback about the app :-)

 

[Philip00]

if they spent an amount of time like the tyre changing time , should be OK then :-)

I'm still interested to have just the track name, just to have a look at pits positions in blender and project pitlane.

I started to work on version 1.1 , in which I'll add possibility to save settings and also working on adding a new log system (in DumbAI main window instead of in the lua debug)

Thanks again for the testing, it is motivating to have some feedback about the app :-)

Sure it's Canada 1998 by shin:

https://www.patreon.com/posts/106612737?utm_campaign=postshare_fan&utm_content=android_share

 

[ancient_3]

Sure it's Canada 1998 by shin:

https://www.patreon.com/posts/106612737?utm_campaign=postshare_fan&utm_content=android_share

Hi Philip,
I tried the track with 31 Kunos F488 GT3 bots and was not able to recreate the issue , sorry. Everyone went to pit and spent the correct time there. I specifically looked at the first pit areas and they spent like 20 seconds there, what I'd have expected considering the time computed from the .ini.

To all, I tried the app with URD GTE2019 pack and noticed the Dumb AI can not work for Tyre Wear as their tyre files are encrypted .ini . I'm a bit bored with that I must say. I may put a default value for tyre wear taken from their former GTE mod that is not encrypted or from a Kunos GT3 so that the app doesn't crash but that makes few sense if you run with specific tyre wear and bots don't have the same...

 

[Philip00]

Hi Philip,
I tried the track with 31 Kunos F488 GT3 bots and was not able to recreate the issue , sorry. Everyone went to pit and spent the correct time there. I specifically looked at the first pit areas and they spent like 20 seconds there, what I'd have expected considering the time computed from the .ini.

To all, I tried the app with URD GTE2019 pack and noticed the Dumb AI can not work for Tyre Wear as their tyre files are encrypted .ini . I'm a bit bored with that I must say. I may put a default value for tyre wear taken from their former GTE mod that is not encrypted or from a Kunos GT3 so that the app doesn't crash but that makes few sense if you run with specific tyre wear and bots don't have the same...

Hey ancient.

To me the first AI always gave magic lit box there when they went for refueling

I will try to recreate again see of there is any changes and let you know.

 

[ancient_3]

Hey ancient.

To me the first AI always gave magic lit box there when they went for refueling

I will try to recreate again see of there is any changes and let you know.

Hi Philip,

While debugging future 1.1 version, I noticed the bots behave strangely if you are running the race as a bot yourself and if you navigate between bots to observe what they do. And I was able to observe something like you did.

1) I saw a bot going back to pit without writing anything in the log, just as if DumbAI had been disabled.

2) this bot was really quick to do the pitstop. I looked at my code and saw that I gave a 3 seconds bonus for bots as they are a bit slower in the pitlane and depending on cars, the way I wake up them to make them go back on track may make them lose another couple of seconds. That may explain why with F1 cars, the pitstop is too quick but most likely, it is rather just vanilla AC that took control on the pitstop loop and disabled DumbAI

3) if you run a race as spectator, player 0 (yourself made as a bot by ctrl-C) does not follow DumbAI rules as the app is applied only to cars 1 to cars xx (considering they are bots). I wonder if it is not the same that happens if you get focus on another bot car.

I made the exact same race again but driving the car instead of running as a spectator and everything went well , all DumbAI functions were correctly applied.

Anyway, I changed the pit bonus to only one second for future version 1.1

Also I'll try to clear a bit how DumbAI is applied : maybe if I check if car is driven by AI instead of just using car index, it will be cleaner.

Here is a preview of UI for 1.1 as a bonus

Load / save file system using .ini format has been added and is debugged. I added the possibility to set a default ini that is loaded at start of the session so that one can start to race without bothering about DumbAI settings

I just finished to debug Tyre Change only , with a new functions that make bots able to run out of fuel.

Still have to debug ReFuel only and Mandatory Refuel strategies, and verify that TyreChange&Refuel and Mandatory Mixed Compounds have not been destroyed by my modifications.

And then define alternate strategies and grid position accounting, for each strategy, and debug them

 

[Philip00]

Hi Philip,

While debugging future 1.1 version, I noticed the bots behave strangely if you are running the race as a bot yourself and if you navigate between bots to observe what they do. And I was able to observe something like you did.

1) I saw a bot going back to pit without writing anything in the log, just as if DumbAI had been disabled.

2) this bot was really quick to do the pitstop. I looked at my code and saw that I gave a 3 seconds bonus for bots as they are a bit slower in the pitlane and depending on cars, the way I wake up them to make them go back on track may make them lose another couple of seconds. That may explain why with F1 cars, the pitstop is too quick but most likely, it is rather just vanilla AC that took control on the pitstop loop and disabled DumbAI

3) if you run a race as spectator, player 0 (yourself made as a bot by ctrl-C) does not follow DumbAI rules as the app is applied only to cars 1 to cars xx (considering they are bots). I wonder if it is not the same that happens if you get focus on another bot car.

I made the exact same race again but driving the car instead of running as a spectator and everything went well , all DumbAI functions were correctly applied.

Anyway, I changed the pit bonus to only one second for future version 1.1

Also I'll try to clear a bit how DumbAI is applied : maybe if I check if car is driven by AI instead of just using car index, it will be cleaner.

Here is a preview of UI for 1.1 as a bonus
View attachment 1514613

Load / save file system using .ini format has been added and is debugged. I added the possibility to set a default ini that is loaded at start of the session so that one can start to race without bothering about DumbAI settings

I just finished to debug Tyre Change only , with a new functions that make bots able to run out of fuel.

Still have to debug ReFuel only and Mandatory Refuel strategies, and verify that TyreChange&Refuel and Mandatory Mixed Compounds have not been destroyed by my modifications.

And then define alternate strategies and grid position accounting, for each strategy, and debug them

Hey Ancient,

Yes — I was actually using Ctrl+C at that time as well when I observed the quick fuel usage, usually for the pole sitter.

I’ll run another test without using it. So just to confirm — the solution is simply not to use Ctrl+C?

The new features look awesome — I can’t wait to try them out! 😍

Best Wishes,
Philip