Hello everyone, I'm trying to edit the impact on tyre, fuel and ERS charge of the various orders you can set to the drivers, especially because (after the last patch) pushing leads tyres to be totally destroyed within 10-15 laps.
I tried to edit something (as tyre temperature) from savegames but, as someone already said, it's useless. However I'm sure something can be done, as I've seen some trainers (but no one for free...). I'd probably try to extract other files, even though it seems a loooong research.
Maybe someone has an idea on where to start working on?
As expected, is not possible to reduce tyre wear while attacking with Cheat Engine, so I just modified the *.pak file. Unfortunately, infinite ERS is not possible and massive push on fuel would increase engine wear throughout the season, so the file will just reduce the tyre wear on "attacking" mode., which I think is already a very good help on race without necessarily reducing the fun.
To install it, you just need to copy the file in F1Manager2022\F1Manager22\Content\Paks. To disable it, you just need to cancel the file. With the upcoming patches, the file will likely not be usable anymore, but if anyone will be interested I'll keep update it.
Off topic: Has anyone notice the stints seem off? Like when I choose a soft/medium/soft it's like over a minute slower than soft/hards/medium? This is the first race. It seems to only be that way when choosing not actually while racing. It seems like the Hards are showing as faster than other tyres while choosing, but not actually that way in the race. Could this be something to do with the new patch? Anyone else noticing this? The only thing I have changed tyres wise is from page 3 on better grip levels. However it didn't start doing this I believe until after the patch when I had like 3 or 4 races left in the first season.
Edit: Ah I just found a post on reddit and I guess the F1 team knows about this and are planning on fixing it. Looks like it's a display bug for hard tyres showing faster than medium and softs.
Last edited by awardone on Mon Oct 10, 2022 5:35 pm, edited 1 time in total.
I don't have time to fix it now. You can try the alternative I've created, which you can find here -> [Link]
Why you guys dont have the video for cmd and pyhton. I installed it and typed "C:\Users\Myusername\Desktop\F1 Manager\SaveFileRepacker" to cmd and nothing happened. I know I did totally wrong. But can someone show how is it possible to edit the files again? I stoped playing the game since 1.8 update came out. Cuz my tyre grip rates changed. Can anyone help?
I don't have time to fix it now. You can try the alternative I've created, which you can find here -> [Link]
Why you guys dont have the video for cmd and pyhton. I installed it and typed "C:\Users\Myusername\Desktop\F1 Manager\SaveFileRepacker" to cmd and nothing happened. I know I did totally wrong. But can someone show how is it possible to edit the files again? I stoped playing the game since 1.8 update came out. Cuz my tyre grip rates changed. Can anyone help?
It looks like you didn't put CD before you put the location of your savefilerepacker. So you when you bring up CMD it should show
C:\users\username>
After > put CD than the location of the repacker.
C:\users\username> cd "C:\users\username\desktop\f1manager2022"
After that it should bring up the new pointer and that is when you copy and paste the python script.
Just for clarity if people run into this issue, if you right click save the script.py file from the github page using firefox (and maybe other browser but I haven tested that). It (firefox) adds a bunch of meta and ccs data to the file, breaking the script in the process.
You can get around this easily it by just opening the file on github by left clicking on it so you end up here [Link]
You then just copy all the text that's here (142 lines at the time of writing this) paste them into a text editor like notepad or notepad++ and save your file as script.py
Just for clarity if people run into this issue, if you right click save the script.py file from the github page using firefox (and maybe other browser but I haven tested that). It (firefox) adds a bunch of meta and ccs data to the file, breaking the script in the process.
You can get around this easily it by just opening the file on github by left clicking on it so you end up here [Link]
You then just copy all the text that's here (142 lines at the time of writing this) paste them into a text editor like notepad or notepad++ and save your file as script.py
You should then have a functioning script.
thank you for your help but, for me, i still have the same issue :/
