Unresolved

Pit stop new problem

¿Qué has intentado hacer?
Fix

¿Qué es lo que ocurrió?
Cuando configuramos una carrera estando en directo las paradas se saltan 1 vuelta, también tenemos quejas de esto cuando no estamos activos, esto nos pasa a unos cuantos mánagers por no decir a todos. Y no nos ayuda a la hora de competir

¿El problema ocurrió mientras usaba wi-fi, datos móviles o ambos?
Both

¿El error se produjo en la app, en PC o en ambos?
Both

¿Cuál es el modelo de su dispositivo?
Android

¿Qué sistema operativo posee?
Android

¿Cuál es el número de versión del sistema operativo?
Ultimo

¿Qué sistema operativo posee su PC?
Ultimo

¿En qué navegador ha experimentado el problema?
Ultimo

¿Se puede reproducir el error?
Si ya a sucedido en dos carreras simultáneamente

Comentarios adicionales:
..

Yeah I've had this problem in my offline league ever since the update. I've had to ask for all teams to just 0 stop every race from now on, so with tyres that will just explode before the end (brilliant!) as we can't run our intended strategies and just get screwed over.

the issue is that the pit boxes for each team are in different places on the start straight of every circuit, some cars have already crossed the line to start their next lap before they have pit so are recorded as having made their stop on the wrong lap.

I should imagine once Jack sees this and can get to amending the issue it ca be an easy enough and quick fix but right now it is impossible to run an offline league properly which is why I asked for my race in France to be voided (no one replied unfortunately).

Ya entiendo eso, apenas veo un par de fallos respondidos y cada día ahí más sin hacer caso, bastante frustrante aun teniendo mucha paciencia, 

There is a fundamental problem at certain circuits (i've seen France and USA so far) where the AI will extend all their stint lengths by 1 lap which completely corrupts race results, especially in offline leagues. This happened in my league yesterday and I have asked for the race to be voided as a result. Hopefully the underlying bug is fixed, as this issue did not exist before the big update in December.