Couldn't even complete a lap lol, the banking gets so steep it just sucks you to the edge of the track, then you're stuck.
Had some hard time trying to complete it aswell
. But finally managed to get through the last corner and save the track
.
I honestly wish I knew. I happen to take full advantage of the work you guys do.
Ah, thankyou, I see it's down to the source code. Makes me want to go back and retake my programming course. A lot of it remindes me of Javascript. Although I can not remember the program we used to code software. Looking at it's appearence number, it's no wonder its rare to get one to pop up. Once I get this figured out, I'll try it out. I've been wanting a touge with a PA either at the end or halfway through.
When I first looked into these files. All I had done to APK:s previously was decompile and look what's inside them. And for C# assemblies I had only decompiled them with .NET Reflector and nevery modified one of those either. So I started from a scratch aswell ^^.
So go ahead and inspect the files
.
Tools you can use to modify the assembly:
1. 7Zip (To extract the Assembly-CSharp.dll from the APK and put it back after modifying)
2. .NET Reflector (To dissasemble the Assembly-CSharp.dll)
3. Reflexil addon for .NET Reflector (To be able to modify Assembly-CSharp.dll without re-compiling it)
4. APK Signing tool (I have signapk.jar and I use the testkeys)
As for uploading the GT6TED, I would say the interesting files are CompanionPlugin.cs and ps2zip.cs. Altough it appears you don't need to encrypt the GT6TED even though the APK does it. You can just send the unencrypted one and it will still work.
And well you could also just code a application that does the uploading so you don't even need to modify the assembly. The one I build with Unity is taking only 54 lines of code and even that could be squeezed down a bit. You can pretty much use the ready code from the CompanionPlugin.cs, you only need to get the cookie generated. For that you could use the PSNLib
@PR1VATEJ0KER mentioned and then the code from the CompanionPlugin.cs to get the Cookie from the AuthenticationToken. Alternatively you could just take it from the cookie storage of your browser
.
As for modifying the GT6TED, I already shared my 010 Editor templates which you can use to figure out what is what.
For the rail_def files, you can just use the Notepad++ for modifying that. The asset file keeps track of the filesize so if it changes, you need to modify them. But you can just keep the filesize intact. Example you want the value 100 to 10, use 010
. Resign after modifying:
https://www.gtplanet.net/forum/thre...racks-discussion.337816/page-15#post-11364770
Have fun