Gran Turismo 7 with KytyPS5: prepared game root, tessellation and Lago Maggiore testing
ItsOOGWAY · PC guides & recorded tests
Gran Turismo 7 with KytyPS5: prepared game root, tessellation and Lago Maggiore testing
Gran Turismo 7 running on PC through KytyPS5: the Windows build, launcher setup, game-folder selection, graphics settings and real Lago Maggiore gameplay from my own test.
The key checkpoint: This guide starts with an already extracted game. Compare the exact Kyty GT7 build and per-game tessellation setting; an early incomplete car model and later gameplay are separate observations.
Before you start
- Use the recorded versions and the supported inputs listed in the original notes below.
- Compare the last successful checkpoint before choosing a fix.
- Keep original files, relevant logs and a known working setup when testing changes.
Resources from this video
Links, downloads & documentation
Every original URL from the video description is collected here, including recorded releases, setup discussions and related videos. Use the version-specific notes when following a recorded build.
Watch the complete video
Open this video on YouTube ↗. Screenshots below link to their exact recorded moments.
Walkthrough 01
Budget extraction space and identify the prepared inputs
The biggest surprise for me was how much space the preparation needed. There was the original archive, another copy after extracting it, and then the unpacked game files. Those copies can exist at the same time. Before you begin, check the space available on both the drive holding your files and the drive receiving the extraction. The download size alone does not tell you how much working space you need. I am starting this walkthrough with my extracted game folder ready.
Use game files that you have obtained legally. Keep your original backup until you have checked that the extracted files are complete and the game can launch. I would much rather you check that now than discover halfway through that you need to repeat the entire extraction.
Walkthrough 02
Download and extract the tested Kyty build
There are two separate pieces here: the Kyty program that runs the game, and the game folder that the launcher needs to find. Keeping those separate makes the next steps easier to follow. You do not need to put every game inside the emulator's folder. First, open the GitHub project linked in the resources section. The one in this recording is the Gran Turismo 7 fork by usa-ratt, called KytyPS5-GT7. That detail matters. I am demonstrating a specific build of that project, rather than assuming that any Kyty download will behave exactly the same way.
Open Releases and expand the assets for the build. On Windows, choose the Windows x64 ZIP. The Source code download is a different option; it is not the ready-to-run Windows package used in this video. I have linked the recorded release as well, so you can identify the version behind the footage even if the project has received more updates by the time you watch. Once the ZIP has downloaded, extract the whole package into its own folder.
Open that extracted folder and run launcher dot exe. Keep the other files beside it. The launcher is only one part of the package, and copying that executable out on its own is not the setup I am using here.
Walkthrough 03
Add the actual game root to the library
Now we need to tell it where the game is. Open the launcher settings and find the Game folders section. Use the folder button to add the location containing your extracted Gran Turismo 7 files. In my recording, this folder is on another drive. Your drive letter and folder name can be completely different. The useful thing to recognise is the folder's contents. Mine contains eboot.bin, along with folders such as contents and sce underscore sys.
I am selecting that extracted location. An unopened archive or the folder containing only your downloaded package is not the same thing. Save the settings and refresh the library. Gran Turismo 7 should now appear in the list. Select it and check the information against the copy you prepared. My recorded game is version one point seven one zero, with the serial PPSA zero one three one seven. That gives you something concrete to compare if your result differs from mine.
Walkthrough 04
Set per-game graphics and inspect tessellation
Before launching, open Edit game config for Gran Turismo 7. Pay attention to that window title. There are global settings, and there is a configuration for the selected game. I want the choices we are about to make to apply to Gran Turismo itself. Here is the configuration visible before my later gameplay. I selected nineteen twenty by ten eighty, Mailbox presentation, a Vblank frequency of sixty, and Performance for shader optimisation. I selected my NVIDIA GeForce RTX 4070 SUPER explicitly, and enabled fullscreen.
The important checkbox to find is Enable tessellation support. Turn that on. I will show you the visual problem this relates to after we get through the launch, so you can recognise it if you run into it yourself. These are the choices visible in my recording. They are a starting point for understanding this particular result, rather than a claim that every experimental checkbox should match mine on every computer. I have included the project's own settings guide in the description, because its recommended configuration has details worth checking for the exact build you use.
Save the configuration and launch the game. You should see the console and then the game window. I am shortening the waiting in the video, while keeping the important clicks at normal speed. Do not mistake that edit for an instant first boot on the PC. Getting to the title screen is the first checkpoint. We have moved from a folder of files to the game actually starting through the emulator. Now we can deal with the part that made the biggest difference to the final presentation: the graphics setup and the first trip onto a circuit.
Walkthrough 05
Compare in-game settings and earlier visual failures
Once the game is open, go into Options, then the Global section and Display Settings. Find Graphics Priority for PlayStation 5 and choose Prioritise Frame Rate. That is the mode I use for the driving shown here. Save or confirm the selection before continuing. Now, if your first attempt shows a car with missing bodywork or the scene looks unfinished, here is the short version of what to check. Close the game, reopen its configuration, and confirm that tessellation is enabled.
Check the selected graphics card and the in-game frame-rate priority setting as well. Make one deliberate change at a time, then relaunch and compare the same scene. You can see why I am pointing this out. Earlier in the recording, the presentation was much rougher. Later, I reached the cockpit driving that you saw at the beginning. I changed several settings and revisited scenes during that session, so I am not going to pretend that every improvement came from one magic switch.
There is also work happening the first time a new area appears. The project's notes describe shaders compiling in the background, with some scenery and details appearing late. Keep that distinction in mind: a scene that is still filling in and a game that has stopped responding are not automatically the same problem. Waiting can help with compilation, but it is not a guarantee that every visual error will disappear.
Walkthrough 06
Test the same circuit and retain build-specific evidence
This is still a development build. Some of my attempts had obvious rendering problems, and getting into a drive does not establish that every event or the entire game works. I am showing the successful path from my own session, together with enough of the earlier result that you can understand what changed. For the driving test, I went into World Circuits, selected Europe, and opened Autodrome Lago Maggiore. From there, I used Circuit Experience and the one-lap attack.
You can see those selections on screen, so you have a recognisable route to compare with your own setup. That route also gives us a useful way to look at the result. We are watching one car on a circuit, rather than assuming that it represents a full grid of opponents. Different events put different demands on the emulator. The most useful comparison is the same build, the same track, the same settings, and the same type of event.
I am going to leave a longer stretch of driving at normal speed now. Watch the movement through the corners, the cockpit, and the track ahead. Listen to the game as well. This gives you a much better sense of the experience than a few fast cuts between the best-looking frames. There is one number I want to keep clear. Recording or exporting this video at sixty frames per second does not prove the game itself stayed at sixty.
I did not record a readable performance counter throughout this drive, so treat this as a gameplay demonstration, rather than a locked-sixty benchmark. The footage lets you judge what I actually reached on this machine. For me, the exciting development is that we can get beyond the title screen, navigate the game, load this circuit, and drive it on Windows. After all the preparation and retries, seeing that happen on my own PC is the part I wanted to share.
The developers deserve the credit for making this possible. If you try it and need help comparing your result, keep the build version, game version, settings, and a description of where the problem happens. Those details make a report much more useful than simply saying that the game does not work.
If your result differs
| Situation | Next useful check |
|---|---|
| The process stops at a different checkpoint | Record the exact message, current build and last successful stage. Compare that stage with the matching video section. |
| A setting is selected but the result differs | Repeat the same scene and change one option at a time. A menu target does not establish measured performance. |
| A newer release changes the interface | Check the linked release notes and instructions. This companion preserves the recorded route and its limitations. |
Comments
Post a Comment