PC launch, audio and crash troubleshooting

The latest fetched notes are Hotfix 1.4.2. They address missing Zoe in The House in Distress, being trapped in the Gap after leaving the post-Artist ability prompt, unavailable Busken dialogue about Underhill, the missing dog-quest reward, an inactive Firebreaker, escort positioning, Wallet Artifact Burn damage and localization. The patch guide separates these fixes from the older 1.4.1 Park Mold and Dash/Elevate fixes. Kingy has not tested affected saves.

Remedy acknowledged that its launch hotfix triggered PC platform behavior that made some players download CONTROL Resonant again after preloading it. The developer did not publish a method to restore those preload files. A new download beginning is different from a download that remains stuck; clearing the cache is Remedy’s step for the latter, not a way to avoid the hotfix redownload.

These steps are for Steam on PC. Remedy says clearing temporary download data does not uninstall games or delete saved progress. If the download still fails, follow its installation article or contact Player Support with the exact error.

1. If Steam has started downloading again, allow the current download to complete if it is progressing; check available SSD space before retrying a failure.
2. If the download stays stuck, repeatedly restarts or fails before installation completes, close the game and open Steam → Settings → Downloads → Clear Download Cache.
3. Confirm, sign in to Steam again if prompted, then return to Library or Downloads and retry CONTROL Resonant.

The September 24 PC 1.3.3 list is historical. Update 1.4.0 announces fixes for Steam Input controller reconnection, subtitle speaker names with non-English voice-over, incorrect vendor prices, audio desync, HDR highlights and crashes when toggling ray-tracing modes. Kingy has not tested these fixes.

Update 1.4.0 links an AMD optional driver release for performance and crashes. Use your GPU vendor’s current compatibility guidance; this is not a recommendation to install an old optional driver on every AMD card.

For the historical FPS drop after changing ray-tracing quality, Remedy gave a restart workaround. The fetched later notes do not explicitly resolve that exact symptom. If it persists, compare the same scene after a restart and report the current build. Historical Underpass ultrawide black bars also had a restart workaround; later broad ultrawide fixes do not establish that every old report is resolved.

1. Check your PC version and read the latest developer known-issues thread.
2. For a listed symptom, try only the workaround Remedy gives for that symptom.
3. For unlisted or persistent failures, continue with the installation, stability and support-report steps below.

Let verification finish, restart the launcher and retry. Remedy’s installation article also covers runtime components and a clean reinstall if the problem persists. Use its linked Microsoft and GPU-vendor downloads.

Update 1.4.0 announces audio-desync fixes and adds a radio-dialogue volume slider. Persistent crackling or missing sound can still require Remedy’s PC audio checks; the notes do not identify one cause for every report.

These instructions apply to Windows PC. They do not establish the cause of any individual report or a console fix.

1. Close the game and play sound in another app. If that also fails, check the Windows audio device and connection first.
2. In Options → Audio, check Master, Speech, Music, Effects and Controller Speaker volume. For a neutral test, set Dynamic Range to Default, Hyperacusis Filter to Off, and Speaker Tuning bass and treble to 0; keep Mono Audio if you need it for accessibility.
3. Close the game. In Windows Settings → System → Sound, select the intended output device and confirm its volume. After relaunching, check the Windows volume mixer for the game’s level and output routing.
4. If sound still crackles, temporarily turn off Windows Audio enhancements and Spatial sound for that output device, then test again. Restore either feature if it does not affect the problem.
5. If the issue persists, follow Remedy’s article for supported audio formats, the correct device manufacturer’s driver, and game-file verification. Record your device, driver and symptom when contacting support.

Keep notes of the resolution, preset, driver and scene. These are official troubleshooting checks, not tested optimal settings or an FPS promise. Ask support before advanced driver-removal procedures if the routine steps fail.

1. Restart the PC and install pending Windows updates.
2. Check the final hardware requirements and leave SSD room for updates.
3. Install the appropriate current driver from NVIDIA, AMD or Intel.
4. Temporarily close extra recording tools and overlays, then retry the same scene.
5. If you use custom overclocks or undervolts, test the normal settings.

Close the game and its launcher, then copy the complete relevant folder to a separate backup location. Keep the original in place. For a non-default Steam install, start in that installation’s userdata directory.

1. Choose the account folder that contains your Resonant saves.
2. Copy the folder without renaming or removing its contents.
3. If Player Support requests it, ZIP the copy and attach it through the official support channel.

Open Remedy’s CONTROL Resonant Help Center and use the support chat for a bug or crash report. Include the storefront or console, mission or area, exact error, steps to reproduce it and recent loadout changes.

For PC issues, support can request DxDiag, MSInfo and a save copy. The reporting article permits direct attachments under 25 MB and gives separate instructions for larger files. Keep account credentials and unused redemption codes out of public screenshots.

BenchmarKing’s settings table is a useful starting point when you want to compare individual options. It is a creator recommendation, not an official preset or a measured result for your PC. The recording’s exact game build is not established.

1. Record your GPU, VRAM, driver, resolution, upscaler and current game version before comparing results.
2. Choose one option to adjust, then compare the same scene. The table recommends Low or Medium textures specifically for 8 GB GPUs; do not read that as a requirement for every card.
3. If changing ray-tracing quality still causes the historical FPS drop, try Remedy’s restart workaround. Later 1.4.0 notes address crashes when toggling RT modes; that is a separate symptom.
4. If the same scene becomes less stable or loses too much detail, restore the previous value before testing another option.