Linux Gaming Matures on Bazzite: AMD Shines in GN GPU Benchmarks

  • Thread Author
A high‑profile benchmarking video from Gamers Nexus — conducted on a Fedora‑based gaming image called Bazzite and covering modern GPUs from both Nvidia and AMD — argues that Linux gaming is no longer niche and, in many real‑world cases, is good enough to be a practical alternative to Windows for a large number of players, especially those running AMD hardware.

A dim, neon-lit gaming setup with an RGB PC tower and a Steam library displayed on the monitor.Background / Overview​

The timing of the Gamers Nexus tests is consequential: Microsoft’s move to retire widespread Windows 10 support and the ongoing friction around Windows 11’s hardware requirements have pushed many users to reconsider their OS choices. Dell has even highlighted a still‑huge installed base of Windows 10 machines — roughly 500 million systems that could upgrade to Windows 11 but haven’t — a figure widely reported across the industry. At the same time, Valve’s work on Proton, improvements in Mesa, and a growing ecosystem of SteamOS‑style images have made gaming on Linux far more approachable than in the past. One community project at the center of recent tests is Bazzite, a SteamOS‑style distribution built on Fedora and tuned for handhelds and gaming PCs. Bazzite bundles a gaming‑centric stack — Proton, tuned Mesa (for AMD), curated kernels, and performance utilities — to deliver a console‑like experience on general purpose hardware. Gamers Nexus’ experiment asked a pointed question: if you run modern AAA titles on a curated Linux image (Bazzite), how do contemporary GPUs behave — and does Linux now offer a viable path for gamers who want to leave Windows?

Test scope and methodology​

What was tested​

  • A mix of recent AAA titles and high‑shader workloads were selected to stress drivers and runtimes: Baldur’s Gate 3, Cyberpunk 2077, Resident Evil 4 (remake), Black Myth: Wukong, Starfield, and others. These games represent a range of engines, rendering paths, and runtime complexities.
  • Hardware: modern discrete GPUs across vendors, including Nvidia flagship and midrange silicon (RTX 5090, 5080, 5070 family references in the coverage) and AMD Radeon RX 9070 / RX 9070 XT class cards. Tests included a variety of systems to capture how vendor drivers behave under Linux.
  • OS: Bazzite (a Fedora‑based gaming image), frozen to a test baseline so driver/runtime versions didn’t change mid‑test. The decision to lock the software stack makes results reproducible for that exact environment but also means subsequent updates could alter outcomes.

How the tests were framed​

Gamers Nexus intentionally focused on Linux‑side comparative behavior across GPUs rather than a strict, instrumented Windows vs Linux head‑to‑head. The team argued that cross‑OS measurement stacks are hard to make perfectly identical — different capture stacks and telemetry hooks can bias results — so the emphasis was on which GPUs offered the most consistent, playable experience under the Linux stack itself. That avoids a single “Linux beats Windows” claim and instead paints a Linux‑specific hardware compatibility and maturity map.

Headline findings — what matters to gamers​

  • Linux gaming is robust and improving. For many single‑player and some non‑competitive titles, games run very well on a modern Linux gaming image; the compatibility and performance gap has narrowed significantly.
  • AMD often delivered the steadier experience. Across the tested titles, Radeon cards (the RX 9070 series in the report) produced more consistent frame‑pacing and fewer micro‑stutter incidents. Where averages were close, AMD’s frame‑time graphs tended to look cleaner.
  • Nvidia sometimes led in raw averages but showed variability. Nvidia cards often recorded higher peak FPS on certain scenes, but a number of runs showed odd frame‑pacing and micro‑stutter behavior that degraded perceived smoothness. The result: higher average FPS doesn’t always mean a better play experience.
  • Ray tracing support remains spotty. Hardware‑accelerated ray tracing works in some titles and configurations, but cross‑vendor, cross‑driver support is inconsistent; several RT‑heavy scenes crashed or failed on certain driver combinations. Gamers Nexus documented mixed RT results and warned that RT support on Linux still trails Windows in reliability.
  • Anti‑cheat is still the show‑stopper for many online games. Titles that rely on kernel‑level anti‑cheat (VAC, certain EAC/BattlEye implementations) will not run on many Linux setups because their anti‑cheat middleware only exists for Windows or injects kernel components unavailable or unacceptable on Linux. This remains the primary blocker for competitive and multiplayer gamers.
  • Long initial shader caches and occasional stutters are part of the experience. Several tested titles required long shader cache warm‑ups — sometimes 30+ minutes — to reach steady‑state smoothness. This is a known quirk of runtime shader compilation across Proton and driver ecosystems, and it can create a rough first session even when performance settles later.

