Post by lazyracer on Dec 26, 2019 22:53:27 GMT
DISCLAIMER because unlike RPG's, racing games require precise timing of race control actions, you will need to tweak the provided script for your situation. It's unlikely that it will work out of the box...
License
The bot is licensed under GPL-3.0 which means that you can use change and redistribute it freely under the same GPL-3.0 license. It means that upon request you need to provide the source code of any version you release.
Purpose
In the F1 update of RR3 (8.0), a new Motorsports currency was introduced: M$.
It can only be earned by competing in F1 events.
The maximum amount that can be earned per day is M$ 180,000 and the maximum that can be owned in M$ 4,000,000.
The bot presented here can win the speed snap event at Suzuka Circuit which is event 5.1 of the 2019 Champion Series.
You will need to own a F1 car and unlock event 5.1 of the 2019 Champion Series.
There may also be a speed snap at Suzuka Circuit in the daily race, in which case the free F1 Academy Car can be used.
Platform
The bot was developed on Nox player Android emulator from bignox on Windows 10 running on a Dell Latitude laptop with Intel Core i7 processor.
RR3 works reliably on Nox. On BlueStacks RR3 often crashes after which it has to be re-installed completely. Also Nox has a Root option as standard whereas BlueStacks requires a series of steps using a tweaking tool to root the emulator.
The bot was also made to work on an older Dell Latitude laptop with Intel Core i5 after tweaking of its timing (see below).
It has not been tested on native Android devices.
Nox settings
Check "Root":
Resolution 1280x720:
Note that the script contains hard coded locations and AnkuLua has trouble recognizing buttons with a different resolution. So if you choose to use a different resolution you will need to adjust the locations in the script and take new screenshots and cut out the buttons used in the image directory.
20 fps:
Android settings
AnkuLua:
Superuser:
Switch off logging and notification.
RR3 settings
Buttons:
High assistance:
Installation
Download the zip file.
The easiest way to install the bot is to extract it in the Nox shared directory C:\Users\...\Nox_share\OtherShare. Then in a Terminal Emulator for Android window use
/mnt/shared/Other/deploy.sh
which copies the extracted files to the AnkuLua script directory.Usage
Start the AnkuLua service.
Switch off Wi-Fi to avoid getting fast cloud opponents:
In RR3 navigate to event 5.1 of the 2019 Champion Series.
The bot will start operating in two situations:
- The screen with the RACE button:
The bot will press RACE.
Note that you should use a car that has no maintenance left, so that its performance will be the same in each run. - The screen after the race with the COLLECT button.
The bot will press COLLECT, then RETRY and CONTINUE, or exit in case the daily limit has been reached.
After both options, the race is started and the bot waits for red and then green light, after which the scripted race action sequence starts.
The script displays "toast" messages for each action performed which can be used to correct the timing.
This video shows a successful run:
Tweaking
Run the bot and use the messages to compare your run with the above video.
After the bot completes, adjust the times in the script accordingly and run it again until it works all the way.
You can keep the working version of the script in the Nox shared directory C:\Users\...\Nox_share\OtherShare, so that you can edit the script easily in Windows and use the deploy.sh script in the Terminal Emulator for Android window to copy the script and images to the script directory (as described above for installation).
Since the bot takes less than a minute to run, the trial version of AnkuLua can be used for the tweaking. When done, you can surround the script with an endless
while true do ... end
loop so that it will keep running until no more M$ is available. Since this will last more than 30 minutes, you will need the AnkuLua Pro version to collect everything in one run.Using this procedure the script was successfully tweaked for a Dell Latitude laptop with Intel Core i5 processor.
This resulted in the following race sequence:
wait(3.2)
toast("right")
longClick(right, 0.3)
wait(1.0)
toast("brake")
longClick(brake, 1.5)
toast("left")
longClick(left, 0.8)
wait(2.6)
toast("right 1")
longClick(right, 0.3)
wait(0.2)
toast("right 2")
longClick(right, 0.3)
wait(0.2)
toast("right 3")
longClick(right, 0.3)
wait(0.5)
toast("right 4")
longClick(right, 0.2)
Please share your working race sequence in a reply to this post, quoting your system, OS, CPU and RR3 F1 car and upgrades.
I hope this is clear. Post a reply if you have problems or questions.
Cheers,
Lazyracer