Should I optimize my game or add scalable settings?

Both, they solve different problems. Optimization makes the game run faster for everyone at the same quality, improving the baseline, but has limits (you can't make full quality run on anything). Scalable settings let players sacrifice quality to run on weaker hardware, extending your reach below those limits. Doing both gives you a better baseline experience (optimization) plus the widest possible device range (scalable settings), which is why they're complementary rather than alternatives.

How do scalable settings help reach low-end hardware?

They let players lower visual quality, resolution, effect detail, draw distance, so the game runs acceptably on weaker hardware that couldn't handle the full-quality version. Where optimization keeps the experience the same for everyone (and has limits), scalable settings give low-end players a lighter version that fits their hardware. This widens the range of devices that can run your game, reaching players on budget phones and older PCs who'd otherwise be excluded, which directly affects your potential audience.

Optimization vs Scalable Settings

Quick answer: Optimization makes the game run faster for everyone by reducing its cost; scalable settings let players lower quality to run on weaker hardware. Optimization raises the floor; scalable settings widen the device range. Do both.

Optimization and scalable settings are two ways to make your game run well across hardware, but they work differently: one improves performance universally, the other lets players trade quality for speed. Here's the comparison.

What Optimization Does

Optimization makes your game run faster by reducing its computational cost, more efficient code, better algorithms, less wasted work, without changing what players see. It raises performance for everyone universally: every player benefits from the same content running faster. Optimization improves the baseline experience across all hardware.

Optimization is about doing the same thing more efficiently. Bugnet's performance data helps you find what's slow so you can optimize it. The benefit is universal (everyone gets faster), but optimization alone has limits, there's only so much you can speed up the full-quality experience, which is where scalable settings come in.

What Scalable Settings Do

Scalable settings let players lower visual quality, resolution, effects, draw distance, to run the game on weaker hardware. Unlike optimization, this changes what players see: a low-end player gets a lighter version. Scalable settings widen the range of devices that can run your game acceptably, by letting players trade quality for performance.

Bugnet shows which devices struggle, so you know what your low settings must accommodate. Scalable settings are about giving players a lighter option, which optimization (which keeps the experience the same) doesn't. They extend your game's reach to hardware that can't run the full-quality version.

Why They're Complementary

They solve overlapping but distinct problems: optimization raises performance for everyone at the same quality, scalable settings let players sacrifice quality to run on weaker hardware. Optimization has limits (you can't make full quality run on anything), and scalable settings let you reach below those limits, so they work together.

Bugnet's device-tagged performance data informs both, what to optimize and what your low settings need. So do both: optimize to make the game run better for everyone, and offer scalable settings to extend reach to low-end hardware, since together they give you both a better baseline and the widest possible device range.

Optimization makes the game faster for everyone at the same quality (raises the floor); scalable settings let players trade quality for performance on weaker hardware (widens the device range). Complementary, do both.