GT Pro Tune - The GT7 Tuning Calculator - Tune every car in Gran Turismo with this app!

  • Thread starter Thread starter hookedonturbo
  • 1,686 comments
  • 422,946 views
Hi,

Just thought I would follow up, I thought initially you were just coming on here to show off or try and “derail my thread” as you mentioned. But then I thought about it and that wouldn’t make sense. Apologies for jumping to conclusions.

I guess maybe you were looking for a common ground convo, I know making this calculator was a very lonely process, lots of hours in game evaluating and testing and re evaluating! Then even more hours in front of of an excel spreadsheet taping in formula after formula making equations from car suspension tuning books and blogs make sense!

For your comfort, you were definitely on the right track (no pun intended)! The base (stable) setup, is foremost the right place to start then be able to soften or harden to suit the car and drivers preference (both variables that cannot be calculated) I also incorporated a drivetrain denominator that uses a guesstimate weight for the differentials and driveshafts based on the fact if it has those upfront/rearward or both axles.

Also built into the calculations is a multiplier for ROAD/GR4/RACE/VGT or Formula. This give an initial shift of hardness to suit the probable physics model differences of the different suspension types.

There are many other factors that I have built into this that I’m not going to divulge here, but I can safely say that this is the most complex and accurate tuning app ever built for the game. Although I’m sure someone will put me back in my place after saying that! Haha!

If you do ever get back into the game, let me know I’ll hook you up dude!

To be fair, you don't have to apologise, you were right. To cut a long story short, too many beers, hefty natural dose of 'fight or flight' and getting triggered, ended up with the inevitable. But, to be fair, I'd been popping back under the same conditions for a while, but always managed to walk away, well until last week. Oh well, managed to get one decent post in. So will try posting when sober from now on

I did write a full on proposal/presentation for an app based on our calculator, but that along with pretty much everything else is now long gone.

I do remember a bit about the 'solution' I was thinking about (from where last post left off i.e. looking at dealing with driver variables the wrong way).

I'll see about typing it up and posting it if you want. In a way it's exactly the same as what you posted (separating problem areas i.e. braking, mid corner etc), but the ideas for how the app and user 'fixes this' are a little bit different, so maybe this might help give some ideas.

One of the negatives of using drivetrains as the starting variable is that sometimes/usually there are cars that are odd ones out (i.e. that don't conform to the handling norm for that drivetrain or type of car). At first it seemed like a problem, but then you get to realize the amount of cars that are like this are a very small minority, so dialling in an individual custom setting especially for these wasn't too much hassle. Although, sometimes they can be a right pain in the butt i.e. Z4 GT3, on GT6 I think.

Sometimes it might not be the 'handling', it might be a setting that sets them apart from the others of a similar kind, like the DTM Merc that had way more aero than the other FR DTM cars. I think we used to run that on hards and let everything else on mediums just to stop it being a 'cheat car'. As good as the drivetrain variable was to start with, there always had to be a way to deal with exceptions to the norm, but I'm guessing you got that covered.

There's a few other things that I never 'went public' with regarding the calc, obviously, got no idea about the app or your tuning history, plus haven't got GT7, so don't know if some if this would help or is stuff you already do / or know?

Sometimes I did something that I called 'reverse tuning' (others probably have different names for it or probably do it as 'normal' nowadays?). I don't think many people did it back in t'day, but happy to be corrected, but I'll try and explain it:

Car understeers, normal fix would be to change something at the front, but instead I'd change something at the rear
Car oversteers, normal fix would be to change something at the rear, but instead I'd change something at the front

i.e. you 'tune' the opposite end of the problem rather than 'tune' the end of the car which has the problem. There's more to this, but don't want to write an essay if you already know. This was the 'secret' to tyre wear (or lack of it ;) ) on some of my setups. But hey ho, might as well go for it now the cat is out the bag, happy Xmas(!), let me know.

There was another 'reverse' trick on certain cars that was from the calc. Normally the dampers should be roughly the same approximate (%) strength as the springs and the reverse of roll bars (which gives that core stability). But on some cars that I used high default % values (i.e very stiff) at the front and low at the rear, you can switch the dampers around and put the low rear ones on the front and vica versa. Not sure if I've explained that clearly(?) or you know about this little 'trick' already. It only ever worked for dampers though and was very handy at helping out on cars that understeered like an ocean liner going into a corner.

I'll shut up now, and go see what I can dig up that I might have left and write up my proposed 'solution' to the driver variables as best as I can remember it if you want.

Keep rockin' :D

H
 
Last edited:
Getting back into GT7, and found this post. Went to try out the app, I want to get the Advanced version without the AI, if I just hit the 'Buy Now' button, it doesn't do anything. If for some reason, I check the box for the AI, and then hit Buy Now, it goes to the purchase page, but only has the monthly AI listed, not the Advanced version of the main app.

Any help would be appreciated.
 
Getting back into GT7, and found this post. Went to try out the app, I want to get the Advanced version without the AI, if I just hit the 'Buy Now' button, it doesn't do anything. If for some reason, I check the box for the AI, and then hit Buy Now, it goes to the purchase page, but only has the monthly AI listed, not the Advanced version of the main app.

Any help would be appreciated.

Hi Pat,

Sorry, bit of a technical glitch happening at the moment! Bear with us while we fix the database.
 
