NC and Big Fire Games opened Cinder City’s Steam page on June 30, 2026, alongside a new developer preview for the open-world sci-fi third-person shooter set in a ruined near-future Seoul, and the listing names Windows 10/11 PCs with 64GB of RAM as the recommended configuration. That number is the story because it turns a familiar wishlist-page beat into a hardware referendum. Cinder City may or may not ship as a memory-hungry monster, but its Steam listing has already exposed how fragile the old “16GB is enough” PC gaming assumption has become.
Most Steam page launches are marketing maintenance. A trailer lands, screenshots get rearranged, genre tags settle into place, and players click wishlist if the premise survives the first thirty seconds. Cinder City’s page does all of that, but the system requirements table has become the loudest part of the announcement.
The game itself is not small in ambition. NC, formerly NCSOFT, is positioning Cinder City as a cinematic third-person shooter with open-world exploration, cooperative PvE, and MMO-flavored progression. Big Fire Games is not merely promising a corridor shooter with a ruined skyline painted behind it; the pitch is a connected battlefield built around recognizable parts of Seoul, story missions, shared encounters, and a world that opens as players push deeper into the campaign.
That makes the 64GB RAM recommendation less absurd than it first appears, but no less remarkable. PC games have been creeping upward for years, especially as Unreal Engine 5 projects, high-resolution assets, ray tracing, background streaming, shader compilation, and live-service infrastructure collide. Still, a 64GB recommended spec is not a gentle nudge. It is a line drawn closer to workstation territory than the mainstream gaming desktop.
The listing also specifies 32GB of RAM as the minimum requirement, which may be even more important. A recommended spec can be aspirational, tied to high settings or a target experience the developer has not fully explained. A minimum spec is supposed to describe the floor, and Cinder City’s floor is already where many enthusiast rigs were standing not long ago.
Players take the role of Seven, a Cinder Knight searching for his daughter, Zoe, starting in Samseong-dong. That personal hook gives the game a clean emotional center, but the broader sales pitch is environmental. Big Fire Games wants the city itself to feel like a dense, navigable, hostile place rather than a collection of mission arenas.
That matters for hardware because cities are cruel to game engines. Wide natural landscapes can hide a lot with fog, terrain, and distance. Dense urban spaces demand buildings, interiors, signage, clutter, traffic infrastructure, vertical sightlines, lighting transitions, combat readability, and streaming systems that do not fall apart when a player sprints, drives, flies, or fast-travels across districts.
Earlier reporting from hands-on previews and interviews described Cinder City as using real-world Korean locations as a foundation, including Seoul and Pangyo. The developers have talked about recognizable road layouts, landmarks, and even the ability to move through detailed urban spaces that map onto actual districts. That is a more expensive promise than “post-apocalyptic city” usually implies.
The memory cost might therefore be less about one spectacular graphical feature and more about accumulation. A large open world does not simply need VRAM for textures; it needs system memory for streamed assets, traversal states, AI, mission logic, networking, physics, animation data, audio, and the messy middleware stack modern games carry around like a backpack full of bricks.
That mismatch makes the RAM figure stand out. If the game were asking for 64GB of memory alongside 16GB of VRAM and a flagship GPU, the message would be simpler: this is a top-end target. Instead, the listing suggests a machine that many PC gamers could plausibly build today, except for the memory kit.
The minimum requirements are also unusually aggressive. An Intel Core i5-10400 or Ryzen 5 3600 paired with an RTX 2060 and 32GB of RAM is a curious shape for an entry point. That profile says the game may tolerate older midrange compute and graphics hardware, but not a low-memory environment.
There are benign explanations. Steam requirements are often provisional before launch, and developers sometimes overstate memory needs while optimization work continues. A broad online PvE game may also need headroom for future content, background systems, debug overhead during testing, or worst-case asset streaming scenarios the studio does not want to understate.
There are less flattering explanations too. A high RAM requirement can signal that the game is still brute-forcing systems that should eventually be leaner. It can also be a defensive move: better to ask for too much and avoid angry reviews from players who tried to run a stuttery open-world shooter on 16GB than promise too little and become the next optimization cautionary tale.
Windows itself is not the only culprit, but the operating system sets the stage. A modern Windows gaming session rarely means the game alone: Steam, Discord, browser tabs, capture software, RGB utilities, anti-cheat services, GPU control panels, cloud sync, launchers, overlays, and security tools all live in the background. The practical difference between “the game needs 16GB” and “the PC needs 16GB” has grown enormous.
The console generation also changed asset expectations. The PlayStation 5 and Xbox Series X forced developers to design around fast SSDs, modern CPU cores, and high-bandwidth memory pools. PC hardware is more flexible, but that flexibility becomes a compatibility problem when developers target big worlds and then must support a chaotic range of RAM speeds, SSDs, background workloads, and driver states.
Then there is Unreal Engine 5, which is not the villain but is part of the weather system. Nanite, Lumen, virtual shadow maps, large worlds, and high-fidelity pipelines give developers more visual ambition, but the results can be punishing when streaming, traversal, or shader compilation are not carefully managed. Some of the most bruising PC launches of recent years were not ugly games. They were beautiful games that moved too much data too clumsily.
Cinder City arrives in that context. A 64GB recommendation is shocking because it is rare, but it does not come from nowhere. It is the visible tip of a broader shift in which memory is becoming a performance feature, not merely a capacity checkbox.
A single-player action game can often cheat aggressively. It knows where the player is likely to go, which enemies must exist, which events can be staged, and when the world can be quietly swapped behind a door, cutscene, elevator, or squeeze-through gap. A shared online world has fewer cheap tricks available, especially if squads can split up, converge, trigger events, and fight through dense areas with persistent state.
Memory pressure grows when a game has to keep more possibilities alive. Multiplayer characters bring gear, cosmetics, abilities, network state, replication rules, matchmaking logic, social systems, and anti-cheat. PvE encounters bring AI coordination, spawn logic, world events, loot, mission progress, and server-client synchronization. None of that automatically requires 64GB on the client, but it can create a design culture where headroom is prized.
The MMO heritage of NC also matters. The company knows persistent online games, and Cinder City appears to be trying to merge that lineage with a more cinematic shooter wrapper. That is commercially sensible: a one-and-done campaign is hard to monetize for years, while an evolving PvE shooter can carry seasons, expansions, cosmetics, and recurring player habits.
The risk is that the PC version becomes the place where ambition sends the invoice. Console platforms give developers fixed memory budgets and force hard decisions. PC lets them publish a table, target a wide range, and let players decide whether the upgrade is worth it.
Does 64GB mean 1080p at high settings and 60 frames per second? Does it mean 1440p with ray tracing? Does it assume upscaling? Does it apply to the open-world multiplayer experience, the campaign, or some future large-scale activity not yet shown? Without target resolution, graphics preset, frame-rate goal, and upscaler assumptions, a requirements table is only half a contract.
The GPU recommendation makes this ambiguity more frustrating. An RTX 4060 is a capable mainstream card, but its 8GB of VRAM can be limiting in modern games at higher settings. If Cinder City truly benefits from 64GB of system memory while recommending an 8GB GPU, players will reasonably wonder whether the game is leaning on system RAM to compensate for streaming pressure that might otherwise hit VRAM.
Storage is another unresolved point. The listing calls for 50GB of available space, which is modest for a contemporary open-world game. It does not specify an SSD requirement in the table surfaced so far, even though any game built around dense city streaming would logically benefit from fast storage. In 2026, “50GB available space” tells players less than “NVMe SSD strongly recommended” would.
The absence of a release date sharpens the uncertainty. NC has said the game is targeting 2026, and the Steam launch suggests the marketing cadence is accelerating. But a requirements table published before launch can be a placeholder, a conservative warning, or a snapshot from a build that still has months of optimization ahead of it.
The most immediate impact is on midrange systems built during the last GPU cycle. A machine with a Ryzen 5 3600, RTX 2060, and 16GB of RAM was a perfectly respectable gaming PC for years. Cinder City’s minimum table effectively says that class of machine may still have enough CPU and GPU muscle but not enough memory capacity.
That is a different upgrade story than the one PC gamers are used to. Graphics cards are expensive, glamorous, and obvious. RAM upgrades are cheaper, quieter, and less emotionally satisfying, but they can determine whether a game stutters, crashes, pages heavily to disk, or survives a long online session with a browser and Discord running.
For Windows 11 users in particular, the memory conversation intersects with everything else Microsoft is pushing onto the desktop. AI features, background indexing, security services, game launchers, cloud sync, widgets, overlays, and productivity apps all compete for headroom. A game that wants 32GB minimum does not arrive on a clean-room benchmark machine; it arrives on the PC people actually use.
Sysadmins and IT pros should also pay attention because gaming hardware often previews workstation expectations in miniature. The same users who ask for a RAM bump to play a Korean sci-fi shooter may also be running virtual machines, local AI tools, development environments, video editing workloads, or browser-heavy research sessions. The consumer and prosumer baselines are converging.
The bad news is that the market is messy. Prebuilt gaming PCs still ship in configurations that look powerful on a spec sheet because the GPU name is large and the memory line is small. Laptops are worse, with soldered RAM, limited slots, and upgrade paths that disappear at purchase. A 64GB recommendation is trivial for a high-end desktop builder and irrelevant for someone with a sealed gaming notebook.
There is also the platform question. Older boards may support 64GB, but not always at ideal speeds or with four-DIMM stability. DDR5 systems can be sensitive to memory configuration. Enthusiasts know to check qualified vendor lists, BIOS updates, EXPO or XMP profiles, and motherboard topology, but mainstream buyers often learn these lessons after a failed boot loop.
Still, the broader shift to 32GB as the sane baseline is hard to deny. If Cinder City’s listing does anything useful, it may accelerate a conversation that was already overdue. In 2026, a new gaming PC with 16GB of RAM is increasingly a budget compromise, not a balanced default.
That is why Cinder City’s 64GB recommendation is a communications problem as much as a technical one. If NC and Big Fire Games believe the requirement is justified, they should explain it. If it is temporary, they should say so. If it refers to a particular target like high-resolution textures, large-scale PvE, or future open-world content, that context would lower the temperature immediately.
Silence lets players fill in the blanks, and players will not fill them kindly. Some will assume poor optimization. Some will assume a bloated Unreal Engine 5 pipeline. Some will assume the game is built for machines that only a fraction of its target audience owns. Those assumptions may be unfair, but they are predictable.
The irony is that transparency could turn the spec into a strength. PC players are not offended by demanding games when the demand buys something visible and the developer speaks plainly. They are offended by vague tables that imply expensive upgrades without explaining the payoff.
But the hardware conversation will follow the game until launch. Every new trailer, beta, and preview will be read against that requirements table. If the footage looks extraordinary, players may accept the ask. If it looks merely competent, the 64GB line will become a meme before it becomes a benchmark.
The most constructive reading is that the Steam page is early and conservative. Developers often publish requirements before the final optimization pass, and memory budgets can change dramatically as assets are compressed, streaming is tuned, debug overhead is removed, and platform testing hardens. A later revision would not be surprising.
The less comfortable reading is that Cinder City is simply saying the quiet part out loud. Big open worlds, dense assets, multiplayer state, modern Windows overhead, and ambitious engines are pushing the practical ceiling upward. The game may be unusual today because it prints 64GB in the recommended column; it may look less unusual in a few years.
Cinder City Turns a Store Page Into a Stress Test
Most Steam page launches are marketing maintenance. A trailer lands, screenshots get rearranged, genre tags settle into place, and players click wishlist if the premise survives the first thirty seconds. Cinder City’s page does all of that, but the system requirements table has become the loudest part of the announcement.The game itself is not small in ambition. NC, formerly NCSOFT, is positioning Cinder City as a cinematic third-person shooter with open-world exploration, cooperative PvE, and MMO-flavored progression. Big Fire Games is not merely promising a corridor shooter with a ruined skyline painted behind it; the pitch is a connected battlefield built around recognizable parts of Seoul, story missions, shared encounters, and a world that opens as players push deeper into the campaign.
That makes the 64GB RAM recommendation less absurd than it first appears, but no less remarkable. PC games have been creeping upward for years, especially as Unreal Engine 5 projects, high-resolution assets, ray tracing, background streaming, shader compilation, and live-service infrastructure collide. Still, a 64GB recommended spec is not a gentle nudge. It is a line drawn closer to workstation territory than the mainstream gaming desktop.
The listing also specifies 32GB of RAM as the minimum requirement, which may be even more important. A recommended spec can be aspirational, tied to high settings or a target experience the developer has not fully explained. A minimum spec is supposed to describe the floor, and Cinder City’s floor is already where many enthusiast rigs were standing not long ago.
Seoul Is the Star, and Seoul Is Expensive
Cinder City’s most persuasive idea is not its mutants, criminal organizations, or super-soldier faction. It is the decision to turn a devastated version of Seoul into the game’s playable identity. The premise is straightforward: an alternate historical event changes the 21st century, the city collapses under monstrous and human threats, and elite Cinder Knights are sent in to claw back what remains.Players take the role of Seven, a Cinder Knight searching for his daughter, Zoe, starting in Samseong-dong. That personal hook gives the game a clean emotional center, but the broader sales pitch is environmental. Big Fire Games wants the city itself to feel like a dense, navigable, hostile place rather than a collection of mission arenas.
That matters for hardware because cities are cruel to game engines. Wide natural landscapes can hide a lot with fog, terrain, and distance. Dense urban spaces demand buildings, interiors, signage, clutter, traffic infrastructure, vertical sightlines, lighting transitions, combat readability, and streaming systems that do not fall apart when a player sprints, drives, flies, or fast-travels across districts.
Earlier reporting from hands-on previews and interviews described Cinder City as using real-world Korean locations as a foundation, including Seoul and Pangyo. The developers have talked about recognizable road layouts, landmarks, and even the ability to move through detailed urban spaces that map onto actual districts. That is a more expensive promise than “post-apocalyptic city” usually implies.
The memory cost might therefore be less about one spectacular graphical feature and more about accumulation. A large open world does not simply need VRAM for textures; it needs system memory for streamed assets, traversal states, AI, mission logic, networking, physics, animation data, audio, and the messy middleware stack modern games carry around like a backpack full of bricks.
The 64GB Line Is Strange Because the GPU Line Is Not
The oddity of Cinder City’s requirements is not that every component looks extreme. It is that most of the table looks surprisingly normal. The recommended GPU is an Nvidia GeForce RTX 4060 with 8GB of VRAM, not an RTX 4090 or some future fantasy card. The recommended CPUs, Intel’s Core i7-12700 and AMD’s Ryzen 7 7800X3D, are strong gaming processors, but they sit squarely inside the current enthusiast conversation.That mismatch makes the RAM figure stand out. If the game were asking for 64GB of memory alongside 16GB of VRAM and a flagship GPU, the message would be simpler: this is a top-end target. Instead, the listing suggests a machine that many PC gamers could plausibly build today, except for the memory kit.
The minimum requirements are also unusually aggressive. An Intel Core i5-10400 or Ryzen 5 3600 paired with an RTX 2060 and 32GB of RAM is a curious shape for an entry point. That profile says the game may tolerate older midrange compute and graphics hardware, but not a low-memory environment.
There are benign explanations. Steam requirements are often provisional before launch, and developers sometimes overstate memory needs while optimization work continues. A broad online PvE game may also need headroom for future content, background systems, debug overhead during testing, or worst-case asset streaming scenarios the studio does not want to understate.
There are less flattering explanations too. A high RAM requirement can signal that the game is still brute-forcing systems that should eventually be leaner. It can also be a defensive move: better to ask for too much and avoid angry reviews from players who tried to run a stuttery open-world shooter on 16GB than promise too little and become the next optimization cautionary tale.
PC Gaming’s Memory Baseline Is Moving Faster Than Its Marketing
For years, the PC gaming memory ladder was easy to explain. 8GB was survival, 16GB was the sensible mainstream, and 32GB was the comfortable enthusiast choice. That neat hierarchy has been breaking down in slow motion.Windows itself is not the only culprit, but the operating system sets the stage. A modern Windows gaming session rarely means the game alone: Steam, Discord, browser tabs, capture software, RGB utilities, anti-cheat services, GPU control panels, cloud sync, launchers, overlays, and security tools all live in the background. The practical difference between “the game needs 16GB” and “the PC needs 16GB” has grown enormous.
The console generation also changed asset expectations. The PlayStation 5 and Xbox Series X forced developers to design around fast SSDs, modern CPU cores, and high-bandwidth memory pools. PC hardware is more flexible, but that flexibility becomes a compatibility problem when developers target big worlds and then must support a chaotic range of RAM speeds, SSDs, background workloads, and driver states.
Then there is Unreal Engine 5, which is not the villain but is part of the weather system. Nanite, Lumen, virtual shadow maps, large worlds, and high-fidelity pipelines give developers more visual ambition, but the results can be punishing when streaming, traversal, or shader compilation are not carefully managed. Some of the most bruising PC launches of recent years were not ugly games. They were beautiful games that moved too much data too clumsily.
Cinder City arrives in that context. A 64GB recommendation is shocking because it is rare, but it does not come from nowhere. It is the visible tip of a broader shift in which memory is becoming a performance feature, not merely a capacity checkbox.
The Live-Service Shooter Wants Room to Breathe
Cinder City is not being framed as a traditional single-player shooter. The Steam description and developer messaging emphasize cooperative PvE, large-scale encounters, and MMO-inspired systems layered over the story campaign. That design choice changes how we should read the requirements.A single-player action game can often cheat aggressively. It knows where the player is likely to go, which enemies must exist, which events can be staged, and when the world can be quietly swapped behind a door, cutscene, elevator, or squeeze-through gap. A shared online world has fewer cheap tricks available, especially if squads can split up, converge, trigger events, and fight through dense areas with persistent state.
Memory pressure grows when a game has to keep more possibilities alive. Multiplayer characters bring gear, cosmetics, abilities, network state, replication rules, matchmaking logic, social systems, and anti-cheat. PvE encounters bring AI coordination, spawn logic, world events, loot, mission progress, and server-client synchronization. None of that automatically requires 64GB on the client, but it can create a design culture where headroom is prized.
The MMO heritage of NC also matters. The company knows persistent online games, and Cinder City appears to be trying to merge that lineage with a more cinematic shooter wrapper. That is commercially sensible: a one-and-done campaign is hard to monetize for years, while an evolving PvE shooter can carry seasons, expansions, cosmetics, and recurring player habits.
The risk is that the PC version becomes the place where ambition sends the invoice. Console platforms give developers fixed memory budgets and force hard decisions. PC lets them publish a table, target a wide range, and let players decide whether the upgrade is worth it.
The Steam Page Leaves the Most Important Performance Questions Unanswered
The requirements table tells us what parts NC and Big Fire Games want in the box. It does not tell us what experience those parts are meant to deliver. That omission is common on Steam, but it is becoming less acceptable as PC requirements grow stranger.Does 64GB mean 1080p at high settings and 60 frames per second? Does it mean 1440p with ray tracing? Does it assume upscaling? Does it apply to the open-world multiplayer experience, the campaign, or some future large-scale activity not yet shown? Without target resolution, graphics preset, frame-rate goal, and upscaler assumptions, a requirements table is only half a contract.
The GPU recommendation makes this ambiguity more frustrating. An RTX 4060 is a capable mainstream card, but its 8GB of VRAM can be limiting in modern games at higher settings. If Cinder City truly benefits from 64GB of system memory while recommending an 8GB GPU, players will reasonably wonder whether the game is leaning on system RAM to compensate for streaming pressure that might otherwise hit VRAM.
Storage is another unresolved point. The listing calls for 50GB of available space, which is modest for a contemporary open-world game. It does not specify an SSD requirement in the table surfaced so far, even though any game built around dense city streaming would logically benefit from fast storage. In 2026, “50GB available space” tells players less than “NVMe SSD strongly recommended” would.
The absence of a release date sharpens the uncertainty. NC has said the game is targeting 2026, and the Steam launch suggests the marketing cadence is accelerating. But a requirements table published before launch can be a placeholder, a conservative warning, or a snapshot from a build that still has months of optimization ahead of it.
Windows Users Should Read This as a Trend, Not a One-Off
It is tempting to treat Cinder City as an outlier and move on. That would be a mistake. Even if Big Fire Games trims the recommendation before launch, the listing reflects a direction of travel that Windows gamers and PC builders are already feeling.The most immediate impact is on midrange systems built during the last GPU cycle. A machine with a Ryzen 5 3600, RTX 2060, and 16GB of RAM was a perfectly respectable gaming PC for years. Cinder City’s minimum table effectively says that class of machine may still have enough CPU and GPU muscle but not enough memory capacity.
That is a different upgrade story than the one PC gamers are used to. Graphics cards are expensive, glamorous, and obvious. RAM upgrades are cheaper, quieter, and less emotionally satisfying, but they can determine whether a game stutters, crashes, pages heavily to disk, or survives a long online session with a browser and Discord running.
For Windows 11 users in particular, the memory conversation intersects with everything else Microsoft is pushing onto the desktop. AI features, background indexing, security services, game launchers, cloud sync, widgets, overlays, and productivity apps all compete for headroom. A game that wants 32GB minimum does not arrive on a clean-room benchmark machine; it arrives on the PC people actually use.
Sysadmins and IT pros should also pay attention because gaming hardware often previews workstation expectations in miniature. The same users who ask for a RAM bump to play a Korean sci-fi shooter may also be running virtual machines, local AI tools, development environments, video editing workloads, or browser-heavy research sessions. The consumer and prosumer baselines are converging.
The Upgrade Math Is Better Than the Optics
The good news is that RAM is one of the least painful major PC upgrades, assuming the platform cooperates. DDR4 and DDR5 pricing fluctuates, but moving from 16GB to 32GB or from 32GB to 64GB is generally less catastrophic than replacing a GPU. For many desktop users, it is also physically simple.The bad news is that the market is messy. Prebuilt gaming PCs still ship in configurations that look powerful on a spec sheet because the GPU name is large and the memory line is small. Laptops are worse, with soldered RAM, limited slots, and upgrade paths that disappear at purchase. A 64GB recommendation is trivial for a high-end desktop builder and irrelevant for someone with a sealed gaming notebook.
There is also the platform question. Older boards may support 64GB, but not always at ideal speeds or with four-DIMM stability. DDR5 systems can be sensitive to memory configuration. Enthusiasts know to check qualified vendor lists, BIOS updates, EXPO or XMP profiles, and motherboard topology, but mainstream buyers often learn these lessons after a failed boot loop.
Still, the broader shift to 32GB as the sane baseline is hard to deny. If Cinder City’s listing does anything useful, it may accelerate a conversation that was already overdue. In 2026, a new gaming PC with 16GB of RAM is increasingly a budget compromise, not a balanced default.
The More Interesting Risk Is Trust
The PC gaming audience has become deeply skeptical of system requirements because too many launches have used them poorly. Some games run well below their listed specs. Others meet the table and still stutter, hitch, compile shaders in real time, or collapse in specific areas. The numbers alone no longer carry much authority.That is why Cinder City’s 64GB recommendation is a communications problem as much as a technical one. If NC and Big Fire Games believe the requirement is justified, they should explain it. If it is temporary, they should say so. If it refers to a particular target like high-resolution textures, large-scale PvE, or future open-world content, that context would lower the temperature immediately.
Silence lets players fill in the blanks, and players will not fill them kindly. Some will assume poor optimization. Some will assume a bloated Unreal Engine 5 pipeline. Some will assume the game is built for machines that only a fraction of its target audience owns. Those assumptions may be unfair, but they are predictable.
The irony is that transparency could turn the spec into a strength. PC players are not offended by demanding games when the demand buys something visible and the developer speaks plainly. They are offended by vague tables that imply expensive upgrades without explaining the payoff.
A 64GB Recommendation Is Not a Death Sentence, but It Is a Warning Shot
Cinder City still has obvious reasons to be interesting. A ruined Seoul built around recognizable districts is a stronger setting than another anonymous post-apocalyptic sprawl. A PvE-focused shooter with cinematic ambitions could find an audience if it avoids the usual live-service traps. NC has the online-game experience to understand long-term operation, even if that history also makes players alert to monetization and grind.But the hardware conversation will follow the game until launch. Every new trailer, beta, and preview will be read against that requirements table. If the footage looks extraordinary, players may accept the ask. If it looks merely competent, the 64GB line will become a meme before it becomes a benchmark.
The most constructive reading is that the Steam page is early and conservative. Developers often publish requirements before the final optimization pass, and memory budgets can change dramatically as assets are compressed, streaming is tuned, debug overhead is removed, and platform testing hardens. A later revision would not be surprising.
The less comfortable reading is that Cinder City is simply saying the quiet part out loud. Big open worlds, dense assets, multiplayer state, modern Windows overhead, and ambitious engines are pushing the practical ceiling upward. The game may be unusual today because it prints 64GB in the recommended column; it may look less unusual in a few years.
The Spec Sheet Tells PC Builders Where the Floor Is Moving
Cinder City’s Steam page is not enough to judge the final game, but it is enough to shape buying advice. The old memory tiers need updating, especially for anyone building a Windows gaming PC meant to last several years.- A new gaming desktop with 16GB of RAM should now be treated as an entry-level or budget configuration, not a comfortable mainstream build.
- A 32GB system is becoming the practical default for modern Windows gaming, particularly for open-world games, multiplayer titles, and users who keep background apps running.
- A 64GB configuration is still not required for most games, but it is no longer an absurd enthusiast-only choice for players who also stream, create content, mod games, or run productivity workloads.
- Cinder City’s listed 32GB minimum matters more than the headline 64GB recommendation because it suggests the low-memory era is ending for some ambitious PC releases.
- NC and Big Fire Games need to clarify the performance target behind the recommendation before launch, because resolution, preset, frame rate, upscaling, and storage assumptions matter as much as the raw number.
References
- Primary source: xiaomitoday.com
Published: 2026-07-01T11:20:39.745113
Loading…
xiaomitoday.com - Related coverage: store.steampowered.com
CINDER CITY on Steam
CINDER CITY is an open-world cinematic third-person shooter set in a fallen near-future Seoul. Fight alongside allies, push back against overwhelming threats, and reclaim the city from the forces tearing it apart.store.steampowered.com
- Related coverage: wccftech.com
Cinder City's Steam Page Is Out, and This May Be the First Game to Recommend a Staggering 64GB of RAM
Cinder City’s Steam page is live, and the MMO third person shooter game could be among the first to recommend a massive 64GB of RAM.wccftech.com
- Related coverage: videogamelegacy.com
Loading…
www.videogamelegacy.com - Related coverage: invenglobal.com
NC's Shooter 'CINDER CITY' Unveils First Developer Preview and Steam Page - Inven Global
NC's development studio, Bigfire Games, has begun introducing its new shooter, 'CINDER CITY,' by releasing its first developer preview video and launching a Steam page.On the 30th,...www.invenglobal.com - Related coverage: mmorpg.com
NC Shares First Developer Preview for Open-World Sci-Fi TPS Cinder City | MMORPG.com
Cinder City, an upcoming sci-fi third-person shooter from developer Bigfire Games and published by NC gets a first developer preview showing its dystopian Seoul setting and multiplayer, open-world PvE gameplay.www.mmorpg.com