Cripton

I'm a bit late to the party but I don't think it should be removed. It's a very useful tool for casual players that just play for fun. However, I believe there should be an option to disable it in unranked lobbies. When playing at a competitive level, resetting to track can be considered as "cheating" as it prevents you to lose too much time after a spin or a crash. Would it be easy to include that as an option in the lobby settings ? @BarryBL

@BarryBL I'm sorry to ask that again but is the glitch included in the "Various other stability and bug fixes" in the 1.06 patch notes ? Thanks ^^

@BarryBL I've just read the 1.05 Patch notes and didn't see anything about the glitch... Is it included in the "Various other stability and bug fixes" ? If not, any update on the current situation ?

@BarryBL I finally got time to try to replicate the bug myself with a friend. Tried 4 times (only recorded the two first times) and I got the bug 4 times. Here's the footage I was able to record: First try (Screenshot of the race settings in the description): https://youtu.be/T_E2HHHaWZc Second try (Screenshot of the race settings in the description): https://youtu.be/87tDFPbYs0Q It clearly shows you don't need to be on the formation lap when leaving the session to have this glitch. From what I know the glitch is NOT: track specific, dependent of the cars used in the race, dependent of the weather, dependent of when you leave the session. And whether you have set a lap in qualifying or not, the glitch happens.

Good to know you've managed to reproduce it, great work! However you don't need to be on the formation when leaving the session to have that bug. You can leave mid-session and still have that glitch. I have some footage here! A friend of mine left his race (he even restarted the game even though it's not a necessary step to make if you want to reproduce the bug), rejoined and was able to exceed track limits, cut corners without getting warnings/penalties. In his video, his corner cuts/track extendings were not huge but with the strict settings we had in this lobby, he should have and would have been warned by the game, I'm 100% sure of that. Let me know if you have any questions, I'll answer them when I can ^^

When you tried to replicate that bug, did you set the corner cutting stringency to strict ? I've been racing for almost 2 years with that setting so this bug might only happen with strict setting... Also this glitch might only appear in 50% distance races but I'm not very sure about that. The only thing that I'm sure about is that this is NOT track specific. I'll do some testing soon. I'm gonna try to record it and when all that is done, I'll come back to you.

1. A detailed description of the issue. Please include any error codes here. In multiplayer (Unranked lobbies), if you rejoin a race after being disconnected from it, the game won't issue you any warning or penalty when cutting a corner or exceeding track limits. So when you rejoin, you are basically allowed to cut every corner and you won't ever get any warning/penalty. Drivers doing that during gain a huge advantage as on certain tracks, cutting corners can make 20 seconds faster per lap. 2. What version of the game you are using (Shown on the start screen in the bottom left corner of the screen) Latest version, v1.04. BUT, this bug was already existing on F1 2019. 3. Game-mode? Unraked lobby, multiplayer. 4. What are your replication numbers? Minimum test attempts are 4. Please also add EXACT replication steps for us to try too. This bug has been reproduced a lot of times and it's very easy to do. All you have to do is: 1. During the race, leave the session. 2. Rejoin the session And there you go, you can't get any warning/penalty for cutting corners/track extending. 5. What troubleshooting have you attempted? Please always try to attempt to fix the issue A player can't fix that issue. You can't try to disconnect and reconnect but the bug won't go. 6. What peripherals are you are using (gamepad, wheel make & model etc) I'm using a G29 wheel but I don't think it's related to the gear as anyone can get that bug, regardless of their peripherals 7. Any screenshots or video of the issue? If the video is long, please include a timestamp for when the issue appears. Don't have any at the moment but I might link some later. @BarryBL Make sure to send this to the devs, this glitch is game-breaking. Appart from that, keep the good work up, you're all doing great with this fantastic game 😉

I did some more testing! Instead of using L2/R2 for ERs mode, I tried my square and cross. And guess what, the issue is still there. It confirms that the problem has nothing to do with the buttons you use or the gear you have. It's within the game itself.

So I have a Logitech G29 racing wheel with the L2 and R2 button assigned to respectively decrease and increase the ERS Mode. The issue is that when I press those buttons quickly, the game doesn't record all the inputs. For example, if I'm in ERS mode 5 (Hotlap) and want to go to Mode 0 (none) as quickly as I can, I'll press the L2 button 5 times as quick as I can. But after pressing the L2 button 5 times in a very small amount of time, I'll be in ERS mode 2 or 3. The game doesn't record all the inputs. If I take my time though, it records all the inputs This issue doesn't only apply to the L2 and R2 button! The L3/R3, -/+ and the red rotary switch all have the same issues. I went on GT Sport to see if the issue came from my wheel but as expected, I didn't have that problem on this game. The issue is related to the game, not to my wheel. So my conclusion is that the game is too slow to record all inputs or there is input lag with the G29 wheel. Platform: PS4 Version: 1.22 (but the "bug" was there in all previous versions, even on previous games) The problem is always present, it's impossible to avoid it. Accesories : G29 Racing wheel Here's an example: https://streamable.com/efwofa. I'm in ERS Mode 5 and press quickly 5 times my L2 button to go to ERS mode 0 (you can hear the 5 fast clicks in the video). But after clicking quickly 5 times, I'm only in ERS mode 2 instead of ERS mode 0.