Almar Klein

> Transparency should be always controlled through explicit flags rather than implicit logic. Explicitly declaring material.transparent = True/False is a more robust and reliable approach. I disagree with the first...

> I think this is the challenge here Exactly. I think it's going to be a bit awkward one way or another. I do appreciate that making a material opaque...

I've read up a bit about this a bit, and I feel the `.transparent` property, and how it affects things like blending, is actually confusing. I find the `alpha_mode` attribute...

> In my opinion, this proposal conflates two orthogonal concerns: > > * Whether a material is transparent or not (Babylon's transparencyMode, Three.js's transparent flag) > * How the blending...

> There are legitimate use cases where blending is applied to opaque objects, depending on the user’s intent or effect logic — for example, additive blending for glow effects, modulation...

Thanks to the explanation. I'm still a bit confused though. From what I understand now, semantically opaque only really means that it's rendered in the opaque pass, before the "transparent"...

> This is not necessarily the case. opaque objects do not require strict sorting to ensure accurate rendering results (due to depth writing), and the blending here does not require...

> Not really, because opaque will write depth, and A's fragment will be discarded due to depth testing Yeah, that's my point. But if B is supposed to blend, e.g....

I started writing docs for how Pygfx could work in #1124. It includes a list of use-cases, with the (envisioned) API for Pygfx and for ThreeJS. Feel free to suggest...

Well, that would be a bit weird, because the number of days would depend on the month you started in. Note that there is another level that is 7 weeks...