4 ms·
> 10s of millions of textured polygons every 16ms But at what cost? 100% CPU and GPU usage, tons of system/video memory. Also, rendering text with full capabi
by 323 4y ago
> 10s of millions of textured polygons every 16ms
But at what cost? 100% CPU and GPU usage, tons of system/video memory.
Also, rendering text with full capabilities (arbitrary font/size/color, emoji, ...) is much more complicated than drawing a textured polygon.
And how easy is to use a modern 3D engine versus HTML/CSS?
You are right that modern frameworks are slow, but there is a reason we don't write Notepads in Unreal Engine.
- pjc50 4y agoGames also often render text. > And how easy is to use a modern 3D engine versus HTML/CSS? CSS transforms include a little 3D "engine"! https://polypane.app/css-3d-transform-examples/ https://polypane.app/css-3d-transform-examples/
- ben-schaaf 4y ago> But at what cost? 100% CPU and GPU usage, tons of system/video memory. Games use lots of CPU/GPU resources because they're rerendering all the time. You don't do that in GUI apps. You also don't have huge swaths of 3d assets. > Also, rendering text with full capabilities (arbitrary font/size/color, emoji, ...) is much more complicated than drawing a textured polygon. That's exactly how text is rendered: Glyphs cached into textures that are blitted. Filling the cache is a little more involved, but you're not doing that all the time. > And how easy is to use a modern 3D engine versus HTML/CSS? You don't need to use a game engine; traditional GUI toolkits did this stuff out of necessity due to much slower hardware available at the time.