Where are they ?

  • Thread starter Thread starter Mr Grumpy
  • 10 comments
  • 1,023 views
Messages
2,629
United Kingdom
United Kingdom
Where are the tracks saved ?
On the cloud ?
In a hidden folder ?
Or somewhere else ?

I've been trying to locate my track save data just to have a butchers (you never know what you might be able to tweak) but to no avail, any ideas ?
 
If you extracted them then they will be on your GT6. If you just saved them then they should show up as soon as you open the app
 
Where are the tracks saved ?
On the cloud ?
In a hidden folder ?
Or somewhere else ?
I've been trying to locate my track save data just to have a butchers (you never know what you might be able to tweak) but to no avail, any ideas ?
Device?
data/data/jp.co.polyphony.GTCourseMaker (root access required)

GT6?
  1. Start the game with the ID you used to sign in with in the app.
  2. Click on the Track Maker Import button.
  3. Click Load Track Data
    1. Drive 1 full lap.
    2. Exit the track.
    3. Click on the red ^ arrow icon to save the track when finished.
      1. OR Make endless adjustments till satisfied, then save it.
Once saved the track can be accessed through Manage Tracks next to the Load Track Data button.
 
Device?
data/data/jp.co.polyphony.GTCourseMaker (root access required)

GT6?
  1. Start the game with the ID you used to sign in with in the app.
  2. Click on the Track Maker Import button.
  3. Click Load Track Data
    1. Drive 1 full lap.
    2. Exit the track.
    3. Click on the red ^ arrow icon to save the track when finished.
      1. OR Make endless adjustments till satisfied, then save it.
Once saved the track can be accessed through Manage Tracks next to the Load Track Data button.

It was for device but my phone isn't rooted so never mind, just had a idea if it was possible to transfer file data say from a track you created on eifel flat & copy it into another map's file data so you get all the all hills & mountains.

Affectively laying your course over different backgrounds.
 
It was for device but my phone isn't rooted so never mind, just had a idea if it was possible to transfer file data say from a track you created on eifel flat & copy it into another map's file data so you get all the all hills & mountains.

Affectively laying your course over different backgrounds.

It looks like the app keeps its own file list and fails to recognize files whose name was changed (all 3 identically changed). A blank square is presented for view and the app spins its wheels trying to load the now non-existent files. Reverting to the original naming recovers the info though.

When someone finds the location of this list info (Probably an SQL database) we may be able to then rename & add files from other sources.
So rooting will not help with a solution as yet.
 
So rooting will not help with a solution as yet.

The base file name is stored twice in the .meta file, and once in the .bin file. At a guess, those link the .meta to the .bin and the .png, and the .bin to the .meta (dunno why else the .bin would need to know its own name!).

Changing the filenames and those stored inside the files worked fine; I got a second copy of the track showing in the editor (after refreshing the track list by editing another track and quitting back).

I didn't change the length of the names because I haven't looked into the .meta file yet - probably some other bytes need to be altered if the length changes (they certainly would in the .bin). But seeing as the .bin looks hackable, I don't see why the .meta wouldn't also be :D
 
The base file name is stored twice in the .meta file, and once in the .bin file. At a guess, those link the .meta to the .bin and the .png, and the .bin to the .meta (dunno why else the .bin would need to know its own name!).

Changing the filenames and those stored inside the files worked fine; I got a second copy of the track showing in the editor (after refreshing the track list by editing another track and quitting back).

I didn't change the length of the names because I haven't looked into the .meta file yet - probably some other bytes need to be altered if the length changes (they certainly would in the .bin). But seeing as the .bin looks hackable, I don't see why the .meta wouldn't also be :D
I understand you are saying 2015_1002_152422 can be altered to Just_a_test_1234 and it works when both the content and names are altered? That is promising. Keeping the device source linked to the renamed GT6 file becomes a bear with differing versions of a layout as the track count begins to climb. Version Control is non existent ATM.
 
I understand you are saying 2015_1002_152422 can be altered to Just_a_test_1234 and it works when both the content and names are altered? That is promising. Keeping the device source linked to the renamed GT6 file becomes a bear with differing versions of a layout as the track count begins to climb. Version Control is non existent ATM.

Yup. I'm sure a rename tool could be made soon-ish, allowing names to change length. All I did as a test was alter 2015_1006_212241 to 2015_1006_212243 and copy the files back into the 'files' folder.

But, since it limits you to 30 tracks, you'd still be copying them in/out of the 'files' folder a lot anyway :(
 
@Outspacer would you please share which editor you use to view/edit with?

I'm using an old version of '010 Editor' because I happened to have it and it can apply a template to the raw data - very handy for delving into the unknown! It's not freeware though. Any half-decent hex editor would do, as long as it can interpret floating-point and big-endian integer values (first help was to identify f-p values that were in a sensible sort of range).
 

Latest Posts

Back