• "Auto racing began 5 minutes after the second car was built." - Henry Ford
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. Dear Guest. Follow RaceDepartment on Twitter, Facebook, Instagram, Twitch, Steam and YouTube.

Laptime Bug!?

Discussion in 'F1 2017 - The Game' started by fili92, Sep 6, 2017.

  1. fili92

    fili92

    Messages:
    6
    Ratings:
    +0
    Hi guys, take a look at this screen.
    Alonso made better than me in sectors 1 and 2, but in sector 3 i was faster than him.
    Alonso's lap time should be 1.38.xxx (if you sum sector 1, 2 and 3), but the screen report 1.37.993.
    So, something is not working here.
    Have you ever experienced something like that?

    [​IMG]
     
    • Sad Sad x 1
  2. Giovaneveterano

    Giovaneveterano
    Premium

    Messages:
    1,341
    Ratings:
    +463
    "The whole is smaller than the sum of its parts" - (not quite) Aristotle
     
    • Haha Haha x 1
  3. ParkYongLee

    ParkYongLee

    Messages:
    1,027
    Ratings:
    +226
    Programming is hard, really. They didn't have a current licence for a calculator to implement so they programmed some code with many round this round that plus minus random add pi. The trainee was very creative, to make F1 more exciting, you know.
     
  4. Coffer

    Coffer

    Messages:
    381
    Ratings:
    +69
    Or that was simply not Alonso's best time. The sector times are the ones for the last lap done. Alonso tends to be about 3 tenths faster than Wehrlein in this game usually and the gap between the fake times and regular times in China is about 7 tenths (almost exactly that in this case - 0.715s between the displayed time and the sum of the 3 sectors, which is 1:38.708). Odds are the OP did a flying lap instead of simply driving out or teleported to the pits after doing the lap instead of driving back, prompting the game to give Alonso a fake time. Fake times never show up in the race director or via the sector times, so this is likely what happened.
     
    Last edited: Sep 7, 2017