Closed DarioSamo closed 7 months ago
Thank you very much @JohnVeness, applied all of your suggestions.
I wonder if the diagrams should be SVG or something else editable and machine-parseable? I haven't spotted any glaring errors in them (although I would personally prefer text like "Render pass" or "Unrelated commands" instead of "Render Pass" or "Unrelated Commands") but it still might be better for accessibility or for people who might want to translate them etc.
I wonder if the diagrams should be SVG or something else editable and machine-parseable? I haven't spotted any glaring errors in them (although I would personally prefer text like "Render pass" or "Unrelated commands" instead of "Render Pass" or "Unrelated Commands") but it still might be better for accessibility or for people who might want to translate them etc.
I did most of them in diagrams.net which technically allows you to export SVG, but the animated one is a series of images compiled into a webp, since I don't know how to make an SVG animation like that or if diagrams.net lets you make one (I did it very manually). So I guess there's no way to make the entire article consistently SVG, but at least they're lightweight enough as webp.
SVG animation exists as SMIL which is pretty well-supported across browsers, but not a lot of software can export to SMIL.
I think the current animated WebP approach is fine. Videos are typically preferable to animated images, but if you need lossless compression and full chroma, animated images are more suited.
@DarioSamo For the article cover image, any screenshots of a project you are working with could do. Feel free to send a few and we can make it work.
@DarioSamo For the article cover image, any screenshots of a project you are working with could do. Feel free to send a few and we can make it work.
Sure, here's some screenshots of the scene by W4 that was used for benchmarking.
I've finished my first writing pass on the article. Feel free to point out any weirdness in the writing as I'm not a native English speaker so it's a bit harder to tell if something sounds odd.
It's also very dense so I could've forgotten to introduce a concept that people might not be familiar with, although the expected knowledge of the reader should be someone who's at least aware of how graphics in games work (hence why a short paragraph gives a summary of the feature and later does a deep dive into the implementation for the readers who are interested).
TODO: