More like chromatic abberation, as both that and bloom was/is often used to hide graphical shortcomings.
Comment on Anon makes a modern game
False@lemmy.world 4 days agoThat was my first thought. Is it 2008 again?
mriswith@lemmy.world 4 days ago
shalafi@lemmy.world 3 days ago
Always loved that term. Sounds like an illusionist’s D&D spell.
Rekorse@sh.itjust.works 4 days ago
I can’t stand motion blur. Does it take extra processing to blur stuff? Either way it looks awful. Horizon forbidden west is completely different with it on or off.
addie@feddit.uk 3 days ago
There’s two kinds of motion blur, really - camera based, and model based. Camera-based requires calculating one motion vector for the whole screen, which is basically free. Model-based requires projecting the motion of each vertex of the model in the projected view; one matrix multiply per vector is not ‘expensive’ on a modern graphics card. Depth of field requires comparing the depth buffer, which you’ll have already created as part of rendering, and then taking several ‘taps’ around each point on the screen to calculate the blur for the ‘focus distance’ compared to the actual distance. The final image post-processing will generally process the whole screen anyway, so you’re just throwing a couple of extra steps in for the two effects.
Now, what does it save you? If your engine is using TAA (temporal anti-aliasing) then that’s performed by ‘twitching’ the camera a tiny amount (less than a pixel) every frame. If nothing’s moving, then you can merge the last several frames to get a really high-quality anti-alias; all the detail that wouldn’t be caught with a ‘completely static’ camera will be captured, and the result looks great. But things do move; if you recalculate ‘where things were’ then you can get a reasonable idea of what colour ought to be at each pixel. Since we need to calculate all the movement vectors to do that, then using the same info gives us the motion blur data ‘for free’ - we can add a little blur in post-processing to hide the TAA mistakes in post processing, and when implemented well(*) then it looks pretty effective. It’s certainly much, much cheaper to calculate that ‘proper’ antialiasing like MSAA.
(*) It is also quite easy to not implement TAA well, and earn the ire of gamers for turning everything into a blurry mess. Doom (2016) does a fantastic job of it - it’s in the engine at a low level - and I’ve never seen anyone complain about that game being blurry or smeared.
It takes time to load high-quality textures and models from disk, and it uses up the RAM budget for each frame. Using lower-quality textures and models for distant objects greatly helps rendering speed and prevents stutter, and a bit of depth-of-field hides the low-quality rendering with a bit of a smear.
Now, if your graphics card greatly exceeds the design requirement (which was probably some kind of console) then you can switch these effects off and the game will look even better, which might make you question why they’re there in the first place. To help consoles look better with some ‘cinematic’ effects, is why.
Arello@sopuli.xyz 3 days ago
Yeah, it’s more like reversed: Left: Zelda BotW Right: Zelda TP
Dudewitbow@lemmy.zip 4 days ago
bloom was major between like 2005-2009ish maybe, coexisted right before the piss filter of the console generation.
currently tech wise, the current joke trend is blurry TAA caused by the switch to deferred rendering in order to get better lighting. TAA was a stop gap AA to replace older AA methods that are less compatible with deferred rendering. It’s why things look like shit(blurry) ontop of performing like shit (lighting/shadows/raytracing)