Gran Turismo Sport on Windows: RyGT folders, launch recovery and shader behavior
ItsOOGWAY · PC guides & recorded tests
Gran Turismo Sport on Windows: RyGT folders, launch recovery and shader behavior
How to play Gran Turismo Sport on PC with the unofficial RyGT Windows port. This complete setup walkthrough covers the tools, base game and 1.69 update, system modules and fonts, the nested-font-folder setup error, the black-screen launch problem I encountered, shader compilation settings, and actual racing gameplay.
The key checkpoint: Keep base game and update in their separate launcher fields. Distinguish a failed boot from long first-visit shader work before choosing a fix.
Before you start
- Recorded build: gt-sport-2026-10-18-2; game CUSA03220, update 1.69.
- Select actual extracted modules and font folders.
- Keep frame generation off for the recorded starting baseline.
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
Identify the tested game and port
The project I'm using is RyGT. It's a community project for running Gran Turismo Sport on Windows, and it's still being developed. This recording uses the October eighteenth second build. A newer release may look slightly different, so check its instructions before copying settings from any tutorial. For this setup, the game version matters. I'm using Gran Turismo Sport with the title ID CUSA03220 and update version one point six nine. Check both before you start.
A different region or an incomplete update can leave you following the right steps with the wrong files. You'll need the Windows release of RyGT, a PKG extraction tool if your game is packaged that way, your own decrypted game dump and matching update, and the system modules and fonts required by the launcher. The RyGT release itself does not contain the game.
Walkthrough 02
Extract the base, update and application
Open the project's GitHub page, go to Releases, and download the packaged Windows build. Choose the release archive with the application and its supporting files. The source-code archive is intended for building the project yourself. For extraction, I'm using the ShadPS4Plus PKG Extractor shown here. Download its Windows package from its release page and extract it into a normal folder. Keep the supporting files beside the executable. Before extracting the game, make sure the destination has enough free space.
For a while you'll have the original packages and their extracted contents on the drive together. Use a location you intend to keep, because moving the folders later means updating the launcher's paths. Here are my two packages: the base game and its update. In the recording, I extract the update first, then the base game. Drag the package onto the extractor application, let the extraction finish, and repeat for the other package.
Walkthrough 03
Set the four launcher paths
The extraction takes several minutes in my recording. I'll speed up that waiting time while keeping the start and completed result visible. On your PC, wait until the extractor reports completion before closing its window or starting the next step. Once both are extracted, check the resulting folders. My base game is in CUSA03220, and the separate update is in CUSA03220-patch. These are the two locations I'll give to RyGT. Keep them separate for this method; the launcher has an update field for exactly this arrangement.
Next, extract the complete RyGT release. Open the extracted folder until you can see RyGT.exe beside its libraries and other support files. Run the application from that extracted location. The top of the launcher has four paths. Take a moment with these, because a folder-selection mistake can look like a much bigger problem later. For Game, browse to the base game's CUSA03220 folder. Select the actual game directory, where the executable and game data are located, rather than a folder that only contains another CUSA03220 folder.
For Update, select the matching CUSA03220-patch directory with the one point six nine update. Check that you're choosing the extracted update folder, rather than the original PKG file. Now add the system modules and fonts. Extract those files before browsing for them. In this recording, the archive opens into another folder, so pay attention to the folder contents rather than assuming the first directory is the one you need.
Walkthrough 04
Investigate the recorded failed launches
For System modules, select the extracted module location. For Fonts, select the location containing the font and font2 folders. The game's own sce_module directory and the firmware module location serve different purposes. My early attempt involved browsing to the game folder here; use the prepared firmware files for this field. With the paths selected, start with a straightforward display configuration. I'm using Windowed mode and nineteen twenty by ten eighty. Leave the FPS counter enabled so you can see what the game is doing during loading and racing.
Set the memory option to match the RAM actually installed in your computer. My recorded setup uses the thirty-two-gigabyte option. That selection isn't something to copy if your machine has less memory. The launcher also exposes upscaling and frame-generation options. I leave frame generation off in this walkthrough, and I don't install the optional DLSS files. You can establish that the game starts and runs before experimenting with those extras. Now press Set up. This prepares the Windows executable and the files the port needs.
Watch the status and log area at the bottom, and let the operation finish. When setup completes, press Play. This is where my first attempts went wrong. A game window appeared, stayed black, and closed again. Changing the resolution and toggling graphics settings didn't get me into the game on those attempts. Here's the recovery sequence that led to my successful launch. I checked Windows Security because I suspected it had interfered with a required file.
If you're investigating the same symptom, look at Protection History and check the affected filename and location. An empty history doesn't establish that antivirus caused the crash, and a black window alone doesn't identify the cause either. Keep the release from the project's own page, check any detection before deciding how to handle it, and avoid treating a blanket antivirus shutdown as a required installation step. Then close the launcher. In the extracted RyGT folder, right-click RyGT.exe and choose Run as administrator.
That's the application I reopen in my recording. I run Set up again, wait for it to finish, and then press Play.
Walkthrough 05
Understand shader preparation and its trade-offs
After that sequence, my game reaches the Sony screen and the first-run display setup. That's the result we're looking for. Administrator access is a troubleshooting step that I used here; it isn't proof that every startup failure has the same cause. You may also see a save-migration prompt if an older setup already left save files on your machine. Read it before choosing an action. It offers to copy or move existing data, so preserve your saves rather than clicking through it blindly.
On the first successful boot, complete the display settings. I choose standard SDR for this recording, continue through brightness adjustment, and reach the welcome screen and first gift car. Give the game time to finish these first-run screens. If input isn't responding as expected, return to the launcher's Controller ports or Button bindings options and check the assigned device. These are available before you launch the game, so you can verify the controls before entering a race.
Now the game is open, but we're not finished. My first visit to the car selection and race screens has long waits, and the race preview spends time showing almost nothing. This is the part where it's easy to assume the installation has failed again. Look for the compiling-new-shaders message. A newly visited scene can require more graphics work to be prepared, and the launcher lets you choose what the game does during that wait.
I already had Precompile shaders on the splash screen enabled. I keep it enabled. It prepares previously encountered shaders before the game starts, so on the next launch you may see a progress bar and a longer splash screen. That doesn't mean it can prepare every scene you've never visited. New shaders can still appear when you choose another car or enter another track. Keep the cache so the work can be reused on later visits.
The change I make here is under When new shaders compile. It was set to Slow motion. I change it to Keep going, which the launcher labels with objects popping in. That label explains the trade-off. Keep going lets the game continue while new shader work is happening, but some objects can appear late. Pause the game waits for the work to finish, and Slow motion changes how the game progresses during compilation. Choose the behaviour you prefer; none of these removes the work the renderer has to do.
Walkthrough 06
Retest a real race and compare results
For the final attempt in this video, I'm using Keep going with splash-screen precompilation enabled. I leave compile batching at Off. I close the game before changing the options, then relaunch and let the shader progress bar finish. Now I return to Arcade mode and choose the Colorado Springs Lake dirt race. I'm showing this attempt at normal speed so you can judge the result yourself. The earlier loading and compilation waits will be shortened, but this driving section will keep its real timing.
The result is much more useful than the first attempt, because we're actually driving around the circuit. The counter reaches sixty FPS in sections of the recording, and it also drops below that, including while new shaders compile. This isn't a locked-sixty result or a controlled benchmark proving a particular percentage gain. Both the changed shader behaviour and the work already cached from the earlier visit matter here. A fresh track, a different car, more opponents, or different hardware can produce a different experience.
That's the complete setup I used: the matching base game and update, the extracted modules and fonts, the launcher's setup process, and the recovery sequence that got my game started. Then we adjusted how it handles new shaders and tested an actual race. RyGT is still a developing project, so expect some rough edges. If you're troubleshooting, separate a failed launch from a shader-compilation wait, keep your working files and cache, and check the logs instead of changing every option at once.
I'll put the project references and the relevant links in the description.
If your result differs
| Situation | Next useful check |
|---|---|
| Black window then exit | Read logs and any Windows Protection History entry; do not assume antivirus is the cause or turn protection off wholesale. |
| The first race barely progresses | Inspect shader-compilation activity and the selected waiting behavior. |
| Keep going appears smoother | It permits object pop-in while work continues; cache reuse also affects later visits. |
Comments
Post a Comment