Deep dive: AMD vs Nvidia on Linux — stability vs peak​

AMD — the consistency story​

AMD’s open‑source driver stack (RADV / Mesa for Vulkan, and co‑operation on proprietary bindings when needed) has matured quickly. Tests found AMD cards:
  • Delivered more predictable frame‑time lines and fewer visible hitch spikes in shader‑heavy situations.
  • Required fewer last‑minute tweaks to governor settings for a smooth experience.
  • Were often the best value when judged on the combination of average FPS and smoothness, particularly at 1440p and 1080p where driver maturity matters most.
This is consistent with broader community reporting: independent Linux benchmarking outlets and community tests have repeatedly shown AMD’s Rachel/Mesa stack closing the gap against Windows in many modern titles.

Nvidia — peak frames, sporadic pacing​

Nvidia’s proprietary drivers still deliver strong raw throughput on many workloads, but Gamers Nexus documented:
  • Occasional frame‑pacing anomalies and micro‑stutter in specific titles (even when averages were the highest).
  • Periodic stutters that could be tied to driver heuristics, shader handling, or compositor interactions.
  • Better absolute FPS in some cases, but higher end‑to‑end inconsistency in subjective smoothness.
The bottom line for prospective switchers: if you chase absolute peak FPS numbers and your favorite titles are well‑supported, Nvidia remains a strong choice. If you value stable perceived performance and fewer surprises, AMD looks more forgiving on Linux right now.

Game‑by‑game notes (high level)​

  • Baldur’s Gate 3: Native Linux support exists, but results varied by GPU and driver; AMD showed steadier behavior in heavy scenes.
  • Cyberpunk 2077: One of the more demanding titles; Linux runs via Proton showed playable numbers, but shader compilation and RT paths were fragile in certain driver versions.
  • Black Myth: Wukong: A shader‑heavy title that exposed runtime shader‑compilation pain points; warm‑up behavior mattered more than peak FPS.
  • Resident Evil 4 (remake): Mixed results between native and Proton runs. Anti‑cheat isn’t typically a factor here, but RT toggles and driver‑specific issues produced uneven experiences on some GPUs.
These are illustrative — every title behaves differently depending on engine, renderer (DX11/DX12/Vulkan), and shader complexity. The GN team emphasized variability and cautioned against treating single‑scene numbers as universally representative.

Practical friction points and risks for gamers who switch today​

  • Anti‑cheat and multiplayer blockers. If you play competitive multiplayer titles that run kernel‑level anti‑cheat, you may be blocked entirely or forced to remain on Windows. This is the single biggest limitation for many users.
  • Driver version sensitivity. Small changes in Mesa, Proton, or Nvidia driver builds can swing results. Tests that freeze their stacks are useful snapshots — but not guarantees. Gamers must expect to perform occasional updates or rollbacks.
  • Time and skill investment. Switching OSes, tuning power governors, and managing shader caches takes time. Linux gaming is far smoother than in the days of manual Wine plumbing, but it still rewards technical curiosity and patience.
  • Hardware feature gaps. Some vendor utilities, RGB controls, and OEM features (Armoury Crate, vendor‑specific telemetry) are Windows‑first and may remain unsupported for months. This can affect usability and accessory behavior.
  • Ray tracing and ecosystem parity. RT works in some places, but cross‑driver parity and plug‑and‑play reliability still lag Windows. If RT plus DLSS/FSR workflows drive your setup, test carefully.

Why Linux can now feel faster on some systems​

Gamers Nexus and subsequent community coverage explain the reasons Linux images sometimes deliver higher sustained performance or better 1% lows on constrained devices (like handhelds):
  • Lean compositor and fewer background services reduce scheduling noise and I/O interrupts, which matter dramatically on thermally restricted hardware.
  • Different shader‑cache and compilation strategies in Proton/Mesa can reduce blocking shader builds, lowering micro‑stutter in shader‑heavy scenes.
  • Exposed power governor and fan curve controls on Linux images allow more direct tuning for steady clocks rather than aggressive burst behavior that causes thermal throttling.
Those systemic differences are the practical reasons a Linux image can beat Windows in some handheld scenarios; they’re not magic, just different tradeoffs that can pay off when watts and thermal headroom are tight.

