exscape

How I felt 10 minutes ago when I fixed a bug just after zipping it for release.

LCD for extra brightness? I don’t think you’ve been keeping up as mobile OLEDs are usually brighter than mobile LCDs. Not that there are many LCDs left.

The Nokia XR21 is one LCD phone released in 2023:
IPS LCD, 120Hz, 450 nits (typ), 550 nits (HBM)
Another phone with brightness listen on gsmarena is the Oukitel WP30 Pro:
IPS LCD, 120Hz, 430 nits

Take a few popular OLED phones for comparison…
Galaxy S24: Dynamic LTPO AMOLED 2X, 120Hz, HDR10+, 2600 nits (peak)
iPhone 15: Super Retina XDR OLED, HDR10, Dolby Vision, 1000 nits (HBM), 2000 nits (peak)

Or for consoles, Steam Deck LCD is about 400 nits, while the OLED is up to about 600, or 1000 in HDR.

This is less of an issue in multiplayer games, as they rarely have very narrow FOVs by default. The worst offenders are often console ports and slower first-person games.
FWIW while it’s a competitive advantage with high FOV, if there is a slider, it’s still fair since everybody can use a higher FOV if they want to.
It’s not all advantage though, aiming gets harder (aside from the distortions).

I don’t see why it matters at all in single-player. So what if it makes the game easier? Who cares?
The fact that I don’t have to stop due to almost vomiting also makes it easier in a way, but I really don’t mind.

The fact that the optimal FOV differs on a per-player basis is of course exactly why I want a FOV slider everywhere. I usually prefer about 105 degrees horizontal (in 16:9), while some modern games default in the range 75-85.

FOV slider and option to disable head bob if present. Games with a too narrow FOV and/or head bob are unplayable for tons of people who suffer from motion sickness, and it’s such a shame to have so many good games ruined by it.

Doesn’t always look bad, it’s game dependent.

In hardware unboxeds test, it’s better than native in some titles, and better or equivalent in half of titles tested.

It looks way better than native w/ TAA for me in BG3 (at 1440p). TAA is way too blurry. And yet it’s also faster.

How is that relevant? RTX 4080 is not a the minimum requirement for Starfield.

Do most editors do that by default? If so, that’s great – if not, it’s just a downside for tabs, if you need to hit enter, backspace out the automatic indents and then press space 30 times rather than just hit enter and have it aligned automatically.

vim seems to auto-insert tabs when you hit enter mid-function definition, at least with standard settings.

How does that work, and with which editor settings? If you simply set the tab width (tabstop) in vim, things go south.

Say you have a function definition one indent level in, then 22 characters of text. You more want to align the next line to that. How does that work in practice with tabs?

The obvious way with tabs and ts=4 would be 6 tabs and two spaces(one tab for the initial indent, the rest to match 22 characters). But then someone with ts=2 comes along and barely gets half way there, or someone with ts=8 who overshoots by a lot.

The consistent appearance thing is probably more about how mixing tabs (for indentation) and spaces (for alignment, eg in multi-line function definitions of calls) looks like complete crap if you change the tab width.