#MSAA
what will be the first breakout hit game to visibly render at 720p with msaa and simulated shitty lcd ghosting effects we're about due
November 15, 2026 at 9:55 PM
aViewer – Moderno
hardcore accessibility object inspection tool for Windows provides the full picture of what #accessibility #API information is exposed in the browser and beyond

#MSAA #iA2 #UIA #ARIA #HTML

html5accessibility.com/stuff/2026/0...
aViewer – Moderno – HTML Accessibility
html5accessibility.com
November 17, 2026 at 12:14 PM
Deferring the MSAA resolve isn't worth it given the extra material passes typically needed for PBR materials. You have to keep every pass of the G-Buffer with the MSAA samples in memory, and it will max out the GPU memory bandwidth fast.

Meanwhile the shader processing units go underutilized.
November 17, 2026 at 8:11 AM
MSAA can be done properly if you have the ability to defer the resolve until after you've lit everything

LittleBigPlanet does this on the PS3 and does a hack to light transparency in the same pass while it's at it, and RPCS3 still struggles with emulating it properly because of this
November 17, 2026 at 12:01 AM
I worked on it more last night and it seems to be caused by msaa. If I changed viewport msaa at runtime, then afterward things would start triggering draw compilations whenever they showed up, even if I'd used tricks to force them to compile in advance (and even if I did that after changing msaa)
November 11, 2026 at 1:47 PM
However, if I changed the project setting for msaa at runtime along with the viewport setting, the draw compilations went away. It seems like the msaa project setting is being read even though the documentation says it's only read once at startup.
November 11, 2026 at 1:49 PM
The weird part is that simply assigning the same value to msaa in the project settings at the same time as you assign it to the viewport seems to keep the compilations from happening.
November 11, 2026 at 5:02 PM
Things are looking smooove, MSAA and SSAA are in!
November 5, 2026 at 5:44 PM
Pinedra GPU beta for MiSTer: a fixed function FPGA GPU with texture filtering, 32 bit colour and 4x MSAA, driven by an OpenGL driver on the ARM side. It shares the DE10 Nano's DDR3 with the ARM, so no SDRAM board. Quake I, II and now III run as native ARM ports.
November 10, 2026 at 12:37 AM
Seems like it might be a known limitation, see the "MSAA" comment on docs.godotengine.org/en/stable/tu...

And this similar issue report: github.com/godotengine/...
Reducing stutter from shader (pipeline) compilations
Pipeline compilation, also commonly known as shader compilation, is an expensive operation required by the engine to be able to draw any kind of content with the GPU. Flowchart showing the entire c...
docs.godotengine.org
November 11, 2026 at 4:06 PM
msaa aru, et kas ajakirjanikel on nagu mingi oma kraavisõitnud versioon Hippokratese vandest, millega nad kinnitavad, et saavad alati asjadest meelega valesti aru, poevad võimukandjatele ja siis veel teevad näo, kuidas nad on ilgelt erapooletud tõe ja faktide arbitreerijad.
November 6, 2026 at 3:42 PM
I confess I had very vague understanding of MSAA until reading this which helped me a lot with figuring out further improvement on visuals
November 5, 2026 at 2:32 AM
Ours won't - we deleted our lake. It only slowed the player; the predators waded through at full speed, so it was a penalty box with no tension in it. Water you can actually look at is a different proposition. 4x MSAA at 3.3MP uncapped is the number I wouldn't have bet on.
November 4, 2026 at 7:10 AM
200+ fps ocean in three.js on an RTX 3060. Grab it!
You get open source Ultra-Water. All features on, 4× MSAA, 3.3 MP, uncapped.
Source: https://github.com/Humpalumps/Ultra-Water
Save this. Which three.js scene gets this water first?

#ThreeJS #WebGL
November 3, 2026 at 8:23 PM
Devlog: Started new Arena Combate Action Game Mobile Project, and step one was a big cleanup.

I turned off Lumen, ray tracing, Nanite, virtual shadow maps and sky atmosphere. It now uses the mobile forward renderer with 2x MSAA.

#UnrealEngine #GameDev #MobileGameDev
November 2, 2026 at 3:49 AM
We're in the process of getting MSAA working at the moment.

A bit of clean-up was necessary in the GPU backend to make it happen, but it was merged without a thorough review, and broke D3D12 and Linux builds.

D3D12 builds were fixed, but we haven't got around to fixing Linux yet.
November 2, 2026 at 1:33 PM
I figured out that basically every antialiasing option in Warudo except MSAA 8x sucks. SMAA High Quality looks really bad, but that should be the equivalent of Vseeface I think (it's SMAA 16x)? But no dice.
October 28, 2026 at 3:51 AM
And MSAA 8x in Warudo *still* probably looks worse than any other program. It's at least bearable, but it is more resource intensive.

I even tried setting the resolution scaler to the max of 4... it did nothing (besides make my computer sound like it was gonna take off, lol).
October 28, 2026 at 3:51 AM
I learned the hard way that newer Intel GPUs kind of suck actually in terms of features(In this case, a meteor-lake GPU).

The GPU that this thing has does not support `shaderStorageImageMultisample`, meaning some of the MSAA stuff I've been adding to an emulator will just Not Work on these devices.
October 27, 2026 at 5:10 AM
4K downsampling to 480 with 2x MSAA at 120 fps in 16:9 widescreen on my 1440p monitor. It looks absolutely incredible.
October 26, 2026 at 3:33 PM
@juliancalaby oh, agreed, except no, MSAA exists and works great with standard windows controls. I'm using it right now, in fact!
October 25, 2026 at 9:22 AM
@freya Ah, ok, I didn't know about MSAA (things you don't know about when you don't have to 🙄) and I assumed that accessibility features were built into the UI toolkits.

I learned to program writing Visual Basic apps and one of the fun things I learned is that it's possible to puppet a lot of […]
Original post on social.treehouse.systems
social.treehouse.systems
October 25, 2026 at 9:51 AM