Anyone else hoping that they fix this at some point? The records for each track log only the top eight times that you've run it. Ever. You can delete all of the records and start over, sure, but you can't delete individual records like you could in GT4.
This became a bit of frustration for me when I attempted to log lap times on several tracks to compare the Mazda RX-8 to the Nissan 350Z. I literally had to write my times on a piece of paper because they weren't in the top eight (which is filled with nothing but supercars).
They clearly have a system in place to rectify this, but it's server-side. I have to do an online search for track/car to find out what my time was.
It just seems a little like going backwards... since GT always prides itself on featuring cars from all walks of life, it seems a little silly to not allow you to track your laptimes on any car with less than 500hp or so. This is going to be a bigger problem later on when the Top Gear test track is added. Their power-lap board isn't just the top ten.
Personally, I'd like to see a massive list, every lap I've ever set on every track, period. With a changeable option to remove duplicate entries (for example, I'm going to start practicing for this GTP registry thing, and I already know the whole leaderboard will be nothing but F430 after F430, rather than just logging my single fastest lap in that car.. it's going to push off everything slower than the F430).
It's not like it's a matter of storage space, like it may have been back in the old days. I figure, in terms of just the information that's displayed on-screen for the leaderboard (car/track/tires/physics/whatever), you could fit an entire entry in only a few bytes of data. A simple numeric code would work fine:
0618705100245693 That's 14 bytes of data.
Breakdown like so: TT-CCC-RR-P-TTTTTTTT
The first section is track, 06 could be, say, Suzuka. Next is the car, 187 could be a Daihatsu something-or-other. 05 is tires, say S2s. 1 indicates Pro physics, and the rest is the time.. 002:45.693. You could literally fit one million of these inside of a 14MB text file, which is insignificant on even a small 20 or 40GB hard drive. And that's keeping something crazy like ten thousand records for every track in the game. If you remove duplication, most people would probably never have more than a couple hundred records for every track. That's tiny.
So what's holding them back?
(Sorry about rambling, it's just that when something frustrates me, I also think about potential solutions and reasons why it's silly not to already have implemented them.)
This became a bit of frustration for me when I attempted to log lap times on several tracks to compare the Mazda RX-8 to the Nissan 350Z. I literally had to write my times on a piece of paper because they weren't in the top eight (which is filled with nothing but supercars).
They clearly have a system in place to rectify this, but it's server-side. I have to do an online search for track/car to find out what my time was.
It just seems a little like going backwards... since GT always prides itself on featuring cars from all walks of life, it seems a little silly to not allow you to track your laptimes on any car with less than 500hp or so. This is going to be a bigger problem later on when the Top Gear test track is added. Their power-lap board isn't just the top ten.
Personally, I'd like to see a massive list, every lap I've ever set on every track, period. With a changeable option to remove duplicate entries (for example, I'm going to start practicing for this GTP registry thing, and I already know the whole leaderboard will be nothing but F430 after F430, rather than just logging my single fastest lap in that car.. it's going to push off everything slower than the F430).
It's not like it's a matter of storage space, like it may have been back in the old days. I figure, in terms of just the information that's displayed on-screen for the leaderboard (car/track/tires/physics/whatever), you could fit an entire entry in only a few bytes of data. A simple numeric code would work fine:
0618705100245693 That's 14 bytes of data.
Breakdown like so: TT-CCC-RR-P-TTTTTTTT
The first section is track, 06 could be, say, Suzuka. Next is the car, 187 could be a Daihatsu something-or-other. 05 is tires, say S2s. 1 indicates Pro physics, and the rest is the time.. 002:45.693. You could literally fit one million of these inside of a 14MB text file, which is insignificant on even a small 20 or 40GB hard drive. And that's keeping something crazy like ten thousand records for every track in the game. If you remove duplication, most people would probably never have more than a couple hundred records for every track. That's tiny.
So what's holding them back?
(Sorry about rambling, it's just that when something frustrates me, I also think about potential solutions and reasons why it's silly not to already have implemented them.)