Last edited:
Getting back into GT7, and found this post. Went to try out the app, I want to get the Advanced version without the AI, if I just hit the 'Buy Now' button, it doesn't do anything. If for some reason, I check the box for the AI, and then hit Buy Now, it goes to the purchase page, but only has the monthly AI listed, not the Advanced version of the main app.

Any help would be appreciated.
Hi Pat,

Please login with the email and password that you signed up with. Then click the upgrade link to purchase.

That should hopefully solve it for your case.
 
This is 'part 1' of how I was trying to find a solution to driver variable problem. I split this into 2, part 1 was about getting user to communicate feedback accurately, part 2 was taking that feedback and applying it to the setup. I used flow charts (I can't remember if there were 2 or 3 charts to be honest), which were very helpful to 'see' if any areas of the solution were being duplicated or it was becoming maladaptive and was going to end up chasing my tail. Unfortunately, this all got chucked a few years ago when I packed up my wheel etc.

All I got left are a couple of images used on my old sight (that might be applicable?) and a couple of testing videos I was going to 'use' to explain / show how I was testing. Attached are the images, these are just an example of communicating using visual cues rather than words, and these were for 'track limits' in our lobbies. If anyone knows how to post a vid I'll upload the testing vids, that's even if anyone is interested

Obviously, this was all 10 years or so ago, so can't remember everything exactly as it was, but hopefully this shows how looking at things from user perspective can be a bit different to creator perspective, maybe (?). I've tried to do this in a way which could (maybe) make it be easier to extract/copy onto a flowchart if need be. Also, any questions are effectively me 'thinking out loud' to myself i.e. it was basically a brainstorm with myself, which was interesting :boggled: :lol:

I can't remember all the driver variables, but most of them were on the previous post, pretty sure if need be, any ones missed could be found. So, here's the 'brainstorm':
  • Problem 1 - what happens when user asks for more than one driver variable - or when someone chooses a large group of different driver variables for the calc/app to incorporate onto base setup?
  • Problem 2 - the sheer amount of custom values required to deal with all of this (I have no idea, but now it must be running into thousands), would that even be physically possible? Something like steering sensitivity would have multiple options just on it's own. What if two (or more) of the variables start to 'contradict themselves' in terms of what the calc/app is proposing for the 'answer'.

(NOTE: Part of this is applicable to PART 2 where there needs to be a 'decision' by the calc/app as to whether to keep on amending the original base setup, or to start afresh with a new base setup that is better suited to the users needs and therefore would need less amendments, which would reduce the chances of 'contradiction' occuring).


Possible solution:
The one 'thing' who knows the needs/requirements of driver/user better than anyone else is always going to be 'themselves'. So how about getting 'them' to do the fine tuning 'themselves'? But, that leads to a couple of potential new problems...

  • Problem 3 - if user is using a tuning app/calc, chances are they probably don't 'know' about tuning generally (or maybe specific things like terminology i.e. understeer, springs, LSD). So, if there is a terminology issue, how can you get the user to 'fine tune' a setup, the calc/app has given them, to their needs?
  • Problem 4 - also, if user has paid for the calc/app, they might not be too chuffed when calc/app asks them to 'do the fine tuning' themselves. I mean, this is what/why they're paying for the calc/app to do(?)

Possible solution:
Maybe if there was a way whereby the calc/app makes the user 'think' that it's the calc/app that's 'doing the fine tuning', when in fact it's the user who is doing it.

  • Problem 5 - But, this would need a way for the user to accurately tell the calc/app what the problems are, which potentially takes us back to issues highlighted in problem 3(?)

Possible solution:
Before starting to address what is 'wrong' with the 'setup', maybe it would help if we could establish what is the best way for the user to accurately communicate the problem(s). Not everyone has the same knowledge of the terminology involved

  • Problem 6 - this feels like we're going back to what the original problem was (too many variables)
Possible solution:
What about having an option on the calc/app whereby the user can choose how to 'communicate' the problem i.e. a bit like how a person 'personalises' what they see on screen when playing GT i.e. changing the view, what things to display. So, on the calc/app there will be some kind of an 'option'(?) for the user to select between, main possibilites/examples:

Using terminology (words)
Or
Using 'visual' cues i.e. images or video

  • Problem 7 - language, what if user doesn't speak english(?)

Possible solution:
Maybe this reinforces the notion of using of visual cues, rather than words, (thus killing 2 birds with one stone?)

END PT 1

I looked upon these issues as driver variables are going to impact a setup much the same way as the settings within the setup i.e. understeer/oversteer, braking, mid corner, grip/acceleration. So the calc/app can 'react' in the same way whether the 'problem' was with the base setup or driver variable. So that is what part 2 was about.

----------------------------------------------------------------------------------------------------------------------------------------------------

Not sure how soon to post part 2 as this took a while, had to do this from scratch, from memory. Hopefully there might be something here that helps in some way, shape or form, or helps to give 'ideas' for the future(?)

H
 

Attachments

  • Cornercut1_zps14213532.webp
    Cornercut1_zps14213532.webp
    40.9 KB · Views: 1
  • Cornercut2_zps289038e5.webp
    Cornercut2_zps289038e5.webp
    22 KB · Views: 1
Last edited:
Back