A short guide: if you’re a gamer thinking of switching (practical steps)​

  • Identify your must‑play titles and check ProtonDB / Linux ports for compatibility and known fixes.
  • Test without wiping your Windows install: create a bootable USB, try the live image, or dual‑boot so you can fall back.
  • Use a gaming‑focused distro image (Bazzite, SteamOS, Nobara) rather than a generic desktop distribution to get curated stacks out of the box.
  • Freeze your driver/Proton/Mesa stack for any critical benchmark or play session to maintain predictability.
  • Prepare to tweak: TDP settings, compositor, and shader cache policies often need adjustment for best results.
  • Keep Windows available for anti‑cheat or problematic multiplayer titles — dual‑boot remains the safest path for most players.

Strengths and opportunities​

  • Mature compatibility layer: Proton has reached a point where a very large share of Windows games run on Linux; community reports estimate high compatibility percentages and a fast growing “Platinum” category. This makes Linux a viable platform for single‑player and many offline experiences.
  • Better experience on some hardware: Particularly for midrange and AMD GPUs under tuned stacks, Linux often produces fewer frame‑time outliers and more consistent playability.
  • Active community and vendor engagement: Valve, AMD, and the wider open source graphics community continue to invest heavily in Linux gaming — improvements are ongoing and rapid relative to earlier eras.

Risks and open questions​

  • Anti‑cheat politics and kernel‑level restrictions remain an unresolved ecosystem risk for multiplayer titles; adoption depends on publishers and anti‑cheat vendors choosing to support Linux in a way players trust.
  • Vendor driver divergence — proprietary stacks and open‑source stacks evolve at different paces. Nvidia’s consumer drivers remain proprietary and sometimes unpredictable on Linux; AMD’s open ecosystem offers stability in many titles but isn’t immune to regressions.
  • Measurement variability: Benchmarks are scene‑dependent. Numbers quoted for single scenes do not always translate to a universal experience for all players or hardware revisions. Treat single‑scene averages as directional, not definitive.
  • Device support and OEM features: Controllers, integrated vendor utilities, and specialized input hardware may lack parity on Linux. Expect tradeoffs if you rely on manufacturer software.

Final analysis — is Linux a true gaming alternative?​

Short answer: for many players, yes — particularly for single‑player AAA, older multiplayer titles without deep anti‑cheat, and players who value control over their system. Gamers Nexus’ tests demonstrate that Linux gaming has matured from a hobbyist curiosity to a practical option for a broad swath of modern titles, with AMD hardware currently offering the most straightforward, stable experience on curated Linux images like Bazzite.
Long answer: Linux is not yet a drop‑in, universal replacement for Windows for every gamer. Multiplayer titles that require kernel‑level anti‑cheat, certain OEM ecosystem integrations, and the occasional ray‑tracing or DLSS/feature parity issue still tether many players to Windows. The path forward is pragmatic: dual‑boot for the cautious, or try a single‑boot Linux conversion only after ensuring your core games and accessories are supported.

Closing verdict​

The Gamers Nexus “RIP Windows” framing is provocative — intended to start a conversation — but the substance beneath the headline is more measured and pragmatic: Linux gaming has arrived as a realistic option for many players, not because it unambiguously outperforms Windows across the board, but because the Linux stack now offers fewer tradeoffs and more consistent experiences in a wide set of modern titles. For gamers who prioritize stability, reproducibility, and control, and especially those running AMD GPUs, Linux is now a serious contender. For competitive online players and those dependent on certain proprietary vendor features, Windows still holds an edge.
Caveat: specific FPS numbers, RT behavior, and per‑title compatibility are tightly coupled to driver, kernel, Proton, and game patch versions. These results are reproducible in the short term for the exact stacks used in the tests, but updates to any component can change the picture — treat single numbers as snapshots, not immutable truth.

The choice between Windows and Linux for gaming has never been purely technical alone; it’s social, commercial, and pragmatic. Today the technical argument is far closer than it has been in a decade, and for a growing group of players the decision may soon be about preference rather than necessity.

Source: gHacks Technology News Rest in Peace Windows? Large YouTube channel tests gaming performance on Linux - gHacks Tech News
 

Team Ninja’s Nioh 3 will require Windows 11 on PC and a sizable 125 GB of installation space on an SSD — with an NVMe drive recommended — according to the game’s updated Steam technical sheet, which also lists minimum and recommended CPU/GPU targets and confirms support for modern upscaling and frame‑generation technologies.

Windows 11 PC with glowing cyan fans and neon-lit gaming peripherals.Background / Overview​

Nioh 3 continues Team Ninja’s action‑RPG lineage but arrives into a PC ecosystem that increasingly treats Windows 11, fast NVMe storage, and vendor upscalers as baseline expectations for a smooth launch. The Steam product page and associated developer notes now provide a compact but stark technical sheet: Windows 11 is required for both minimum and recommended tiers, the headline install size is 125 GB, and NVMe SSDs are explicitly recommended at the recommended performance tier and above.
This move follows a growing pattern among recent AAA releases that tied new features and streaming performance to the modern Windows and storage stack — a trend observable in other 2025–2026 launches that also enforced Windows 11 requirements or larger SSD footprints. That industry context helps explain Team Ninja’s choice, but it also raises practical upgrade and compatibility questions for players on older systems.

The official PC requirements: what Team Ninja lists​

Minimum (Playable) — 1080p / ~30 FPS target on the Lightest preset​

  • Operating System: Windows 11 (required)
  • CPU: Intel Core i5‑10400 or AMD Ryzen 5 2600
  • RAM: 16 GB (multi‑channel configuration recommended)
  • GPU: NVIDIA GeForce GTX 1060 (6 GB) or AMD Radeon RX 5600 XT Rev. 2.0 (6 GB)
  • Storage: SSD required; 125 GB headline space noted across tiers
  • DirectX: Version 12
  • Playability: listed as 1080p / 30 FPS on the Lightest preset with upscaling enabled.

Recommended (Comfortable) — 1080p / 60 FPS target on Standard preset​

  • CPU: Intel Core i5‑10600K or AMD Ryzen 5 5600X
  • RAM: 16 GB, multi‑channel
  • GPU: NVIDIA GeForce RTX 3060 Ti (8 GB) or AMD Radeon RX 6700 XT (12 GB)
  • Storage: NVMe SSD recommended
  • Playability: listed as 1080p / 60 FPS on the Standard preset with upscaling enabled; Frame Generation support is explicitly noted.
Team Ninja lists Frame Generation support alongside vendor upscalers, and ties the published framerate targets to having upscaling or frame‑generation enabled. The release date on PC and PS5 is shown as February 6, 2026.

Why Windows 11 — technical rationale and practical implications​

Windows 11 being a hard requirement rather than merely “recommended” is an important, deliberate decision with concrete technical reasoning behind it.
  • Modern API and driver expectations: Windows 11 provides a more consistent and modern runtime environment for features like DirectStorage, up‑to‑date driver models, and tighter vendor integrations — all of which reduce platform fragmentation during QA and tuning. Team Ninja’s spec sheet lists Windows 11 for both minimum and recommended tiers, signaling the studio will not certify Windows 10 for this launch.
  • Security and attestation parity: Windows 11’s broader adoption of firmware attestation and standardized platform features (TPM/UEFI Secure Boot ubiquity on many OEM images) gives studios a predictable baseline when integrating anti‑cheat or low‑level driver hooks.
  • Single baseline simplifies testing: Fewer OS permutations mean fewer day‑one surprises. For a title that streams high‑fidelity assets and uses vendor upscaling/frame‑generation features, that fewer‑baseline approach is attractive from a development and support perspective.
Practical implications for players:
  • Users on Windows 10 or legacy installs may need to upgrade or remain on older entries in the franchise; Team Ninja will not support Windows 10 for Nioh 3 at launch.
  • Some older motherboards or custom Windows installs may need firmware/BIOS updates or TPM/UEFI toggles to meet Microsoft’s compatibility checks.
  • Players who run Linux/Proton or handheld SteamOS setups should temper expectations for day‑one compatibility because the official sheet is Windows‑centric.

Storage: the 125 GB headline and why NVMe is recommended​

The headline number is straightforward yet consequential: 125 GB of installation space is listed as the required storage allocation for Nioh 3 on PC. Team Ninja also recommends NVMe SSDs for the recommended performance tier and above, and explicitly warns that SSD performance can affect gameplay.
Why that matters:
  • Modern action RPGs stream large textures, audio banks, and level data in real time. That streaming workload needs both bandwidth and low latency to avoid stutters and asset pop‑in.
  • Upscaling and frame‑generation reduce GPU load in some ways, but they do not diminish the importance of rapid asset streaming; if textures and geometry pages are delayed, frame‑time variance and hitching will still occur.
  • The published 125 GB figure typically reflects the base install and may not include day‑one patches, optional DLC, or temporary caches created during updates. Team Ninja’s notes, and industry practice, suggest planning significantly more free space during preloads and patch windows.
Practical storage guidance:
  • Reserve at least 160–200 GB of free space temporarily on the target SSD during preloads/updates to avoid installer errors.
  • Prefer an NVMe M.2 drive for the install when aiming for the recommended/standard experience.
  • If your system currently uses a SATA SSD for games, consider moving Nioh 3 to a modern NVMe drive to reduce the risk of stutter related to IO bottlenecks.
Flagged for caution: the 125 GB figure is current as published on the Steam page but can change with day‑one patches and post‑launch DLC; treat it as an initial planning figure, not a fixed ceiling.

Performance expectations: presets, upscaling, and Frame Generation​

Team Ninja couples its published framerate targets with upscaling/frame‑generation modes; that matters because the recommended hardware is tuned to a specific modern workflow.
  • Minimum tier: achieves 1080p / 30 FPS on the Lightest preset with upscaling enabled using the listed GTX 1060 / RX 5600 XT class hardware. This is a playable baseline but will require reduced visual fidelity.
  • Recommended tier: targets 1080p / 60 FPS on the Standard preset with upscaling enabled using an RTX 3060 Ti or RX 6700 XT class GPU. Those numbers assume vendor upscalers and, where available, vendor frame‑generation features to boost effective frame rates.
Understanding the nuance:
  • Published FPS targets are explicitly tied to upscaling. Native 1080p (no upscaling) or higher resolutions will likely need hardware above the recommended column.
  • Frame Generation support (for example, NVIDIA’s frame‑generation pipeline in DLSS Super Resolution variants or equivalent vendor tech) can multiply perceived frame rates but may influence latency and visual artifacts depending on driver maturity and engine integration.
  • Streamers and competitive players may prefer native frames for the stability of encoders and input pipelines; frame generation can change input feel even as it raises frame counts, so test before committing to a live setup.
If your goal is native 1440p or 4K with high refresh, plan to exceed the recommended GPU class and prioritize cards with larger VRAM pools and more raw rasterization / ray tracing capability.

Multi‑channel memory and other lesser‑noticed details​

Team Ninja’s sheet recommends a multi‑channel memory configuration (i.e., dual‑channel or better). That’s not a marketing nicety — it is a meaningful performance factor.
  • Single‑channel memory setups can create a clear bandwidth bottleneck and produce uneven frame times in CPU‑sensitive scenes.
  • The practical advice: use a matched 2×8 GB kit (for 16 GB total) as the minimum for consistent results; consider 32 GB if you plan to stream or perform background tasks while gaming.
Other platform notes included on the technical sheet:
  • DirectX 12 is listed as the graphics API baseline.
  • The Steam page and developer notes emphasize driver maturity and recommend using up‑to‑date GPU drivers around launch, especially because vendor upscaling and frame‑generation features depend on modern driver stacks.

Compatibility: Steam Deck, Proton, handheld Windows PCs, and older Windows 10 rigs​

The official baseline targets Windows 11 and an NVMe SSD. For non‑standard platforms, the picture is mixed:
  • Steam Deck / Proton: Nioh 3’s official support is Windows‑focused. Native Proton/SteamOS support is not guaranteed at launch given the OS requirement, SSD recommendation, and potential anti‑cheat or driver dependencies. Community ports or compatibility workarounds may appear over time, but official day‑one functionality is unlikely.
  • Windows handhelds: Devices like ROG Ally that can run Windows 11 may be able to run the game, but expect trade‑offs in settings and battery life. The NVMe and Windows 11 requirement narrows but does not eliminate handheld viability.
  • Windows 10 users: Systems still on Windows 10 will not be officially supported. Upgrading to Windows 11, verifying firmware support for TPM/UEFI where necessary, and ensuring driver compatibility will be prerequisites for a supported experience.

Risks, trade‑offs, and what could go wrong at launch​

