Tyre longevity is handled with the "tyres" table in the database, using the max_distance values. You have to be fairly drastic to notice an effect.
If you modify the database, you must completely restart the game in order for your changes to take effect. Starting a new quick race is not enough, since the database is loaded into memory each time the game starts.
The proof that the "tyres" table is what handles tyre longevity is my 2 databases - 50% & 100%. Those 2 databases are identical, except for the "tyres" table, and you'll see that if you have the 50% database installed, and try to do a 100% race, you'll have no pitstops scheduled. Meaning your tyres won't last until the end of the race, thus indicating the tyre longevity has changed.
So idk what you two are doing with the values in the tyres table...
The only thing I can think of is you've changed the front/rear_tyre_wear values in the "f1teams" table. These determine how hard each individual car is on their tyres.
Last, make sure the database you're editing is located in the \F1 2012\database folder
Good luck...
If you modify the database, you must completely restart the game in order for your changes to take effect. Starting a new quick race is not enough, since the database is loaded into memory each time the game starts.
The proof that the "tyres" table is what handles tyre longevity is my 2 databases - 50% & 100%. Those 2 databases are identical, except for the "tyres" table, and you'll see that if you have the 50% database installed, and try to do a 100% race, you'll have no pitstops scheduled. Meaning your tyres won't last until the end of the race, thus indicating the tyre longevity has changed.
So idk what you two are doing with the values in the tyres table...
The only thing I can think of is you've changed the front/rear_tyre_wear values in the "f1teams" table. These determine how hard each individual car is on their tyres.
Last, make sure the database you're editing is located in the \F1 2012\database folder
Good luck...