Horizon Zero Dawn Remastered Update 1.0.37 - 1.... __link__ (ORIGINAL • FIX)
Updates for Horizon Zero Dawn Remastered typically focus on bringing its technical standards up to parity with its sequel, Horizon Forbidden West
. While there is no specific official documentation for a version labeled exactly " 1.0.37 - 1
the most relevant recent update cycle for the Remastered edition includes Hotfix 1.0.38.0
, which addressed several critical stability and gameplay issues shortly after its October 2024 launch Key Updates and Changes
Recent patches for the Remastered edition (primarily on PC and PS5) have focused on these areas: Gameplay & Controls Concentration Skill
: Resolved an issue where the skill required two R3 presses to toggle after the first use. Aim Toggle
: Fixed a bug that caused the controller's Aim Toggle function to stop working after a cinematic. Bow Charging
: Players can now charge their bow while performing a dodge roll. Input Adjustments
: Corrected X- and Y-axis sensitivity for both mouse and controller inputs. Stability & Performance Crash Fixes
: Addressed crashes occurring after running the benchmark or during specific transitions, such as adjusting mouse and keyboard controls. Audio Balance
: Synchronized audio volume between pre-rendered cutscenes and actual gameplay. Visual Fidelity
: Fixed flickering or disappearing shadows in Meridian when playing at ultrawide resolutions. Quality of Life (QoL) Auto Pickup
: Added an option to automatically collect resources, similar to the feature in Forbidden West Color Blind Mode Horizon Zero Dawn Remastered update 1.0.37 - 1....
: New accessibility settings have been implemented to support more players. HUD Rendering
: Corrected HUD markers for objectives when using custom Field of View (FOV) settings. Remastered Features Overview
The Remastered edition includes significant overhauls compared to the original 2017 release: Visual Overhaul
: Upgraded character models, textures, and lighting to match the fidelity of Horizon Forbidden West Motion Capture
: Includes over 10 hours of additional motion-capture data for livelier conversations. Import Saves
: Players can import their original PS4 save data to continue their progress on PS5 or PC.
Horizon Zero Dawn Remastered — Update 1.0.37 (Summary & Analysis)
Final Verdict: Should You Install?
Yes. Unlike some patches that introduce more bugs than they fix, Horizon Zero Dawn Remastered update 1.0.37 – 1.0.38 is a clear step forward. If you haven’t started your replay yet, install these updates before you leave the Embrace. The audio is synced, the reflections are crisp, and the VRR flicker is dead.
Wait for 1.0.39 if: You rely on DualSense trigger mods, or you play exclusively on 32:9 super-ultrawide monitors. For the other 99% of players, this is the definitive version of a modern classic.
Stay tuned for our coverage of the upcoming 1.0.39 patch, which promises to fix the “floating Tallneck” glitch in the Cut.
*This article has been written for informational purposes. Patch notes are based on official changelogs and community reporting as of November 2024. Horizon Zero Dawn is a trademark of Sony Interactive Entertainment.*
5. General Optimizations
- Load Times: Reduced load times by ~0.7 seconds when fast traveling from Meridian to Devil's Thirst.
- DLSS 3.7: Updated DLL support for Nvidia users to reduce ghosting on tall grass.
- Memory Leak: Addressed a gradual memory leak occurring in the inventory screen after 3+ hours of play.
🖥️ PC-Specific (Steam/Epic)
- Added DLSS 3.7.0 support (replaces 3.5.10) for improved frame generation stability.
- Fixed ultrawide (21:9) cutscene letterbox stretching in The Frozen Wilds intro.
Chronicle: Horizon Zero Dawn Remastered — Update 1.0.37
Scope: a meticulous, chronological account of the development, release, rollout, and immediate aftermath of the Horizon Zero Dawn Remastered patch labeled 1.0.37. This chronicle assumes a single discrete update and documents observable events before, during, and after release, organized by timestamped stages and including technical details, player reactions, and developer communications.
Note: dates/times are presented relatively (Day 0 = release day) since no calendar date was provided.
Day −7 to Day −1 — Pre-release preparation Updates for Horizon Zero Dawn Remastered typically focus
- Development freeze and QA
- Codebase branch for 1.0.37 created from main remaster branch.
- Final feature/bug-list for the patch compiled: crash fixes, performance tweaks, save-file compatibility improvements, minor gameplay fixes, and UI text corrections.
- Automated builds run nightly; final candidate build created on Day −3.
- Internal testing
- QA ran full regression test suite on PS5/PC target builds (if applicable). Tests included: boot/load/save, rendering passes, HDR calibration, DLSS/FidelityFX checks (on PC), frame pacing, AI behavior regressions, and trophy/achievement triggers.
- Known issues logged: one intermittent stutter in Frozen Wilds area; minor UI localization mismatch in three languages.
- Localization and certification
- Localization updated for corrected strings; build packaged for platform certification.
- Submission to console platform certification on Day −2; internal release notes drafted for players and support staff.
Day 0 — Release day (release window: morning–afternoon local time)
- Patch publication
- Update 1.0.37 published to platform storefronts/servers. Manifest shows build id and checksum; size reported (typical small-to-medium patch; e.g., 200–1,500 MB depending on platform asset changes).
- Patch notes posted to official channels (developer blog/announcements) and support pages, listing:
- Fixed crashes during fast travel and entering photo mode.
- Improved memory handling to reduce out-of-memory crashes on 8GB systems.
- Resolved HDR tone-mapping inconsistency on PS5 with specific displays.
- Fixed intermittent stutter in The Cut area (previously noted).
- Corrected localization strings for German, Spanish, and Japanese.
- Minor UI layout fixes for quest log overflow.
- Stability and performance optimizations (CPU thread scheduling, reduced GPU spikes).
- Patch rollout mechanics
- Staged rollout (if used): update enabled for 10% of users for first 1–2 hours to monitor crash telemetry; then ramped to 100% after green signals from telemetry.
- Platform storefronts propagate update; some users begin automatic downloading.
- Immediate telemetry and logs
- Crash reporting shows initial reduction in several signature crashes (fast-travel-related). One new rare crash signature appears tied to a specific user-modified config on PC (if modding supported).
- Server-side analytics record patch adoption rate: ~30% within first 3 hours, increasing as time zones roll.
- Community reaction (first 6 hours)
- Social channels display a mix of praise for crash fixes and immediate bug reports. Top threads: "stutter reduced" and "HDR fixed for my TV."
- A minority report new regression: minor audio desync in certain cutscenes.
- Support and moderation
- Support teams prepare hotfix guidance: clear cache, rebuild shader cache (PC), and verify display HDR settings.
- Known Issues article updated with troubleshooting steps.
Day 0 — Evening (6–12 hours post-release)
- Telemetry assessment
- Stability metrics improve by measurable percentages: total crashes down ~25–40% in targeted areas; overall crash rate trending downward.
- Performance telemetry shows reduced frame-time spikes in sequences where CPU-GPU synchronization had been an issue.
- Bug reports consolidate
- Audio desync reports localized to a specific GPU driver version on PC and one firmware revision on select TVs.
- Regression reports contain reproducible steps; QA reproduces audio issue and files a hotfix candidate.
- Developer communication
- Short-form follow-up posted: “We're monitoring reports about audio in some cutscenes; investigating.” Players appreciate transparency.
Day 1 — Day 3
- Hotfix planning
- Engineering triage assigns priority: high (audio regression that affects cutscene experience), medium (rare mod-related crash on PC), low (minor text overflow).
- Patch 1.0.37.1 (hotfix candidate) created with a targeted audio fix and small stability patches; precision QA run on repro cases.
- Community and modder activity
- Modding communities provide logs showing that one popular HUD mod conflicts with a remastered shader change; mod authors update compatibility notes.
- Players posting side-by-side FPS captures show consistent improvements in previously problematic zones.
- Support updates
- Knowledge base updated with detailed steps to rebuild shader caches on PC and to toggle HDR auto settings on consoles as temporary workarounds.
Day 4 — Day 7
- Hotfix deployment
- Hotfix 1.0.37.1 deployed (staged rollout). Patch notes: fixed audio desync for drivers/firmware combinations; resolved rare mod-related crash by adding additional input validation.
- Metrics show audio desync reports drop to background noise; overall player satisfaction indicators (likes, positive comments) rise.
- Residual issues
- A small segment still reports one remaining crash on save reload after entering Photo Mode; engineering confirms a race condition in asset unloading under rare memory pressure.
- Team schedules a micro-patch (1.0.38) for the next sprint to address the race condition and polish edge-case telemetry logging.
Week 2 — Post-release stabilization
- Analytics and KPI changes
- Average session length increases slightly in affected regions; fewer interrupted sessions due to crashes.
- Support ticket volume for the game drops to baseline within 10 days post-release.
- Changelogs and transparency
- Developer publishes a more detailed postmortem entry in patch notes: lists root causes (memory handling edge cases, HDR metadata misinterpretation on certain displays), and high-level fixes applied.
- Community sentiment
- Overall sentiment becomes positive: players note smoother frame pacing and resolved show-stopping crashes; streamers highlight improved stability in long play sessions.
Technical details (what 1.0.37 likely changed — meticulous breakdown)
- Crash fixes
- Added null checks and locking around fast-travel callback handlers to stop null-pointer dereference leading to crash.
- Fixed reference-counting bug in photo-mode asset manager that caused use-after-free on rapid entry/exit.
- Memory and performance
- Adjusted texture streaming thresholds to reduce thrashing when streaming large environment textures in Frozen Wilds and The Cut.
- Optimized CPU job scheduling for animation update jobs to reduce main-thread stalls; moved non-critical jobs to worker threads.
- Rendering/HDR
- Corrected HDR metadata handling pipeline: clamp and convert metadata according to platform-specific requirements to avoid blown highlights on some TVs.
- Fixed shader permutation bug that caused a fallback codepath on certain GPUs, creating stutter spikes.
- Localization/UI
- Corrected truncated string tokens and adjusted UI layout constraints in quest log and inventory for fixed-width fonts in several languages.
- Platform-specific
- Console: adjusted save-file compatibility check to avoid unnecessary migration flagging older saves.
- PC: added defensive handling for unsupported GPU driver behavior; improved shader cache invalidation flow.
- Telemetry & diagnostics
- Added additional logging around memory pressure and asset unload timing for future debugging of race conditions.
Repro steps and diagnostics (for support teams)
- How to reproduce fixed crash (example)
- Load save near Embrace Outskirts.
- Fast-travel to Meridian Market.
- Immediately open Photo Mode, then exit.
- Previously: ~20% chance of crash during asset swap; fixed in 1.0.37.
- Diagnostic captures recommended
- Collect crash dumps and minidumps, shader cache logs, GPU driver version, TV/monitor model and firmware, and a short video capture showing repro.
After-action and lessons learned
- Importance of staged rollout to catch platform/display-specific regressions early.
- Increased emphasis on cross-team validation for rendering/display metadata changes (QA matrix expanded to include representative TVs and GPUs).
- Need for improved mod-compatibility guidance when remaster changes shader/asset handling.
Appendix — Suggested player actions (concise)
- If you encounter issues after 1.0.37:
- Rebuild shader cache (PC), restart console, clear temporary app cache.
- Update GPU drivers/TV firmware to latest stable versions.
- Remove or disable HUD mods until authors publish compatibility updates.
- If persistent crashes occur, submit crash logs and platform diagnostics to support.
End of chronicle.
The launch of Horizon Zero Dawn Remastered on PC and PlayStation 5 brought breathtaking visual overhauls. To ensure a flawless experience, developers Nixxes Software and Guerrilla Games pushed out incremental launch updates. Following initial release versions such as v1.0.37.0, the dev team quickly followed up with v1.0.38.0 to target critical performance snags. 🛠️ Core Fixes in the Immediate Launch Window
The transition from build 1.0.37.0 to 1.0.38.0 served as a rapid-response deployment to fix breaking bugs reported by early adopters on PC. Horizon Zero Dawn Remastered — Update 1
Benchmark Crash Resolution: A prominent bug in earlier builds caused the game to crash immediately after running the integrated performance benchmark. This was fully resolved.
Control Responsiveness: Adjustments to the X-axis and Y-axis for both mouse and controller inputs were failing to save or calculate correctly in build 37. The update successfully restored precision mapping.
Aim Toggle Rectification: Cinematic cutscenes occasionally locked out the controller "Aim Toggle" function. Normal operation now resumes automatically post-cinematics.
Concentration Skill Mechanic: Players previously had to double-press the R3 button to toggle the time-slowing Concentration skill after its initial activation. A single press now cleanly executes the command. 🎨 Visual and Audio Enhancements
Beyond immediate crash prevention, the post-launch update roadmap for the remaster has heavily focused on leveling out the audio-visual environment.
Audio Leveling: Pre-rendered cutscenes in early builds suffered from jarring volume spikes or drops compared to active gameplay. Patches have normalized dynamic ranges across dialogue and combat.
Ultrawide Asset Culling: Ghosting and flickering shadow artifacts surrounding major settlements like Meridian have been largely eliminated for ultrawide monitor users.
Custom FOV Tracking: Adjusting the Field of View (FOV) slider no longer causes objective markers to detach from their designated targets on the HUD. 🚀 Performance and Stability Under the Hood
To keep the massive world running flawlessly, Nixxes Software implemented several background optimizations: Horizon Zero Dawn Remastered Hotfix 1.0.38.0 - SteamDB
How to Download Horizon Zero Dawn Remastered update 1.0.37 – 1.0.38
On PlayStation 5:
- Go to Home > Horizon Zero Dawn Remastered > Options > Check for Update.
- The combined update is 1.95 GB. You must have 20 GB free for the installation process.
On PC (Steam / Epic):
- Steam: Library > Right-click HZDR > Properties > Updates > Verify files after download (recommended).
- Epic: Auto-downloads. If stuck on “1.0.37,” verify the binary. The 1.0.38 hotfix is labeled as “Build 15874321.”
Important: Existing save files from version 1.0.36 are compatible. However, modded saves (using Reshade or DLSS tweaks) will cause a crash on load. Disable all mods before updating.
Overview
Update 1.0.37 for Horizon Zero Dawn Remastered is a minor post-release patch focused on stability, compatibility with platform system updates, and small gameplay or UI fixes. It does not introduce major content additions or gameplay overhauls; instead it addresses specific bugs and optimizations to improve player experience and reliability across hardware configurations.
