Going back to the screenshot of Route X...

  • Thread starter Thread starter MasterLeaf
  • 39 comments
  • 4,632 views
But we can already get that data, no?
Yes and no.

I mean, loading a replay into Data Logger can provide you with the very detailed data about engine performance.
The data logger interface is hideous however. You don't get a detailed grid to discern intermediate values, you can't export data, only best laps get in a single session displayed quickly.

And, as a final note, not only the data logger interface could adopt vast improvements, it doesn't seem there is a quickly accessible data logger feature here in the Speed Test screen:

user204729_pic39466_1326250653.jpg
 
0-100 Km/h, 0-200 Km/h, 0-400m, 0-1000m, top speed, skidpad g acceleration, make me think... is this all for a feature it took over a year to implement? Either PD developers lack imagination or believe we're all dumb and can't handle too much information.

This must be your first GT game because those tests have been in GT since the first GT game. PD does not lack imagination or believe we are dumb. They seem to not want to over complicate things. Besides its just a game.
 
This must be your first GT game because those tests have been in GT since the first GT game. PD does not lack imagination or believe we are dumb. They seem to not want to over complicate things. Besides its just a game.
I know that those tests have been in GT until GT4.
I meant that since they're introducing them in GT5 only now (over a year after its release date), since they were at it, they could have made them more detailed, interesting and useful.

0-100 m, 0-200 m - 0-60ft - 0-330ft - 1/8 mi? They're important especially when drag racing slower cars. Exit speed too is a very important value that should be known.
0-100 km/h and 0-200 Km/h ? Not enough for either slow or really fast cars.
No reaction time? Most probably this means we won't be getting proper drag racing, again.

There's no need to "overcomplicate things" with a proper UI instead of the clutter proposed above, robbing a lot of screen space for very little information.
 
Last edited:
Bigger screens for Route X, then we can chat about. I'm trying to figure out something about the cones... Looks like there's 2 areas besides the track with cones.

OtmPf.jpg

ZPtwy.jpg
 
Yes and no.

The data logger interface is hideous however. You don't get a detailed grid to discern intermediate values, you can't export data, only best laps get in a single session displayed quickly.

And, as a final note, not only the data logger interface could adopt vast improvements, it doesn't seem there is a quickly accessible data logger feature here in the Speed Test screen:

user204729_pic39466_1326250653.jpg

Doesn't Data logger only come in practice in A-spec. I dunno.
 
It's an interesting point about the Data Logger.

I loved it in GT3, I would spend hours watching my NSX shimmy over the curbs around Complex String in slow-motion. But the one in GT5 is "boring" and doesn't allow the dynamic scrolling through the data, visualised in real time, or slow-mo, and scales on both axes aren't as adjustable either. But that's OK, because it's just meant to be a tool, right? Shame that information isn't exactly forthcoming from its "minimal" design, though...

I think someone at PD took the lessons in The Visual Display of Quantitative Information to heart. I read it whilst I was working on research projects a few years ago, and I was tempted (for a "laugh") to present my results in figures inspired by the most minimal examples from that book to the department; but I never actually mustered the courage, given it would only (severely) enrage those who were used to actually being able to read exact information from charts, as opposed to just being able to gauge roughly what the relationship was (or just being given a number).

In other words, it's a lot of work to actually extract numbers from the data logger; much as it is with the gear ratio chart (oddly enough, GT1 gave you those numbers i.e. max speed in all gears etc.; which is, of course, a waste of "ink", when the same data is in the graph... somewhere. ;)).
 
Back