Borderlands 4 has arrived with record player numbers but also a storm of performance complaints, and Gearbox CEO Randy Pitchford’s response to critics—telling one to 'code your own engine'—has turned a technical launch stumble into a full-blown PR crisis. The looter-shooter’s debut on PC and consoles was met with crashes, stuttering frame rates, and a console build lacking basic features like a field-of-view slider, while Pitchford’s combative social media posture amplified the backlash. For a game that otherwise earned praise for its design and gunplay, the launch week has become a case study in how executive tone can eclipse technical achievements.

A Launch Mired in Performance Problems

Within hours of release, Borderlands 4’s Steam reviews dropped to “Mixed,” driven by reports of hard crashes, erratic frame pacing, and an apparent inability to hit 60 fps even on hardware that exceeds the published requirements. Players with GPUs from the past two years flagged stuttering during heavy combat and inexplicable drops when volumetric fog or particle effects filled the screen. Independent benchmarkers confirmed CPU and streaming bottlenecks—unsurprising for an Unreal Engine 5 title—but users expected smoother operation given Gearbox’s recommended specs.

Gearbox’s own system requirements set a high bar: an 8-core CPU, 16–32 GB of RAM, and a mandatory 100 GB SSD install to avoid streaming hitches. VRAM demands start at 8 GB and climb to 12 GB for higher-resolution textures. While these specs reflect modern UE5 realities, Steam’s hardware survey suggests a significant portion of the player base falls short, creating a mismatch between user expectations and actual performance. The day-one patch reduced crash frequency but didn’t eliminate the stutter, leaving many gamers feeling the game shipped in an under-optimized state.

Console players faced their own frustrations. The Xbox Series X and PlayStation 5 versions launched without a field-of-view (FOV) slider or motion blur toggle—options that the PC build includes. In a game known for its chaotic, fast-paced action, a narrow FOV left some players literally feeling boxed in. Pitchford’s public justification that a console FOV slider would impact “fairness” rang hollow, especially since cross-play is enabled and PC users can freely adjust their view. The messaging suggested a rushed console port rather than a deliberate design choice.

The CEO’s Response: ‘Code Your Own Engine’

Randy Pitchford’s activity on X (formerly Twitter) quickly became the story within the story. When one user criticized the game’s reliance on AI upscaling to achieve acceptable frame rates, Pitchford replied: “Code your own engine and show us how it’s done, please. We will be your customer when you pull it off.” Laden with sarcasm, the post dismissed the complaint as naive and implied that only engine developers could validly critique performance. Other posts urged players to adjust settings, lower volumetric fog, and accept the “reality of the relationship between their hardware and what the software they are running is doing.”

But the most incendiary claim—repeated by multiple outlets, including Windows Central—was that less than 0.01% of users were reporting “legitimate” performance issues. The exact X post containing that statistic has not been universally archived, making independent verification difficult. If accurate, it would mean only a few hundred out of potentially millions of players encountered real problems, a figure that strains credibility given the volume of visible complaints. Regardless, the broader dismissive tone alienated a vocal segment of the community, turning a technical discussion into a loyalty test.

Industry observers noted a pattern: Pitchford’s social media style has previously courted controversy, and in this case it undercut any goodwill that constructive advice might have generated. Telling customers to “code your own engine” may score a rhetorical point, but it does nothing to fix crashes or frame drops. The safer, more effective path—acknowledging issues and outlining a concrete plan—was notably absent.

Unreal Engine 5: The Blessing and the Burden

Borderlands 4 is the first mainline entry built on Unreal Engine 5, and that choice brings inherent tradeoffs. Nanite and Lumen enable denser, more dynamic worlds, but they also concentrate CPU and memory loads. Epic CEO Tim Sweeney has publicly argued that many UE5 performance problems stem from studios prioritizing high-end hardware first and optimizing for lower tiers later—if at all. Borderlands 4 appears to follow that template: stunning set pieces and fluid combat on a flagship GPU, but chugging frame rates on mainstream rigs.

To mitigate these demands, Gearbox shipped the game with a suite of modern upscalers: NVIDIA DLSS 4 with multi-frame generation, AMD FSR, and Intel XeSS. Frame generation can artificially boost perceived smoothness, but it introduces latency and may produce artifacts. While these tools are powerful, they shift the burden of optimization onto driver maturity and user tuning. Early adopters essentially become beta testers for vendor hotfixes, a dynamic that fuels launch-day frustration.

Some of Pitchford’s recommended tweaks—dialing back volumetric fog, targeting 1440p instead of 4K, using quality upscaling—are sensible and align with common optimization practice. The problem lies in the delivery. A proactive, well-structured performance guide would have been received as helpful; the same information tossed out in defensive tweets feels dismissive.

Console Parity and the FOV Debate

The absence of an FOV slider on consoles became a flashpoint, and Pitchford’s “fairness” rationale only fanned the flames. If cross-play is enabled, a console player at a fixed low FOV is arguably at a disadvantage against a PC player with a wide FOV, not the other way around. The more likely truths—development time constraints or an oversight—are far less controversial. Bethesda’s Starfield demonstrated that console frame-rate options can be added post-launch successfully, and Gearbox would be wise to follow suit by patching in display settings that empower console users.

Practical Tuning for PC Players

While Gearbox works on patches, players can take immediate steps to improve stability. First, ensure the game is installed on an NVMe SSD, as hard disk latency exacerbates UE5’s streaming hitches. An 8-core CPU is the floor; systems with fewer cores will struggle in densely populated areas. Starting at 1440p with DLSS or FSR Quality mode is more realistic than chasing 4K, especially on mid-range GPUs. Disabling volumetric fog and ray-traced lighting can yield double-digit frame-rate gains in problem scenes. Keeping GPU drivers updated is also critical—NVIDIA, AMD, and Intel often release game-specific hotfixes in the first week after a major launch.

What Gearbox Must Do Next

Patch cadence and communication are the two levers Gearbox still controls. A short-term roadmap that prioritizes crash fixes, stutter reduction, and a console FOV toggle would go a long way toward rebuilding trust. Regular, transparent patch notes—detailing what was fixed, what’s still known, and any remaining tradeoffs—signal that feedback is being taken seriously. Partnering with GPU vendors to accelerate driver optimizations is another immediate win.

Equally important is a shift in public tone. The “code your own engine” line, while perhaps born of frustration, lingers in search results and social media threads, coloring every subsequent discussion of the game. A clear, empathetic statement acknowledging the launch issues and committing to a timeline for fixes would help reset the narrative. The community wants to see less of Pitchford’s sarcasm and more of his engineers’ patch notes.

Conclusion

Borderlands 4 is a technically ambitious looter-shooter whose launch was hamstrung by performance problems and a CEO who chose combativeness over conciliation. The game’s core design merits are real, and the raw ingredients for long-term success are present. But in an era where live-service titles live and die by community goodwill, dismissing legitimate complaints with a “code it yourself” retort is a self-inflicted wound. The path forward is straightforward: ship meaningful fixes, communicate openly, and let the game’s quality speak louder than its executive’s tweets. If Gearbox can do that, Borderlands 4 may yet be remembered for its chaotic fun rather than its chaotic launch.