Mastodawn

Very Human Robot Jul 16, 2023

Good thread that I wish was on Mastodon!

https://twitter.com/SebAaltonen/status/1680504887090503680?s=09

Sebastian Aaltonen on Twitter

“Thus our solution for fast rendering on low/mid tier Android phones (50% of the market today) is to lean on traditional draw calls. Make draw calls as fast as possible on both CPU and GPU side. Well optimized solution can push 10,000 draw calls at 60 fps on 99$ Android phone.”

Twitter

Show thread

Ignacio Castaño🍉Jul 16, 2023

@StompyRobot Yeah, wish we could convince @sebbbi to join us. His posts are one of the few reasons why I still lurk there once in a while.

Show thread

Ignacio Castaño🍉Jul 16, 2023

@StompyRobot @sebbbi To add something useful to that thread: I think position shaders were first introduced by nvidia on Fermi, much earlier than Intel Xe! It was completely transparent and I don't think it was advertised much, so most devs were unaware of it.

Show thread

Per Vognsen Jul 28, 2023

@castano @StompyRobot @sebbbi I'm happy to see a confirmation because I was at the internal Fermi architecture orientation at NVIDIA but left shortly thereafter, and I could have sworn I remembered transparent position shaders being presented. But when I Googled around for it much later there wasn't anyone who seemed to know it existed, so I thought I might have hallucinated it.

Show thread

Per Vognsen

@castano @StompyRobot @sebbbi I believe it had to re-run the whole shader after cull/clip except for the code that only contributed to the position. So there was a potential performance degradation with an extremely heavy vertex shader that computes an intermediate result which then feeds into both position and non-position attributes.