That's true, although the impact might be bigger than expected. I remember when backwards driving was fixed, it broke all PF maps for some reason.edk wrote: If the only thing that would be changed is the inability to brake (at less than 0.01s) and not drift, where otherwise a drift is intended, then there will be very minimal impact. The number of affected tracks and replays is sufficiently low enough that something like a full reset would not be necessary.
Also true, but driving new times on the affected maps will take some time...edk wrote: Let's be real here for a minute, you're not going to lose that #1 spot with a patch. After a small matter of time this will only have been a minor setback if anything, with little to no affect on the rankings overall. There is also a limited number of drivers that made use of this in the campaign, or are even able to do it in the first place. So again, not to difficult to clean up.
If it wasn't intended, I wonder why it hasn't been fixed earlier. Canyon has exactly the same brake mechanisms (although it's not as exploitable as in Valley due to Canyon's much higher speed).edk wrote: As players we should take into consideration that this car behavior is not intended, as is evidenced by Hylis's response.
Xymph wrote: And also online, if it would affect some or many Dedimania TM2 records (2.6M on Stadium, 1.6M on Canyon, 272K on Valley), and invalidate XX % of the validation/ghost replays stored for them (1.3M files).
Keep in mind such a patch will only affect a fraction of Valley records, still it will be a mess to clean up the database from "impossible" replays.
@Nadeo: If needed I can provide a list of all known official times which would be affected after the patch. I will also get in touch with MX moderators to eventually erase such replays.
Hopefully the patch will be rolled out soon...it's getting more and more ridiculous with a certain player