Nioh 3’s published requirements are technically defensible, but there are known risks that could affect day‑one experience.
  • Exclusionary OS baseline: Requiring Windows 11 locks out players who otherwise have capable CPU/GPU combinations but who remain on Windows 10. The friction of upgrading, firmware toggling, or resolving TPM/UEFI issues can be non‑trivial for some users.
  • SSD footprint and future growth: The 125 GB headline requirement can grow with patches and DLC. Players with cramped drives or older SATA SSDs may face stutters or installation failures during updates if temporary space isn’t available.
  • Driver and integration maturity: Frame Generation and upscaling rely on vendor drivers and engine integration. If vendor drivers are not ready or the engine’s implementation has edge‑case bugs, the real‑world gains could underperform the tabled targets, or introduce new artifacts/latency behavior.
  • Handheld and Proton uncertainty: Expect a lack of official support for Proton/SteamOS at launch. Handheld Windows devices may work but will need manual tuning and might not reach the recommended framerate targets without concessions.

Preparation checklist — how to ready your PC for Nioh 3​

  • Confirm your OS: ensure your PC meets Microsoft’s Windows 11 compatibility checks and upgrade if you plan to play Nioh 3 on release. Check your OEM firmware and update BIOS/UEFI as needed.
  • Reserve sufficient disk space: free up 160–200 GB on your target SSD to accommodate preloads and day‑one patches; plan for 125 GB installed size as the baseline.
  • Prefer NVMe: move or prepare an NVMe M.2 drive for the install if you want the recommended experience. Avoid mechanical drives and slower SATA SSDs when possible.
  • Dual‑channel RAM: install a matched memory kit (2×8 GB minimum) to avoid single‑channel penalties; consider 32 GB if you stream or multitask heavily.
  • Update GPU drivers: install the latest vendor drivers close to launch but monitor community feedback for any reported regressions tied to frame generation or upscaling features.
  • Plan for native vs upscaled targets: if you want native 1440p/4K or high‑refresh gameplay, budget for hardware above the published recommended tier. The listed recommended GPUs are aimed at 1080p/60 with upscaling.

Industry context and what this means for PC gaming​

Team Ninja’s Nioh 3 joins a growing list of high‑profile PC releases that treat Windows 11 and fast NVMe storage as minimal assumptions. This trend accelerates a transition in PC requirements and raises several industry‑level observations:
  • Developer efficiency vs user cost: Consolidating on Windows 11 simplifies testing and reduces cross‑OS QA work, but it increases the upgrade burden for users who prefer to stay on older Windows releases. That burden is both technical (TPM/UEFI toggles) and financial (some older systems cannot be upgraded).
  • Storage becomes a first‑class constraint: Large install sizes plus streaming assets make storage performance a gameplay issue, not just a load‑time convenience. NVMe becomes a quality‑of‑life requirement for recommended experiences.
  • Upscaling/frame‑generation as mainstream tools: Publishers are increasingly tuning for modern upscalers and frame generators to deliver playable framerates on mid‑range hardware. That changes how players evaluate GPU purchases (memory size and driver features often matter as much as raw rasterization throughput).

Final appraisal: technically justified, but a tougher landing for some players​

Team Ninja’s PC requirements for Nioh 3 are defensible from a technical standpoint: Windows 11, multi‑channel memory, NVMe storage, and support for frame generation and upscalers form a modern, consistent stack for streaming‑heavy action RPGs. For players with recent hardware and modern platforms, the published minimums and recommended targets are reasonable and clearly scoped to a 1080p upscaling workflow.
However, the combination of a Windows 11 hard requirement and a large SSD footprint will create friction for a subset of the PC audience. Expect a period of player support cases, driver patches, and community tuning in the immediate weeks after launch. The practical advice for anyone planning to play at or near release is simple: check Windows 11 readiness, allocate extra temporary disk space for preloads/patches, prefer NVMe for installation, and be prepared to experiment with upscaling and frame‑generation settings to find your preferred balance of fidelity, latency, and framerate.
Nioh 3’s PC launch will be a good case study in how modern PC baselines are evolving — balancing developer predictability and performance potential against the real upgrade costs faced by many players. The official Steam sheet gives players the numbers they need to plan; those numbers are technically coherent, but not without trade‑offs.

Conclusion
Nioh 3’s published PC requirements make two things clear: Team Ninja expects players to run a modern Windows 11 stack with fast storage, and the studio is optimizing for a 1080p upscaled experience where frame generation can play a role. That approach will deliver a polished experience for players who meet the specs, but it elevates the barrier to entry for older installs and storage‑constrained systems. Plan for Windows 11, an NVMe SSD, and 125 GB of space (plus headroom), and be ready to tune upscaling and frame‑generation options to hit the framerate/latency balance that fits your setup.

Source: royalsblue.com Nioh 3 requires Windows 11 and 125 GB of installation space on PC - That's Gaming - Royals Blue
 

Back
Top