←back to thread

513 points todsacerdoti | 1 comments | | HN request time: 0.001s | source
Show context
FrostKiwi ◴[] No.42192825[source]
Thanks for sharing! Author here, happy to answer any questions.
replies(14): >>42193691 #>>42193836 #>>42193884 #>>42194114 #>>42195074 #>>42195398 #>>42196248 #>>42196427 #>>42196783 #>>42197142 #>>42197506 #>>42198224 #>>42198810 #>>42202062 #
ferbivore ◴[] No.42193884[source]
> Mobile chips support exactly MSAAx4 [...] the driver will force 4x anyways

On what GPUs and through what APIs did you see this? This seems fairly weird. I especially wouldn't expect Apple to have problems.

replies(2): >>42197952 #>>42200340 #
1. FrostKiwi ◴[] No.42200340[source]
Yes, that also surprised me and I tested it on multiple mobile Apple devices. It's not really a mistake per se, the implementation is free to do what it wants. Selecting MSAAx2 on these types of mobile GPUs simply has no upside and isn't really supported over MSAAx4 and I guess apple still wanted to make the choice somehow possible, as opposed to Android, where there is only an illusion of choice.

It's just so happens to produce visible artifacts in this case. I suppose for 3D scenes it's mostly fine.