When Super Mario 3D Land launched in 2011, it was a showcase for the Nintendo 3DS’s autostereoscopic screen. To maintain a stable 3D effect, the game rendered two viewpoints simultaneously. The result? A hard 30 FPS cap.
Even when you turned the 3D slider off, the engine never flipped a switch. The frame rate remained locked. On original hardware, this made sense—battery life and thermal limits mattered.
But today, playing on Citra (3DS emulator) or modded New 3DS/2DS XL systems, that 30 FPS cap feels like an anchor. And the modding community asked: What if we just… remove it?
This is what most people mean by the "fix." It is a single line of Action Replay or Gateway cheat code that you paste into Citra’s cheat database or your 3DS’s plugin manager. It modifies a specific memory address to allow 60FPS rendering without speed-up. super mario 3d land 60fps code fix
The Super Mario 3D Land 60 FPS fix isn't just about one game. It’s a proof of concept for a whole generation of 3DS titles that were artificially capped for stereoscopic 3D.
All of these render at 30 FPS with 3D on—but 60 FPS is technically feasible today.
The modding scene is already experimenting. Some games work perfectly. Others break physics. But Mario 3D Land shows the template: find the frame cap address, flip two bytes, and unlock what the hardware could always do. When Super Mario 3D Land launched in 2011,
The issue was never that Super Mario 3D Land was unplayable at 30 FPS. Rather, the game’s internal logic—enemy movement, physics calculations, the rotation of the Clockwork stage elements—was hard-coded to 30 frames. Attempting to force a higher frame rate via emulator settings would simply double the speed of the entire game. Mario would zoom across levels at superhuman pace, gravity would malfunction, and timers would tick down twice as fast. It was a classic game-speed bug.
Early emulation attempts left players with a bitter choice: play at a smooth 60 FPS but with broken physics, or play at a sluggish 30 FPS with correct gameplay.
In original game, rotating logs turn 180° over 30 frames. Mario must jump at the flat side. At 60 FPS, logs turn 180° in 15 frames, requiring double the reaction speed. Speedrunners using the 60 FPS code treat it as a separate category (”60Hz TAS-like”). All of these render at 30 FPS with
Mario’s circular shadow (the one directly under his feet) flickers or dissolves into a dotted outline. This happens because the shadow texture’s alpha blending updates every other frame. Solution: Many players ignore it, but you can use a separate cheat to remove the shadow entirely, or switch to “New 3DS” mode if available.
Emulator route (easiest):
Real hardware route (for purists):
Pro tip: On Citra, disable “Enable Hardware Shader” if you see visual glitches. On real hardware, disable power-saving mode in Luma.