Solved

lap with 0 time and 100% tyre consumtion?

I'm preparing for the race of the day, i ran a test lap and i got as a result a lap of 0.00.000, with 100% consumption of the tyre and 0 fuel consuption. what does it mean?

In an attempt to be funny I'd would say your driver spun and hit the wall exiting the pits...

Now the real answer, it is likely you ran the lap when there was a high demand on the server and something timed out. If you close the app or browser and go back in, your driver should have a laptime and it should have tire wear.

thanks for the explanation, I think you are right. However, I logged out then logged in again on each device I use but I still get the same problem. Anyway, I think it's not so bad for the today race, but I hope someone of the staff will read it and it won't happen again

Happening to me now (19:10). 2nd driver (Thompson) 5 runs only the first run had data. Couple of "oops an error" messages

Team/manager id=37560

Mine just did this also, did a test run fine, tried another and got Car on Track... for around a min or more, refreshed and now shows laptime as 0:00:00

click save before refreshing the page then once the page reloads it should show fuel & tyre info and lap time.
Plus any changes the driver may want.

I didn't make any changes from the run that worked, I just pressed the try setup button for again. I can't see that screen now as race is about to go live

This happens to me when i lose internet connection then it comes back..

Hitting save before refreshing the page works a treat in the mean time.

It happens yesterday to me, one of my drivers in practice got 0.00.000 time and 100% tyre wear and 0 fuel consumption.

I'm sorry I couldn't replay earlier: it happened only once, then I tried few hours later and there where no problems. now I can't the see the data because after the race they are reset, I don't know if they are stored somewhere

It happend to me some minutes ago. Save and refresh doesn't work. I had to shut down the app complettly to get one time. the next try got stuck and after closing the app and entering again, it was displayed with 0 time but correct driver feedback.